Skip to content

Commit 8297851

Browse files
wenshaowenshao
committed
style(docs): format 09-event-schema.md so the Prettier lane passes again
Upstream #13281 landed the doc with 4 badly wrapped table lines; its own lint lane ran a 15 s light profile that never scanned it, so the violation reached main unnoticed and began failing every PR merge ref computed after 2026-10-07T04:45Z (this PR's run on 13d1735 inclusive). Format-only change: `prettier --write` (4 lines); the whole-tree `--check .` now passes, and upstream #13536's version of the same file is already clean, so the next main merge stays green by construction.
1 parent 13d1735 commit 8297851

1 file changed

Lines changed: 4 additions & 4 deletions

File tree

‎docs/developers/daemon/09-event-schema.md‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -164,10 +164,10 @@ These events are workspace-keyed, not session-keyed. The session reducer treats
164164

165165
### Pending prompt queue
166166

167-
| Type | Direction | Trigger | Key payload fields |
168-
| -------------------------- | --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------ |
169-
| `pending_prompt_added` | S->C | A prompt was appended to the session's prompt FIFO and is waiting behind the active turn. Published only when the prompt is *genuinely queued* — the first prompt on an idle session starts immediately and emits no queue events. | `sessionId, promptId, text, queuedAt` |
170-
| `pending_prompt_started` | S->C | The queued prompt reached the head of the FIFO and was promoted to running (also emitted for a promoted mid-turn message that starts immediately). Skipped when the prompt is aborted before promotion. | `sessionId, promptId, text` |
167+
| Type | Direction | Trigger | Key payload fields |
168+
| -------------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------ |
169+
| `pending_prompt_added` | S->C | A prompt was appended to the session's prompt FIFO and is waiting behind the active turn. Published only when the prompt is _genuinely queued_ — the first prompt on an idle session starts immediately and emits no queue events. | `sessionId, promptId, text, queuedAt` |
170+
| `pending_prompt_started` | S->C | The queued prompt reached the head of the FIFO and was promoted to running (also emitted for a promoted mid-turn message that starts immediately). Skipped when the prompt is aborted before promotion. | `sessionId, promptId, text` |
171171
| `pending_prompt_completed` | S->C | A queued prompt settled — `state: 'completed'` (it ran; execution errors still report `completed` and ride the terminal `turn_error` frame) or `state: 'removed'` (removed from the queue and never ran). Only emitted for prompts that were genuinely queued (an `added` was published). This is queue-view bookkeeping, **not a turn terminal**; correlate `turn_complete` / `turn_error` by `promptId` for completion. | `sessionId, promptId, state: 'completed' \| 'removed'` |
172172

173173
### Turn lifecycle / assistant pushes

0 commit comments

Comments
 (0)