release: publish cross-platform queue CLI binaries independently from npm

[chrisbbreuer]

Problem

The npm workspace publishes only README.md and dist, but its prepublishOnly lifecycle currently compiles and zips five native CLI targets. Those binaries are excluded from the npm tarball, make package publication slow, and have no retained release artifact contract.

Required work

• Add an explicit runner/target matrix for Linux x64/arm64, macOS x64/arm64, and Windows x64.
• Smoke-test each compiled CLI on its native runner where available.
• Produce checksums and upload the archives to the matching GitHub release.
• Retain a manifest that records source revision, runner, target, archive digest, and test result.
• Keep npm prepublishOnly limited to the files that actually enter the npm package.

Acceptance criteria

• Native binaries are produced outside the npm publish lifecycle.
• Every advertised target has an artifact, checksum, and retained test result.
• npm publication completes without compiling excluded native assets.
• Release documentation links the binary manifest and npm tarball verification.