Repository navigation
Fix terminal lifecycle for granular plan activation #2049
Description
Bug
/squad plan activate can create all planned issues successfully and still end red because the terminal lifecycle safe-output validator accepts /squad activate and /squad plan accept, but not the granular command /squad plan activate. The terminal repair path has the same command omission and only recognizes the fast-path plan-accepted artifact, not granular impl-accepted.
Evidence
- Reference failure: https://github.com/octodemo/eshop-bradyg-dev/actions/runs/34987615314
- Durable activation output: https://github.com/octodemo/eshop-bradyg-dev/issues/4#issuecomment-5682975648
- Failing job message:
Lifecycle body must include an H2 lifecycle heading plus state, last-command, and a nonterminal next-action value consisting of a backticked /squad command.
Acceptance criteria
- Terminal lifecycle upsert accepts
/squad plan activate. - Idempotent terminal repair recognizes
/squad plan activateafter a trustedimpl-acceptedartifact. - Existing fast-path commands remain supported.
- Targeted lifecycle tests and all seven strict gh-aw compilations pass.
Activity
github-actions commentedon Sep 15, 2026
📋 Assigned to agentic-workflows-dev (Agentic Workflows Engineer)
Issue: #2049 — Fix terminal lifecycle for granular plan activation
agentic-workflows-dev will pick this up in the next Copilot session.
fix(gh-aw): accept granular activation lifecycle
bradygaster commentedon Sep 23, 2026
Closing as resolved — this was fixed by PR #2050, and current lifecycle validation accepts
/squad plan activate(workflows/shared/squad.md:338,scripts/check-workflow-input-interpolation.mjs:78-80).