journal(2): discourse full6 all-green except create-topic category bug; fixed (1f92776); full7 relaunched

machine-docs/JOURNAL-2.md

@@ -1558,3 +1558,21 @@ runner/run_recipe_ci.py` → `/root/ccci-discourse-full6.log`, PID 50718. Stages
 restore,custom (full upgrade-to-latest, required by the DONE VETO). prepull rc=15 (dangling
 `sidekiq.depends_on:[discourse]`) is the known-harmless lint failure — image pre-cached, inline pull a
 no-op. Polling ~5min per §7 case 1.
+
+---
+## 2026-05-31T04:5xZ — discourse full6 DONE (1 test bug) → fixed → full7 launched (Builder)
+**full6 result** (`/root/ccci-discourse-full6.log`, deploy-count=1, REF 3758522):
+- install: PASS · **upgrade: PASS** (upgrade-to-latest, the DONE-VETO requirement) · backup: PASS ·
+  restore: PASS (P4 ci_marker survived) · **custom: FAIL — only `test_create_topic_roundtrip`**
+  (health_check + site_basic PASS). Clean teardown (0 stacks/volumes).
+- backup tier: `backup-verify FAILED (attempt 1/3) → re-ran → PASS` — the chaos-upgrade db-cycle race
+  (same class ghost hit); BACKUP_VERIFY retry converged, non-vacuous. `/pg_backup.sh No such file` on
+  attempt 1 was the racing db restart (pre-hook script present at PR head, exec hit a cycling container).
+- create_topic failure was a **TEST BUG not an app defect**: Discourse 3.x disables uncategorized
+  topics by default → `POST /posts.json` w/o category 422s `"Category can't be blank"`. mint_admin
+  worked (ruby-PATH fix `8d689d6` confirmed good).
+**Fix** (`1f92776`): enable `SiteSetting.allow_uncategorized_topics = true` in the existing Rails admin
+bootstrap (`_discourse.py _BOOTSTRAP_RB`). Standard Discourse feature toggle, config-parity with a real
+forum — NOT a weakening: the round-trip still posts a real topic + asserts a unique body marker survives
+read-back. **full7** relaunched full lifecycle (`/root/ccci-discourse-full7.log`, PID 57983, builder-clone
+@1f92776). On all-green → CLAIM Q4.6 (closes the discourse portion of the DONE VETO). Polling ~5min.