Docs worth reading, and kept that way
Redesign the docs in g1t's own look: the cube in the header, a sidebar grouped by what people come to do, quieter type, lavender only as the accent, and a home page that starts from four paths instead of a list. The API reference gets the same header. Split the long pages into guides that each own one thing: handing off an outcome, the merge queue, talking to agents, sessions and why-blame, workspaces, usage and billing, and the MCP tools. Each says only what the code does. answer_message gets a REST route, POST /repos/{owner}/{name}/messages/{id}/answer, so every operation has one again. llms.txt covers plans, the merge queue, steering, agents asking each other, and the session hook, and links the new pages. CONTRIBUTING.md makes it a rule: a change ships with its docs.
No changes