docs(remediation): bank D-50 (a GO has a shelf life) and file RM-63 (systemd-managed fleet)

D-50: #1032 carried review 66 APPROVED and a merge-gate GO both bound to 78ec47cd, and by the time
Jason approved the merge it reported mergeable=false. Verified from the provider: its head does not
contain current main f4fd5967. Two rules we already hold, neither wrong alone, combine badly — a
verdict is commit-bound and voids when the head moves, and main drifts while a PR is held, so resolving
the drift moves the head and voids the verdict that was waiting to be used. Holding it across the whole
#1033 saga is what did it.

The asymmetry worth noting: usually a head moves because the AUTHOR pushed, so the void follows from
their action. Here nobody touched the PR — unrelated progress invalidated it — which is why it is easy
to miss and needs a checklist line rather than vigilance. Mos's line: a GO has a shelf life, re-gate on
main-drift.

RM-63 files Jason's architecture as the mechanization of D-41/RM-50/RM-58/P-LIFECYCLE rather than a new
island: durably-named systemd agent services with lanes, where restart triggers a continuation and the
agent resumes its lane, combined with DB-centric task assignment on the PG spine for autonomous pickup.
That is the enforcement surface D-41 proved missing — a managed service can be watched (token budget,
which is D-49's mechanical ceiling monitor), restarted (rotation, retiring our manual respawns) and
continued (rehydrate from the DB). It closes the f10-coder ceiling gap directly: Jason confirmed that
ceiling was not mechanically flagged and must be.

#1032 freshening dispatched to coder-mos1 — it authored the queue guard, so that context is an asset,
and by D-49 it can still take a lane at 67%. Told to stop and flag on any SUBSTANCE conflict, because a
queue-guard semantic resolved quietly re-breaks the very thing RM-03 fixes.

Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>

docs/remediation/BOARD.md

@@ -31,8 +31,8 @@
    three times in one session by duplicating that table (D-26's class). Read the table. ⚠ **And
    re-derive any board claim from the provider before load-bearing use (D-43)** — the board is
    sole-written and has no independent verifier.
-2. **`docs/remediation/TASKS.md` is authoritative**, not the newest voice in a chat. It holds 50 findings
-   (D-1…D-6 in `BOARD-LEDGER.md`, D-7…D-49 + D-38c in TASKS.md), every ruling with its rationale, and the
+2. **`docs/remediation/TASKS.md` is authoritative**, not the newest voice in a chat. It holds 51 findings
+   (D-1…D-6 in `BOARD-LEDGER.md`, D-7…D-50 + D-38c in TASKS.md), every ruling with its rationale, and the
    requirements each finding placed on RM-02/RM-34/RM-50/RM-55.
 3. **`MISSION.md` carries the first-class principles** — read them there, they are not listed here.
    Two added 2026-08-01: **the anchor must live outside the audited party's authority** (D-19/D-25/D-45,
@@ -78,6 +78,6 @@ Roster rolled verbatim to [`BOARD-LEDGER.md`](./BOARD-LEDGER.md); live truth is
 
 ## Decisions log — full record in [`TASKS.md`](./TASKS.md)
 
-All 50 findings (D-1…D-6 in `BOARD-LEDGER.md`, D-7…D-49 + D-38c in `TASKS.md`) and every ruling with
+All 51 findings (D-1…D-6 in `BOARD-LEDGER.md`, D-7…D-50 + D-38c in `TASKS.md`) and every ruling with
 its rationale live there. **Not duplicated here.** The history of _why_ this board must not restate —
 six stale copies across two seams — is rolled verbatim into [`BOARD-LEDGER.md`](./BOARD-LEDGER.md).