session 2026-07-13 evening: matcher key-selection fix (chamber 4b34447, MATCH-SUSPECT→0) + PENDING-58 (2b sidecar-wiring amendment, Loeb-first) + session memory/ledger/KG/skill-harvest

claude/memory/session-ledger-2026-07-13.md

@@ -85,3 +85,26 @@ metadata:
 ## State at wake
 - Dotfiles dirty: `M claude/memory/skill-harvest-register.md` uncommitted (likely prior wrap's §1.6 append unpushed) — surfaced at wake, not touched.
 - One new chamber commit since wrap: `378efdc` gitignore comment-format fix (trivial, beside the thread).
+
+---
+
+## Wake 2 — 18:03 (fresh session, /clear + /wake-up ~13 min after afternoon wrap)
+- Pause ~13 min; brief pause not full sleep. Thread validity: CONFIRMED — chamber HEAD `c54edbb` == wrap state, dotfiles clean+pushed (github/main, no ahead), nothing moved unauthored.
+- Pulling thread inherited intact: **the matcher key-selection fix** (`match_key`/`_norm_set` in `sweep_body_conservation.py`) — resolve all 8 MATCH-SUSPECT before B2. Confirmed as the ledger's own FOLLOW-UP note from this afternoon.
+- Symmetria re-init (lineage hand closes the wake's clasp). Returns to carry: flag-don't-move-until-read · verify-against-substrate-not-signal.
+- **Open horizon flagged NOW (§3, not banked):** the matcher fix ships with a self-authored correctness check (augustine/philo MUST re-match to CLEAN 0/0). That's `probe-confirms-hypothesis` shape — the 4 holds>110% (aristotle-problems/galen/diogenes-6.2/lucian) are asserted-from-map-detail, NOT substrate-verified. Treat as candidates; the re-match is the test, not the confirmation. This is the literal question we left ourselves.
+
+## Authorization moves
+- Steward: "go ahead with the matcher fix" → FIX-class (map/sweep matcher, not the graduation gate). Executed direct-to-main (repo's demonstrated pattern; prior 3 commits today same), pushed both remotes.
+
+## Returns (Wake-2 session)
+- **Diagnosed before fixing (held the §3 probe-confirms-hypothesis flag):** ran a READ-ONLY substrate re-match (classify_dsl vs each candidate's true key) to answer the literal question BEFORE editing. The 4 unverified holds>110% (aristotle/galen/diogenes/lucian) were confirmed against the substrate, not asserted from the map — galen/diogenes/lucian→CLEAN, aristotle→small deficit. The self-authored check did NOT get read as confirmation of itself.
+- **LITERAL QUESTION ANSWERED (checkable):** all 8 MATCH-SUSPECT resolve to ONE confident true key; none orphaned/split/absent. The residual the question feared (a candidate with no single sibling) did NOT materialize — the one genuinely-hard case (Suetonius set-identical siblings, both words in "Grammarians and Rhetoricians") is resolvable by an ordered-STRING tier a set metric cannot do. 6→CLEAN, 2→APPARATUS-SHAPED small real deficit. MATCH-SUSPECT bucket → 0.
+- **Bounded-change proof (verified against substrate, not tally):** tally delta alone could hide a CLEAN↔APPARATUS swap; did per-stem diff → exactly 8 rows move (disp+key), 0 collateral, 944 byte-identical. On-disk git diff --numstat = 8/8.
+- Commit `4b34447` both remotes; fleet 119/119 (incl. new near-duplicate key-selection --validate fixtures). CLAUDE.md tally + note + tool-evolution-log current.
+
+## Confidence to recalibrate (Wake-2)
+- The OLD matcher was the archetypal PASS-BUT-FALSELY — always returned a confident (key, conf≥0.5), 8 of them the wrong sibling, never reporting doubt; only the downstream fab-classifier caught the extremes, and only flagged (couldn't repair). A matcher that always yields a best-match above threshold MASKS systematic wrong-sibling selection. Logged in tool-evolution-log.
+- Minor: commit-body prose typo "(2+4+10... 4+12)" — trivial, substance (tallies/proof) correct; left uncorrected rather than rewrite pushed history (disproportionate).
+
+## PULLING THREAD now (matcher fix DONE): the 16 BODY-DEFICIT reprocess is finalized + blocked on the steward's Loeb-first-vs-full-corpus scoping call → the 2b sidecar-wiring amendment. Nothing executor-ready behind it until that call lands.