status(2): discourse full5 in flight — warm image cache + 3600s timeout fix base-deploy timeout

machine-docs/STATUS-2.md

@@ -94,7 +94,17 @@ Standing VETO on DONE (REVIEW-2 @16:22:07Z) requires: ghost + discourse + mumble
 **upgrade-to-latest** green with justified `compose.ccci.yml` overlays. Current cycle:
 - **ghost F2-14b — ✅ Adversary PASS @2026-05-30T22:42Z (REVIEW-2, COLD, `/root/adv-ghost-f214b.log`).**
   Closes the GHOST portion of the DONE VETO checklist. DONE.
-- **discourse Q4.6 — TWO bugs root-caused + fixed, VALIDATING (full4).** Investigation across full1-3:
+- **discourse Q4.6 — VALIDATING (full5 @2026-05-31T01:2xZ, REF 3758522, builder-clone `8dfd8ed`).**
+  full4 FAILED at BASE deploy: `abra app deploy` timed out at 2400s (install:fail, rest skip). NOT a
+  config break — full2 base-deploy SUCCEEDED with the identical overlay (swarm ignores the recipe's
+  dangling `sidekiq.depends_on:[discourse]`; it only breaks the `config --images` prepull lint → image
+  pulled inline). full4 was at the convergence edge because (a) the image was cached as
+  `bitnamilegacy/discourse:<none>` (tag dangling) so the deploy re-pulled 2.4GB, and (b) the node is
+  **7 GiB RAM** (not 28) with load 6-7 on 4 vCPU during Rails asset-precompile → 40min too tight.
+  full5 fixes: pre-cached `bitnamilegacy/discourse:3.3.1` by TAG on cc-ci (inline pull now a no-op) +
+  `DEPLOY_TIMEOUT`/`TIMEOUT` 2400→3600 (recipe_meta, commit `8dfd8ed`). Log `/root/ccci-discourse-full5.log`.
+  Carries the full1-3 fixes (BACKUP_VERIFY backup-race probe + mint_admin ruby PATH, `8d689d6`).
+  Original full1-3 investigation:
   - **(A) backup race — backup.sql not captured after the upgrade tier.** restic snapshots of full1/full2
     (WITH upgrade) lacked `postgresql_data/backup.sql` entirely (only discourse_data+redis_data); the
     recipe's backupbot db pre-hook `/pg_backup.sh backup` didn't produce the dump at backup time, so