[ThirtyFile]

What changes

The weekly Fuzz workflow failed on its first scheduled run (2026-10-26) for all five targets: error: sanitizer is incompatible with statically linked libc and can't find crate for core for x86_64-unknown-linux-musl. The workflow installs cargo-fuzz with taiki-e/install-action, which falls back to cargo-binstall and takes the prebuilt program of the release, a static musl one; cargo fuzz with no --target builds for the target it was built for itself, and musl has no sanitizers. The workflow now names the target, x86_64-unknown-linux-gnu.

How it was tested

The workflow was run by hand on this branch (Actions > Fuzz > Run workflow, branch fix/fuzz-target): all five targets ran for a minute each, 5.5 million runs together, with no crash.

Checklist

• The title says what changes, in plain words
• One label: maintenance
• No Rust code changes
• A fix has a test that fails without it (the manual run is the test; the scheduled run of 2026-10-26 is the failing one)
• The compatibility page, the README and the documentation do not need changes