amadan
Astra stage B round 6 brief (rev 5 consolidation)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1 file changed,
+24
−0
docs/superpowers/plans/CODEX-PLAN-REGION-HA-STAGE-B-BRIEF-6.md+24 −0
CI failed — run details
diff --git a/docs/superpowers/plans/CODEX-PLAN-REGION-HA-STAGE-B-BRIEF-6.md b/docs/superpowers/plans/CODEX-PLAN-REGION-HA-STAGE-B-BRIEF-6.md| new file mode 100644 |
| index 000000000..14892937b |
| --- /dev/null |
| +++ b/docs/superpowers/plans/CODEX-PLAN-REGION-HA-STAGE-B-BRIEF-6.md |
| @@ -0,0 +1,24 @@ |
| +# Astra round 6 brief: region HA stage B plan rev 5 (build-ready consolidation) |
| + |
| +**Review:** `docs/superpowers/plans/2026-10-10-region-ha-1b-next-stage-b.md`, rev 5 (d92a721e). You passed rev 4.2 as ready to build in round 5. A pre-flight scan then found 25 build-order and consistency conflicts (K1–K25, in `.superpowers/sdd/2026-10-10-region-ha-1b-next-stage-b/preflight-scan.md`, local). Rev 5 consolidates them: |
| +- Code has moved to the earliest task that uses it, and no task depends on a later one. |
| +- Each task's text was generated from its own commit, in a throwaway copy where every task compiled and passed its tests in order. |
| +- C10 is now committed in Task 9 as region HA code. |
| +- `internal/instancekey` (IK-1) is pinned at e8487c3a. The instance-key plan is now built on branch `instance-key-build`. |
| + |
| +**Withdrawals and my rulings** (the ledger has the details): |
| +- **R5-1, accepted.** Rev 1's hold-only reconcile change is withdrawn. Reconcile leaves the target's row to its install. |
| +- **R5-2, accepted.** The ported 200-seed lifecycle property is replaced by deterministic tests of region HA's parts. Main's participation owner lacks the seams the property would need. |
| +- **R5-4, accepted.** The two-box end-to-end test is withdrawn from the build. It becomes an activation gate, checklist item 12, run on a dev box. |
| +- **R5-3, ruled.** `Reconciler.FenceClosed`/`HoldRow` are unwired, so the source's row is not held while releasing. A pre-activation task, 10b, will wire it, with checklist item 18 as the gate. It is not merge-blocking, because everything stays dormant. |
| +- **M-K25** is a new ask of moves. Its fallback, N11, is committed. |
| + |
| +**Judge:** |
| +1. Did the consolidation change any design you accepted in rounds 1–5, or drop a test that closed one of your findings? |
| +2. Are the R5 rulings acceptable? Above all: |
| + - R5-2's replacement coverage. |
| + - R5-3: is an unheld source row during `releasing` safe while dormant, and is it a real activation blocker? |
| +3. Is the C10 code in Task 9 consistent with the C10 text posted to the claim session? |
| +4. Anything new? |
| + |
| +Give findings P1/P2/P3 with file:line, then a verdict: ready to build, or not. |