amadan
Instance key provision: Astra round 4 brief (confirming)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1 file changed,
+13
−0
docs/superpowers/plans/CODEX-PLAN-INSTANCE-KEY-BRIEF-4.md+13 −0
CI cancelled — superseded by a newer push — run details
CI log
=== gate === cd launchctx && go vet ./... && go test ./... -count=1 ok amadan.net/carlos/platform.git/launchctx 0.011s ? amadan.net/carlos/platform.git/launchctx/controlname [no test files] ? amadan.net/carlos/platform.git/launchctx/wireid [no test files] go vet ./... gofmt -l .: clean go test ./... -count=1 -timeout 30m amadan: job cancelled — a newer push superseded it
diff --git a/docs/superpowers/plans/CODEX-PLAN-INSTANCE-KEY-BRIEF-4.md b/docs/superpowers/plans/CODEX-PLAN-INSTANCE-KEY-BRIEF-4.md| new file mode 100644 |
| index 000000000..27d03950e |
| --- /dev/null |
| +++ b/docs/superpowers/plans/CODEX-PLAN-INSTANCE-KEY-BRIEF-4.md |
| @@ -0,0 +1,13 @@ |
| +# Astra round 4 brief: instance key provision, rev 3.1 (confirming) |
| + |
| +**Review:** `docs/superpowers/plans/2026-10-10-instance-key-provision.md`, rev 3.1 (0317f5d1). It answers your round 3 (`CODEX-PLAN-INSTANCE-KEY-R3.md`): |
| + |
| +- **P2, replica exclusion (ruling 25, Task 3b).** Every replica launch strips `CARLOS_INSTANCE_KEY` from its composed env. An app that adopted rastrillo's helper and has no key of its own then refuses to start as a replica (`ErrNoInstanceKey`) until the follow-up delivers the home's key. Apps that use their own key are unaffected. |
| +- **P3, dependency order.** O7 now ships before O6. |
| + |
| +**Judge:** |
| +1. Are both findings closed? |
| +2. Is refusing to start safe and honest as the replica behaviour, or does it introduce an availability regression the plan must gate? For example, it could forbid adopting the helper on apps that have replicas until the follow-up. |
| +3. Is anything new introduced? |
| + |
| +Give findings as P1/P2/P3 with file:line, then a verdict: ready to build, or not. |