[codex] correct auth user API example

[charlesrhoward]

Summary

Follow-up to PR #40 review feedback.

• restore the /api/auth/user example response to the current API shape: platform_access.allowPlatformAi, platform_access.allowPlatformSandbox, and vercel.personalState
• keep the managed-billing framing by noting that the current API names are the route's managed account-access flags

Why

PR #40 intentionally reframed the docs around managed billing, but the working-requests example renamed response fields ahead of the app contract. The app currently returns platform_access, so the docs example should match live behavior.

Validation

• git diff --check
• pnpm lint
• pnpm types:check
• pnpm build
• pre-push hook reran pnpm lint, pnpm types:check, and pnpm build

---

^{Need help on this PR? Tag @codesmith with what you need.}

• Let Codesmith autofix CI failures and bot reviews

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
mogplex-docs	Ready	Preview, Comment	May 18, 2026 7:28pm

[mogplex]

Mogplex PR Review

Status: Attention needed

This is a clean, well-scoped documentation fix that correctly restores the /api/auth/user response example to match the live API shape (platform_access, allowPlatformAi, allowPlatformSandbox, and vercel.personalState). No code, logic, or security concerns. One minor prose clarity issue worth addressing before merging.

1 finding was added inline.

View check run

[mogplex]

Suggestion: Prose note could imply upcoming deprecation

The sentence "Current API field names still use platform_access and allowPlatform*." uses "still use" in a way that implies a future rename is planned or in progress. A reader scanning the docs may reasonably conclude these field names are transitional and will change soon, and may write defensive code against that assumption.

If no rename is planned, consider replacing the note with something unambiguous, e.g.:

The managed account-access flags are exposed under platform_access with allowPlatformAi and allowPlatformSandbox sub-fields.

If a rename is planned, a brief note like "(these names will change in a future release)" would make the intent explicit.