rust-toolchain.toml

# Exec/boot build toolchain. The nucleus boot spike builds on STABLE Rust against
# the built-in `x86_64-unknown-none` target (naked/inline asm and no_std are stable).
#
# The Verus PROOF track does NOT need a nightly, and does not read this file.
# Measured 2026-08-11: Verus 0.2026.08.09 pins STABLE 1.97.1 and carries its own
# rustc driver, so it ignores this rustup pin entirely. It also cannot share a
# build with it -- rustc 1.95.0 rejects a Verus-built rlib with E0514 -- so any
# in-tree `verus!{}` would move this whole repo to 1.97.1. In-tree adoption was
# DECLINED on 2026-08-11; see the decision block at the top of
# docs/verification.md. `toolchain/verus.lock` remains an unfilled placeholder.
[toolchain]
channel = "1.95.0"
targets = ["x86_64-unknown-none"]
profile = "minimal"
# `minimal` installs no rustfmt, and CI's FIRST step is `cargo fmt --all --check` — so every run
# died on step one with "'cargo-fmt' is not installed for the toolchain '1.95.0'". Forty runs
# back, to 2026-08-14, not one was green: the whole DMA/IOMMU arc was pushed against a CI that
# had never once reported on it. Naming the component here fixes it everywhere the pin is
# honoured rather than only on the runner.
components = ["rustfmt"]