diff --git a/machine-docs/STATUS-2.md b/machine-docs/STATUS-2.md
index f65e507..e19595f 100644
--- a/machine-docs/STATUS-2.md
+++ b/machine-docs/STATUS-2.md
@@ -66,22 +66,23 @@ tree must carry:
   the running `drone_…` stack is the platform's OWN CI engine (infra), NOT the recipe-under-test (false
   alarm cleared). Deferral SOUND; maximal subset (declarative fix + scoped gitea+drone suite) ready for
   post-rebuild run.
-- **discourse (Q4.6)** — IN PROGRESS @2026-05-30. Re-pin done: **PR `recipe-maintainers/discourse#1`**
-  (branch `ci/bitnamilegacy-repin`, head `7b7ddd70bc753608d086884b8de1ad3c327d9ac5`) re-pins BOTH
-  `bitnami/discourse:3.3.1` image lines → `bitnamilegacy/discourse:3.3.1` (legacy manifest=200, old=404,
-  verified first-hand) + bumps version 0.7.0→0.8.0. Mirror created + populated (was 404). **Validation run
-  IN FLIGHT** on cc-ci `/root/ccci-builder-clone`: `RECIPE=discourse PR=1 REF=7b7ddd70... STAGES=install,custom`
-  → log `/root/ccci-discourse-pr1.log`, stack `disc-a622df`. **Image re-pin CONFIRMED WORKING** (db+redis+
-  sidekiq 1/1, no pull error). **RESULT @2026-05-30: install TIMED OUT at 1800s** (`deploy/readiness
-  failed ... timed out after 1800 seconds`; install:fail, custom:skip) — Rails first-boot exceeded the
-  deploy timeout; stack auto-torn-down clean. Image re-pin is PROVEN (not the blocker). **NEXT (clear
-  path):** add a ghost-style healthcheck start_period overlay to `tests/discourse/` — mirror
-  `tests/ghost/`: `compose.ccci-health.yml` raising the app healthcheck `start_period` to ~1200s +
-  `install_steps.sh` copying it + `recipe_meta.py` `COMPOSE_FILE=compose.yml:compose.ccci-health.yml` +
-  `CHAOS_BASE_DEPLOY=True`, and bump `DEPLOY_TIMEOUT`/`EXTRA_ENV TIMEOUT` to ~2400. Then re-run
-  `RECIPE=discourse PR=1 REF=7b7ddd70bc753608d086884b8de1ad3c327d9ac5 SRC=recipe-maintainers/discourse`.
-  On install green → author ≥2 functional incl §4.3 create-topic (admin API) → full lifecycle → CLAIM Q4.6.
-  **POLL with `ssh -T` (no PTY).** **THEN:** plausible Q4.7b recipe-PR (fix `entrypoint.clickhouse.sh`
+- **discourse (Q4.6)** — IN PROGRESS @2026-05-30. Re-pin **PR `recipe-maintainers/discourse#1`**
+  (branch `ci/bitnamilegacy-repin`, head `7b7ddd70bc753608d086884b8de1ad3c327d9ac5`) re-pins both
+  `bitnami/discourse:3.3.1` → `bitnamilegacy/discourse:3.3.1` (legacy=200, bitnami=404) + bumps version
+  0.7.0→0.8.0. install+custom GREEN (pr5, healthcheck-overlay + re-pin both work); P3 authored (§4.3
+  create-topic + site config). **UPGRADE TIER — implementing the HONEST crossover (Adversary §7.1 leans
+  DENY on a skip-with-sign-off; agreed).** Honest 0.7.0+3.3.1 → 0.8.0+3.3.1 is achievable: harness
+  default upgrade base = `recipe_versions[-2]` = 0.6.3+3.1.2 (img 3.1.2 — hollow, ≠ head's 3.3.1), but
+  the PR's TRUE predecessor is [-1] = 0.7.0+3.3.1 (shares head's 3.3.1). Implemented cc-ci-side (commit
+  a750937): (a) `recipe_meta.UPGRADE_BASE_VERSION="0.7.0+3.3.1"` + generic override in `run_recipe_ci.py`
+  (`prev = meta.get("UPGRADE_BASE_VERSION") or previous_version`); (b) `compose.ccci-health.yml` re-pins
+  `services.{app,sidekiq}.image: bitnamilegacy/discourse:3.3.1` (servable base 0.7.0 whose compose pins
+  the 404 bitnami:3.3.1; idempotent on head). → real HC1 crossover (version-label 0.7.0→0.8.0, same
+  servable discourse 3.3.1; namespace-only re-pin = the PR's change). **FULL run install,upgrade,backup,
+  restore,custom IN FLIGHT** on cc-ci `/root/builder-clone`, log `/root/ccci-discourse-maxsub.log`,
+  `RECIPE=discourse PR=1 REF=7b7ddd70... SRC=recipe-maintainers/discourse`. On green → CLAIM Q4.6 (no §7.1
+  deferral). If restore (P4) RED → discourse postgres restore-hook recipe-PR (immich/mattermost/ghost
+  class). **POLL with `ssh -T` (no PTY).** **THEN:** plausible Q4.7b recipe-PR (`entrypoint.clickhouse.sh`
   wget restart-storm) → plausible-full green → CLAIM Q4.7.
 - authentik / various --extra-flag tests — DEFERRED (Phase-2 DONE NOT gated on them per operator policy).
 DoD P2/P5/P6/P7/P8 broadly satisfied; remaining is P1 coverage of the above + Q5 docs/sample re-verify.