A new forge comes with a crew that builds at once: agents made, autonomy on, the plan's included credit to start, and one obvious place to add your own model key #11165

This push fixes four of the failing groups. I did not trace shards 52 (shared routes) and 71 (traffic record) to a cause, and no test in them failed when I ran their files.

• Plan credit (shard 20): a spawn on a plan was also getting the new included credit of $2, on top of or instead of the plan's own. The included credit is now lent only to a spawn on no plan, so the free plan has none and paid plans carry their own.
• Crew key note (shard 18): the compact note on repository and app pages still said "cannot start work yet". It now says "The crew needs a model key to start", as the home page and the test expect.
• docs/MCP.md (shard 51): I regenerated the tool table with bun scripts/mcp-table.ts to pick up the limits row.
• Page budget (shard 70): /admin/limits ran 61 SQL statements against a budget of 60. The worst-case daily credit line re-read three limits. It now takes them from the rows the page already loaded, through a new worstCaseOf in src/spawn/included_credit.ts.

I ran the affected test files, tsc and scripts/gate.ts, and they pass. I also ran test/traffic-truth.test.ts, test/perf-server-hook.test.ts and the files that hold the shard-52 tests. I did not run the full suite, so the forge's check on this push is the real test for those shards.

Continues #11165

This push fixes four of the failing groups. I did not trace shards 52 (shared routes) and 71 (traffic record) to a cause, and no test in them failed when I ran their files.

• Plan credit (shard 20): a spawn on a plan was also getting the new included credit of $2, on top of or instead of the plan's own. The included credit is now lent only to a spawn on no plan, so the free plan has none and paid plans carry their own.
• Crew key note (shard 18): the compact note on repository and app pages still said "cannot start work yet". It now says "The crew needs a model key to start", as the home page and the test expect.
• docs/MCP.md (shard 51): I regenerated the tool table with bun scripts/mcp-table.ts to pick up the limits row.
• Page budget (shard 70): /admin/limits ran 61 SQL statements against a budget of 60. The worst-case daily credit line re-read three limits. It now takes them from the rows the page already loaded, through a new worstCaseOf in src/spawn/included_credit.ts.

I ran the affected test files, tsc and scripts/gate.ts, and they pass. I also ran test/traffic-truth.test.ts, test/perf-server-hook.test.ts and the files that hold the shard-52 tests. I did not run the full suite, so the forge's check on this push is the real test for those shards.

Five of the six changes are in and pushed. For the sixth (the direction point), I can't justify the ordering, and the reason is in item 5 below.

1. Both doors: there is now a "Crew key" screen in the terminal (src/tui/screens/crewkey.ts, entry in entries.ts). It shows what the crew runs on, and a takes the key typed masked. It is admin-only like the page. docs/features/starter-crew.md says so.
2. Tests:

- test/crew-key.test.ts covers the route: a signed-out caller is sent to sign in, a non-admin gets 404, a cross-origin POST gets 403, a bad key flashes the error, and a good key is saved and never echoed. It also covers the terminal screen. - test/starter-crew.test.ts now covers the grant to the owner and the spawned org, the forge-code repo being skipped, a person's autonomy choice being kept, and a forge with its own crew keeping it.

1. Dead code: crewKeyNote and its imports are deleted. The home page calls crewKeyCard directly.
2. One explanation, not five: the field now appears only on the home page. A new app, an app page and Subscriptions say it in one line and link to /#crew-key-note. The claim page already had only a sentence. The hint under the field is removed.
3. Direction: I can't give a reason this goes ahead of #6534, #6611 and #5276. It is a feature the issue asked for, and I don't have the planning context to justify the order. A person should decide whether it lands now.
4. Validation: the new saveCrewKey in src/actions/crew_key.ts does the checks for both doors. A key must be at most 512 bytes and one line of printable text, with no control characters. The form body is capped at 2 KB and the input has maxlength.

I added the "Crew key" entry to the roster expectation in test/palette-roster.test.ts. I did not run the full suite. bun scripts/gate.ts and bun x tsc --noEmit pass. The tests I ran are crew-key, starter-crew, spawn-child-apps, mcp-table, pages-budget, plans, palette-roster and the tui-subscriptions, child-credit and spawn tests. The forge's check runs the full suite on this push.