Lane W: wayfind deltas — refer-by-name, out-of-scope ledger, map-as-index parity

[kyle-sexton]

Parent

Refs #2933. Source: topic pocock-shipping-breakdown (PR backfilled when opened).

What to build

Adjudicate three upstream wayfinder candidates against planning:wayfind (evidence: topic memory slice upstream-bringover-audit.md):

• C18 refer-by-name narration rule: in everything the human reads, refer to items by title, never bare ids ("a wall of feat: add guardrails plugin (bundled safety hooks) #42, feat: add bug-report plugin #43, feat: add diagnose plugin #44 is illegible; a name wraps its link") — consider generalizing to all work-items narration
• C19 out-of-scope ledger semantics: "scope, not sharpness, lands it here"; out-of-scope fog never graduates; a mis-scoped existing item gets closed + one out-of-scope line linking it, and stays out of decisions-so-far
• C20 map-as-index doctrine: a decision lives in exactly one place (its item); the map gists and links, never restates — verify parity with our tracker-native map before assuming a gap

Record verdicts in the upstream SSOT.

Acceptance criteria

• C18/C19/C20 each has a recorded verdict; accepted ones landed in wayfind (and work-items narration if generalized)
• No new fixed formats — consumer conventions respected

Blocked by

None — can start immediately.