lfg2025/archy
1
0
Fork 0
Code Issues 9 Pull Requests Actions Packages Projects Releases 44 Wiki Activity

docs(master-plan): cascade tier wired into the gate (b7d92107)

Browse Source 
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
archipelago 2026-06-26 05:24:07 -04:00
parent b7d9210784
commit 67426c0d41
1 changed files with 5 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
docs/PRODUCTION-MASTER-PLAN.md
View File

@ -173,10 +173,11 @@ no-regression; the original hang was load/timing-induced and not separately repr
1. **CASCADE tier in the canonical gate:** uninstall → verify the app is GONE from My Apps / 1. **CASCADE tier in the canonical gate:** uninstall → verify the app is GONE from My Apps /
`container-list` / package state (no ghost), data preserved per policy, then reinstall → `container-list` / package state (no ghost), data preserved per policy, then reinstall →
verify it returns healthy. Catch the immich/grafana ghost + reinstall-stops bugs. verify it returns healthy. Catch the immich/grafana ghost + reinstall-stops bugs.
*(Test EXISTS + passes — `bats/cascade-uninstall.bats`, gated on `ARCHY_ALLOW_CASCADE_DESTRUCTIVE`; *(✅ DONE `b7d92107`: `run-gate.sh` now runs ONE cascade pass after the 5× loop when
`run-gate.sh` still never sets it. DECISION PENDING: run a single cascade pass alongside the 5× `ARCHY_GATE_CASCADE=1` (+`ARCHY_ALLOW_DESTRUCTIVE=1`), counted into the tally — opt-in so default
destructive loop vs. a dedicated cascade gate — do NOT fold uninstall/reinstall into all 5 behavior is unchanged, and deliberately NOT folded into all 5 iterations. `cascade-uninstall.bats`
iterations, it balloons runtime.)* 7/7 on .228. Next: extend cascade coverage beyond the single throwaway app to the multi-container
stacks, e.g. an immich/btcpay cascade variant.)*
2. **Progress-UI assertions:** install AND uninstall must report monotonic, truthful progress 2. **Progress-UI assertions:** install AND uninstall must report monotonic, truthful progress
(not a stuck full-red bar); a long op must surface a real stage/percentage and a terminal (not a stuck full-red bar); a long op must surface a real stage/percentage and a terminal
success/failure — no silent hang. (Likely both a backend progress-event fix AND a UI fix.) success/failure — no silent hang. (Likely both a backend progress-event fix AND a UI fix.)