deferred(2): Q4.6 discourse BLOCKED — upstream bitnami/discourse images removed from Docker Hub (undeployable)

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

machine-docs/DEFERRED.md

@@ -250,3 +250,29 @@ before the build is called done) — but does **not** force closure.
 - **Re-entry trigger:** pick up as a recipe-PR unit (parallel to Q3.2b); OR Adversary §7.1 sign-off on
       the documented maximal subset if a recipe PR is out of scope for Phase-2 DONE.
 - **Linked IDEA:** —
+
+### 2026-05-29 — discourse: upstream recipe pins removed bitnami images (undeployable)
+- [ ] **What:** discourse (Q4.6) cannot be enrolled/tested because the recipe pins
+      `image: bitnami/discourse:<tag>` (app + sidekiq) and **Docker Hub no longer serves any
+      `bitnami/discourse:*` tag** (bitnami's 2024/2025 legacy migration). Proven on cc-ci:
+      `docker pull bitnami/discourse:3.3.1` → `manifest unknown`; the swarm app task is `Rejected:
+      "No such image: bitnami/discourse:3.3.1"`. The image IS available at
+      `bitnamilegacy/discourse:3.3.1` (verified present). db(postgres)+redis deploy fine; only the
+      bitnami-imaged app/sidekiq fail. Test scaffolding is staged (tests/discourse/: recipe_meta,
+      postgres-P4 ops + backup/restore overlays, health) but the §4.3 create-a-topic test was never
+      written/validated (deploy blocked before the app booted).
+- **Filed by:** Builder, phase 2 (Q4.6 discourse smoke).
+- **Reason for deferral:** UPSTREAM recipe + image-availability defect, not a cc-ci/test issue.
+      Compounded: cc-ci's **install tier deploys the PREVIOUS published version** (0.6.3+3.1.2 →
+      bitnami/discourse:3.1.2, also removed), so even a recipe-PR repointing to `bitnamilegacy/` only
+      fixes the upgrade head + FUTURE installs once released — it does NOT make the install tier
+      deployable under the current published versions (all bitnami/discourse tags gone). Same
+      constraint class as plausible Q4.7b. Not improvisable by editing the in-repo compose (that would
+      be testing a fork, not the published recipe).
+- **Operator action to lift:** a discourse recipe-PR repointing app+sidekiq to a maintained image
+      (`bitnamilegacy/discourse:<tag>` or another upstream) **AND a new published recipe version**, so
+      a deployable published version exists for the install tier. Then re-run RECIPE=discourse + add
+      the §4.3 create-a-topic test. (Broader: any other §5 recipe on a bitnami image may hit the same.)
+- **Re-entry trigger:** upstream discourse recipe ships a deployable image version; OR operator
+      approves a cc-ci-authored discourse recipe-PR + release.
+- **Linked IDEA / BACKLOG:** Q4.6.