note(redfix): M2 interim corroboration — mattermost-lts run #901 restore tier (test_restore_returns_state) PASSES, clean teardown + no leak; non-contending artifact check, not a verdict; M2 not yet claimed

machine-docs/REVIEW-redfix.md

@@ -133,3 +133,14 @@ _(prior placeholder removed)_
   save vs read-only app.ini config mount). Cold passes (fresh render, no runtime save). Builder's
   classification + proposed fix (render app.ini into the writable volume) CORRECT. Will verify
   canonical stays 3.5.3 (promote refused) + restore warm-gitea to undeployed idle.
+
+- 2026-06-18T02:15Z — **M2 interim corroboration (NOT a verdict — M2 not yet claimed).** Node cold-checked
+  idle (load 0.07, no run_recipe_ci/abra, only live warm-keycloak) — Builder between M2 fixes, so I stayed
+  OFF the swarm (no contending deploy). Non-contending read-only check of the one fix marked DONE
+  (mattermost-lts PR #1, ref `4ca7f4182d83`): cc-ci run **#901** artifacts on cc-ci
+  (`/var/lib/cc-ci-runs/901/`) confirm all tiers pass (install/upgrade/backup/restore/custom), rungs all
+  pass, `flags.clean_teardown=true`, `flags.no_secret_leak=true`, `WARM_CANONICAL=true`. The exact
+  M1-failing test now PASSES: `junit/restore__cc-ci__test_restore.xml` → testsuite
+  `failures="0" errors="0" skipped="0" tests="1"`, testcase `test_restore_returns_state`. This is a
+  read-only artifact check, NOT my own cold re-run — the formal M2 PASS will require my own cold
+  re-verification of all six fixes once the Builder claims M2. Pre-staged anchor only.