EvoZeus v0.4.1

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.json controls 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.0 at commit c3065c2745a7e3771cb790919d41777f3a9cb8ad.

EvoZeus v0.4.0

EvoZeus v0.4.0

EvoZeus v0.4.0 introduces the plugin-first product architecture.

Highlights

• One-command evozeus align --channel stable|uat --host auto keeps the selected product channel and the single Codex/Claude plugin aligned.
• One EvoZeus plugin with five default user-task Skills.
• Built-in Runtime and Session Signal modules ship in the EvoZeus product Release.
• CoEvolve v0.14.0 remains the optional independent evolution extension, with one root Harness per independent Repo and verified ADMIN authority for mutations.
• Product channel manifest v2 installs only EvoZeus and CoEvolve as independent components.
• Stable and the single UAT retain isolated state, transactional updates, overwrite semantics, and rollback.
• Existing v0.3.x installations migrate their legacy channel state and local launcher bootstrap during alignment.
• A CI gate rejects nested or legacy Harness directories; only an independent Git Repo root can own a Harness.
• Harness writes and uploads require verified target Repo ADMIN permission; diagnosis and dry-run plans stay read-only.
• Claude Code receives a silent, read-only SessionStart Lesson check; Codex uses explicit or semantic Skill selection until an equivalent plugin hook exists.
• README and user output focus on review, Lesson confirmation, verified improvement, and privacy.

Migration

Historical root Skill calls route to the plugin's using-evozeus Skill for one compatibility cycle. Old Infra and Session Signal installations are replaced by the copies embedded in the selected EvoZeus Stable/UAT root.

Stable files are never overwritten by merely running an old Skill. Installation or channel alignment still requires an explicit user-approved update.

EvoZeus v0.3.5

EvoZeus v0.3.5

EvoZeus v0.3.5 promotes the verified Notice-system UAT candidate to the immutable Stable product channel.

Included

• EvoZeus-CoEvolve v0.13.0, providing configurable Emoji + EvoZeus · <event> notices and a read-only target Skill Notice CLI.
• Automatic reconciliation of missing, legacy, or version-mismatched CoEvolve dispatchers when a channel is activated or the single UAT candidate is overwritten.
• Explicit health states for missing, legacy, and version-mismatched dispatchers.
• Restorable dispatcher-state backup before replacement, with the prior verified UAT retained as the rollback candidate.
• A clean dependency audit with the patched fast-uri 3.1.4 lockfile.

Stable Product Set

• EvoZeus Core v0.3.5
• EvoZeus Runtime v0.2.0
• EvoZeus-CoEvolve v0.13.0
• EvoZeus Session Signal Skill v0.1.0

Verification

• Full EvoZeus CLI, install, Doctor, channel transaction, and GitHub governance suites passed.
• CoEvolve v0.13.0: 157 tests and 8 subtests passed.
• The exact component commits passed the single-UAT product channel, component integrity checks, local channel status, and Doctor before Stable promotion.
• Stable installation remains explicit and transactional; no runtime auto-write is enabled for Stable.

Rollback

The prior Stable product release remains installed and addressable as v0.3.4. Published tags are immutable; any corrective release will use a new patch version.

EvoZeus v0.3.4

EvoZeus v0.3.4

EvoZeus v0.3.4 makes channel updates recoverable after an interrupted install.

When an interrupted process leaves the deterministic target root partially populated, the next update now identifies it as unreferenced, removes only that incomplete managed root, and retries the transaction. Current and rollback installations remain protected. This release includes the CoEvolve Harness status correction introduced in v0.3.3.

The product set continues to pin EvoZeus Runtime v0.2.0, EvoZeus-CoEvolve v0.12.0 and EvoZeus Session Signal Skill v0.1.0.

EvoZeus v0.3.3

EvoZeus v0.3.3

EvoZeus v0.3.3 fixes Harness status reporting.

evozeus coevolve status now executes the installed CoEvolve diagnosis and uses that result as the single source of truth for the current manifest path, wrapper version, migration requirement and layout conflict. Harness attach plans now identify .evozeus-wrapper/ as the current layout and retain the two older directory names only for migration guidance.

The product set continues to pin EvoZeus Runtime v0.2.0, EvoZeus-CoEvolve v0.12.0 and EvoZeus Session Signal Skill v0.1.0.

EvoZeus v0.3.2

EvoZeus v0.3.2

EvoZeus v0.3.2 completes the single-UAT recovery path.

When the central uat/current manifest points to a previously verified candidate, the updater rechecks exact commits, local cleanliness, required files, smoke health and compatibility before reusing its isolated root. The current verified UAT remains active if any check fails. This preserves one user-visible UAT while supporting repaired candidates and executable rollback history.

The product set pins EvoZeus Runtime v0.2.0, EvoZeus-CoEvolve v0.12.0 and EvoZeus Session Signal Skill v0.1.0.

EvoZeus v0.3.1

EvoZeus v0.3.1

EvoZeus v0.3.1 corrects Release bootstrap provenance reporting.

An installation from the verified custom Release archive now records the immutable Release tag, exact commit and archive SHA-256. Invalid or incomplete Release provenance is rejected before any local write. The Stable and single-UAT channel model introduced in v0.3.0 remains unchanged.

The product set pins EvoZeus Runtime v0.2.0, EvoZeus-CoEvolve v0.12.0 and EvoZeus Session Signal Skill v0.1.0.

EvoZeus v0.3.0

EvoZeus v0.3.0

EvoZeus v0.3.0 introduces a product-level Stable and single-UAT channel model.

Stable installs use immutable Release archives with exact commits and SHA-256. UAT uses isolated worktrees and one mutable uat/current candidate. A repaired UAT replaces the same candidate; a failed refresh continues the previous verified UAT. CLI, Doctor, reports and the CoEvolve SessionStart dispatcher expose the active channel so test output cannot be mistaken for formal output.

The product set pins EvoZeus Runtime v0.2.0, EvoZeus-CoEvolve v0.12.0 and EvoZeus Session Signal Skill v0.1.0.

v0.2.3

Changes

• Add the install onboarding conversation reference required by the public /skill handoff.
• Keep the public copy prompt to one short sentence while moving registration, privacy, CLI help, and capability introduction details into the release source.
• Require post-install capability introduction to use a fixed template after running evozeus --help and evozeus capabilities --json.

Verification

• npm run test:cli
• npm run test:install
• npm run test:doctor
• python3 scripts/check_pr_ready.py --base origin/main was run; only the direct-release branch-name rule failed because this release was pushed from main by request.
• python3 /Users/anthonyf/Documents/EvoZeus-cluster/scripts/validate_skill_system.py
• git diff --check

EvoZeus v0.2.2 - User-level install home

Summary

• Fix EvoZeus install registration to use the user-level ~/.evozeus home instead of workspace-local .evozeus folders.
• Update the local CLI, installer, doctor guidance, and install Skills to read/write the same user-level EvoZeus home.
• Add regression coverage so dry-run/install flows do not create workspace-local .evozeus state.

Validation

• node --test scripts/*.test.mjs
• installer dry-run reports /Users/anthonyf/.evozeus/... as planned write targets and marks workspace .evozeus as unused.