mushi-integrationlisted

# Mushi Integration Smoke Test Exercises every stage of the Mushi pipeline end-to-end. Run after setup, after a deploy, or any time you need proof that the whole loop works. ## Prerequisites - `mushi doctor` passes (all green) — run [`mushi-health`](../mushi-health/SKILL.md) first if unsure. - At least one BYOK key for `anthropic` and `firecrawl` is active. - You have the app URL you want to map stories from. --- ## Stage 1 — Bug capture Send a real test report through the SDK pipeline: ```bash mushi test ``` Expected: `Test report submitted — id: rep_...` **Verify in DB** (Supabase MCP): ```sql SELECT id, status, severity, category, created_at FROM reports ORDER BY created_at DESC LIMIT 1; ``` Expected: a row with `status` = `classified` and a non-null `severity` within ~30 seconds. If still `pending` after 60 s: `classify-report` edge function failed — check `get_logs(service: 'api')`. --- ## Stage 2 — AI triage Confirm the classifier ran: ```bash mushi reports list --limit 1 ``` Expected output includes `severity`, `category`, and `blast_radius`. **Verify via MCP:** ``` get_report_detail(reportId) ``` Confirm `classification.severity` and `classification.category` are set. --- ## Stage 3 — Story mapping Map user stories from a live URL: ```bash mushi stories map --url https://your-app.com --wait ``` `--wait` polls until the crawl finishes (usually 30–90 s). Expected terminal output: ``` ✓ Crawled 12 pages ✓ Claude drafted 8 user stories ✓ Prop