From 5152f0baa41fe5f37b0b65f430db3a0a955b1ded Mon Sep 17 00:00:00 2001 From: Lukas May Date: Sat, 31 Jan 2026 09:45:13 +0100 Subject: [PATCH] docs(09): capture phase context 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 --- .../09-extended-scenarios/09-CONTEXT.md | 52 +++++++++++++++++++ 1 file changed, 52 insertions(+) create mode 100644 .planning/phases/09-extended-scenarios/09-CONTEXT.md diff --git a/.planning/phases/09-extended-scenarios/09-CONTEXT.md b/.planning/phases/09-extended-scenarios/09-CONTEXT.md new file mode 100644 index 0000000..ae74a2e --- /dev/null +++ b/.planning/phases/09-extended-scenarios/09-CONTEXT.md @@ -0,0 +1,52 @@ +# Phase 9: Extended Scenarios - Context + +**Gathered:** 2026-01-31 +**Status:** Ready for planning + + +## How This Should Work + +This 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: + +1. **Conflict hand-back** — When a merge fails, the agent receives the conflict and resolves it. The full round-trip works. + +2. **Multi-agent parallel work** — Multiple agents dispatched simultaneously, each working in their worktree, merging in correct dependency order. + +3. **Recovery/resume after interruption** — System can pick up where it left off after crash or interruption. + +4. **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. + + + + +## What Must Be Nailed + +- **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 + + + + +## Specific Ideas + +- 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 + + + + +## Additional Context + +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*