idunn rollback: flip a static release back to the previous one #3
Loading…
Reference in a new issue
No description provided.
Delete branch "eureka-self/static-rollback"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Follow-ups
idunn-deploy-provenance:follow_up:chat-mind-20261113T125202436Z-t35andchat-s6737-6737; cut_specidunn-deploy-provenance:cut_spec:cut-static-release-rollback.r1. Second half of Cut A (forward half is #2,9f15cee1).idunn rollback <target>: one verb, one new brake-gated transaction that flipscurrentback to the previous release, copying the plan and sealed release from the transaction that flipped it (no source, no build). The previous release is the newest Admitted static flip (control + history) checked against the observed link; a rollback of a rollback flips forward again. The carry is re-applied from the site file at rollback time (a missing file fails before the link moves). Typed refusals leavecurrentuntouched: no previous release, current not at the newest flip, previous directory gone or drifted, bindings differ.verify_installedruns at intake and again at Starting.Command::Upgained akind(deviation from the spec's separate variant; Soul checked callers and encodings).CommandKind::Rollbackis stored in v5 records with no schema change, so an Idunn at9f15ceeor earlier cannot decode them (forward-only).Tests: 10 rollback tests; full lib suite 565 passed / 107 failed, the 107 being root-only tests failing identically on base. Soul: accepted
01b6016with findings; fixed in7ba27c3(Starting-time verify test shown to fail with the check removed, cross-binding refusal, docs); other Lows documented (wall-clock ordering, no cancel).Not verified: real root install of a rollback target, a real two-release history on a live store, a rollback whose own flip never completed beyond the post-rename fault test. Deploy nothing.
🤖 Generated with Claude Code