Repository navigation
Decide whether to drop bots: from squad.md (compiler concurrency warning) #1763
Description
The warning
workflows/squad.md (~L8–14) co-configures both slash_command and bots:. The gh-aw compiler emits a warning on every gh aw add:
a bot listed in
bots:posting a comment starting with the slash command text will trigger the workflow and occupy the concurrency slot, potentially blocking manual invocations
Reproduced again during the 2026-08-19 workflow refresh. Pre-existing — not introduced by #1741, #1742, #1744, #1747, or #1752.
Why it's not a trivial delete
The compiler's own recommendation is to remove bots:. But before doing that, verify nothing depends on bot-authored comments triggering Squad.
Specifically: the merge-continuation path posts as github-actions[bot]. If that path relies on a bot comment to trigger the router, removing bots: breaks epic continuation — the exact chain that took three PRs (#1741, #1747, #1752) to get working.
Check this before changing anything.
The decision
- (a) Remove
bots:— follows the compiler's recommendation, only if the continuation path is confirmed not to depend on it - (b) Keep it and document the warning as a known, accepted trade-off
Small and isolated. Needs a decision more than it needs code.
⚠️ If you do edit squad.md
Never put a ## heading inside a ## skill: block. The block closes implicitly at the next H2, and everything up to the next skill marker is silently discarded — ~29 KB was lost this way once and it still compiled clean. Skills use #####.
Run npx vitest run test/gh-aw-quality.test.ts before pushing; it asserts zero discarded bytes.
Origin
Finding D from the 2026-08-19 live end-to-end run.
Activity
bradygaster commentedon Aug 20, 2026
Flight sequencing note — revised 2026-08-20.
Wave: 5.
Depends on:
Blocks: nothing else in this stream.
Safe to run in parallel with: mechanically, #1770, #1760, #1761, #1762, #1768, #1756, and #1759 touch disjoint areas. Architecturally, defer this decision until #1772 is fixed and a continuation run is green.
Why / evidence:
workflows/squad.mdstill hasbots: ["github-actions[bot]"]besideslash_commandat lines 7-15;workflows/squad-implement-worker.mdalso hasbots:at lines 6-19. Tests assert both attest/gh-aw-implement-workflow.test.tslines 102-115. #1767's latest outcome showed the implement-dispatch hop is clean but the merge-continuation hop fails; that strengthens the case for deferring #1763. It does not provebots:caused the failure — #1772's evidence points todispatch-workflow max: 1at worker lines 202-205 and a schema probe despite prompt guard lines 226-233.bradygaster commentedon Aug 20, 2026
Closing — keep \�ots:. Removing it breaks a tested expectation with zero functional benefit.
Booster's triage confirmed:
This is distinct from #1730's concurrency axis, which addresses issue-scoped concurrency and actor authorization — that remains open (deferred to wave:3). The \�ots:\ compiler warning can be revisited in wave:5 if the team identifies a scenario where it bites.
chore(squad): repair archival data loss and record gh-aw triage sessi…