A local Windows check for the CLI execution-budget change failed while compiling the unchanged crypto-common 0.2.2 dependency, without a compiler diagnostic explaining the failure.
Observed command: cargo check --locked --manifest-path fuzz/Cargo.toml.
Environment: rustc 1.98.1 (48a229cea 2026-09-01), cargo 1.98.1 (797e8a9bc 2026-08-05), stable x86_64-pc-windows-msvc. Source base: a1249033b0f1cff87ecea8282619808f727d22c3; candidate changes only CLI invocation-budget selection plus WFL tests/docs/CI. No dependency or lockfile changes.
Sanitized error:
error: could not compile `crypto-common` (lib)
Caused by:
process didn't exit successfully: rustc --crate-name crypto_common ... (exit code: 1)
warning: build failed, waiting for other jobs to finish...
The captured output contained neither an ordinary Rust diagnostic nor an identified resource/host failure. The diagnostic build, cargo check --locked --manifest-path fuzz/Cargo.toml -j 1 --verbose, then passed the entire fuzz workspace, including fuzz_frontend, in 5m22s. No source, dependency or lockfile change occurred between these builds. This later successful check does not establish the cause of the first failure.
Local logs are retained under ignored target/reports/cli-budget/fuzz.log and fuzz-diagnostic.log. This issue preserves the unexplained observation under the repository's evidence policy; it is not a waiver of fuzz compilation or any CI gate. No claim of a transient infrastructure cause is supported yet.
Acceptance: identify a reproducible compiler/build/environment cause with evidence, or collect enough subsequent diagnostic evidence to delimit the unresolved failure accurately. Keep the original failure visible even when a later build succeeds.
A local Windows check for the CLI execution-budget change failed while compiling the unchanged
crypto-common 0.2.2dependency, without a compiler diagnostic explaining the failure.Observed command:
cargo check --locked --manifest-path fuzz/Cargo.toml.Environment:
rustc 1.98.1 (48a229cea 2026-09-01),cargo 1.98.1 (797e8a9bc 2026-08-05), stablex86_64-pc-windows-msvc. Source base:a1249033b0f1cff87ecea8282619808f727d22c3; candidate changes only CLI invocation-budget selection plus WFL tests/docs/CI. No dependency or lockfile changes.Sanitized error:
The captured output contained neither an ordinary Rust diagnostic nor an identified resource/host failure. The diagnostic build,
cargo check --locked --manifest-path fuzz/Cargo.toml -j 1 --verbose, then passed the entire fuzz workspace, includingfuzz_frontend, in 5m22s. No source, dependency or lockfile change occurred between these builds. This later successful check does not establish the cause of the first failure.Local logs are retained under ignored
target/reports/cli-budget/fuzz.logandfuzz-diagnostic.log. This issue preserves the unexplained observation under the repository's evidence policy; it is not a waiver of fuzz compilation or any CI gate. No claim of a transient infrastructure cause is supported yet.Acceptance: identify a reproducible compiler/build/environment cause with evidence, or collect enough subsequent diagnostic evidence to delimit the unresolved failure accurately. Keep the original failure visible even when a later build succeeds.