Say that the reference is checked, and add the script that checks it The reason to trust a hand-written reference is that something fails when it drifts. Now something does, so the page says so.
Name the third class, since two of the three were named and it was not
The framework's whole surface too, not the twelve of twenty-one Same question as the client, same honest answer. Missing: say, named, free, slug, the two tunable constants, Agent.state / arrived / branch / label, Group iterating and having a length, Result.path and its truthiness. And `o.argus`, which is the important one and the exact counterpart of the client's `call`: the framework does not hide the layer under it, and that is worth a line rather than being something you find by reading the source.
Every method the client has, not the eight I happened to name Asked whether all of them were documented and the honest answer was no. Missing: call, sessions, launchers, worktrees, wait_for, config_path and credentials — in the code and nowhere else. `call` is the one that matters most of those. It is the escape hatch: any route at all, with the token attached and the errors unwrapped, which is what makes it true that nothing is hidden behind the convenience methods.
The framework has a reference, not only a story Asked for plainly: the three layers exist and only one of them was written down. This is the surface — every argument, what each call returns, the prompt an agent actually receives with both of the framework's own additions marked, and which layer to reach for when. Also the two things that arrived with it and were only in the code: /api/runs, and the desk flag on a launch.