Discharge the two fired deferrals, and correct a trigger that fired vacuously on arrival

Both 2026-09-08 triggers were discharged by today's sitting and would otherwise
have reported COME DUE at every wake forever, which is alarm decay by construction.
Each `resolved:` names what discharged it, per the schema's own rule that non-empty
is not enough. The four VERDICTS are explicitly NOT discharged by the report.

The classification deferral filed with PENDING-180 fired the instant it was written:
its needle was the bare string "PENDING-168", which already occurs three times in
REVIEWED.md from REVIEWED-136's own text. A vacuous trigger, committed inside the
item reporting vacuous controls. Corrected to the em-dash ruling-header form,
verified absent at filing rather than assumed — which is the check the first one
skipped.

The needle's limitation is disclosed in the block rather than left to be found: the
register writes ruling headers in at least four forms (80 em-dash, 3 parenthetical,
1 joint, 1 slash), text-present takes one needle and cannot be OR-ed, so silence
from this trigger is weak evidence and not proof.

Drift check: 6 deferred decisions tracked, none due, 4 resolved and kept.

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

PENDING-archive.md

@@ -4115,6 +4115,7 @@ Named here so that a later reader looking for the correlation datum does not go
        existed. Disclosed rather than left for the reader to discover.
        ⚠ Same date as mumble-rate-two-week-report, deliberately: one reading, one
        deletion, one occasion.
+     resolved: 2026-09-09 — corpus deleted per REVIEWED-128 cond. 2 as scoped by REVIEWED-136 AMD 1 cond. F, after the content-free statistics were banked under cond. A (commit 3d45e3a). The WRITER was also made inert per cond. G; what replaces it is filed open.
 -->
 
 ### AMENDMENT 3 — 2026-08-25 — ⚖ STEWARD DECISION: option 1. The item closes. **Ruled: REVIEWED-129.**