Launch-readiness CLI

Running the check

pnpm tokenone:check

Or directly:

pnpm exec tsx scripts/launch-check.ts

What it checks

• Database · connection + 5 critical tables (builder_projects, project_memberships, project_connector_credentials, platform_settings, audit_logs)
• Redis · raw TCP PING on the configured port (no ioredis dep required)
• Security · CONNECTOR_VAULT_KEY set (fails · prod unsafe without it)
• Routing · at least one upstream key set (fails otherwise · all proxies return 503)
• Email · SENDGRID_API_KEY (warns if missing · invite emails disabled)
• Connectors · GITHUB_CLIENT_ID + _SECRET(warns if missing · no git connector available)

Output

Colour-coded table per category. Summary line: X pass · Y warn · Z fail. Exit code 0 on pass, 1 on any fail. Wire into pipeline.yml deploy step to gate prod rollouts.

Precedence

Checks use the same resolution order as runtime-config: PlatformSetting value first, env var second. So a key set via the admin UI (db source) satisfies the check just like an env var would (env source).