fix(ci): remove weekly MSRV release run

docs/dependency-policy.md

@@ -14,11 +14,9 @@ missing, or the dependency lacks an implemented responsibility in
 consumer and dependency scope, all approved duplicate sets, native direct
 dependencies, review dates, and the resolved external package count.
 
-The policy intentionally distinguishes Rust 1.96.0, the minimum supported Rust
-version, from current stable Rust used for development and release validation.
-The release matrix checks both. Raising the MSRV requires an explicit policy,
-matrix, documentation, and changelog review; ordinary dependency updates may
-not raise it accidentally.
+Development and release validation use the current stable Rust toolchain pinned
+by the workflows. Dependency review records compiler requirements without
+installing or testing an additional historical toolchain.
 
 ## Automated gates
 
@@ -67,7 +65,7 @@ The graph is reviewed at least quarterly using `reviewed_on` and `review_by`.
 RustSec advisories are reviewed immediately. For every update:
 
 1. identify the implemented caller and confirm the dependency remains needed;
-2. inspect release notes, maintenance state, license, MSRV, enabled features,
+2. inspect release notes, maintenance state, license, compiler requirements, enabled features,
    native code, and target-specific build behavior;
 3. update one crate deliberately with `cargo update -p NAME --precise VERSION`;
 4. rerun the dependency audit, `cargo-deny`, `cargo-machete`, and the affected

docs/release-artifacts.md

@@ -14,9 +14,8 @@ duplicate inventory.
 
 ## Clean Ubuntu prerequisites
 
-The automated gate runs only on `ubuntu-latest`, using Rust 1.97.1 for normal
-release work. Rust 1.96.0 remains a separate minimum-supported-version check;
-it is not used to build these release artifacts. The clean worker installs:
+The automated gate runs only on `ubuntu-latest`, using Rust 1.97.1 for all
+release work. The clean worker installs:
 
 - a C/C++ build toolchain, Clang, CMake, Ninja, `pkg-config`, Python 3, and
   `curl` for the pinned Skia build/download path;

docs/release-candidate.md

@@ -12,8 +12,7 @@ is evidence of remaining work, never permission to waive it.
 - Portable, default-feature-disabled library surfaces are cross-compiled from
   Ubuntu for Windows GNU x86-64 and macOS x86-64. Those checks do not claim
   native runtime, installer, physical-device, CoreAudio, or WASAPI validation.
-- Rust 1.97.1 is the release toolchain. Rust 1.96.0 is exercised separately and
-  only supports the minimum-version compatibility claim.
+- Rust 1.97.1 is the release toolchain.
 
 ## Features and prerequisites
 

docs/release-ci-matrix.md

@@ -4,8 +4,8 @@ MetaCrate has one routine code-ready signal: the `required` job in
 `.gitea/workflows/ci.yml`. It runs for every push and pull request on
 `ubuntu-latest`, has a hard 15-minute timeout, and cancels an older run for the
 same branch or pull request. `.gitea/workflows/release.yml` is the only other
-workflow. It is manual, weekly, and tag-only; it never runs for an ordinary
-source push or pull request.
+workflow. It runs only when manually dispatched or when a release tag is
+pushed; it never runs for an ordinary source push or pull request.
 
 The reviewed coverage map is `ci/ci-coverage.json`. It maps every responsibility
 from the former 13 workflows to the required gate, the non-routine release
@@ -107,8 +107,8 @@ cargo clean --target-dir target/release-gate
 
 ## Non-routine release gate
 
-The Rust `release-gate` command owns clean MSRV and portable cross-target
-checks, benchmark compilation, the 16-cycle resource soak, all 16 source
+The Rust `release-gate` command owns portable cross-target checks, benchmark
+compilation, the 16-cycle resource soak, all 16 source
 packages, release binaries, native artifact inspection, and the aggregate
 release-candidate audit. Reference C# performance regeneration and live-grid,
 physical-audio, proprietary-service, signing, and platform-native installer