Phase 9: Extended Scenarios - Vision and goals documented - Four core scenarios: conflict hand-back, multi-agent, recovery, question/answer - CI deferred - focus on test coverage
1.8 KiB
Phase 9: Extended Scenarios - Context
Gathered: 2026-01-31 Status: Ready for planning
## How This Should WorkThis phase proves the system handles real-world complexity — not just happy paths, but the messy scenarios that happen when multiple agents work in parallel, things go wrong, and the system needs to recover.
Four core scenarios to validate:
-
Conflict hand-back — When a merge fails, the agent receives the conflict and resolves it. The full round-trip works.
-
Multi-agent parallel work — Multiple agents dispatched simultaneously, each working in their worktree, merging in correct dependency order.
-
Recovery/resume after interruption — System can pick up where it left off after crash or interruption.
-
Agent question/answer resume — When an agent asks a question (AskUserQuestion), the system pauses, receives the answer, and the agent continues from where it stopped.
- All four scenarios proven — Each must have E2E test coverage demonstrating the flow works
- Conflict resolution round-trip — Agent receives conflict, fixes it, merge succeeds
- Question/answer resume — Agent pauses for input, receives response, continues execution
- Use MockAgentManager scenarios to simulate waiting_for_input and crash states
- Use MockWorktreeManager to inject merge conflicts
- Test multi-agent by pre-seeding multiple idle agents and dispatching parallel tasks
- No CI pipeline needed — focus purely on test coverage
CI was explicitly deferred — not part of this phase scope. Phase goal is proving system resilience and coordination, not automation infrastructure.
Phase: 09-extended-scenarios Context gathered: 2026-01-31