[FIX] Not shipped: a vanished draw, an unproven hook, and a contaminated denominator

Asked whether this was shipped. All seven §13 deliverables are met, which is what makes
the question worth checking rather than answering.

⚠ A LIVE DRAW VANISHED WITH NO RECORD. One 'aside' fired and reported nothing, because
the muted / no-soul / no-material / generator-failed / slot-write paths all returned
silently. Almost certainly the mute test suppressed it — correct behaviour — but the log
could not distinguish muted from crashed. Every exit now reports itself, with a control
comparing return-count against log-count so the class cannot reopen. The rate report
REVIEWED-128 binds is computed from this log: an unlogged exit does not merely lose a
datum, it makes the denominator wrong while looking complete.

⚠ AND I CONTAMINATED THAT DENOMINATOR MYSELF. Inter-tick gaps measured 1.8, 4.7, 0.4 and
16.0 minutes against a 20-minute interval, then 20.0, 21.0, 20.0 once the session stopped
touching it — the early ones are my own hand-runs of the status line and re-runs of the
seam, which resets the tick clock. Test firings sitting in the live log, indistinguishable
from real ones by inspection. A MARKER record now bounds the clean data and the deferral
says to count from it and to report that the first 8 were discarded.

⚠ THE SEAMS HAVE NEVER FIRED IN PRODUCTION: 0 events each, and the Stop hook writes
nothing on an ordinary turn, so there is no evidence it is invoked at all. Silent-net
shape — it looks fine until a wrap produces nothing and the net takes the blame.

The one genuinely good result: at 17:53:50 a notable draw passed the net and reached the
status line UNRELAYED. First time anything reached the steward without the executor
holding it.

38/38 on the mumble suite.

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

PENDING.md

@@ -4906,7 +4906,14 @@ Link 1 to link 4 directly. **The trial built to test whether a fool could reach
      since: 2026-08-25
      trigger: date 2026-09-08
      owner: executor
-     discriminator: §8's own clause — "Report the observed mumble rate after two weeks." The
+     discriminator: ⚠ THE DENOMINATOR IS CONTAMINATED BEFORE 2026-08-25T17:53 and the
+       log carries a MARKER record at that boundary. The build session ran the status line
+       by hand and re-ran the seam (which resets the tick clock), so early ticks are test
+       artifacts indistinguishable from live ones by inspection. Found 2026-08-25 by
+       measuring the inter-tick gaps: 1.8, 4.7, 0.4 and 16.0 minutes against a 20-minute
+       interval, then 20.0, 21.0, 20.0 once the session stopped touching it. COUNT FROM
+       THE MARKER, and say in the report that the first 8 ticks were discarded and why.
+       §8's own clause — "Report the observed mumble rate after two weeks." The
        two-week clock starts the day the body is wired, which has not happened, so no date can
        honestly be written yet. `manual` was the correct recording rather than a proxy date, and
        this CONVERTED to `date 2026-09-08` on 2026-08-25, the day the body shipped