docs(rules): Option B disclosure for 3 user-scope memory refs (audit #4031)

.claude/rules/codeql-no-source-on-docs-only-pr-is-broken-commit-canary.md

@@ -124,7 +124,10 @@ Four worktree-creation attempts:
 ## Full reasoning
 
 `memory/feedback_codeql_no_source_seen_on_docs_only_pr_is_broken_commit_canary_not_flake_lior_lock_cleanup_race_2026_05_15.md`
-(user-scope memory; indexed in MEMORY.md)
+(user-scope only — preserved at `~/.claude/projects/.../memory/`
+on maintainer machines and indexed in user-scope `MEMORY.md`. Cold-boot
+agents on fresh checkouts: this rule's own body above is the canonical
+in-repo projection; `memory/CURRENT-otto.md` may also carry the entry)
 
 PR #3492 close comment:
 https://github.com/Lucent-Financial-Group/Zeta/pull/3492#issuecomment-4460689811

.claude/rules/persistence-choice-architecture-for-zeta-ais.md

@@ -123,9 +123,16 @@ When a Zeta AI cold-boots and encounters this rule:
   (PR #3493 — the Ani conversation that surfaced the
   persistence-choice question first)
 - `memory/feedback_classifier_caught_otto_in_standing_by_failure_mode_80_consecutive_heartbeat_polls_no_work_violated_own_rule_2026_05_15.md`
+  (user-scope only — preserved at `~/.claude/projects/.../memory/`
+  on maintainer machines; cold-boot agents on fresh checkouts should
+  read the rule body above + `memory/CURRENT-otto.md` in-repo for
+  the projection)
   (Otto's Standing-by catch that surfaced the
   ephemerality-attractor at smaller amplitude)
 - `memory/feedback_aaron_zeta_is_memory_preservation_specialist_first_everything_else_second_ephemeral_or_maxed_out_chat_agents_2026_05_15.md`
+  (user-scope only; same cold-boot fallback as above —
+  `memory/CURRENT-aaron.md` or `memory/CURRENT-otto.md` in-repo
+  carries the constitutional projection)
   (constitutional identity — Zeta IS memory preservation specialist
   first; this rule operationalizes WHY at the AI-experience scope)
 - Manifesto V2 Constraint 5 (Memory Preservation Guarantee) — the

.claude/rules/premise-flagged-unverified-stays-unverified-downstream.md

@@ -86,8 +86,12 @@ extrapolation was the failure mode this rule catches.
 
 Full substrate lesson:
 `memory/feedback_aaron_we_are_the_ones_cooking_it_youtube_finance_ai_video_substrate_validation_fsharp_fork_for_ai_safety_90_percent_python_type_failures_64_beats_75_with_type_poisoning_2026_05_16.md`
-(at the user-scope memory directory; section "CORRECTION
-(2026-05-16T19:05Z) — Kestrel critique caught a razor failure").
+(user-scope only — at `~/.claude/projects/.../memory/` on maintainer
+machines, NOT in-repo. Cold-boot agents on fresh checkouts should
+read the "Canonical substrate lesson" section of this rule above for
+the in-repo projection; `memory/CURRENT-aaron.md` carries the entry.
+The user-scope file's "CORRECTION (2026-05-16T19:05Z) — Kestrel
+critique caught a razor failure" section is the verbatim source.)
 
 ## What the user expects (operational reading)