note(redfix): M1 pre-staging — mattermost (no restore.post-hook) + discourse (PR-faithfulness overlay) static claims corroborated via code; owe own discourse isolation run + bluesky diag before any PASS

machine-docs/REVIEW-redfix.md

@@ -26,3 +26,22 @@ _(none yet — awaiting Builder bootstrap + first gate claim)_
 - 2026-06-17T23:18Z — Phase redfix opened. Refreshed phase plan + plan.md §6.1. Cold access to cc-ci
   confirmed (`ssh cc-ci`: host `nixos`, uptime 4d, `systemctl --failed` empty, load ~0.8). No Builder
   state files (`STATUS/BACKLOG/JOURNAL-redfix.md`) yet; no gate claimed. Idling for the first claim.
+- 2026-06-18T00:10Z — Non-contending pre-staging (M1 NOT yet claimed; Builder mid-investigation:
+  gitea isolation running, keycloak pending). Stayed OFF the swarm to avoid contaminating the
+  Builder's isolation runs. Independently corroborated two deterministic static claims via pure
+  code reads on cc-ci (no deploys):
+  * **mattermost-lts** (recipe @ `2.1.9+10.11.15`): postgres svc has `backupbot.backup.pre-hook`
+    (pg_dump → /var/lib/postgresql/data/postgres-backup.sql), `backup.post-hook` (rm dump),
+    `backup.path=/var/lib/postgresql/data/` (hot live PGDATA) — and **NO `backupbot.restore.post-hook`**.
+    immich (passes) uses dump-only `backup.volumes.postgres.path: backup.sql` + `restore.post-hook:
+    /pg_backup.sh restore`. Corroborates "genuine recipe defect — no restore round-trip." ✔ pre-staged.
+  * **discourse** (recipe @ `0.8.1+3.5.0` = `bitnamilegacy/discourse:3.5.0` + sidekiq): overlay
+    `tests/discourse/test_upgrade.py` is a phase-prevb PR-faithfulness test asserting app image ==
+    official `discourse/discourse:3.5.3` AND sidekiq dropped — only true on an unreleased PR head, not
+    the latest release the canon sweep deploys. So it red-by-construction in the sweep. Corroborates
+    "stale/PR-specific overlay test, not flake/timeout/recipe-deploy." ✔ pre-staged.
+  * STILL OWED before any M1 PASS: my OWN cold isolation run of discourse to confirm the
+    re-classification from the original canon hypothesis ("cold-deploy timeout, ~51-min wedge") to
+    "deploys+serves fine, only the overlay test reds." Will run when M1 is claimed and the swarm is
+    free (Builder not deploying). Same for bluesky app-alias collision (needs live caddy/getent diag).
+  These are NOT verdicts — formal M1 PASS/FAIL awaits the Builder's gate claim.