health-ecosystem-auditlisted

<!-- prettier-ignore-start --> **Document Version:** 1.0 **Last Updated:** 2026-03-10 **Status:** ACTIVE <!-- prettier-ignore-end --> # Health Ecosystem Audit Deep diagnostic of the health monitoring system — `scripts/health/` checkers, scoring pipeline, data persistence, consumer integration, test coverage, and mid-session alert system. Produces per-category scores, a composite health grade (A-F), trend tracking, live test execution, and an interactive walkthrough with patch suggestions. **Invocation:** `/health-ecosystem-audit` ## Critical Rules (MUST follow) 1. **CHECK for saved progress first** (MUST) — resume from `.claude/tmp/health-audit-progress.json` if it exists and is < 2 hours old. 2. **ALWAYS run the script first** (MUST) — never generate findings without data. 3. **ALWAYS display the dashboard** (MUST) — show to user before walkthrough. 4. **Use conversational Q&A for decisions** (MUST) — NEVER use AskUserQuestion. 5. **SAVE progress after every decision** (MUST) — write updated state immediately. 6. **Show patch suggestions inline** (SHOULD) — with each patchable finding. 7. **Create TDMS entries** (MUST) — for deferred findings via `/add-debt`. 8. **Save decisions** (MUST) — to session log for audit trail. --- ## When to Use - User explicitly invokes `/health-ecosystem-audit` - After modifying `scripts/health/` checkers, lib, or scoring - After changes to `data/ecosystem-v2/` JSONL schemas - After health check test failures are observed - Afte