From e52f458c12c777696301fa72a823e604719128b3 Mon Sep 17 00:00:00 2001 From: archipelago Date: Wed, 29 Jul 2026 12:20:37 -0400 Subject: [PATCH] =?UTF-8?q?docs(01):=20plan-checker=20fixes=20=E2=80=94=20?= =?UTF-8?q?01-06=20depends=5Fon=2001-04;=20lifecycle-gate=20step=20in=2001?= =?UTF-8?q?-10?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- .../phases/01-federation-mesh-hardening/01-06-PLAN.md | 2 +- .../phases/01-federation-mesh-hardening/01-10-PLAN.md | 7 +++++++ 2 files changed, 8 insertions(+), 1 deletion(-) diff --git a/.planning/phases/01-federation-mesh-hardening/01-06-PLAN.md b/.planning/phases/01-federation-mesh-hardening/01-06-PLAN.md index 4ad07fc3..64d26f80 100644 --- a/.planning/phases/01-federation-mesh-hardening/01-06-PLAN.md +++ b/.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 diff --git a/.planning/phases/01-federation-mesh-hardening/01-10-PLAN.md b/.planning/phases/01-federation-mesh-hardening/01-10-PLAN.md index 71f8724a..ad2e6409 100644 --- a/.planning/phases/01-federation-mesh-hardening/01-10-PLAN.md +++ b/.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.