chore(toolchain): pin Rust to 1.94.1 + fix CI fmt/i686 (matches sibling repos)

[AdaWorldAPI]

Summary

Pins Rust to 1.94.1 + fixes two CI failures the user surfaced.

Changes

File	Change
rust-toolchain.toml	Bump 1.94.0 → 1.94.1 (latest 1.94 patch, 2026-03-25)
.github/workflows/ci.yaml	Three coordinated fixes — see below

CI fixes

1. Drop target-cpu=x86-64-v3 from global RUSTFLAGS

Was: RUSTFLAGS: "-D warnings -C target-cpu=x86-64-v3" at job level.

Was breaking cross_test for i686-unknown-linux-gnu (32-bit) and s390x-unknown-linux-gnu — target-cpu=x86-64-v3 is a 64-bit-x86 feature level that doesn't apply. Also contradicts .cargo/config.toml's recorded design intent: "No global target-cpu. Each kernel uses #[target_feature(enable = "avx512f")] per-function, with LazyLock runtime detection. One binary, all ISAs."

Now: RUSTFLAGS: "-D warnings". Per-job opt-in if a job specifically needs higher target-cpu.

2. Pin clippy + format actions to 1.94.1

dtolnay/rust-toolchain@stable and @master silently auto-track latest-stable. Nothing was actually pinned. Replaced with explicit @1.94.1 on the clippy and format jobs.

3. Format job uses nightly rustfmt + continue-on-error: true

rustfmt.toml declares 13 nightly-only options (brace_style = AlwaysNextLine, imports_granularity = Preserve, unstable_features = true, etc.). Stable rustfmt warns and ignores them, then produces drift on every nightly-formatted file.

The format job MUST use nightly rustfmt for the project's chosen style to be enforceable. Compile + clippy stay on 1.94.1 stable — only format needs nightly.

Local audit (2026-04-30) under cargo +nightly fmt --all -- --check reports 5,679 drift sites — too large to bundle into a toolchain-pin PR. The format job is marked continue-on-error: true so it stays in the pipeline as a continuous signal but does not gate merge. A separate fmt-sweep PR should run cargo +nightly fmt --all and commit, then this PR's continue-on-error: true gets dropped.

What this PR does NOT do

• No fmt sweep — separate follow-up (5,679 drift sites mechanical reformatting).
• No latest-deps.yaml change — that workflow's @master and @stable are intentional cross-toolchain matrix testing for upstream lib, not consumer pinning.

Cross-ref

• MedCare-rs PR Add ARM NEON SIMD support for Raspberry Pi (3/4/5) #89 — same pin pattern (consumer side; full failure-mode story).
• lance-graph PR #325 — sibling 1.94.0 → 1.94.1 bump.
• smb-office-rs PR Claude/continue session 0m a va #27 — sibling new pin (no prior toml).

https://claude.ai/code/session_01SbYsmmbPf9YQuYbHZN52Zh

---

Generated by Claude Code