~15 minutes · Unblocks signup → deploy → trades and CBO growth. Site + billing are already live.
Checking gates…
DATABASE_URL on Railway paper-worker and redeploy.
Pooler: aws-0-ap-northeast-1.pooler.supabase.com · session mode · port 5432.
Copy URI from Supabase
[brackets]) → Railway → Deploy.
Or add Cloud Agent secret DATABASE_PASSWORD. Full guide
./scripts/verify-activation-path.sh --partial ·
./scripts/guide-partial-e2e.sh ·
GSC ·
Pro checkout ·
./scripts/guide-founder-parallel.sh ·
./scripts/guide-worker-recovery.sh ·
Guide index
Enables funnel v2 events (signup_complete, deploy_success, checkout_click) in /admin.
One-shot (recommended): add DATABASE_PASSWORD (password only) or DATABASE_URL + RAILWAY_API_TOKEN to GitHub Secrets → Run “Apply P0” → type APPLY (validates credentials, migration + worker + post-P0).
Cloud Agent: add secret DATABASE_PASSWORD (after Supabase reset) or full DATABASE_URL → agent runs ./scripts/run-p0-if-ready.sh on main.
Railway: set DATABASE_URL on paper-worker: agent auto-resolves from Railway.
URI: Supabase → Database → Connection string (session pooler, port 5432).
Checking…
Without this, deploys save but no trades run on live Binance prices. Railway service: paper-worker (root saas/worker). RAILWAY_API_TOKEN is already configured for the agent.
Checking…
Run E2E: signup → deploy → trades within ~15 min. Agent/CI runs post-p0-success.sh (activation verify + security smoke). Then QA&VAPT · first Pro MRR.
Locked until P0 green
Track progress: GitHub issue #4 ·
CLI: ./scripts/check-p0-readiness.sh · ./scripts/guide-cto-founder-standup.sh · ./scripts/guide-worker-recovery.sh · ./scripts/status-report.sh · Auto-refresh 30s