Decisions 149-150 recorded; instruction files kept true; R-890, R-891, R-644 closed, R-469 narrowed (142 -> 139)

Decision 150 (operator 13:25): sessions correct stale facts in instruction files themselves,
naming each edit; never loosen a rule. Added to unprompted-work.md §5 (all copies) and
PROMPT-TEMPLATE.md §9. CLAUDE.md gates paragraph (R-891), architecture pointer, docs/website
rules, the doubled R-286 sentence in the workspace CLAUDE.md.
Decision 149: vaultwarden's step proven on bench 9401 and box 9202 (evidence here).

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS

documentation/PROMPT-TEMPLATE.md

@@ -272,6 +272,13 @@ Then:  [exact refusal — HTTP status, error, and the proven non-effect, e.g. "m
    shippable change; **overwrite** REPORT.md.
 8. **Coding standards:** follow `<repo>/CLAUDE.md` (cross-cutting) and the feature doc / README for
    domain patterns.
+9. **Instruction files (`CLAUDE.md`, `.claude/rules/*`) are kept true by the session that finds them wrong**
+   (operator ruling 2026-10-06, `09` §3 decision 150). A session MAY, without asking: correct a stale fact (a command, a
+   count, a version, a path, a description of what a gate does), add a fact it proved, and remove a reference to something
+   that no longer exists. Each edit is named in the report (file, line, before, after, why). A session MAY NOT, without the
+   operator's word: loosen a safety rule, a fence, a „never", a protected machine, a secret rule, or a review step; or
+   remove a rule. When in doubt, it is a rule change, and it goes to the operator. If Claude Code's own permission check
+   asks before such an edit, wait for the operator's click; if it refuses, record that and file the exact line.
 
 ---