mushi-healthlisted

# Mushi Health Check Run these checks in order. Stop and fix at the first ❌ before continuing. ## Component map | # | Component | How to check | |---|-----------|-------------| | 1 | CLI credentials | `mushi doctor` | | 2 | API + edge functions | `mushi deploy check` | | 3 | Project overview | `mushi status` | | 4 | BYOK key pool | `mushi keys list` or MCP `list_byok_keys` | | 5 | Supabase logs | Supabase MCP `get_logs` | | 6 | QA cron running | DB query on `qa_story_runs` | --- ## Step 1 — CLI credentials ```bash mushi doctor ``` Expected output — all lines green: ``` ✓ ~/.mushirc found ✓ MUSHI_API_KEY valid (mushi_...) ✓ MUSHI_API_ENDPOINT reachable (200 OK) ✓ MUSHI_PROJECT_ID matches a live project ✓ Feature flags fetched ``` **Fix if red:** Re-run `mushi login --api-key mushi_... --endpoint https://<ref>.supabase.co/functions/v1/api --project-id <pid>`. --- ## Step 2 — API + edge functions ```bash mushi deploy check ``` Probes each edge function with a lightweight ping. Healthy output: ``` ✓ api ✓ classify-report ✓ fix-worker ✓ story-mapper ✓ test-gen-from-story ✓ pdca-runner ✓ qa-story-runner ``` A `✗` on any line means that function is down. Check its logs in Step 5. --- ## Step 3 — Project overview ```bash mushi status ``` Confirm: - Report count is non-zero (or expected zero for a brand-new project). - `autofix_agent` shows the expected agent (`cursor_cloud`, `mcp`, etc.). - No `billing: quota_exceeded` warning. --- ## Step 4 — BYOK ke