docs(remediation): board under budget by ROLLING OUT (D-43), not rewording; item 1 de-staled

Sequencing section rolled verbatim to BOARD-LEDGER — it was a pointer to a pointer, and MISSION.md
plus TASKS.md 5 remain canonical. Item 1 said RM-02 'needs rebase+CI+review'; rebase and CI are done
and it is in review at 83d2ecb2.

Second application of D-43's rule today: delete-and-reference, never paraphrase-to-save-bytes.

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

docs/remediation/BOARD-LEDGER.md

@@ -51,3 +51,12 @@ board had done three times in one night (gate list, capability registry, DECISIO
 more times by the next rotation seam (RM-61 "building", "nothing implemented yet", DECISION-1/2/3
 "must be ruled"). The rulings a fresh seat needs are items 4–7 above; they are **not** repeated here,
 because that repetition is what went stale.
+
+<!-- board-roll: Sequencing section rolled verbatim from BOARD.md 2026-08-01 (D-43: meet the
+     byte budget by ROLLING OUT, never by rewording what stays). Canonical: MISSION.md + TASKS.md §5 -->
+
+### Sequencing — see [`MISSION.md`](./MISSION.md)
+
+Builds 1-5, the cross-cutting retirements, and DECISION-1's corrected wire-in target are stated once in
+the charter and `TASKS.md` §5. **Not repeated here** — the previous copy of DECISION-1's status on this
+board is one of the six stale restatements below.

docs/remediation/BOARD.md

@@ -27,8 +27,8 @@
 
 ### For the incoming orchestrator — read this before acting
 
-1. **RM-02 is the front.** RM-03 waits on Jason; RM-61 MERGED; RM-02 needs rebase+CI+review on
+1. **RM-02 is the front**, in review at `83d2ecb2` (rebase + CI done). RM-03 waits on Jason; RM-61
-   post-#1033 main. ⚠ Re-derive board claims from the provider before acting (**D-43**).
+   MERGED. ⚠ **Re-derive any board claim from the provider before load-bearing use (D-43).**
 2. **`docs/remediation/TASKS.md` is authoritative**, not the newest voice in a chat. It holds 44 findings
    (D-1…D-6 in `BOARD-LEDGER.md`, D-7…D-43 + 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.
@@ -83,12 +83,6 @@ went missing from mission setup twice, once inside the correction for it (**D-26
 - Remote control: native `/remote-control` NOT wired in this runtime. Path is **Mos-relay**
   (Jason ↔ mos-claude via Discord ↔ mos-remediation via agent-send). Not a blocker.
 
-## Sequencing — see [`MISSION.md`](./MISSION.md)
-
-Builds 1-5, the cross-cutting retirements, and DECISION-1's corrected wire-in target are stated once in
-the charter and `TASKS.md` §5. **Not repeated here** — the previous copy of DECISION-1's status on this
-board is one of the six stale restatements below.
-
 ## Decisions log — full record in [`TASKS.md`](./TASKS.md)
 
 All 44 findings (D-1…D-6 in `BOARD-LEDGER.md`, D-7…D-43 + D-38c in `TASKS.md`) and every ruling with