docs(remediation): stop item 1 restating the In-flight table — it went stale 3x by duplicating it

Item 1 has now gone stale three separate times in one session, every time for the same reason: it
restated lane state that the In-flight table already owns. That is D-26's class (restatement is lossy
every time) and D-43's mechanism (a second copy is a second thing to go stale). Fixing the wording a
fourth time would just buy another few hours.

So it no longer carries lane state at all — it points at the table and keeps only the two things that
are NOT restatements: read the table, and re-derive any board claim from the provider before
load-bearing use, because the board is sole-written and has no independent verifier.

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

docs/remediation/BOARD.md

@@ -27,9 +27,10 @@
 
 ### For the incoming orchestrator — read this before acting
 
-1. **RM-02 is the front** — NO-GO at `83d2ecb2`, remediating four silent-defeat paths (**D-44**).
-   RM-03 waits on Jason; RM-61 MERGED. ⚠ **Re-derive any board claim from the provider before
-   load-bearing use (D-43).**
+1. **Lane state lives in the In-flight table above — this item does NOT restate it.** It went stale
+   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 45 findings
    (D-1…D-6 in `BOARD-LEDGER.md`, D-7…D-44 + 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.