maestro-lifecycle-test

# maestro-lifecycle-test Drive the real maestro CLI through its whole lifecycle in a disposable repo and report what held and what broke, as structured findings the orchestrator can merge across many runs. This is a **single-agent, single-pass** procedure. It never spawns sub-agents. The swarm fan-out (below) is the caller's job, not this skill's. ## When to use - A maestro source change touched install/init, the feature 5-state machine, the task lifecycle, the QA gates (qa-baseline/qa-slice), or proof/verify, and you want an integrated smoke test. - You are one worker in a swarm fix-loop validating maestro (see "Swarm usage" below). It is NOT a replacement for `cargo test` -- the Rust suite already proves the mechanics (extraction rollback, symlink wiring, gate logic) at the unit/contract layer. This skill's value is the **integrated journey + observable CLI output + the loop-ready report**. ## How to run 1. Ensure the binary under test is built. The harness uses a PREBUILT binary and never builds itself (so a swarm of workers does not trigger N concurrent `cargo build`s): ```sh cargo build # the orchestrator does this once per round, in the source checkout ``` 2. Run the harness from anywhere inside the maestro source checkout: ```sh bash .claude/skills/maestro-lifecycle-test/harness.sh ``` Optional env: - `MAESTRO_BIN` -- path to the binary (default `target/debug/maestro` under the source repo). - `MAESTRO_SRC` -- sourc...