amadan
spec: console release defences rev 5, test line for codex 14
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1 file changed,
+5
−2
docs/superpowers/specs/2026-10-06-console-release-defences-design.md+5 −2
CI passed — run details
diff --git a/docs/superpowers/specs/2026-10-06-console-release-defences-design.md b/docs/superpowers/specs/2026-10-06-console-release-defences-design.md| index d2917d481..d277db6aa 100644 |
| --- a/docs/superpowers/specs/2026-10-06-console-release-defences-design.md |
| +++ b/docs/superpowers/specs/2026-10-06-console-release-defences-design.md |
| @@ -629,8 +629,11 @@ they have a managed home they should go in instead. |
| valid proof for the manifest's sha256 with a staged cache hit whose bytes |
| hash differently (refused at the binding check). The policy file changes |
| between passes and the agent sees the change without a restart; an |
| - unparseable policy file keeps the gate closed. The agent re-requests a mint until the proof appears. No |
| - requirement set: no bucket GET is made (assert on the fake store). |
| + unparseable policy file keeps the gate closed. The agent re-requests a mint |
| + until the proof appears. A non-canary listed route with a live version |
| + stays in `fastMembers` while it waits for a proof, and leaves once it |
| + adopts. No requirement set: no bucket GET is made (assert on the fake |
| + store). |
| - **The dev rehearsal in §6 step 6** is the end-to-end test. Mocks cannot show |
| that systemd's start-limit state and `reset-failed` behave as written. |