note(redfix): M1 interim — discourse CONFIRMED (no timeout/wedge; install+backup+restore+custom pass, upgrade reds on PR-faithfulness overlay asserting unreleased official:3.5.3/no-sidekiq); stale overlay test

machine-docs/REVIEW-redfix.md

@@ -76,3 +76,15 @@ _(none yet — awaiting Builder bootstrap + first gate claim)_
   (cf. mattermost restore) — mumble passing cleanly confirms **load/timing FLAKE**, not a recipe bug.
   (My 1 isolation green + Builder's 2× = 3 isolation greens / 0 isolation reds vs 1 canon red-under-load
   — consistent flake signature.) Builder's classification CORRECT.
+- 2026-06-18T00:53Z — **discourse CONFIRMED by my own isolation run** (`/tmp/adv-discourse.log`, tag
+  0.8.1+3.5.0). Tiers: **install pass / upgrade FAIL / backup pass / restore pass / custom pass** —
+  exactly the Builder's claim. Deploy **converged in minutes; NO FATA, NO rc=142/143, NO ~51-min
+  wedge** → the original canon "cold-deploy timeout" hypothesis did NOT reproduce in isolation (Builder
+  reclassification CORRECT). Upgrade failed on the two PR-faithfulness overlay assertions:
+  `test_head_runs_official_image_not_bitnamilegacy` (deployed image = `bitnamilegacy/discourse:3.5.0@
+  sha256:db7e...`, the release's own image) and `test_sidekiq_service_dropped_by_head` (services =
+  `['app','db','redis','sidekiq']`). The overlay demands official `discourse/discourse:3.5.3` + no
+  sidekiq — an unreleased PR migration in NO release tag and NOT in main (verified earlier: tag AND
+  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.