l0ng-ai a67234266b docs(cli): name doctor's config section, and pin the shape ...

`tty7 doctor --json` has emitted a fourth top-level section, `config`, since
it started answering for a config file that parses but carries keys tty7 does
not read. The reference went on describing three. Checked the documented shape
of every `--json` verb against a live daemon; this was the one that disagreed.

It matters more here than elsewhere. `doctor` is one of the three verbs whose
JSON is printed even when the verb fails — an unreachable server is the
finding, and `tty7 doctor || alert` needs the rows as well as the code — so
something is always parsing this.

The page now names `config`, says what `ok` and `state` mean, and says which
of the table's rows are prose rather than fields, so the next reader is not
left looking for `config keys` in the JSON.

The guard compares doctor's top-level sections against the ones the reference
line names, both directions. Top level only: the fields inside vary with what
a server could be asked — `context` gains `workspace_gone` and `pane_gone`
only when one answered — and the page explains that in prose it would be wrong
to pin to a fixed list. Verified by dropping the section from the page, and by
dropping it from doctor.

2026-08-23 05:06:39 +08:00

..

agent-skill.mdx

docs(skill): restructure the agent skill around a delegation playbook (#702)

2026-08-20 21:02:11 +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): name doctor's config section, and pin the shape

2026-08-23 05:06:39 +08:00