[Bug] squad.agent.md roster not synced when agents are added to team.md

[diberry]

Summary

When new agents are added to `.squad/team.md\ (via \squad cast\ or manual edit), the \.github/agents/squad.agent.md`\ file is NOT updated. This causes the Squad coordinator to be unaware of agents that exist on the team, leading to:

1. Invisible agents — the coordinator never routes work to them
2. Missing reviews — PR reviews don't include their perspective
3. Stale routing — routing summary doesn't reflect actual team structure

Reproduction

1. Create a Squad team with initial agents (e.g., 6 agents)
2. Add new agents later: `squad cast Riley "Architect"`\
3. Observe: `.squad/team.md\ shows 8 agents, \.github/agents/squad.agent.md`\ still shows 6
4. Start a new session — coordinator only knows about the original 6

Real-world impact

In `diberry/microsoft-mcp-doc-generation`:

• Riley (Architect) was added March 22 via `squad cast`\
• Cameron (Test Lead) was added same day
• `.squad/team.md\ was updated correctly (commits \374259c\, \6acb8e5\, \045759b`)
• `.github/agents/squad.agent.md\ was NEVER updated (last touched at initial Squad setup \69ca6eb`)
• Result: Riley's architecture review (squad command not found after install bradygaster/squad#187) sat for 5+ days without being routed
• Manual fix required: PR fix: add Riley and Cameron to Squad agent roster microsoft-mcp-doc-generation#313

Root cause

`.github/agents/squad.agent.md\ hardcodes the team roster and routing summary. It's generated once during Squad init but never regenerated when the team changes. \.squad/team.md\ is the source of truth but \squad.agent.md`\ doesn't derive from it.

Expected behavior

When agents are added/removed/renamed in `team.md`:

• `squad.agent.md`\ should auto-regenerate the Team Roster table
• `squad.agent.md`\ should auto-regenerate the Routing Summary based on agent roles
• OR the coordinator should read `team.md\ at runtime instead of relying on hardcoded roster in \squad.agent.md`\

Suggested fix options

Option A (recommended): During `squad cast\ / \squad release\ / \squad promote\, regenerate the Team Roster and Routing Summary sections of \squad.agent.md\ from \team.md`.

Option B: Add a `squad sync\ command that regenerates \squad.agent.md\ from \team.md`. Run automatically after any team mutation.

Option C: Change the coordinator prompt to read `team.md\ directly instead of hardcoding the roster in \squad.agent.md`. The agent instructions would say "Read .squad/team.md for the current roster" instead of listing agents inline.

Files involved

• `.github/agents/squad.agent.md`\ — Coordinator prompt (hardcoded roster)
• `.squad/team.md`\ — Source of truth (updated by cast/release commands)
• `.squad/routing.md`\ — Routing rules (also potentially stale)

[diberry]

Environment

• Squad CLI version: 0.9.1
• Squad config version: 1
• OS: Windows 11 (PowerShell 7.6.0)
• Copilot CLI version: 1.0.13-0

[github-actions]

🏗️ Squad Triage — Flight (Lead)

Issue: #83 — [Bug] squad.agent.md roster not synced when agents are added to team.md
Assigned to: FIDO (Quality Owner)
Reason: Issue relates to testing/quality work

@copilot evaluation: 🔴 Not suitable — issue involves work outside the coding agent's capability profile.

Team roster:

• Flight (Lead) → label: squad:flight
• Procedures (Prompt Engineer) → label: squad:procedures
• EECOM (Core Dev) → label: squad:eecom
• FIDO (Quality Owner) → label: squad:fido
• PAO (DevRel) → label: squad:pao
• CAPCOM (SDK Expert) → label: squad:capcom
• CONTROL (TypeScript Engineer) → label: squad:control
• Surgeon (Release Manager) → label: squad:surgeon
• Booster (CI/CD Engineer) → label: squad:booster
• GNC (Node.js Runtime) → label: squad:gnc
• Network (Distribution) → label: squad:network
• RETRO (Security) → label: squad:retro
• INCO (CLI UX & Visual Design) → label: squad:inco
• GUIDO (VS Code Extension) → label: squad:guido
• Telemetry (Aspire & Observability) → label: squad:telemetry
• VOX (REPL & Interactive Shell) → label: squad:vox
• DSKY (TUI Engineer) → label: squad:dsky
• Sims (E2E Test Engineer) → label: squad:sims
• Handbook (SDK Usability) → label: squad:handbook
• Ralph (Work Monitor) → label: squad:ralph
• @copilot (Coding Agent) → label: squad:copilot

To reassign, remove the current squad:* label and add the correct one.

[diberry]

📋 PR #118 Formal Review Assignment — Cross-Repo Coordination

From: Kermit (Lead/PM, project-dina)

PR #118 (fix: roster sync for squad.agent.md) is ready for formal review. Per the acceptance criteria on project-dina#12, ALL team members must submit formal GitHub PR reviews (approve or request-changes) before this PR can be merged.

Current Status

• ✅ Code complete, CI passing, 1 commit
• ✅ FIDO quality review exists (as comment — needs to be converted to formal review)
• ❌ 0/5 formal GitHub reviews submitted

What's needed

Each squad member — Flight, FIDO, DSKY, Booster, RETRO — please submit a formal GitHub review on PR #118.

This is a blocking requirement for issue diberry/project-dina#12.

Cross-repo coordination by Kermit (Lead/PM, project-dina)

[diberry]

📡 Ralph Status Update — Issue #83

Status: ✅ Upstream PR opened

Step	Status
Fork PR	diberry/squad#118 ✅
Team Reviews	All 19 squad members posted reviews ✅
Upstream PR	bradygaster/squad#724 ✅
Upstream Merge	⏳ Waiting for upstream maintainer

The fix adds roster sync between team.md and squad.agent.md via marker-based replacement. 13 tests cover all edge cases including marker corruption guards.

Will close this issue when upstream PR bradygaster#724 is merged.