菜单
Use when deploying HEATER App B, changing Railway or Vercel env vars/service config, diagnosing live 502s/timeouts/blank data after deploy, operating the Yahoo-token or Statcast relays, or driving Railway/Vercel headlessly from a terminal.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | heater-appb-deploy-ops |
| description | Use when deploying HEATER App B, changing Railway or Vercel env vars/service config, diagnosing live 502s/timeouts/blank data after deploy, operating the Yahoo-token or Statcast relays, or driving Railway/Vercel headlessly from a terminal. |
| Service | What | Config |
|---|---|---|
Railway celebrated-respect (App B) | FastAPI API — THE product backend | service setting railwayConfigFile=railway.api.toml → builds api/Dockerfile, runs sh start-api.sh; healthcheck /healthz; 1 replica (hard invariant: in-process SQLite writer) |
Railway heaterv100-production (App A) | Streamlit fallback | root Dockerfile/railway.toml — leave alone |
Vercel heater-v1-0-1 | Next.js frontend | proxies /api/* server-side → App B |
Deploy = push to master — Railway auto-deploys App B. Each deploy re-runs bootstrap: ~10 min until projections/pool are warm; judge "did the fix work" only after re-bootstrap (the Marcel fix looked dead until the re-bootstrap regenerated projections). Vercel deploys are a separate owner/CLI step.
start-api.sh: first-boot Yahoo token seed → background scheduler loop (HEATER_SCHEDULER_BOOT=1, HEATER_SCHEDULER_IS_OWNER=1, sole DB writer) → exec python -m uvicorn api.main:create_app --factory --port $PORT.
CLERK_ISSUER, CLERK_AUDIENCE (setting ISSUER flips the login gate live).STRIPE_SECRET_KEY, STRIPE_WEBHOOK_SECRET, STRIPE_PRO_PRICE_ID — intentionally UNSET on the beta (free friends). Setting them activates the 402 paywall.HEATER_API_WRITE_TOKEN, HEATER_ADMIN_CLERK_IDS.HEATER_TOKEN_RELAY_URL + HEATER_RELAY_KEY (Yahoo token pull — Yahoo blocks refresh from Railway IPs, so the owner's PC refreshes and gists it, Task \HEATER Yahoo Relay every 30 min; to switch Yahoo apps: local oob re-auth → run scripts/yahoo_token_relay.py once → App B pulls within ~8 min, NO redeploy); HEATER_STATCAST_RELAY_URL (Savant xwOBA, Task \HEATER Statcast Relay daily — disable before monetization, scraped data is commercial-use-prohibited).HEATER_AI_ADMIN_KEY_<PROVIDER> ×6 (anthropic/openai/gemini/deepseek/xai/openrouter). Key VALUES live only in Railway, gitignored .env, and C:\Users\conno\.heater_ai_keys — never in git or docs.HEATER_API_DB_PATH (api_state.db), HEATER_DB_PATH, DATABASE_URL (unset = SQLite; Postgres wiring is owner-gated B2.2 — get_connection() raises NotImplementedError on non-SQLite by design).HEATER_API_BASE (App B URL — server-side only), NEXT_PUBLIC_HEATER_LIVE=1, NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY (derivable: pk_<env>_ + base64(<frontend-api-host>$)). HEATER_API_CORS_ORIGINS NOT needed — the proxy makes calls same-origin.Railway/Vercel CLIs reject the available tokens — drive the APIs directly: Railway GraphQL backboard.railway.app/graphql/v2 with Authorization: Bearer $(cat /c/Users/conno/.railway_token) plus a browser User-Agent (Cloudflare); helper scripts C:\Users\conno\railway_gql.py / vercel_api.py (tokens are ephemeral; IDs are in the token file's notes). me may be unauthorized — query projects.
2026-06-22: App B returned 502. Fix 1: Railway serviceDomain targetPort 8000→8080 mismatch. Then it "worked" but served the WRONG APP — the service was building the root Streamlit Dockerfile; only adding railway.api.toml + the railwayConfigFile service setting made it run FastAPI. Rule: after any service-config change, verify /healthz AND one real endpoint's shape, not just HTTP 200.
Owner-gated flips (Stripe live, Clerk prod/custom domain, Postgres provisioning, leaguemate team assignment — the LAST launch step): surface to owner, don't execute. Code-level debugging → heater-appb-debugging.
Use when starting any task on HEATER's live product — the api/ FastAPI backend (Railway service "celebrated-respect") or web/ Next.js frontend (heater-v1-0-1.vercel.app) — or when unsure where code lives, how a request flows, which database owns what, why CORS/Yahoo-writes/billing seem "missing", or which app (Streamlit vs React) is the real one. Load this first on App B work.
Use when working on HEATER App B auth or billing — Clerk JWT verification, unexpected 401/402, HEATER_API_WRITE_TOKEN, Stripe checkout/webhooks/subscription tiers, require_pro gating, tier-based AI spend caps — or when auth "works locally but not live" (or vice versa), or a page bounces to /sign-in on hard load.
Use when working on Bubba, HEATER's AI assistant — /api/chat/* endpoints, provider streaming (src/ai/providers.py), token metering and spend caps, AI provider keys, attachments/page-context, saved prompts, or the chat composer in web/src/components/bubba/.
Use when proving a HEATER algorithm works — calibrating constants, backtesting projections or recommendations, validating win probabilities, adding uncertainty intervals, checking calibration drift — or before letting any new math drive user-facing recommendations. Also when asked "is this signal real?" or when a calibration run finds no clear winner.
Use when editing api/contracts/*, when api/openapi.json or web/src/lib/api/generated.ts drift (test_openapi_contract or the CI openapi-ts-sync job failing), when JSON responses 500 or render "nan"/"+nan" badges, or when adding/renaming fields on a response the live frontend already consumes.
Use when App B misbehaves and the cause isn't obvious — works locally but not on Railway/Vercel (or vice versa), a live page renders empty/zero/wrong data, an endpoint 500s or times out, or tests see different data than the app. Run this playbook before changing code.