Repository navigation
feat: add initial linter diagnostics integration path #104
Description
Add the initial diagnostics/linter integration path for common languages without relying on VS Code extension runtime execution.
Scope:
- deterministic diagnostics model
- non-fatal missing linter handling
- project-local tool/config detection
- initial integrations through existing LinterBridge/service boundaries
- no auto-install of external tools
- no hidden command execution from extension metadata
Initial targets:
- Python via ruff when available
- JSON parser/schema validation path
- shellcheck/eslint/cargo checks only when explicitly available and configured
Done when:
- diagnostics can represent file, line, column, severity, source, and message
- missing tools do not crash ECLI
- tests cover diagnostic parsing and missing-tool behavior
Activity
SSobol77 commentedon Jul 12, 2026
Completed by the merged F4 Diagnostics work in PRs #113, #117, and #123, followed by the Debian provisioning and installed-runtime validation track. The normalized diagnostics model, safe provider execution, missing-tool handling, provider registry/service boundaries, parsers, and regression coverage are implemented. Current runtime accurately distinguishes 14 registered providers from 19 provisioned toolchain executables. Closing as completed.