harness-doctorlisted

# harness-doctor — Harness Structure Diagnosis + Prescription "A good harness gets simpler over time. If it's getting more complex, something is wrong." Diagnoses harness structural health across 3 layers and proposes M/S/R prescriptions: 1. **L1 Structural completeness** — required file existence (CLAUDE.md · .claudeignore · .claude/) 2. **L2 Complexity** — current state vs. simplification principle (line count · unused files · duplicate definitions) 3. **L3 Drift** — rule vs. actual pattern mismatch (broken references · stale files · conflicting rules) 4. **L4 Connection diagnosis** *(FH environment only)* — meta hub ↔ field project reference consistency 5. **L5 Pattern analysis** *(FH environment only)* — skill activity · call context appropriateness · effect metric measurement --- ## Execution Steps ### Step 1. Confirm Diagnostic Target ```bash # Check current cwd harness file structure ls -la .claude/ 2>/dev/null || echo "NO .claude DIR" ls -la CLAUDE.md .claudeignore 2>/dev/null ls .claude/rules/ 2>/dev/null ls .claude/agents/ 2>/dev/null ``` Determine if FH environment: ```bash # tracks/ present = FH or hub environment ls -d tracks/ knowledge/ plugins/ 2>/dev/null ``` --- ### Step 2. L1 — Structural Completeness Diagnosis Check required file existence: | File | When Missing | |---|---| | `CLAUDE.md` | **M-tier** — harness entry impossible | | `.claudeignore` | S-tier — context-doctor execution recommended | | `.claude/` directory | M-tier (when rule files e