From f2e903619615190d607dded512d95c55dc960cdb Mon Sep 17 00:00:00 2001 From: Claude Date: Sun, 12 Jul 2026 17:33:05 +0000 Subject: [PATCH] gates: set diff-test default-run so `cargo run -p diff-test` stays unambiguous MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The kernel lane (PR #14) added a second binary to the diff-test crate (src/bin/fp-compare.rs), which made `cargo run -p diff-test -- ` — the exact invocation the target-gates-no-net CI job uses to run a target's equivalence gate — ambiguous: error: `cargo run` could not determine which binary to run. available binaries: diff-test, fp-compare Naming the primary binary via `default-run` restores the single-binary behavior without touching the CI workflow or the gate command. Regression was latent on main since #14 merged; this PR's CI re-run surfaced it. Co-Authored-By: Claude Fable 5 Claude-Session: https://claude.ai/code/session_01EcKPWQ3MQD4NdEHwar96u2 --- crates/diff-test/Cargo.toml | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/crates/diff-test/Cargo.toml b/crates/diff-test/Cargo.toml index a516f4a..1e6ab7a 100644 --- a/crates/diff-test/Cargo.toml +++ b/crates/diff-test/Cargo.toml @@ -5,6 +5,11 @@ version.workspace = true edition.workspace = true license.workspace = true repository.workspace = true +# The crate ships two binaries — the `diff-test` gate driver and the +# `fp-compare` kernel-lane helper (src/bin/fp-compare.rs). Name the primary +# one so `cargo run -p diff-test` stays unambiguous (CI runs it as the +# per-target gate: `cargo run -p diff-test -- `). +default-run = "diff-test" [dependencies] anyhow.workspace = true