Phase 1 run-control semantics and run_state events

2026-02-25 10:22:44 -08:00
parent ae21681958
commit e4ee6acce8
13 changed files with 485 additions and 120 deletions
@@ -91,6 +91,7 @@ Within a lane:

 - Only one request executes at a time.
 - Later requests queue (FIFO) and start after the active request finishes.
+- `interrupt` mode enforces "latest wins": any queued backlog is superseded and the active run is asked to cancel so the newest request becomes the next (or immediate) execution.

 Across lanes:

@@ -112,6 +113,7 @@ Important:

 - Cancellation is best-effort for the currently running work: it stops at the next safe point in the agent loop.
 - Queued work is deterministically rejected.
+- Gateway streams `run_state` events (`start`, `cancel_requested`, `cancelled`, `complete`, `error`) so clients can render lifecycle state without parsing assistant text.

 Key files: