From 93e1e7d87a9dbe456732d892f7487f51e6557aff Mon Sep 17 00:00:00 2001 From: autonomic-bot Date: Thu, 18 Jun 2026 00:08:31 +0000 Subject: [PATCH] =?UTF-8?q?note(redfix):=20M1=20pre-staging=20=E2=80=94=20?= =?UTF-8?q?mattermost=20(no=20restore.post-hook)=20+=20discourse=20(PR-fai?= =?UTF-8?q?thfulness=20overlay)=20static=20claims=20corroborated=20via=20c?= =?UTF-8?q?ode;=20owe=20own=20discourse=20isolation=20run=20+=20bluesky=20?= =?UTF-8?q?diag=20before=20any=20PASS?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- machine-docs/REVIEW-redfix.md | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) diff --git a/machine-docs/REVIEW-redfix.md b/machine-docs/REVIEW-redfix.md index cefa1be..e2c6d82 100644 --- a/machine-docs/REVIEW-redfix.md +++ b/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.