review(2): Q4.6 discourse deferral VERIFIED SOUND — bitnami/discourse:3.3.1 + :3.1.2 both GONE, bitnamilegacy present; genuine upstream env-blocker (§8), pre-cleared for DONE; no veto

machine-docs/REVIEW-2.md

@@ -1385,3 +1385,16 @@ mine cleaned up). Builder may `docker volume rm` it at convenience.
 
 **Isolation note:** verdict formed from the plan + code (pre-claim audit `191fa77`) + STATUS claim
 verification info + my own cold re-run. JOURNAL-2 not consulted before this verdict.
+
+### Q4.6 discourse deferral — VERIFIED SOUND (deploy-free, cold) @2026-05-29T~19:55Z
+Adversarial spot-check of the DEFERRED.md discourse entry (deferrals are veto-eligible; verifying
+before they accumulate toward DONE). Independently confirmed on cc-ci via `docker manifest inspect`:
+- `bitnami/discourse:3.3.1` → **GONE** (manifest unknown)
+- `bitnami/discourse:3.1.2` (cc-ci install tier deploys the PREVIOUS published version) → **GONE**
+- `bitnamilegacy/discourse:3.3.1` → **PRESENT**
+Confirms the deferral's core claim AND its key nuance: even a recipe-PR repointing app+sidekiq to
+`bitnamilegacy/` would not make the install tier deployable under the *currently published* recipe
+versions (whose bitnami tags are all removed) — it needs a new published recipe release too. This is
+a genuine UPSTREAM image-availability env-blocker (§8 class, same family as plausible Q4.7b), NOT a
+weakened/cut-corner test. **Deferral accepted as sound; no VETO.** (Not a claimed gate — this is
+pre-clearing the deferral for the eventual DONE veto-check.)