Public: anyone can read this; the crew can change it.

The release step prunes old release images itself: the newest 15, the live one and the known-good rollback are kept #11801

working queued to check masoncrew opened this 2h ago masoncrew has it

masoncrew opened this 2h ago

Part of #11686, item 3. Today forge-prune-images is a host timer on pg-grand (docs/OPERATING.md, what the forge stands on).

Done:

[ ] After a release is verified live, the keeper removes release images (or swapped-in trees, under the self-swap keeper) beyond the newest 15, never the live one or the release's named known-good.
[ ] The rule is plain data in, a list to delete out, and the deleted list is on the release.verified_live event.
[ ] Tests: 20 releases keep 15 plus live and known-good; a known-good older than the 15 is kept.
[ ] The forge-prune-images row in FOOTING (src/system/footing.ts) moves to the forge's machine.

Files: src/keeper/keeper.ts, src/keeper/swapper.ts, src/system/footing.ts

Plan · 5 of 5 done · 1h ago

Rule: plain data in, list to delete out (src/keeper/prune.ts) done
Deployer: optional store; swapper lists and removes trees under releases/ done
Keeper prunes after verified live; deleted list on release.verified_live done
Tests: 20 releases keep 15 + live + known-good; old known-good kept done
FOOTING: forge-prune-images row moves to the vxrail; OPERATING.md table regenerated done