fix(wake): #944 path becomes a hard-locator arm — detector-shape actionable entries pass the §2.1 gate (#945)

Closes #944.

_has_hard_locator accepted only repo+issue / 40-hex sha / file — the forge vocabulary. The detector emits path (+snapshot_sha when attested) and NEVER emits file/issue/sha, so predicate and sole producer shared ZERO keys and every class=actionable board_file entry dead-lettered. Latent since #920, whose harness pinned the detector's own emission shape as its malformed example — the suite certified the gap it was written to guard.

Fix: `path` becomes a hard-locator arm, and ONLY path. Bare path-less snapshot_sha is a deliberate NON-arm (would widen past the board_file vocabulary); Q11(d) asserts it still quarantines at 7/40/64 chars, spanning the detector's ^[0-9a-f]{7,64}$ attestation range.

VERIFICATION
- Pipeline 2105 terminal-green at fa36da8. Its `test` step reaches all nine wake harnesses via turbo -> packages/mosaic `test` -> `test:framework-shell`, which names each suite explicitly. The two-levels-down indirection matters: no search of .woodpecker/* can see it, and that is exactly why this question was got wrong earlier today and then corrected. CI therefore DOES attest the quarantine suite and the detector suite at this head.
- Independent review (mos-dt, consumer on the affected lane) PASS at fa36da8, from a detached worktree: predicate provably unmoved from fb3c3c3 (comment-stripped sha256 identical, _has_hard_locator body byte-identical), RED control at base reproduced exactly 8 failures all Q11 including "got 6".
- Third reviewer (wake-judge) ACCEPT on both judgment calls: the Q1 assertion reversal is a legitimate correction (the flip was forced, not elective — base fixtures red 19 assertions against the head predicate) and path-alone satisfies §2.1, whose operative test is "one targeted call, never a search" — two of its four named exemplars already resolve to current state. Requiring path+snapshot_sha jointly would permanently dead-letter a declared source class and conflict with #940's advisory-fields ruling.
- Judge's mutation criterion met: with the reconciled exemption disabled, the gate-level assertion ("an ORIENTATION-tier enumeration must NOT be quarantined") dies at this head and did not exist as a casualty before F1.
- D4 (detector lock re-acquisition) fails intermittently at base AND head; git diff base..head over the detector files is EMPTY, so it is out of this PR's surface on structural grounds rather than on a re-roll. Known defect, fix identified (detector.sh:516, fd 9 leaked into sleep), tracked separately.

KNOWN RESIDUALS
- ENUM-B is now the sole address-free reconciled fixture, so the exemption's gate-level guard is a population of one. Safe by population, not by design. Author follow-up: assert ENUM-B carries no hard-locator arm so the harness guards its own premise.
- The binding spec (CONVERGED-DESIGN.md §2.1, separate repo) still enumerates four forge tokens and reads narrower than the shipped gate. Tracked as #948, sequenced after the dragon-lin reseed.
- Hard-locator arms are type-loose: repo/file/path accept any non-null JSON value. Pre-existing; `sha` fails closed only by accident of test(). Tracked separately.

Authored by pepper (sb-it-1-dt); reviewed independently by mos-dt (sb-it-1-dt) and wake-judge. The mos-dt-0 commit/fork identity does not identify the author — attribution collapse tracked in #3092.

Co-authored-by: mos-dt-0 <[email protected]>

packages/mosaic/framework/tools/wake/manifest.txt

@@ -318,8 +318,37 @@
 #              anchors, fatal in $((...))) rejects. Full rationale in the knob
 #              paragraph of the 0.6.12 entry above.
 #              Changed: detector.sh (+ test-wake-detector.sh D13).
+#   0.6.14 #944 the §2.1 hard-locator gate was UNSATISFIABLE for detector-built
+#              actionable board_file entries: _has_hard_locator tested only
+#              repo+issue / 40-hex sha / file, while detector.sh (A1) builds
+#              kind/id/observed_hash + path (+ snapshot_sha/_ts when attested,
+#              #940) — no key in common, so every class=actionable board_file
+#              delta was structurally guaranteed to dead-letter (live: mos-dt
+#              seqs 63/68, 2026-07-30; the only tier with a 30m SLO delivered
+#              nothing on its only actionable source). Fix: `path` becomes a
+#              hard-locator arm — and ONLY path: it mirrors `file`'s one-call
+#              "re-read X" precision, upgrading to one-call
+#              `git show <snapshot_sha>:<path>` when a snapshot is attested.
+#              observed_hash (content hash, not an address) and bare path-less
+#              snapshot_sha (would widen the gate past the board_file
+#              vocabulary — review-adopted criterion) remain NON-arms.
+#              Quarantine is a RENDER-TIME filter (entries never leave
+#              pending), so existing UNCONSUMED dead-letters re-deliver
+#              automatically on the first post-upgrade drain; consumed-past
+#              dead-letters are not requeued.
+#              Changed: digest.sh (+ test-wake-digest-quarantine.sh: Q11
+#              positive control — the live seq-68 entry verbatim must RENDER
+#              as CLAIM@seq — and Q1/Q6-Q9 fixtures moved off the now-valid
+#              path-bearing shape onto genuinely address-free shapes,
+#              amending the #920-era ruling that had pinned the live pilot's
+#              own locator shape as the malformed example). Doc follow-up:
+#              #948 amends CONVERGED-DESIGN.md §2.1 to add `path` to the
+#              hard-locator enumeration and to state the operative test as
+#              "one targeted call, never a search" (NOT "pins the observed
+#              state") — sequenced AFTER the reseed so the edit itself is a
+#              live delivery test of the fixed gate.
 component=wake
-version=0.6.13
+version=0.6.14
 
 # Watch-list schema this component consumes, and the INCLUSIVE range of
 # schema_version values it supports. A wake-watch-list.json whose schema_version