dcdpr / jp / 28774224049

69%

Build Type

push

github

Committed by web-flow

Commit Message

chore(tools): Add checksum freshness opt-in and touch to unix_utils (#844)

Cargo tools (`cargo_check`, `cargo_expand`, `cargo_test`) can now set
`CARGO_UNSTABLE_CHECKSUM_FRESHNESS=true` via a new `checksum_freshness`
tool option, enabled by default in the `.jp/mcp/tools/cargo/*.toml`
definitions. This makes cargo compare file content checksums instead
of mtimes when deciding what needs rebuilding, so sibling checkouts
(git worktrees) sharing a target directory can no longer serve each
other's stale build artifacts, matching CI behavior. The option
requires nightly cargo (https://github.com/rust-lang/cargo/issues/14136)
and defaults to off at
the code level so the tools keep working on stable Rust.

`unix_utils` gains `touch` as its first write-capable utility. Every
other utility stays read-only; `touch` is carved out in the sandbox
profile with `file-write*` access scoped to the workspace root (and
its canonicalized path, since seatbelt checks resolved symlinks). This
lets the model bump a file's mtime to force a rebuild, e.g.
`{"util": "touch", "args": ["crates/jp_cli/src/main.rs"]}`. The tool
description warns against `-t`/`-d`/`-r` timestamp flags, since
backdated mtimes can corrupt build-freshness tracking. `nl`, already
supported in code but missing from the tool's `util` enum, is added
there too, and a new test pins the enum and the code allowlist
together so future drift between them fails the test suite.

---------

Signed-off-by: Jean Mertz <git@jeanmertz.com>

Coverage Stats

22 of 65 new or added lines in 5 files covered. (33.85%)

5 existing lines in 3 files now uncovered.

38643 of 56754 relevant lines covered (68.09%)

672.98 hits per line