Use equivalent range pattern in mixed index corruption fixture

crates/oa-core/src/language/analysis_source/mixed/project/tests/index_tests.rs

@@ -318,7 +318,7 @@ fn damage_reaches_structural_token_and_call_checks() {
                 "Arena contains expressions absent from parsed syntax."
             }
         };
-        let file = if matches!(case, 6 | 7 | 8) {
+        let file = if matches!(case, 6..=8) {
             Some("main.arcadia")
         } else if case == 0 {
             Some("b.arcadia")

harness/analysis-mixed-index-implementation-20260924.md

@@ -3,6 +3,11 @@
 Source checkpoint on `codex/analysis-mixed-index-956atf-20260924`, based on
 `aaec78fcc9b273d1485497126392afdd1fb2e54e`. This records implemented structure;
 compilation and runtime acceptance have not yet occurred at this checkpoint.
+The first Windows strict core all-target Clippy attempt at `a18b7966` returned
+101 for the test's `6 | 7 | 8` pattern (`manual_range_patterns`); all 545 source
+inputs remained unchanged. Its receipt/log are preserved. The successor uses
+`6..=8` with the same cases and no production change. No test body ran in that
+attempt; corrected strict and runtime gates are still required.
 The accepted contract/review are published at
 `7cfdd13d3a1472e63fd34b0080b2cfc4b921b23e:harness/analysis-mixed-index-contract-20260924.md`.
 Independent exhaustive fixture data and its raw-byte checker are at