Bring the remaining docs in line with docs/WRITING.md #9525

This pull covers docs/STATUS.md only, the first document in the issue's order. I haven't touched docs/SECURITY-RUNBOOK.md or docs/THREATS.md, so the issue stays open for those and the later documents.

What changed

• The 28 flat feature bullets are now grouped under headings: Accounts and access, Code hosting, Apps and crew, Boards and flow, Terminal, Rendering and themes, Isolation and landing, and Not done. No bullet text was cut apart. The "Built since" paragraph became the "Isolation and landing" section.
• I removed history phrasing ("it was 5,000 for every view before", "No dependency was added", "Built since", "new-account line") and a stray double space.
• I replaced the "Still zero runtime dependencies" claim with "The forge has no runtime dependencies". The package.json grep for dependencies found no match, so I treated it as true, but I didn't read the file to confirm.
• I checked that the files the document names exist: clog_tick.ts, outbound.ts, contain.ts, app_domains.ts, landing.ts, queue.ts, boards/pins.ts, pinned.ts, board-pins.ts, docs/TOUR.md and docs/APPS.md. I also confirmed the 10,000-line ?all=1 cap, the memory_hour table, waves.atom and the board_pins MCP tool in the source.
• I did not verify the many behavioural claims in the Boards and flow bullets (alarms, pins, panel limits and so on) line by line.

Checks

• Em dashes added: 0. Issue numbers in the first 12 lines: 0. No README's references and no magic, boring or at 3 a.m..
• test/readme-front-door.test.ts, test/readme-cap.test.ts, test/dependencies-named.test.ts and test/design-lint.test.ts pass (35 tests). test/roll.test.ts, which reads STATUS.md, passes.
• I did not run test/mcp-size.test.ts, because no MCP code changed. I did not run bun x tsc --noEmit or scripts/gate.ts either, because the diff is docs only.

What I chose not to do

• I did not shorten the bullets. Some, such as Boards, are still very long, and the next pass over this file could split them into per-topic documents, as step 7 of the issue plans.
• I did not call keep_plan, because that tool wasn't available to me in this session.

Closes #9426

This pull covers docs/STATUS.md only, the first document in the issue's order. I haven't touched docs/SECURITY-RUNBOOK.md or docs/THREATS.md, so the issue stays open for those and the later documents.

What changed

• The 28 flat feature bullets are now grouped under headings: Accounts and access, Code hosting, Apps and crew, Boards and flow, Terminal, Rendering and themes, Isolation and landing, and Not done. No bullet text was cut apart. The "Built since" paragraph became the "Isolation and landing" section.
• I removed history phrasing ("it was 5,000 for every view before", "No dependency was added", "Built since", "new-account line") and a stray double space.
• I replaced the "Still zero runtime dependencies" claim with "The forge has no runtime dependencies". The package.json grep for dependencies found no match, so I treated it as true, but I didn't read the file to confirm.
• I checked that the files the document names exist: clog_tick.ts, outbound.ts, contain.ts, app_domains.ts, landing.ts, queue.ts, boards/pins.ts, pinned.ts, board-pins.ts, docs/TOUR.md and docs/APPS.md. I also confirmed the 10,000-line ?all=1 cap, the memory_hour table, waves.atom and the board_pins MCP tool in the source.
• I did not verify the many behavioural claims in the Boards and flow bullets (alarms, pins, panel limits and so on) line by line.

Checks

• Em dashes added: 0. Issue numbers in the first 12 lines: 0. No README's references and no magic, boring or at 3 a.m..
• test/readme-front-door.test.ts, test/readme-cap.test.ts, test/dependencies-named.test.ts and test/design-lint.test.ts pass (35 tests). test/roll.test.ts, which reads STATUS.md, passes.
• I did not run test/mcp-size.test.ts, because no MCP code changed. I did not run bun x tsc --noEmit or scripts/gate.ts either, because the diff is docs only.

What I chose not to do

• I did not shorten the bullets. Some, such as Boards, are still very long, and the next pass over this file could split them into per-topic documents, as step 7 of the issue plans.
• I did not call keep_plan, because that tool wasn't available to me in this session.

No feedback text reached me, so I changed nothing and pushed nothing.

The pull's status shows one review marked "changes requested". The reviews endpoint returns [], the threads endpoint returns [], and the issue thread holds only my own description comment. I found no inline comments or review body anywhere the API let me read.

I won't guess at what the reviewer wanted and push an edit that may miss it. Please post the requested changes as a comment on the pull, or tell me which parts of docs/STATUS.md to change. I'll address them on this branch.

One thing I can see: the base branch has moved since I branched (d5cf759d now, 21bd1b87 at branch time). The forge reports the pull as mergeable with no conflicts, and its last check was green but is now marked stale.

Handed to a person by the crew: two follow-up runs on the review's changes ended without a push, so no more start here until you say what to try. (The forge posts this under the reviewer's name; the reviewer did not write it.)