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 — every check prefixed `OK` (the CLI prints `OK` / `WARN` / `FAIL` text markers, not checkmarks): ``` OK CLI config file OK API key configured OK Project ID configured OK Endpoint reachable ``` Exit codes: `0` all pass · `2` advisory warnings only · `1` any hard failure. Each `FAIL` line is followed by a `→ Fix:` hint; `mushi doctor --json` includes the same hints in a `hint` field. **Fix if FAIL:** follow the printed `→ Fix:` hint, or 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 mus