record: D821 is recorded 2026-09-25, not 10-01 — steward correction, superseded explicitly

The inherited date was wrong and I repeated it twice in one evening, including in
a line telling the steward the register is not the only thing with a deadline.
Five days, not eleven, and it is a recording date — the one deadline on the list
that cannot move.

Superseded rather than overwritten: both records name the old value as
superseded, so no reader meets two live versions.

MEMORY.md now 99.2% (margin ~210 B). PENDING-186 rules Monday or the next wrap
breaches.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

claude/memory/MEMORY.md

@@ -106,7 +106,7 @@ permalink: claude-memory/memory
 > ⚠ **The open-item count is itself contested: 58 (digest predicate) vs 71 (heading-only) —
 > PENDING-142 owns why.** ⚠ 10 k hook-output cap still unresolved (jurist vs my reader); `wake-digest.py`
 > at 8,136 chars has **no write-time guard either way**.
-> ⚠ **Seb's 08-04 reply still unread** — L1 'blocked' UNSETTLED. 🎻 **D821 due 10-01.**
+> ⚠ **Seb's 08-04 reply still unread** — L1 'blocked' UNSETTLED. 🎻 **D821 RECORDED 09-25 — 5 days** (steward, 09-20; supersedes "due 10-01").
 
 
 - [Session 2026-09-20 — the cold run was the protocol](session-2026-09-20-the-cold-run-was-the-protocol.md) — the register caught up with a cold Fable design session; **PENDING-187 AUTHORIZED**. **Three corrections of mine, the central one overturned by the steward in one sentence:** I called the cold run's missing wrap a seam, and `/model-handoff` §5 says the opposite — report-and-stop, next phase **from the artifacts**. **PULLING: the week needs a plan across 58 open items, and PENDING-146 is still the gate.**