Mushi Health Check

Degree of freedom: MIXED. First-red diagnosis [HIGH freedom]; Steps 1–6 in order [LOW freedom — run exactly].

How to reason

1. Observe — doctor, deploy check, keys, logs, cron — in that order
2. Interpret — first red is root vs downstream symptom
3. Classify — creds / functions-down / keys / logs / cron-missing
4. Severity — paused project or invalid API key outranks a quiet QA cron on a new project

Worked example

Observe: mushi doctor green; mushi deploy check ✗ qa-story-runner; qa_story_runs empty for 2h. Interpret: first red is the runner; empty cron is downstream. Classify: function-down — check get_logs for qa-story-runner; do not add keys yet. Verify: stop at Step 2; fix the runner; continue remaining steps only after it is green.