docs/wiki/agent-events-reference.md

@@ -113,28 +113,7 @@ Full 61-line transcript is stored on OSA, outside the repository.
 | `text_delta`              | `message_update`        | Streaming text response                                                          |
 | `done`                    | `agent_end`             | Session end                                                                      |
 
-### Glasspane gaps
-
-**None.** All 15 real-key event types have valid, non-duplicate mappings.
-
-**Resolved:** `tool_call` was previously mapped to
-`tool_execution_start` (same as `tool_use_start`), causing a double-fire.
-The standalone `tool_call` event is now skipped — it returns `None` from the
-normalizer. `tool_use_start` is the sole entry point for tool execution start.
-
-### Verified facts (observed, not inferred from source)
-
-- `tool_use_start/args/end` for streamed tool calls
-- standalone `tool_call` appears after `tool_use_start`; Glasspane skips it to avoid a duplicate start
-- `text_delta` streams response text character by character
-- `assistant_message` appears in two contexts (tool block + final text)
-- `turn_end.stop` distinguishes "tool_use" vs "end"
-- `tool_result` carries `is_error` boolean
-- `usage` carries `cache_read`, `cache_write`, `cost_usd`, `cumulative`
-
-The wire format work is complete — format and all 15 event types are
-validated against real output. The `tool_call` double-fire gap is resolved by
-skipping the duplicate standalone event in Glasspane.
+All 15 event types are validated against real zot output. The `tool_call` event is intentionally skipped — `tool_use_start` is the canonical entry point for tool execution.
 
 ## See also