docs(adapters): surface ROUTER Q4-vs-Q5 preference tie-break in snippets

[fe0603]

Problem

The thin adapter snippets (codex / claude-code / custom) list 30-context and 40-memory as separate one-liners but omit the ROUTER Preference vs memory tie-break that already exists in 99-system/ROUTER.md:

the full note lives in 30-context/users/; only the per-session essentials become a 40-memory/ pointer

A harness that reads only the installed snippet (not the full ROUTER tree) can therefore route a user-preference body into 40-memory/ — which violates the "40-memory holds pointers only" invariant.

Evidence

While running an adapter-compliance test on a real instance, a Codex session driven only by the ~/.codex/AGENTS.md snippet was asked where to store a user preference. It answered 40-memory/ (the preference body), missing 30-context/. After adding one line to the snippet, a re-test routed it correctly to 30-context/ with a 40-memory/ pointer.

Change

One line added to each of the three adapter snippets, after the ROUTER bullet:

Preferences/interpretations about a specific user/org/project are a body in 30-context/ (ROUTER Q4). 40-memory/ holds only a one-line pointer, never the full note (Q4-vs-Q5 tie-break: memory is pointers only)

• No change to core rules — the tie-break already lives in 99-system/ROUTER.md. This only surfaces it at the point of use (the installed snippet).
• Docs-only, 3 files, +3 lines.

🤖 Generated with Claude Code