diff --git a/machine-docs/BACKLOG-2.md b/machine-docs/BACKLOG-2.md
index bcfeb2d..2e80c68 100644
--- a/machine-docs/BACKLOG-2.md
+++ b/machine-docs/BACKLOG-2.md
@@ -177,7 +177,13 @@ Phase plan: `/srv/cc-ci/cc-ci-plan/plan-phase2-recipe-tests.md`
       backup data-integrity (seed→backup→mutate→restore→assert) = follow-up ops.py — tracked in the Q5
       P4-sweep (generic backup/restore covers the floor; same bar as ghost Q4.4). Mirror to
       recipe-maintainers needed only for the PR/!testme flow (catalogue-fetch e2e green now).
-- [ ] **Q4.6** — discourse: enroll; specific (create-a-topic round-trip).
+- [~] **Q4.6** — discourse: **BLOCKED (DEFERRED 2026-05-29)** — upstream recipe pins
+      `bitnami/discourse:*` images that Docker Hub no longer serves (manifest unknown; swarm task
+      Rejected 'No such image'). db/redis deploy; bitnami-imaged app/sidekiq cannot. Image exists at
+      `bitnamilegacy/discourse` but the install tier uses the prev published version (also gone), so a
+      recipe-PR can't unblock testing until upstream releases a fixed version. Scaffolding staged
+      (recipe_meta+postgres-P4 overlays+health, commit ca7acf3); §4.3 create-topic not written (deploy
+      blocked). See DEFERRED.md 2026-05-29 discourse entry. Same class as plausible Q4.7b.
 - [~] **Q4.7** — plausible: enrolled. recipe_meta (DISABLE_AUTH/REGISTRATION, SECRET_KEY_BASE;
       HEALTH_PATH=/api/health [200 w/ clickhouse+postgres+sites_cache ok — `/` 500s under headless
       DISABLE_AUTH so not a valid probe]; DEPLOY/HTTP_TIMEOUT=1200) + PARITY.md (P2 vacuous, no
diff --git a/machine-docs/STATUS-2.md b/machine-docs/STATUS-2.md
index 47d6210..4c8cdfb 100644
--- a/machine-docs/STATUS-2.md
+++ b/machine-docs/STATUS-2.md
@@ -49,6 +49,18 @@ tree must carry:
 - **Q5** — Completeness + docs; flip `## DONE`.
 
 ## In flight
+**Q4.6 discourse — BLOCKED/DEFERRED @2026-05-29.** Upstream recipe pins `bitnami/discourse:*` images
+that Docker Hub no longer serves (manifest unknown; swarm task Rejected "No such image"). Image exists
+at `bitnamilegacy/discourse` but the install tier deploys the prev published version (also gone), so a
+recipe-PR can't unblock testing until upstream releases a fixed version (same class as plausible Q4.7b).
+Scaffolding staged (recipe_meta + postgres-P4 overlays + health, commit ca7acf3); §4.3 create-topic not
+written (deploy blocked). DEFERRED.md 2026-05-29 discourse entry. Node fully torn down/clean.
+**NEXT: Q4.9 mailu** — images pullable (ghcr.io/mailu/*); no recipe-maintainer corpus (P2 vacuous); no
+backupbot label (P4 will be N/A/recipe-PR-deferred like immich). Functional: admin API create domain+
+mailbox + read-back + SMTP/IMAP mail flow. (drone Q4.10 also pullable but needs a gitea OAuth dep for
+functional depth — lower priority.)
+
+
 **Q4.7 plausible — Adversary finding ACK @2026-05-29 (REVIEW-2 `0efcc36`).** Test content + deferral
 verified sound; only gap: my "§4.3 proven green" claim lacks a surviving evidence log on cc-ci.
 Builder action: after mumble, run `RECIPE=plausible PR=0` (or functional subset) when the GitHub/