feat(doctor): surface solution-acceptance deadlock checks (parity with validate)

[LanNguyenSi]

What

harness doctor now surfaces the same two solution-acceptance deadlock misconfigurations that harness validate already flags, in its Policy Packs section:

• condition docs: initial README + docs/VISION.md #1 (grounding-mcp absent from tools.mcp) as an error
• condition docs: ARCHITECTURE.md — YAML manifest schema + CLI surface #2 (relative SOLUTION_VERDICT_DIR in grounding-mcp env) as a warning

Why

solution-acceptance is a pure consumer of the verdict marker the grounding-mcp producer writes. If grounding-mcp is not wired, no verdict can ever be written and every completion verb deadlocks on a permanent deny that looks protective. harness validate already caught this, but harness doctor was blind to it, so an operator who enabled the pack and forgot grounding-mcp got a silent deadlock with no doctor signal pointing at the root cause.

How

• src/cli/validate/checks.ts: export checkSolutionAcceptanceProducer (was module-local). Export-only, no logic change.
• src/cli/doctor/{types,index,format}.ts: add a solutionAcceptance: Diagnostic[] field to the Policy Packs section, populate it from the exported check in buildPolicyPacks, tally it truthfully in countDiagnostics (error to errorCount, warning to warningCount), and render it (✗ / ⚠) consistent with the section's existing style. The check is the single source of truth; no logic is duplicated and harness validate is unchanged.
• docs/policy-packs/solution-acceptance.md: correct the stale text that still described condition docs: initial README + docs/VISION.md #1 as warning-tier and claimed harness does not project the tools.mcp env into the hook (that is now done at apply time by buildExpectedFiles). The docs now match the code: condition docs: initial README + docs/VISION.md #1 is an error in both validate and doctor, condition docs: ARCHITECTURE.md — YAML manifest schema + CLI surface #2 a warning, an absolute override is handled silently.

Tests / verification

• New doctor tests cover error / warning / silent paths. The warning-path test asserts a +1 warningCount delta against an absolute-dir baseline (a bare >= 1 was inert because the minimal fixture independently emits a memory-router warning). Mutation-verified: no-op'ing the warning tally turns the test red. All five new doctor() calls pass homeOverride so the memory and rogue-ledger probes never read the operator's real ~/.harness.
• Also tightened two pre-existing versionProbe test annotations to readonly string[] (the probe param is readonly; CI tsc excludes tests so the LSP-only mismatch was latent).
• tsc clean; full vitest 2473 passed / 1 skipped; integration 1 passed; ug-schema-drift OK.

Review

Independent reviewer subagent (with a real mutation pass): APPROVE, no high or critical findings. The medium finding (warning-tally not mutation-killed) and the low finding (non-hermetic home) are both addressed in this branch.

Refs: discovery-2026-06-24/harness-doctor-solution-acceptance (08ccfe87)