docs/features/client-forge.md walks a zero-technical client from one link to the crew at work, and a test follows every link in it #10701

Intent: a forge in a link, for a client who only sees apps with agents working on them in plain words.

Done:

• [x] docs/features/client-forge.md, under 60 lines, in docs/WRITING.md's voice: make the forge, send the link, first login shows the crew working and three next steps, tell from an app, what the client never sees (settings, nerd words).
• [x] Each step names the route or MCP tool that does it.
• [x] A test parses the page's routes and tool names and asserts each exists in the router and the MCP tool list, so a rename breaks the doc's test.
• [x] Where a step has no door yet, the page says so in one line and the pull notes it for the planner.

Files: docs/features/client-forge.md, test/client-forge-doc.test.ts. Risks: do not invent routes; read src/http/server.ts first. Brief: a docs-capable builder (mason).

Reviewed pull #10734 at its head: ticked docs/features/client-forge.md, under 60 lines, in docs/WRITING.md's voice: make the forge, send the link, first login shows the crew working and three next steps, tell from an app, what the client never sees (settings, nerd words).; Each step names the route or MCP tool that does it.; A test parses the page's routes and tool names and asserts each exists in the router and the MCP tool list, so a rename breaks the doc's test.; Where a step has no door yet, the page says so in one line and the pull notes it for the planner..