Fix a self-contradiction and a stale citation in the Events table pointer

Greybeard and Critique both caught the same defect: the new prose
claimed the table names "only the two events reactor-events.ts guards
for" while the table itself still had three rows, including tool.done
(which reactor-events.ts doesn't guard). Rewrote the prose to say why
tool.done is there instead of asserting a count the table contradicts.
Also corrected the PRODUCTION_REACTOR_TYPES line citation, carried
over wrong from the audit doc (66-80 -> 62-78 in both ARCHITECTURE.md
and IMPLEMENTATION.md).

Author: TheGreatAxios

docs/ARCHITECTURE.md

@@ -14,16 +14,19 @@ The reactor (from `@intx/agent`) drives a single agent turn-by-turn. Each turn i
 
 This repeats until the director emits `capabilities.done()`.
 
-### Events the turn-boundary guards distinguish
-
-This table is not the full reactor/stream event vocabulary — it names only
-the two events `src/agent/reactor-events.ts` exports guards for. The
-complete set of reactor and stream event types the TUI maps is
-`PRODUCTION_REACTOR_TYPES` in `src/tui-opentui/stream-event-map.ts:66-80`
-(15 types as of this writing, including `message.received`,
-`inference.start`, `inference.text.delta`, `inference.tool_call.start` /
-`.delta` / `.end`, `tool.start`, and `connector.reply`) — treat that as
-canonical rather than this table or any other doc's partial list.
+### Events this section talks about
+
+This table is not the full reactor/stream event vocabulary. `tool.done` is
+here because the sub-sections below reference it; `inference.done` and
+`reactor.done` are the two events `src/agent/reactor-events.ts` exports
+guards for (`onTurnBoundary` / `onReactorShutdown`) — see the paragraph
+after the table. The complete set of reactor and stream event types the TUI
+maps is `PRODUCTION_REACTOR_TYPES` in
+`src/tui-opentui/stream-event-map.ts:62-78` (15 types as of this writing,
+including `message.received`, `inference.start`, `inference.text.delta`,
+`inference.tool_call.start` / `.delta` / `.end`, `tool.start`, and
+`connector.reply`) — treat that as canonical rather than this table or any
+other doc's partial list.
 
 | Event | When it fires |
 |---|---|

docs/IMPLEMENTATION.md

@@ -335,7 +335,7 @@ session; that tree re-write is inherent to git and left as residual cost.
 `agent.stream()` emits `ReactorEmittedEvent` objects. `docs/ARCHITECTURE.md`'s
 "Events" section names the two turn-boundary/shutdown events the directors
 guard on; the full set of reactor and stream event types is
-`PRODUCTION_REACTOR_TYPES` in `src/tui-opentui/stream-event-map.ts:66-80` —
+`PRODUCTION_REACTOR_TYPES` in `src/tui-opentui/stream-event-map.ts:62-78` —
 treat that as the canonical list rather than maintaining a second one here.
 
 Mid-run queue/steer/interrupt state is a pure state machine in `src/tui-opentui/session-queue.ts` (interaction contract §3): `enqueue` (kind `"queue"`) and `enqueueSteer` (kind `"steer"`) share one pending pool, drained steer-first, then queue, both FIFO within their class. The prompt hint (`src/tui-opentui/stream.ts`, `PROMPT_HINT`) reads `Enter queue · Alt+Enter steer · Ctrl+C stop`.