harness-doctor

# 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 5 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 metrics --- ## Execution Steps ### Step 1. Confirm Diagnostic Target Check current cwd harness file structure and determine if FH environment (tracks/ + knowledge/ + plugins/ all present). ### Step 2. L1 — Structural Completeness | File | When Missing | |---|---| | `CLAUDE.md` | **M-tier** — harness entry impossible | | `.claudeignore` | S-tier — context-doctor execution recommended | | `.claude/` directory | M-tier (when rule files exist) | ### Step 2-E. L1-E — ETCLOVG Layer Coverage *(functional-layer lens — orthogonal to the file-presence table above)* A harness is not only files; it is **seven functional layers** (ETCLOVG — arXiv:2606.06324, a component taxonomy *orthogonal* to FH's 6-axis process model...