canvas-health

# Canvas Health Check Audit the canvas knowledge base for quality, consistency, and completeness. The canvas is Mycelium's source of truth -- its quality directly determines agent output quality (Raschka: "context quality = model quality"). ## When to Use - Before any diamond phase transition (called automatically by `/mycelium:diamond-assess`) - After a period of inactivity (>7 days since last canvas update) - When agent output quality seems to degrade - After onboarding a new team member (ensures canvas is self-explanatory) - Proactively: run periodically to catch silent drift ## Workflow 1. **Load project configuration**: - Read `.claude/diamonds/active.yml` for `product_type` and `project_type` - Read `${CLAUDE_PLUGIN_ROOT}/engine/canvas-guidance.yml` for required/recommended/optional files per project type 2. **Check file presence**: - For each **required** canvas file: does it exist? Is it non-empty (>50 bytes)? - For each **recommended** canvas file: does it exist? Flag as gap if missing. - Report: `N/M required files present, K recommended files missing` 3. **Check `_meta` blocks**: - For each existing canvas file, check for `_meta:` block - Flag missing `_meta` blocks - Flag `last_validated` past **the horizon for that file's category**, per the "Which threshold applies to which canvas file" table in `${CLAUDE_PLUGIN_ROOT}/engine/evidence-decay.md` (strategic 180d, technical feasibility 120d, user-needs/competitive/market...