ci: install nasm in release-plz — the one workflow that links a binary was the one without it

[Ttimmahlax]

Nine crates published and the release still exited non-zero. cargo package reached ffai-cli and the link failed:

rust-lld: error: undefined symbol: McHorVer22Width8VerLastAlign_sse2
  referenced by rusty_h264-accel-0.8.0/src/lib.rs:376
rust-lld: error: undefined symbol: PixelAvgWidthEq4_mmx

Why only ffai-cli

rusty_h264-accel's build.rs skips assembling OpenH264's x86 kernels when nasm is absent, emits a warning, and lets the crate compile as a library anyway. So every library in the release packaged and published cleanly — ffai-media, all four engines, ffai-argus-wasm.

ffai-cli is the only binary. A binary is the only thing that links, and that's where the missing symbols surfaced. ffai-mercury-wasm and ffai-wasm sort after it and never got their turn.

The asymmetry

workflow	installs nasm	links a binary
harden.yml	✅	✅ (that's why Test/Clippy pass)
release.yml	✅	✅
release-plz.yml	❌	✅ — and it's the one that publishes

harden.yml's copy of this step has carried a comment predicting this exact failure — "a missing BUILD TOOL, not broken code" — since before it happened here.

This adds the same step, with the same time-box and retries.

Do not merge Dependabot #11 expecting it to help

The open rusty_h264 0.8.0 → 0.10.0 bump does not fix this. The symbols are absent because nothing assembled them, not because of anything that changed between those versions. I checked build.rs rather than assuming.

After this merges

The release should complete: ffai-cli 0.6.7, ffai-wasm 0.1.2 and ffai-mercury-wasm 0.1.0 are the three still outstanding.

🤖 Generated with Claude Code