gh-aw lifecycle overwrites a merged cast with the default preset on later runs #1657

Summary

A successful /squad cast can generate and merge a repository-specific team, but the next gh-aw lifecycle run initializes the default preset again and plans with the generic roster instead of the committed cast.

Tested version

• Squad SHA: 47e04dc73663cba40b47f00dd8e2ac42c37f6419
• Consumer: https://github.com/bradygaster/squad-planning-e2e
• Root intent: https://github.com/bradygaster/squad-planning-e2e/issues/2

Prerequisites

• Install bradygaster/squad/workflows/squad.md@47e04dc73663cba40b47f00dd8e2ac42c37f6419 with the supported gh aw add path.
• Compile strictly and activate the workflow on the default branch.
• Allow Actions to create pull requests.

Reproduction

1. Run /squad cast on the intent.
2. Merge the generated cast output into main.
3. Run /squad research on the same intent.
4. Inspect the repository state seen by research and the later implementation agent assignments.

Evidence

• Cast run: https://github.com/bradygaster/squad-planning-e2e/actions/runs/31240094826
• Cast output PR: https://github.com/bradygaster/squad-planning-e2e/pull/4
• Cast team: neo, switch, interface, trinity, tank, oracle
• Research run: https://github.com/bradygaster/squad-planning-e2e/actions/runs/31240447391
• Research output: https://github.com/bradygaster/squad-planning-e2e/issues/2#issuecomment-5224630555

The research output reports that .squad/team.md contains the generic lead, reviewer, devrel, security, and docs scaffold and recommends re-casting. Later implementation planning assigns work to those generic roles, not the merged cast members.

The distributed shared bootstrap runs squad init --preset default --state-backend local on every workflow activation. Sanitized observed behavior is consistent with that step replacing the committed cast state before the agent job.

Expected behavior

Once cast output is merged, subsequent research/planning runs should preserve and use the committed .squad/ team. Default initialization should occur only when no usable team exists, or it should avoid overwriting existing repository state.

Actual behavior

Each lifecycle run sees a fresh default roster, disconnecting cast from research, planning, validation, acceptance, and activation.

Impact

The advertised cast-through-activate lifecycle does not operate as one team-aware lifecycle: casting has no effect on later specialization or assignment. Generated plans can assign generic roles that contradict the accepted repository-specific cast.