detect-commands names a tool binary it never checks is reachable #221

New issue

Closed

opened 2026-08-18 20:49:39 +00:00 by john · 1 comment

john commented

2026-08-18 20:49:39 +00:00

Owner

Verified on this machine 2026-08-18: ruff, mypy, eslint and tsc are all absent from PATH, and a pyproject.toml carrying [tool.ruff]/[tool.mypy] still yields {"lint":"ruff check .","typecheck":"mypy ."}. Same for cargo clippy under rustups minimal profile.

The command is named from the presence of its config table alone. The executor contract turns a surviving static-analysis failure into a blocked checkpoint, so a missing binary stops the plan after three wasted attempts rather than being absent up front.

An unreachable binary should yield no command, the same answer as no config table.

Verified on this machine 2026-08-18: `ruff`, `mypy`, `eslint` and `tsc` are all absent from PATH, and a `pyproject.toml` carrying `[tool.ruff]`/`[tool.mypy]` still yields `{"lint":"ruff check .","typecheck":"mypy ."}`. Same for `cargo clippy` under rustups minimal profile. The command is named from the presence of its config table alone. The executor contract turns a surviving static-analysis failure into a `blocked` checkpoint, so a missing binary stops the plan after three wasted attempts rather than being absent up front. An unreachable binary should yield no command, the same answer as no config table.