MBT v1 — Launch Readiness Checklist

Owner: Kristerpher Henderson Last updated: 2026-05-03 Anchor epic: #256 Deliverable card: #265

Pre-flight — what must be green before sign-off

Section 1 — End-to-end user flow walkthrough

Flow 1: First-visit SetupWizard → Dashboard

1. User visits app.raxx.app for the first time → redirected to /setup-wizard
2. Header reads "Set up your account" (vendor-name-free per Confidence Engine direction)
3. Step 1: pick paper / live mode. Live-mode guard — selecting Live surfaces an inline alert "Credentials required. Live trading will not execute unless…" before the user can advance.
4. Step 2: enter API credentials (passwords masked).
5. Step 3: validate connection → "Connected — retrieved N data feed(s) and verified broker access for $SYMBOL".
6. Finish Setup → redirect to /dashboard

Flow 2: Dashboard → Historical Data → symbol lookup

1. Click "Historical Data" in nav.
2. Enter symbol, pick date range.
3. Empty state if no data: "No history yet — pick a symbol and date range to load chart" (no blank screen).
4. Loading state: spinner + "Loading historical data…" while /api/historical-data resolves.
5. Error state: typed messages for feed_unavailable, rate_limited, feed_disabled, feed_credentials_missing — each with a Retry button.
6. Chart shell renders with tabular numbers in any data tables.

Flow 3: Dashboard → Backtest → configure + run securities backtest → view results

1. Click "Backtest". Header includes the persistent paper/live badge derived from settings.tradingMode.
2. Configure: strategy + parameters + symbol + dates.
3. Click "Run Backtest" → loading state with progress.
4. Results render with metrics + equity curve + trade list.
5. Options entry point (e.g. "Add Options Leg" toggle) — if ENABLE_OPTIONS_BACKTEST=false, renders the OptionsBacktestComingSoon panel instead of the options form. No options backtest can be triggered.
6. Errors mapped via friendlyError() — no raw delayed_sip / internal feed IDs leak to UI copy.

Flow 4: Dashboard → StrategyComparison → compare two results

1. Click "Strategy Comparison".
2. Pick two saved backtests from dropdowns (or empty state with CTA back to Backtest).
3. Side-by-side comparison table renders with metric tooltips on Sharpe, Max Drawdown, Profit Factor, Win Rate.
4. Mobile (390 px viewport): table scrolls horizontally with shadow indicators.

Flow 5: Dashboard → Trading → options screening + paper options order

1. Click "Trading". Persistent paper/live badge in the header reflects settings.tradingMode.
2. Empty / loading / typed-error states cover the four broker conditions: broker-credentials-missing, broker-rate-limited, broker-feed-disabled, broker-unavailable.
3. Submit a paper options order — confirmation modal renders before the POST fires.
4. Live-mode submit (if mode=live) — already gated by the Settings live-mode confirmation modal earlier.

Flow 6: Settings → credential update + mode confirmation

1. Click "Settings".
2. Mode cards are <button> elements (not bare <div>).
3. Click "Live Trading" → confirmation modal requires typing LIVE TRADING exactly before commit.
4. Credentials section: passwords masked, last-4 visible only after explicit "Show" tap.
5. Feature-flag visibility tab: shows ENABLE_OPTIONS_BACKTEST: false with a "Coming soon" badge + tooltip explaining the data-licensing gate.

Flow 7: Any entry point to options backtesting → "coming soon" panel

• Default state: ENABLE_OPTIONS_BACKTEST=false.
• Affected entry points: Backtest's options leg toggle, any explicit /options-backtest route, the StrategyComparison "Add options strategy" affordance.
• Each renders <OptionsBacktestComingSoon /> instead of the actual options-backtest UI.
• Backend /api/backtest/options route returns 503 {"feature": "options_backtest", "enabled": false} when the flag is off (defense in depth — frontend may be cached).

Section 2 — Regression-test matrix

Smoke-test contract (frontend/trademaster_ui/src/tests/smoke.contract.test.js): - Setup wizard shell renders ✅ - Setup data-retrieval contract ✅ (regex tolerates pre/post-polish copy) - Historical data chart shell renders ✅

Backend smoke (scripts/ci/run_smoke.sh): - /api/health 200 ✅ - /api/settings 200 with feature_flags.ENABLE_OPTIONS_BACKTEST: false ✅ (after Heroku deploy) - /api/backtest/options returns 503 when flag off ✅ (after Heroku deploy)

Section 3 — Staging smoke (run before GA)

⏳ Cannot run until HEROKU_API_KEY GH Actions secret is refreshed (#925). After that:

# 1. Trigger deploy
gh workflow run deploy-heroku.yml -f environment=staging -f ref=main

# 2. Wait for deploy
gh run watch  # pick the deploy-heroku.yml run

# 3. Verify staging
curl -sS https://api-staging.raxx.app/api/health
curl -sS https://api-staging.raxx.app/api/settings | jq '.feature_flags'
# expect: { "ENABLE_OPTIONS_BACKTEST": false }

# 4. Toggle flag on staging only
heroku config:set ENABLE_OPTIONS_BACKTEST=true -a raxx-api-staging >/dev/null 2>&1
curl -sS https://api-staging.raxx.app/api/settings | jq '.feature_flags.ENABLE_OPTIONS_BACKTEST'
# expect: true

# 5. Toggle back off before customer demo
heroku config:set ENABLE_OPTIONS_BACKTEST=false -a raxx-api-staging >/dev/null 2>&1

Walk Flows 1–7 against staging at https://app-staging.raxx.app (or local CRA proxied to staging API). Capture screenshots for the launch-readiness artifact.

Section 4 — Production rollout sequence

1. ✅ All Wave 0–2 PRs merged
2. ⏳ Resync HEROKU_API_KEY GH Actions secret (operator action #925)
3. ⏳ gh workflow run deploy-heroku.yml -f environment=staging -f ref=main → soak ~30 min on staging
4. ⏳ Walk Flows 1–7 on staging — log results in this doc as a "Staging smoke 2026-05-03" subsection
5. ⏳ gh workflow run deploy-heroku.yml -f environment=production -f ref=main
6. ⏳ Verify production: curl https://api.raxx.app/api/settings | jq '.feature_flags'
7. ⏳ Attorney sign-off (#197)
8. 🚀 GA

Section 5 — Rollback plan

If the deploy is bad: - heroku rollback v<previous> -a raxx-api-prod (Heroku release rollback is instant) - Revert the offending PR via gh pr revert <num> and force-deploy - Antlers: CF Pages preserves prior builds — toggle via CF dashboard if needed (no Antlers-side rollback strategy is automated yet — file as follow-up)

If ENABLE_OPTIONS_BACKTEST was flipped on by mistake: - heroku config:set ENABLE_OPTIONS_BACKTEST=false -a raxx-api-prod >/dev/null 2>&1 (instant; takes effect on next request) - Frontend cached settings refresh on next page load — communicate via Slack DM if customers active

Refs

• Epic: #256
• Wave 0 (gate): #257 → PR #929
• Wave 1: #264 → PR #922, #262 → PR #923, #263 → PR #924
• Wave 2: #258 → PR #926, #259 → PR #927, #260 → PR #928, #261 → PR #930
• Wave 3: #265 (this doc), #266 getraxx copy (in flight)
• Blocker: #925 GITHUB_API_SECRETS_TOKEN for autonomous secret rotation
• Final gate: #197 attorney sign-off