Establish controlled red-suite baseline

RUSTREWRITE.md

@@ -364,6 +364,32 @@ The test-suite gate is complete only when:
 - no production method contains real behavior beyond what is required to make
   signatures and constants compile.
 
+### 3.3 Fixed controlled-red baseline
+
+Milestone 03 closes against the pinned 1,289-invocation catalog, not the older
+1,295 source-text estimate. The six-case difference is intentional: five
+attributes were commented out and one parameterless `[Test]` marker duplicated
+a parameterized `[TestCase]` method. Reintroducing those entries would create
+tests that NUnit never runs.
+
+`tests/red-suite-baseline.json` fixes the machine-checked ledger at 1,266
+ordinary translations, 19 live-grid translations, four benchmarks, and zero
+pending, drifted, duplicate, missing, or unreviewed cases. Run the controlled
+audit with:
+
+```sh
+python3 tools/audit_red_suite.py
+```
+
+With all three live-grid credentials present, the baseline executes every case:
+22 tests pass, 1,287 fail at 131 standardized C# member IDs, and none are
+ignored. Twenty passes are gate/support tests. The only two passing parity cases
+verify the required `BAKED_TEXTURE_COUNT` constant and composable validation
+flags; they do not represent implemented production behavior. Without complete
+credentials, the same audit conditionally ignores exactly the 19 live-grid
+cases and requires the remaining 1,268 parity failures to retain standardized
+member IDs. Production crates remain the failure-only milestone-02 shims.
+
 ## 4. Validated Rust dependency map
 
 Versions below were queried from crates.io on 2026-08-08 with `cargo search`