docs(01): plan-checker fixes — 01-06 depends_on 01-04; lifecycle-gate step in 01-10

.planning/phases/01-federation-mesh-hardening/01-06-PLAN.md

@@ -3,7 +3,7 @@ phase: 01-federation-mesh-hardening
 plan: 06
 type: execute
 wave: 3
-depends_on: ["01-05"]
+depends_on: ["01-04", "01-05"]
 files_modified:
   - core/archipelago/src/federation/types.rs
   - core/archipelago/src/federation/sync.rs

.planning/phases/01-federation-mesh-hardening/01-10-PLAN.md

@@ -110,6 +110,13 @@ and the demo RPC parity harness.
        Expected: the same modals appear in the same situations, the changes are visible in both, and
        the browser console shows no "Method not found" errors on either.
 
+    6. **Single-node gate stays green (CLAUDE.md mandate).** Phase 1 modified daemon internals
+       (`federation/storage.rs`, `server.rs` — a periodic loop was removed), which falls under the
+       "re-run the gate after orchestrator/lifecycle changes" rule. Run `tests/lifecycle/run-gate.sh`
+       ON a dev-pair node (gate runs on-node, never via RPC). Expected: green, 0 not-ok. A full 5×
+       run on .228 is NOT required here (that is Phase 3's multinode criterion) — one clean pass on
+       the dev pair is the insurance this checkpoint needs.
+
     If anything fails, describe what you saw and which numbered step it was — that becomes the gap
     list for a closure pass rather than a re-run of the whole phase.
   </how-to-verify>