l0ng-ai a4d0a10a6e docs(cli): events had no schema, and promised a pane-exit event nothing sends ...

`events` is the streaming interface an agent builds on, and it was the one verb
whose JSON shape the reference did not give — every other one lists its fields
exactly. Now it does: the externally tagged envelope, the four event kinds a
listener sees, and the thirteen `layout` delta kinds.

The prose also listed "pane exits" as an event type. There is no such event.
`ControlEvent::PaneExited` is defined, encodes, and has a line
`tty7 events` would print for it — and nothing anywhere constructs one outside
the round-trip tests in its own file. `AgentStatus`, `Preempted` and
`LayoutResync` have 2, 10 and 6 emitters respectively; this one has none. An
agent waiting for a pane-exit line waits for good.

What actually happens is checked against a running server: exit the shell in a
pane and exactly one event arrives — a `layout` delta carrying `pane_facts` for
that pane with `"live": false`, and the pane is gone from `pane ls --all`. The
docs now say to watch for that, in a note that says outright there is no
pane-exit line whatever the wire protocol's shape suggests.

The variant keeps a comment saying the same thing, and that resolving it means
either emitting it where the pane is reaped or removing it along with the
`event_line` arm — not something to do in passing, since taking a variant out
of a wire enum is a dialect change.

2951 tests pass.

2026-08-15 19:30:16 +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): events had no schema, and promised a pane-exit event nothing sends

2026-08-15 19:30:16 +08:00