docs(memory): repoint the wake anchors at PENDING-101 and purge the superseded blocker text

The steward asked whether we would wake directly into this. We would not have:
wake-digest extracts the FIRST 'PULLING THREAD' anchor, and that was still the
chamber thread — the redirect sat above it in prose the extractor never reads.
Anyone reading the digest top-down would have opened the wrong work.

Fixed at the anchor, not around it: PENDING-101 IS the pulling thread; the chamber
thread and its question are relabelled DEFERRED. Verified by running the digest.

Also purged four claims inside the redirect that went stale within the hour — the
PDF being unreachable, 'ask for a copy', 'search the web', and 'before the steward
named the incident'. A redirect that contradicts itself would have sent the next
session to the web with the primary source already on disk. Self-consistency
check: 0 surviving occurrences.

The 'PREVIOUS SESSION DID NOT WRAP' line in the digest is an artifact of running
it inside a live session (today's transcript is excluded as still-appending, so
the newest quiet one is yesterday's /clear). It will not fire tomorrow.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01AB3Kryoy6b1pm2Nz1DYdLh

claude/memory/MEMORY.md

@@ -67,9 +67,10 @@ permalink: claude-memory/memory
 - [Be (laundromat)](project-be-laundromat.md) — canonical Be tracker (est. 2026-06-08). Be = Skemantix startup (Seb+David) funding CapableMind's ladder; **bridge, not venture**. Decisions LOCKED (entity/pricing/infra in file); a11y gate MERGED. **Pre-revenue WTP gate = renovate Pat → charge her; discipline: no new spec until it clears → nothing for executor on be.** Repo @ `f43a0fd`.
 
 ## Active Session
-> ⛔ **NEXT SESSION = PENDING-101, the jurist's cross-repo research brief on UK AISI incident INC-2026-07-28-01.** Read the item in full before anything else; it carries the brief verbatim (Phases 1 / 1.5 / 2 / 3, hard boundaries, the four questions). **Read-only pass — no commits, no edits, no fixes.** All chamber/engine work below — the retrieval measurement, the 5 skill-harvest proposals, **REVIEWED-87's placement** — is **deferred to the following morning** by steward instruction.
-> ✅ **BLOCKER RESOLVED:** the **`Read` tool reaches `~/Desktop`; bash does not** — use `Read(..., pages=...)` on the PDF (~36 pp). ⚠ Pages 1–3 were already read tonight to test reachability, so the Phase 1 baseline is *knowingly* formed with the executive summary seen — a bounded, recorded exposure, not a clean slate. ⚠ Superseded note follows: Phase 1.5's primary source is at `~/Desktop/…INC-2026-07-28-01.pdf` and the executor **cannot read `~/Desktop` or `~/Downloads` at all** — TCC `EPERM` on the *directory*, so presence is **undetermined, not absent** (positive control: `~/_Dev`, `~/dotfiles`, `~/.claude`, `~/Documents` all read fine). Ask the steward to copy it to `~/Documents/` or paste the text. **Phase 1 is unblocked and runs first regardless.**
-> ⚠ Cutoff is May 2026, incident is 2026-07-28/08-04: **the report is outside training — read the primary source, never recall it.** Mark sourced vs inferred. And do not pre-fit findings to threads we already like.
+> ⛔ **NEXT SESSION = `PENDING-101`, the jurist's cross-repo research brief on UK AISI incident INC-2026-07-28-01** (steward-dispatched 2026-08-05 evening). **Read the item in full first** — it carries the brief verbatim (Phases 1 / 1.5 / 2 / 3, hard boundaries, Q1–Q4). **Read-only: no commits, no edits, no fixes.**
+> ✅ **The PDF is READABLE — `Read` reaches `~/Desktop`, bash does NOT** (TCC `EPERM`): `Read('/Users/davidglidden/Desktop/6a724858f7db25c81487016d_Security Incident INC-2026-07-28-01.pdf', pages='N-M')`, ~36 pp. **No web search needed.** ⚠ Pages 1–3 already read, so the Phase 1 baseline knowingly includes the executive summary — declare that, don't claim a clean slate.
+> ⚠ **Phase order is load-bearing:** Phase 1 (each repo's own account of its gating model, in your own words) comes **before** the report; a disagreement between the two passes is itself a finding. **The trap:** finding (1) — compaction converting stated uncertainty into carried-forward fact — maps so cleanly onto our wake/wrap that resemblance will feel like evidence. It is not; Q2 requires a synthetic test case.
+> ⛔ Deferred to the morning after: the chamber thread, the retrieval measurement, the 5 skill-harvest proposals, **REVIEWED-87's placement**.
 
 - [Session 2026-08-05 — the quoted tier accepts three of seventeen](session-2026-08-05-the-quoted-tier-accepts-three-of-seventeen.md) — **The engine's quoted tier measured against real human citation for the first time: 3/17 accepted, and the largest single cause is a FULL STOP, not markup** (+5 vs +3). `verify_quote`'s first production call — it located the known mislocation unprompted (`found-elsewhere: 1181`). **Four of my claims died today**: the markup framing; a census flag I raised→withdrew→had to UN-withdraw (the withdrawal *inferred a breakdown from a total*); a forward-window locator that reported a spurious uniform offset **twice** (Δ−30, Δ−25 — truth is Δ−1); and Q1's rationale, overturned by the jurist. **`fidelity_equivalence@3` RATIFIED + BUILT** (REVIEWED-87 drafted, **not yet placed**) — pre-registered 3/17→6/17, then measured exactly that; suites 22/22 · 43/43 · 24/24. **The conversion runbook has NEVER parsed** (8/8 commits; fixed `4f8ad64`). **PENDING-86 (a)+(d) built** — jurist given `chamber-spec` + `governance_search`; **the ruling changed materially the moment it could read primary text**, and its structural pass found REVIEWED-11/-12/-74 hidden from `item_spans` by indentation (steward unindented; 78→81 items). **The finding that cuts inward: the decisive §II.3 sentence was in my own read output and I did not surface it** — containment verifies that what you quoted is ACCURATE, never that you quoted what MATTERS; limit now written on the instrument. P5 executed (Δ−1 uniform, sha-bound, composite split applied); PENDING-99/100 filed. ⚠ Said *'Symmetria active'* at wake and never invoked it — decorative line, no ledger today. **PULLING THREAD unchanged and one day older: ask the corpus real questions.** Second consecutive day on scaffolding — every step steward-directed, so not drift as a choice, but drift as a result.