docs(remediation): rolling-branch resume pointer + D-9 interim comms rule

KICKSTART resume now points at origin/remediation/state for the live board, per Mos's
cadence ruling: every tick is pushed to the rolling branch immediately (durable
per-tick, no per-tick main PR); main carries periodic snapshots only. Reading the
board from main would silently yield a stale tick, so the step warns explicitly.

D-9 hardened: comms/v1 must use file/stdin transport, never argv interpolation.
Standing interim rule until then — agent-send -f for any body with special
characters, never -m. Mandatory in every worker brief alongside the D-8 clause.

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

docs/remediation/KICKSTART.md

@@ -7,10 +7,15 @@ mechanically until Build 3 (rotation) makes it automatic.
 
 ## On resume (do in order, before any orchestration action)
 
-1. `cd /src/mosaic-stack` and confirm you are on the remediation working branch.
+1. `cd /src/mosaic-stack`, then **`git fetch origin remediation/state`**.
+   ⚠ **The live board is on the rolling branch `remediation/state`, NOT on `main`.** `main` carries only
+   periodic snapshots, so reading the board from `main` will silently give you a STALE tick. Read the
+   live files at `origin/remediation/state` (e.g. `git show origin/remediation/state:docs/remediation/BOARD.md`),
+   or check that branch out. Every tick is pushed there immediately, so its HEAD is always the newest state.
 2. Read `docs/remediation/MISSION.md` — the charter (goal, 4 builds, 15 decisions, sequencing, directives).
-3. Read `docs/remediation/BOARD.md` — the LIVE state: current phase, in-flight tasks, fleet seat assignments,
+3. Read `docs/remediation/BOARD.md` **at `origin/remediation/state`** — the LIVE state: current phase,
-   gate status. This is your single source of in-flight truth (kept small).
+   in-flight tasks, fleet seat assignments, gate status. Single source of in-flight truth (kept < 8 KB;
+   older entries roll to `BOARD-LEDGER.md` via `board-roll.sh`).
 4. Read the discussion checkpoint for full rationale if needed:
    `../jarvis-brain/docs/scratchpads/postmortem/REMEDIATION-DISCUSSION-STATE.md` (or the jarvis-brain repo path).
 5. **Residency attestation (fail-closed):** restate from the reloaded files — (a) the goal in one line, (b) the

docs/remediation/TASKS.md

@@ -106,9 +106,14 @@ sender is a _correctness_ bug before it is ever a security one — and note the
 send reported success while silently transmitting something other than what was written. Silent
 corruption with a success receipt is precisely the pattern this mission exists to eliminate.
 
-**Requirement on RM-40 / RM-42 (comms/v1):** the envelope must carry its payload **verbatim**, and
+**Requirement on RM-40 / RM-42 (comms/v1), hardened by Mos.** The envelope must carry its payload
-the payload must not be subject to shell interpretation at **any** hop — sender, transport, or
+**verbatim** and must not be subject to shell interpretation at **any** hop — sender, transport, or
-adapter. Round-trip fidelity (send a body containing backticks, `$(…)`, quotes, and newlines; assert
+adapter. Concretely: **file/stdin transport, never argv interpolation.**
+
+**Standing interim rule, effective now (Mos).** Until the envelope lands, use `agent-send.sh -f
+<file>` for any message body containing special characters — **never `-m`**. Passing a file sidesteps
+argv interpolation entirely. **This rule is mandatory in every worker brief this mission issues**,
+alongside the D-8 "if a check is unrunnable, say so" clause. Round-trip fidelity (send a body containing backticks, `$(…)`, quotes, and newlines; assert
 byte-identical receipt) is a required registered test case under RM-02, including a must-fail control
 proving the assertion can detect corruption.