mushi-debuglisted

# Mushi Debug Guide ## SDK Not Reporting Events **Symptoms**: Inventory → Discovery shows 0 events. 1. Check the SDK is initialized before any navigation: ```ts Mushi.init({ projectId: '...', apiKey: '...', capture: { discoverInventory: { enabled: true } } }) ``` 2. Verify the API key starts with `mushi_` and belongs to the correct project. 3. Check browser console for `[Mushi]` errors. 4. Run `mushi doctor` — confirms reachability. ## API Key Exhausted / Rate Limited **Symptoms**: "ALL_KEYS_EXHAUSTED" error, quota banner in Settings. ```bash # Check key health mushi keys list # Add a backup key mushi keys add --provider anthropic --key sk-ant-... --label "Backup" ``` In the console: **Settings → API Key Pool** → keys in `quota_exhausted` state show cooldown timer (resets in 1 hour automatically). ## Story Mapping Failed **Symptoms**: `mushi stories map` returns error or crawl run shows `failed`. 1. Confirm Firecrawl key is configured: ```bash mushi keys list # Should show firecrawl [active] ``` 2. Verify the URL is publicly reachable (not localhost). 3. Check the console: **Inventory → Discovery → Recent crawls** for the error message. 4. Try with fewer pages: `mushi stories map --url <url> --max-pages 5 --wait` ## QA Story Failing Hourly **Symptoms**: Slack message every hour — `:warning: QA story <name> errored` — or `Firecrawl 401`. Most common root causes and fixes: | Error | Cause | Fix | |-------|-------|-----| | `Firecrawl 401 Unaut