Repository navigation
v0.3.0 — Automation lifecycle modes
Manage a single automation across its whole life — on Codex, Claude, Gemini, or Cursor — with four new verbs in scripts/lifecycle.py. Every verb runs one pipeline: mutate suite.toml → validate the fleet → gate on approval → materialize per agent. Default is a dry run; --apply is the confirmation.
Added
setup— profile a project and stand up its whole suite (propose → confirm → install).add— add one pattern (P1..P8) to an existing suite, capability-checked and fleet-validated.remove— retire a job: disable by default (reversible);--purgearchives sidecar state then deletes. Refuses to orphan the fleet.update— change schedule / params / scope / mode / model; a safety-relevant change re-enters the approval gate.- All four agents executable via
scripts/agent_materializers.py:native_file(Codex, Claude) writes registry files;external_cron(Gemini) andcloud_api(Cursor) emit config and never edit cron or touch the cloud. - Cross-agent merge-authority guard — exactly one active integrator even across agents; others run in shadow.
scripts/pattern_bodies.py(P1..P8 prose as shared data) andscripts/selftest_lifecycle.py(23 end-to-end checks).
Changed
scaffold_suite.pyimports its template bodies from the shared module; output is byte-identical to v0.2.0 (verified by diff).
Full changelog: CHANGELOG.md