fix(ci): build Linux ARM releases natively

[mstuart]

Summary

• build the Linux ARM64 release artifact on GitHub's native ARM64 runner
• remove the incomplete x64-to-ARM cross toolchain setup that cannot satisfy openssl-sys
• add a safe manual build-only dispatch; release creation and npm publication remain tag-only

Root cause

The v0.1.0 release run failed while cross-compiling aarch64-unknown-linux-gnu because fastembed -> hf-hub -> native-tls requires an ARM64 OpenSSL development toolchain. Installing only the ARM GCC/G++ cross compilers does not provide it.

Verification

• parsed .github/workflows/release.yml successfully as YAML
• cargo test --all-features (all tests pass; one integration test intentionally ignored)
• cargo fmt --package code-memory -- --check
• cargo clippy --all-targets --all-features -- -D warnings
• git diff --check

After merge, the new manual dispatch can verify the complete release build matrix without creating a release or publishing the npm package.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-09-26T18:10:53.884766Z	d601d8e	PR opened
🔒 Security Review	✅ Completed 2026-09-26T18:11:30.963706Z	d601d8e	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: d601d8e4ea

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Sanitize dispatched branch names before packaging

When this workflow is manually dispatched against a slash-delimited branch such as feature/foo, github.ref_name retains that slash, but the packaging steps interpolate it directly into the archive filename. The Unix command consequently tries to write beneath a nonexistent code-memory-feature/ directory and fails, so the newly added manual build verification cannot run on common feature-branch names; derive a filesystem-safe artifact suffix or omit the ref name for dispatch runs.

Useful? React with 👍 / 👎.