EvoZeus v0.4.1
EvoZeus v0.4.1 makes verified in-channel updates automatic for both Stable and the single UAT.
Highlights
- Stable and UAT check their selected product channel automatically at SessionStart and EvoZeus/CoEvolve entry, with a one-hour freshness window by default.
- EvoZeus Core, the active Codex/Claude plugin, Runtime, Session Signal, and pinned CoEvolve update as one verified transaction.
- Updates remain inside the selected channel. UAT fixes overwrite the single UAT candidate; they do not create parallel UAT installations.
- The active pointer changes only after integrity checks, host registration, and Doctor pass. A failed candidate keeps or restores the previous verified product.
- User-visible lifecycle markers appear only when state changes: update found, updating, completed, or safely retained after failure.
~/.evozeus/update-policy.jsoncontrols automatic checks, per-channel enablement, and the check interval.
Upgrade
Stable v0.4.0 and earlier require one explicit alignment because their installed launcher cannot acquire the new Stable updater retroactively:
evozeus align --channel stable --host auto --approve-write --json
After that bootstrap, later Stable updates run automatically inside Stable. An active v0.4.0 UAT with auto-refresh can bootstrap from the overwritten uat/current candidate.
Verification
- Node plugin, host, installer, Doctor, channel, user-visible event, release-note, Harness-boundary, and governance suites pass.
- Python Runtime and Session Signal suites pass.
- Channel regressions cover Stable automatic promotion, single-UAT overwrite, quiet current-version checks, visible lifecycle logs, and safe continuation after a failed candidate.
- Claude SessionStart regressions cover automatic checks; Codex checks when an EvoZeus or CoEvolve-managed entry runs.
- CoEvolve remains pinned to verified release
v0.14.0at commitc3065c2745a7e3771cb790919d41777f3a9cb8ad.