First: phase is not manually edited
Do not hand-edit phase to force progress. Use the workflow transition that matches the evidence.
Available transition events
Typical events include proposal approval, design approval, build completion, verify pass, verify fail, archive completion, and preset upgrade.
Scenario 1: edit spec during build
If the spec changes during build, Comet should detect drift and decide whether the current design still applies.
Scenario 2: implementation is wrong and you want to rebuild
Use a verify-fail or explicit rollback path. Preserve evidence, then return to build with a clear reason.
In the normal flow, branch_status remains pending; do not write handled during re-verification. Archive records the confirmed delivery method.
Scenario 3: verify passed but you want another check before archive
Use archive-reopen to return to Verify. It resets branch_status to pending; Archive only after the evidence is acceptable and you are ready for immediate remote delivery.
Scenario 4: hotfix or tweak grows larger
Upgrade the preset to the full workflow when the work needs design, broader verification, or spec changes.
Scenario 5: resume finds uncommitted changes
Inspect the worktree. Do not discard changes unless the user explicitly asks.
Rollback reference
Last modified on July 24, 2026
