[FIX] Discharge the beacon trigger: it fired once, for real, and was answered

The DEFERRED-DECISION block added yesterday announced fool-beacon-derivation-run-once
BY NAME at today's wake — the first time it carried a real trigger rather than the
positive control that proved it could. The act ran. Record: 5694b925.

Renamed to DISCHARGED-DECISION rather than deleted. governance-drift-check.py's parser
has no `resolved:` field, so a taken decision would be reported COME DUE forever and the
instrument would degrade into crying wolf — the failure mode census 01 named as the one
that actually happens to gates here (decay, not construction). Renaming stops the report
while leaving the record that a trigger existed, fired, and was answered.

Verified after the edit, not assumed: the checker now reports "3 tracked, none due"
(was "1 of 4 have COME DUE"), with the other three unaffected.

Also updated the item's Awaiting line, which read "nothing, the next act is the beacon"
and would otherwise have been silently false from today.

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

PENDING.md

@@ -4207,10 +4207,18 @@ Jurist: *"Confirm that lowercasing is applied at exactly one point in the code a
 | PENDING-89 source (iv) | **AUTHORIZED to read** — 55 files; answers generation diversity only, never correlation of misses |
 | §13.6 block | ⚠ **LIFTED** — its stated condition (§5 ratification) is met |
 
-<!-- DEFERRED-DECISION: fool-beacon-derivation-run-once
+<!-- DISCHARGED-DECISION: fool-beacon-derivation-run-once
      since: 2026-08-22
-     trigger: date 2026-08-25
+     trigger: date 2026-08-25  — FIRED. Announced BY NAME at the 2026-08-25 wake, which is
+              the first time this mechanism carried a real one rather than a rehearsed one.
      owner: executor
+     discharged: 2026-08-25 — the derivation ran ONCE. Record:
+              claude/governance/fool/seed/FOOL-BONES-2026-08-25.md, commit 5694b925.
+     RENAMED, not deleted: governance-drift-check.py's parser has no `resolved:` field, so a
+     taken decision would be reported COME DUE forever and the instrument would degrade into
+     crying wolf. Renaming the key stops the report while leaving the record that the trigger
+     existed, fired, and was answered. If a `resolved:` field is ever added, this reverts to
+     DEFERRED-DECISION with that field set.
 -->
 
 ⚠ **TRIGGER BLOCK ADDED 2026-08-24.** Until today this run-once, irreversible, dated act had **no
@@ -4237,7 +4245,15 @@ Against `claude/governance/fool/seed/FOOL-SEED-RULE.md`, pulse epoch-ms `1787659
 
 ⚠ **Carried forward as structural, not as an aside:** the jurist could not read the filed draft and ruled on steward-supplied text, leaving `9aceed7f…` unverified from its side. **The ruling's subject was the pasted text, not the filed artifact.** They match here — the executor diffed a duplicate paste and both bodies hashed `72af4115…` — but that check was available only because it happened to be run, and is unavailable to the jurist at all. **PENDING-82 / PENDING-86 recurring, now inside a ruling.** No remedy ruled; it belongs to PENDING-82.
 
-**Awaiting:** nothing. The next act is the beacon.
+**Awaiting:** nothing. ~~The next act is the beacon.~~
+
+✅ **EXECUTED 2026-08-25, ran ONCE.** Pulse `2026-08-25T12:00:00.000Z` (chain 2, index 1917365),
+fetched by curl ~38 min after the instant, `outputValue` recorded before anything ran and served
+**UPPERCASE** as the dry run predicted. Seed `6ea9383b…f05d`. Bones: **peak SUCCESSION 96 · dump
+ABSENCE 8** · AIM 75 · SCALE 60 · STAKE 29. Full record with the raw response, the independent
+verifications performed at execution time, and one named-but-uncorrected discrepancy:
+`claude/governance/fool/seed/FOOL-BONES-2026-08-25.md` (commit `5694b925`). No retry, no second
+pulse, no regeneration. The four owed-after-the-beacon items above are now unblocked.
 
 ---