Run the real-alpha program: 3–5 sessions, feedback log, targeted fixes

[spaceshipmike]

Per docs/public-readiness-plan.md this is the single remaining Pending item before launch sequencing starts. The instruments already exist (tester packet, checklists, feedback logs) — what's missing is the sessions.

• Recruit 3–5 testers from the same direct-outreach list the launch plan builds at Day -11 (alpha testers become launch-day voices)
• Cover: first-run onboarding (at least one code repo AND one non-code workspace) and Settings > MCP client controls, per docs/alpha-mcp-client-controls-tester-packet.md
• One entry per session appended to docs/alpha-feedback-log.md / docs/alpha-mcp-client-controls-feedback-log.md
• Make only targeted copy/UX refinements where testers actually got stuck (readiness plan's explicit rule — no speculative polish)
• Use findings to order the deferred UX items (health-tier explanations, staleness indicators, etc.)

Suggested gate: alpha complete + sharpest edges fixed → start the Day -21 launch clock in marketing/launch-plan.md.