Doctor link v0.6.0

v0.6.0 Release Notes

Doctor Link v0.6.0 upgrades failure explanation from advisory file hints to an evidence-bounded diagnosis and repair workflow for Python and Node.js JavaScript/TypeScript projects.

Highlights

• Structured pytest and JavaScript failure parsing with expected/actual values and project-owned stack frames.
• Exact file, line, function, and source excerpts with explicit evidence scoring.
• Test-to-production call chains that filter virtual environments, dependencies, generated files, and synthetic frames.
• Opt-in explain --verify-hypothesis counterfactual checks with exact byte and worktree restoration.
• Evidence-bounded repair guidance that separates observed facts, inferences, and verified evidence.
• Opt-in solve --require-grounded-root-cause admission control before automatic editing.
• Focused verification followed by the complete regression contract, with separate receipts for both layers.
• Required checks must have explicit passing results; missing results can no longer be accepted vacuously.

Validation

• 409 automated tests passed locally with 85.30% branch-aware coverage before release versioning.
• Ruff and Bandit medium/high gates passed.
• Click 8.3.0, p-limit 7.2.0, and Chalk 5.6.2 passed native-baseline, reversible fault, exact location, hypothesis confirmation, repair-guidance, and restoration checks (3/3).
• Eight adversarial cases passed, including multi-file call paths, conflicting evidence, dependency-only errors, focused-pass/full-regression-fail, protected-input tampering, worktree pollution, and exact counterfactual restoration.
• A fresh Python 3.12 environment installed the pre-version-bump wheel from local artifacts, imported from site-packages, confirmed and restored a changed-file hypothesis, generated actionable guidance, and blocked a dependency-only repair.
• The final v0.6.0 release workflow must repeat Python 3.10–3.14, Linux/macOS/Windows, security, dependency audit, build, Twine, installed-wheel, and full-capability gates from the merged release commit.

Safety boundary

Root-cause hints remain advisory unless a counterfactual experiment confirms them. A confirmed file-level hypothesis does not prove that an arbitrary line-level patch is correct. Automatic repair still requires explicit authorization, operates on an isolated branch, protects tests and verification configuration, limits repair rounds, and never auto-commits, pushes, or publishes project changes.

Doctor Link remains a local-first CLI. This release does not add a hosted platform, cloud synchronization, external account system, telemetry, marketplace, hosted knowledge base, or managed RBAC.