OpenAITPM Deployment Runbook

The repo now has the local pieces for GitHub branch builds, automatic pull requests, and stable dynamic idea routes. Vercel and DNS are the external account steps.

Branch to PR Flow

First run npm run launch:bootstrap -- --push <repo-url>.Then run npm run idea:ship -- --push "My Idea Name".The helper creates an idea/<idea-name> branch and commits the page JSON.Push the branch to GitHub.GitHub Actions opens or updates a pull request into main.The workflow runs npm run verify so the PR records build status.

Vercel and Domain

Create a Vercel project from the GitHub repository.Enable pull request previews and keep main as the production branch.Add VERCEL_TOKEN, VERCEL_PROJECT_ID, and VERCEL_ORG_ID as GitHub secrets.Add openAITpm.com and www.openAITpm.com in Vercel.Point DNS at the exact Vercel records shown in the domain screen.Merge the PR so production serves openAITpm.com/<idea-name>.Run npm run smoke:production or the Production Smoke workflow.

Launch Readiness Audit

Run this any time to see whether the repo is ready for the real openAITpm.com publishing loop.

npm run launch:audit

Current State

Local commitpass Idea content filespass Idea ship helperpass Idea route verifierpass Dynamic routepass Auto-PR workflowpass Launch bootstrap helperpass Sitemap and robotspass Production smoke checkerpass Vercel configpass GitHub origin remotemissing

Owner Access Still Required

I can put the repo-side machinery in place here. Creating the GitHub remote, connecting Vercel, and changing registrar DNS require account access from the owner of those systems.