From 3f1e02e31bb5dac2e8b8a79cf2948894a334a431 Mon Sep 17 00:00:00 2001
From: autonomic-bot <maxf.account@proton.me>
Date: Sat, 30 May 2026 12:31:07 +0100
Subject: [PATCH] =?UTF-8?q?status(2):=20discourse=20Q4.6=20install+custom?=
 =?UTF-8?q?=20GREEN=20(re-pin=20+=20healthcheck=20overlay=20both=20work,?=
 =?UTF-8?q?=20pr5)=20=E2=80=94=20next:=20=C2=A74.3=20create-topic=20+=20fu?=
 =?UTF-8?q?ll=20lifecycle=20=E2=86=92=20claim?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 machine-docs/STATUS-2.md | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/machine-docs/STATUS-2.md b/machine-docs/STATUS-2.md
index 8187ad2..23359ce 100644
--- a/machine-docs/STATUS-2.md
+++ b/machine-docs/STATUS-2.md
@@ -1064,3 +1064,13 @@ API HTTP 200, wildcard DNS resolves to gateway 143.244.213.108.
   `runner/run_recipe_ci.py::fetch_recipe`. Pre-existing in Phase 1d; not a 1e regression. Drone
   caps `MAX_TESTS=1` today, so practical impact bounded. Tracked for Phase-2 breadth-ramp if
   concurrent recipe runs become routine.
+
+### discourse Q4.6 — UPDATE @2026-05-30: install+custom GREEN (re-pin + healthcheck overlay both work)
+`/root/ccci-discourse-pr5.log` (REF 7b7ddd70bc753608d086884b8de1ad3c327d9ac5, cc-ci HEAD 0e3049b):
+RUN SUMMARY deploy-count=1, **install:pass, custom:pass**. Both fixes proven: (1) bitnamilegacy
+re-pin (PR#1), (2) cc-ci healthcheck-overlay (compose.ccci-health.yml version:"3.8"+app
+start_period:1200s via install_steps + recipe_meta COMPOSE_FILE+CHAOS_BASE_DEPLOY+TIMEOUT/DEPLOY_TIMEOUT
+2400). Earlier failures were: 1800s timeout (slow Rails boot) → bumped timeout+start_period; then lint
+R011/R012 version-mismatch FATA → overlay needed matching version:"3.8". **NEXT:** author ≥2 discourse
+functional (incl §4.3 create-topic) for P3 — currently only health_check; then FULL lifecycle
+(install,upgrade,backup,restore,custom) green → CLAIM Q4.6. NOT yet claimed.