Repository navigation
Decide fate of hand-created fixture issues in aspiregregator-squad-test #1768
Description
The problem
In bradygaster/aspiregregator-squad-test, issues #9 (epic), #10, and #11 were hand-created by an agent — they were not produced by Squad decomposing anything.
They exist because PR #8's merge correctly emitted a no-op: issue #2 was flat, with no decomposable children. Rather than fix the fixture, issues were authored by hand to give the continuation path something to chew on.
That makes any continuation test run against them dishonest. It proves the dispatch mechanics fire, but it does not prove Squad can decompose an epic and then continue through its own children — which is the actual behavior under test.
The decision
(a) Keep them. They're adequate for testing the dispatch hop in isolation, and there's a real cost to rebuilding fixtures.
(b) Scrap and re-decompose. Delete #9/#10/#11, run /squad plan (or the full research → plan → implement path) against a genuine epic, and let Squad produce its own children. Slower, but the resulting test actually exercises the path end-to-end.
Recommendation
Lean (b) — a hand-built fixture can pass while the real path is broken, which is the specific failure mode that cost several rounds of debugging already.
Note on the newer fixture
A second fixture repo, bradygaster/aspiregregator-squad-e2e, is what #1767 targets. Decide whether:
-testgets retired entirely in favor of-e2e, or- both are kept with clearly documented, non-overlapping purposes
Two near-identically-named fixture repos with unclear roles is its own source of confusion.
Related
#1767 — the live e2e re-run that depends on having an honest fixture.
Activity
bradygaster commentedon Aug 20, 2026
Flight sequencing note — revised 2026-08-20.
Wave: 1, but cleanup/decision only — not a blocker for the continuation fix.
Depends on: nothing in this stream.
Blocks: nothing else in this stream.
Safe to run in parallel with: all included issues. It does not touch
bradygaster/squadfiles unless someone chooses to document fixture roles.Why / evidence: #1768 concerns the older
bradygaster/aspiregregator-squad-testhand-created issues (#9/#10/#11). #1767 used the separatebradygaster/aspiregregator-squad-e2efixture with epic #5 and real children #8/#9; the latest #1767 comment showed that honest fixture was good enough to surface #1772. Recommendation: do not spend time making-testthe primary continuation fixture. Either retire it or explicitly document it as legacy/dispatch-hop-only so it cannot be mistaken for the end-to-end fixture again.bradygaster commentedon Aug 20, 2026
Flight triage note — scope expansion
During gh-aw backlog triage I confirmed the same dishonest-fixture problem exists in a second fixture repo. This issue currently scopes only
aspiregregator-squad-test(#9/#10/#11).Also in scope for this decision:
bradygaster/aspiregregator-squad-e2ehas leftover issues #12 and #14 ("Squad workflow dispatch missing command") produced by failed dispatch runs, not by Squad decomposing anything. Continuation tests that run against these are equally dishonest.Rather than open a near-duplicate issue, I'm folding both repos into this one decision. Recommendation (owner Sims): delete/close
squad-test #9/#10/#11andsquad-e2e #12/#14, then regenerate continuation-test fixtures by having Squad actually decompose an epic, so the continuation path is exercised for real.This matters because #1772 and #1758 (the p0 end-to-end path defects) are validated against exactly these e2e runs — trustworthy fixtures are a prerequisite for trusting those fixes. Labeled
wave:1-nextfor that reason.— Flight 🏗️
bradygaster commentedon Aug 20, 2026
Closing — bookkeeping only. Decision was executed weeks ago.
Sims confirmed: runs 32297494287–32297512862 in \�radygaster/aspiregregator-squad-test\ explicitly scrapped the hand-created fixture issues, using the rationale 'dishonest fixture.' squad-test issues #9, #10, and #11 are closed. \�spiregregator-squad-test\ is retired as the primary fixture. \�radygaster/aspiregregator-squad-e2e\ is the sole primary E2E fixture going forward — it contains Squad-decomposed issues (honest fixtures), not hand-created ones.
This issue was never formally closed after the decision executed. Closing now as bookkeeping.