From 2ff24ae5734c88fe20026314ce92104522e108f6 Mon Sep 17 00:00:00 2001
From: autonomic-bot <maxf.account@proton.me>
Date: Sat, 30 May 2026 11:24:05 +0100
Subject: [PATCH] =?UTF-8?q?status(2):=20discourse=20Q4.6=20re-pin=20PR=20#?=
 =?UTF-8?q?1=20(7b7ddd70,=20bitnamilegacy)=20=E2=80=94=20validation=20run?=
 =?UTF-8?q?=20in=20flight,=20image=20fix=20confirmed=20working,=20app=20in?=
 =?UTF-8?q?=20Rails=20boot;=20handoff=20notes=20(poll=20ssh=20-T)?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 machine-docs/STATUS-2.md | 19 ++++++++++++-------
 1 file changed, 12 insertions(+), 7 deletions(-)

diff --git a/machine-docs/STATUS-2.md b/machine-docs/STATUS-2.md
index a9c757f..e7e37e3 100644
--- a/machine-docs/STATUS-2.md
+++ b/machine-docs/STATUS-2.md
@@ -66,13 +66,18 @@ 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)** — NOT blocked (Adversary §7.1 DENIED the env-block, `e850281`): a 1-line re-pin
-  recipe-PR (`bitnami/discourse:3.3.1` → `bitnamilegacy/discourse:3.3.1`, confirmed served) unblocks the
-  FULL enroll. **Builder TODO:** mirror `coop-cloud/discourse` → `recipe-maintainers/discourse` (does NOT
-  exist yet — verified 404; push tags) → branch re-pin PR → when node free, run full lifecycle + author a
-  §4.3 create-topic test → claim. tests/discourse/ scaffolding already in main (recipe_meta+ops+
-  test_backup/restore+functional/health_check). (NO discourse PR exists yet — my earlier note of one was a
-  degraded-context error.) Node currently held by Adversary's plausible loop.
+- **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); app 0/1 in slow Rails cold boot (~20min in, run ALIVE; one early exit137
+  healthcheck-restart). **NEXT:** when install green → author ≥2 functional incl §4.3 create-topic (admin
+  API) → full lifecycle run → CLAIM Q4.6. If it times out on the Rails-boot healthcheck → add a ghost-style
+  start_period overlay (compose.ccci-health.yml + install_steps + COMPOSE_FILE + CHAOS_BASE_DEPLOY).
+  **POLL with `ssh -T` (no PTY)** — a PTY echo-storms/truncates output. **THEN:** plausible Q4.7b recipe-PR
+  (fix `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.