Ship OAuth MCP server, full regression

/goal Execute specs/03-ship.md (read it and BRIEF.md first). Write README.md and SECURITY.md per the spec, then run the full macro regression and attempt deploy. Final turn must contain ALL of: (a) npx tsc --noEmit output with exit code 0 stated; (b) npm test full output with exit 0; (c) against a running wrangler dev, quoted curl -sS output of GET /.well-known/oauth-authorization-server AND GET /.well-known/oauth-protected-resource, both returning JSON; (d) quoted curl -i POST /mcp with no Authorization header showing HTTP 401 and a WWW-Authenticate header; (e) quoted curl -i POST /token with Content-Type: application/x-www-form-urlencoded and a bogus grant showing an HTTP 4xx OAuth JSON error body (not 415, not 500); (f) ls README.md SECURITY.md output plus the quoted markdown headings of both files; (g) quoted grep output showing README.md contains the literal strings GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET, ALLOWED_HOSTED_DOMAIN, /callback, and all three Google OAuth scope URLs from BRIEF.md; (h) EITHER wrangler deploy output plus quoted curl of the deployed /.well-known/oauth-authorization-server returning JSON, OR the literal line "DEPLOY BLOCKED: <reason>" followed by the exact commands for me to run; (i) the literal heading "HUMAN ACCEPTANCE CHECKLIST" followed by the human-only steps from specs/03-ship.md verbatim. Stop after 10 turns and output a status report if not complete