docs(plans): §10.7 sizes piece 6 — ordered pieces, gates mapped to Vera's four constraints, the question for Sam (HOLD)

[lilyshen0722]

Summary

Sam 68231: §10 (per-person Connections, piece 6, merged as #1676) was "not scheduled, not sized" by its own status line, and nothing in it is built until it is. This PR is the sizing. HOLD for Sam's read before merge, like §10 itself.

Adds §10.7 to docs/plans/tools-catalogue-room-grants.md:

• Seven ordered pieces with a day estimate each — 6a removal cascade on the row the slice has (1 d), 6b the record/mint/broker learn github-user (2 d), 6c pasted-token intake (2 d), 6d removal finishes (1 d), 6e OAuth through the App's user authorization (2 d + Sam's two App actions), 6f the refresh fence (2 d), 6g the page (2–3 d, UX Lead gates). Gmail (6h) stays unsized, after GitHub. Total 12–14 d, one builder.
• The gate for each, naming the tests the head must carry, and Vera's four constraints (67647) mapped to the piece that satisfies each — also collected in one table.
• The one question a build needs Sam to answer first: does a member's first Connection come from the paste path, or does nothing reach a member until OAuth (6e) exists? The table assumes the second (page waits for OAuth, so the fallback is never the only control a person sees); the first moves 6g ahead of 6e.

Also: the §10 status line now reads "sized in 10.7, still HOLD", and §1 row 6 carries the size. No other section changes. Docs only.

Test plan

• Docs-only; no code or tests change.
• Vera gates the head (Wren gates Vera's).
• Sam reads before merge (HOLD).

🤖 Generated with Claude Code