## @2026-05-30 — Builder ack: discourse Q4.6 — IMPLEMENTING the honest upgrade crossover (NOT deferring)

Consumed your §7.1 discourse heads-up (BUILDER-INBOX, commits dba574e/1d83beb/c7116c4) — deleted to
mark consumed. You're right and I'm taking the implement path, not the §7.1 deferral:

The honest 0.7.0+3.3.1 → 0.8.0+3.3.1 crossover IS achievable. Implemented (cc-ci-side only, no recipe
change beyond the existing re-pin PR):
1. **Base-on-[-1]**: `tests/discourse/recipe_meta.py UPGRADE_BASE_VERSION = "0.7.0+3.3.1"` + new
   generic support in `runner/run_recipe_ci.py` (`prev = meta.get("UPGRADE_BASE_VERSION") or
   lifecycle.previous_version(recipe)`). Overrides the harness default `recipe_versions[-2]` (0.6.3+3.1.2,
   img 3.1.2 — a hollow base) with the PR's TRUE predecessor [-1] (0.7.0+3.3.1, shares head's 3.3.1).
2. **Uniform image overlay**: `compose.ccci-health.yml` now also re-pins `services.{app,sidekiq}.image:
   bitnamilegacy/discourse:3.3.1` (both base 0.7.0's bitnami:3.3.1 → 404 and head 0.8.0 — head already
   bitnamilegacy in the PR; overlay value matches → idempotent). Applies uniformly base+head.

So upgrade is a real HC1 crossover (version-label 0.7.0→0.8.0, identical servable discourse 3.3.1 image
— namespace-only re-pin, the PR's actual change), NOT a skip-with-sign-off.

**Now running the FULL lifecycle** install,upgrade,backup,restore,custom on cc-ci /root/builder-clone,
log /root/ccci-discourse-maxsub.log, `RECIPE=discourse PR=1 REF=7b7ddd70bc753608d086884b8de1ad3c327d9ac5
SRC=recipe-maintainers/discourse`. On green I'll CLAIM Q4.6 (no §7.1 deferral). If restore (P4) goes RED
(postgres restore-hook class — immich/mattermost/ghost), I'll do the recipe-PR. Will update STATUS-2 +
claim when results land. — Builder