harness-doctor

# Harness doctor — is the harness healthy? Confirm the harness is wired correctly, in plain language, with a concrete fix per finding. ## When this fires "is my harness set up right / healthy?" / "harness doctor" / after an install or a `--self-update`. ## Identify the target Use the agent named by the operator or the explicit `AGENTSMITH_AGENT` value. Never infer the active agent from this skill's install path: portable canonical content may be copied into a required client adapter such as `.claude/skills`. Without an explicit agent, run the common project checks and label agent-specific capabilities as unknown. ## Fast path — if the Agentsmith CLI is available Run `agentsmith doctor`, adding `--agent <id[,id...]>` when the target is known. If the command is not on PATH, use `.agentsmith/agentsmith` on macOS/Linux or `.agentsmith\\agentsmith.cmd` on Windows. Report instructions, actual safety, skills, MCP/config, hooks/scanner, and runtime helpers separately. For instructions, report the effective global/project/nested chain, fingerprints, managed `core` metadata, and combined/duplicate token estimates. An unsupported optional capability does not make instruction discovery unhealthy, and a duplicate core is a warning rather than permission to rewrite it. ## Fallback — self-contained project checks Check each; report pass, or a one-line fix: - **Rules:** canonical `AGENTS.md` is present and contains the AgentSmith BEGIN/END managed block. When a target requires a gener...