Session 2026-08-24: grounding gates ruled, daybook rule changed, two censuses run

PENDING-95: Amendment 2 (jurist ruling — (a) rejected, (d) discharged, (b)/(c)
deferred) plus the (b)/(c) census that discharges the deferral's condition.
60 guarded / 32 marked (record said 59/31); date 75%, sections 97%, quoting 47%.
Date broadly present => the jurist's cheaper third form is the live option.

PENDING-156 opened (kind (c): mechanisms off the path the work takes) and its
option (b) census run the same session. PENDING-109 prior confirmed by direct
read. PENDING-89: two docket entries, one same-direction miss and one
cross-direction catch, filed the same day and at the same speed.

Mechanisms: daybook-cue.py rewritten on steward ruling — the daily note must be
appended to until end of day, so the trigger is staleness, not note size, and the
matcher now includes Bash (it had never fired once). daybook-ensure.py and
/wrap-up 7.5 gain a standing Corrections slot per REVIEWED-126.
governance-mcp.py gains two read-only keys so the jurist can read the artifacts
it rules on; the doctrine that read-surface changes should arrive as rulings is
adopted, and the next key is proposed rather than added.

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

claude/skills/wrap-up/SKILL.md

@@ -253,7 +253,9 @@ A reader who was not in the session must be able to follow it. This is the regis
 asked for on 2026-08-23 — *"relatively simple terms"* — and it is the hardest part of this step,
 because the executor's default register is dense, hedged, and written for itself.
 
-**Shape** (steward-specified 2026-08-23):
+**Shape** (steward-specified 2026-08-23; `## Corrections` added 2026-08-24 per REVIEWED-126).
+⚠ **This list is a SECOND copy of the format — `daybook-ensure.py`'s `SKELETON` writes the first.**
+They will drift. Change both, or make one derive from the other:
 - `## The day in short` — one paragraph. What actually happened, and why it mattered.
 - `## <Project>` — **one H2 per project touched**, H3 beneath if it needs it. Project work goes
   under its own heading, *not* into project folders. Put commit hashes here, inline, next to what
@@ -266,6 +268,13 @@ because the executor's default register is dense, hedged, and written for itself
   way the executor's do. Claude.app cannot write to the vault itself (its MCP surface,
   `governance-mcp.py`, is structurally read-only and audited to stay that way), so this step is
   where its side of the exchange gets kept.
+- `## Corrections` — what any party got wrong today, and **who caught it**. Name both: an error the
+  steward caught, one the jurist self-reported, one the executor found by running a check it nearly
+  skipped. **Added 2026-08-24 on the jurist's reasoning (REVIEWED-126):** *"an entry format that has
+  a slot for insights and none for corrections will systematically under-record the second"* — the
+  pressure in any self-authored account runs toward insight over error. **An empty `## Corrections`
+  on a working day is itself a claim, and usually a false one.** Cross-party misses caught here may
+  also be owed to PENDING-89's docket.
 - `## Open / next` — what is unfinished, with dates where they exist.
 
 **Accrete DURING the session; do not save it all for the wrap.** A session that dies unwrapped loses