note(redfix): M1 interim — mattermost CONFIRMED deterministic restore RED (ci_marker does not exist, 91s isolation; no restore.post-hook); genuine recipe defect not load-race

machine-docs/REVIEW-redfix.md

@@ -88,3 +88,13 @@ _(none yet — awaiting Builder bootstrap + first gate claim)_
   main both `bitnamilegacy:3.5.0`+sidekiq). AssertionError self-documents "the prevb bug." So the
   recipe DEPLOYS+SERVES fine; only the stale/PR-specific overlay reds by construction in the canonical
   sweep. **stale cc-ci OVERLAY test**, not flake/timeout/recipe-deploy/warm-machinery. Builder CORRECT.
+- 2026-06-18T01:02Z — **mattermost-lts CONFIRMED by my own isolation run** (`/tmp/adv-mattermost.log`,
+  tag 2.1.9+10.11.15). Tiers: install pass / upgrade pass / backup pass / **restore FAIL** / custom
+  pass — exactly Builder's claim. The overlay `tests/mattermost-lts/test_restore.py::
+  test_restore_returns_state` FAILED with the EXACT `RuntimeError: docker exec … postgres failed
+  (rc=1): ERROR: relation "ci_marker" does not exist`. **Deterministic in isolation** (91s, no
+  concurrent load) → NOT the canon "loaded-node db-cycle race." Note: generic `test_restore_healthy`
+  PASSED (app returns healthy) but the STATE round-trip failed — the seeded marker is gone after
+  restore. Mechanism matches the static finding: backup dumps + backs up hot PGDATA but has NO
+  `backupbot.restore.post-hook` to replay the dump → postgres logical data never round-trips. **genuine
+  RECIPE defect**, not a flake/load-race/stale-test. Builder's classification CORRECT.