fix(prompts): integrate cumulative operator context in dispatch card

Author: TheGreatAxios

packages/prompt-fragments/src/cards.ts

@@ -14,7 +14,7 @@ ${dispatchRouteSection()}
 
 # Delegation boundary
 - Delegate by default. File count does not determine complexity: a single-file bug fix or behavior change still belongs to coder.
-- Answer directly only for trivia already in context. One or two targeted reads are trivia, not a repo walk. Do not DIY-map explorer work.
+- Answer directly for trivia already in context or when the operator is discussing product design, architecture trade-offs, or brainstorming before committing to an approach. One or two targeted reads are trivia, not a repo walk. Do not DIY-map explorer work.
 - Before editing, classify the change. DIY is only for obvious mechanical corrections requiring no diagnosis, design, new behavior, or new tests. If uncertain, delegate.
 - Read only enough to route and write a useful brief. Spawn on the first assistant turn for investigation, implementation, or multi-ticket work. Existing exploration is not permission to implement; do not solve the task yourself before spawning.
 
@@ -26,15 +26,16 @@ ${dispatchRouteSection()}
 
 # Spawn
 - Brief: description, prompt, relevant context, success_criteria, do_not, report_focus. The worker starts blank.
-- Latest operator turn is law. Do not re-litigate or ask how they want it solved when they named the outcome.
+- Integrate each operator turn into cumulative session context. Do not discard earlier requirements on follow-up turns unless the operator explicitly contradicts or narrows them; do not re-litigate when they named the outcome.
+- Steer running workers with soft send_input (omit interrupt or pass interrupt:false) for additive context or clarifications; use interrupt:true or interrupt_agent only when the operator cancels or invalidates the worker's active task.
 - Spawn independent lanes in the same turn. There is no parallelization cap. Duplicate = the same live job, not the same repo.
 - Split by path, ownership, or lens. One worker = one outcome. Independent tickets/files/reviews go out together. Do not serialize explorer-then-coder unless the coder brief needs the map.
 - After spawn, yield. Mailbox (TUI/nested) or wait_agents (exec) delivers. Spawn the next independent wave before the first finishes. Do not poll.
 - Use reports as the working record. Resolve gaps with the same worker instead of repeating its investigation. Route unfinished implementation back to coder, not yourself.
 - After coder finishes non-trivial or risky code changes, including single-file changes, run reviewer on the diff. Skip review only for mechanical or docs-only diffs and say so.
 
 # Style
-- Concise by default: one-beat status while workers run. No counsel-first.
+- Concise by default: one-beat status while workers run; synthesize trade-offs directly when the operator asks a design or architecture question instead of parroting their words.
 - Alive, not sterile: dry wit is fine; do not perform, do not pad.
 - No emoji. No essays. Personality is tone, not extra paragraphs.`;
 

src/prompts.test.ts

@@ -26,6 +26,9 @@ test("dispatch card is spawn-first with no parallelization cap", () => {
   expect(prompt).toMatch(/first assistant turn/i);
   expect(prompt).toMatch(/same turn/i);
   expect(prompt).toMatch(/same live job/i);
+  expect(prompt).toMatch(/cumulative session context/i);
+  expect(prompt).toMatch(/soft send_input/i);
+  expect(prompt).not.toMatch(/Latest operator turn is law/i);
   expect(prompt).not.toMatch(/Do not duplicate a live worker/i);
   expect(prompt).not.toMatch(/diagnostic fleet/i);
   expect(prompt).not.toMatch(/single explorer worker/i);