[HARDENING] PENDING-142: the open/closed criterion verifies an adjacent property

Filed from Task 1 of the 2026-08-17 jurist relay. `governance_state()` computes
openness from one signal — whether a REVIEWED header names the PENDING id — and
never reads the item's `Awaiting:` field, any status field, or the ruling's
`Decision:`. Six items are misclassified in both directions:

- 3 falsely OPEN (78, 81, 82): rulings that name the title, not the id. All
  AUTHORIZED 2026-07-28. REVIEWED-78's own Notes record that it was filed as a
  separate entry precisely to satisfy the closure rule as it then stood; the rule
  later changed, breaking the entries written to comply with it.
- 3 suppressed under a design gate rather than a steward authorization, one of
  which (PENDING-121) is marked HELD OPEN by its own ruling.
- 2 structurally unclosable: no `PENDING-N` in the header, so no ruling can ever
  close them. One is the ICP-19 item gating Observer Problem work.
- 39 suppressed items still carry a live-reading `Awaiting:` line.

Removing the false opens and restoring the false closures leaves 29 — the number
the tool reports. The change proof standing behind the current implementation
measured exactly that count (18 to 19). A count-based control cannot see a
classification wrong in both directions by equal amounts: its subject was the
population size, the claim's subject was each item's disposition.

Addendum 1 flags that the selftest asserts the defect as intended behaviour,
with one of the three hidden items as its fixture.

Nothing patched — the relay scoped this to findings only.

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

claude/memory/session-ledger-2026-08-17.md

@@ -0,0 +1,51 @@
+---
+name: session-ledger-2026-08-17
+description: "Practice-of-return ledger maintained by /symmetria — returns, open horizons, recalibrations, authorization moves, sub-agent dialogues, bypasses."
+metadata: 
+  node_type: memory
+  type: feedback
+  originSessionId: 81f817e9-4016-4867-ae16-a486f1e8fb46
+  modified: 2026-08-17T12:34:44.862Z
+---
+
+# Session Ledger — 2026-08-17
+
+## Returns
+
+- **2026-08-17T~12:15 — the digest's `PREVIOUS SESSION DID NOT WRAP` alarm, overridden a second
+  time.** Same false alarm the 08-14 ledger records overriding at ~09:40. Read the substrate, not
+  the derived label: `session-2026-08-14-…md` exists, is complete, and was extended twice today
+  (CODA, CODA 2). The banner also instructed the wake to "expect no record of what that session
+  did" — the record is the fullest of the week. Third firing, third false alarm; it is the
+  candidate task the steward left open for today.
+
+## What held
+
+- The wake read every claim it reported against the substrate rather than relaying the digest:
+  drift-check re-run live (4/4 clean, 2 amendments seen), `~/dotfiles` git status re-run (clean and
+  pushed), the wrap record and Symmetria ledger opened rather than summarized from the banner.
+
+## Open horizons
+
+- **Steward direction: tooling, not governance, today.** Three candidates, `wrap_inside` fix
+  recommended; S2 ladder batch is BLOCKED by PENDING-141 and must not execute; engine retrieval /
+  PENDING-97 is the day-sized one.
+- **Hypothesis, not yet verified** — beyond wrapped-then-continued, `sec_unwrapped` may select the
+  *wrong transcript* (`now - mtime > 60` skips a just-quiet session) and `wrap_records()` mtimes
+  are *mutable*, so any later edit to a session memory file moves it out of its own session's span.
+  If the fix is taken up, verify both before designing the third value.
+- No Symmetria ledger was opened for the earlier 2026-08-17 session (the CODA / PENDING-140 / -141
+  sitting). Noted, not chased.
+
+## Confidence to recalibrate
+
+- Holding the inherited literal question in front: *was the control's SUBJECT the claim it was
+  cited as verifying, or an adjacent property?* If today's task is the detector fix, its selftest
+  is precisely where that shape recurs — a control over the *detector's* inputs is not a control
+  over the *verdict's* truth.
+
+## Authorization moves
+
+## Sub-agent dialogues
+
+## Bypasses