Completion you can run

Launch state should be measurable, not vibes.

The readiness command checks the repo, workflows, public site, generated visual packet, and free/local-first copy. It writes JSON and Markdown reports without API calls, Railway, databases, or paid services.

Checked surfaces

The command checks the parts users actually touch.

It is intentionally boring: no network, no SaaS dependency, just concrete files and copy that should exist before launch.

Governance

License, security policy, contribution guide, code of conduct, changelog, issue templates, and PR template.

Automation

CI, CodeQL, container, Pages, package workflow, and GitHub Action metadata.

Runtime

App entrypoints, scripts, Docker, Compose, and package metadata.

Public site

Home, FAQ, challenge, reports, integrations, launch room, media kit, releases, sitemap, robots, and llms.txt.

Visual packet

Generated proof dossier, offline proof PDF, UI mockup, share page, report JSON, SARIF, JUnit, telemetry, eval kit, and HF manifest.

Free path copy

Confirms the public surfaces state the no-key local path and do not imply a required hosted backend.