l0ng-ai 3edcc3884a docs(cli): agent_status is never sent either — correcting yesterday's table ...

The previous commit documented the `events` schema and listed `agent_status` as
one of the kinds a listener sees. It is not: `ControlEvent::AgentStatus` has the
same shape of problem as `PaneExited`, which is how it slipped through — the
only two references anywhere are the round-trip test in its own file and the
formatter in `tty7-cli`, with no emitter.

Auditing all six protocol enums is what turned it up. `ControlRequest` (42
variants), `ClientMsg` (30) and `DaemonMsg` (28) are clean; every `LayoutDelta`
and every other `ControlEvent` has a real emitter — `Preempted` and
`LayoutResync` in `host::server`, `GuiOpen` beside them — which is exactly what
made these two look supported.

Agent status is reported the same way a pane exit is: a `layout` delta whose
`pane_facts` carries the pane, with `agent.status` on it (`AgentFacts.status`
rides on `PaneRecord`). The note now covers both, and points at `tty7 wait` and
`tty7 agents` as the supported way to ask about an agent, since neither is
built on this stream.

Both variants now carry the comment; the recommendation is unchanged — emit
them or remove them together with their `event_line` arms, but not in passing,
because it is a dialect change.

2951 tests pass.

2026-08-15 19:34:35 +08:00

..

agent-skill.mdx

docs(skill): show how to update an installed tty7 skill

2026-08-12 17:09:55 +08:00

overview.mdx

docs: correct claims that no longer match the code

2026-08-11 14:35:54 +08:00

reference.mdx

docs(cli): agent_status is never sent either — correcting yesterday's table

2026-08-15 19:34:35 +08:00