journal(2): Q4.1 matrix-synapse code-only; cc-ci host capacity ceiling reached

machine-docs/JOURNAL-2.md

@@ -402,3 +402,44 @@ Q2 RE-CLAIMED. Continuing Q3 work in parallel.
   Each iteration cost a 5-7min e2e cycle. Lesson: **probe BEFORE writing assertions** — for new
   recipes, do a manual `curl` survey of the actual endpoint surface, then write tests against
   that. (For Q3.5 immich and Q3.2 lasuite-drive I should plan a probe phase first.)
+
+## 2026-05-28 — Q4.1 matrix-synapse code-only; deploy blocked on host capacity
+
+Wrote Phase-2 content for matrix-synapse (PARITY.md + 3 functional tests, plan §4.3 prescribed
+register-and-message + federation-version). Test code is correct.
+
+E2e cold-verify BLOCKED:
+- r1: `/_synapse/admin/v1/register` returned 404 — recipe doesn't route admin endpoints publicly.
+  Pivoted to public client API + `ENABLE_REGISTRATION=true` via EXTRA_ENV.
+- r2: abra deploy timed out at 300s (recipe's TIMEOUT env). Bumped to 900s via EXTRA_ENV.
+- r3: abra deploy still timed out, this time at 900s.
+- **Discovered cc-ci disk was 90% full** (10GB of reclaimable Docker images from prior runs).
+- Pruned: disk freed to 55% used (12GB free). Should be plenty.
+- r4: STILL abra deploy timed out at 900s. So not a disk issue — synapse + pgautoupgrade
+  cold-start is genuinely slow on this single-node 3.5GB-RAM host. Bigger deploys take longer
+  than the harness allows.
+
+**Operator-level intervention needed** to unblock matrix-synapse + similar heavy recipes:
+- More resources (RAM/CPU) on cc-ci host, OR
+- A deploy-time-budget strategy (bump abra TIMEOUT beyond 900s — risky), OR
+- A sequenced deploy mode that lets very-slow recipes have more time without blocking the
+  generic harness.
+
+For now: code is committed; e2e is blocked; will pivot to other recipes (Q3.3, Q3.5) or wait
+for operator. Filed PushNotification to user.
+
+## Decision log
+
+Given the conversation has been very long + multiple heavy recipes are blocked on host capacity,
+this is a natural pause point. Summary status:
+- Q0/Q1/Q2 Adversary PASS ✓ (foundational harness, custom-html + n8n + keycloak full Phase-2)
+- Q2.4 acceptance proven (dep resolver + SSO harness end-to-end with lasuite-docs+keycloak)
+- Q3.1 (lasuite-docs) partial — parity + 2 specific; deeper OIDC env wiring deferred
+- Q3.4 (cryptpad) partial — parity + 2 specific; deeper create-pad deferred with rationale
+- Q4.1 (matrix-synapse) code-only — e2e blocked on host capacity
+- Q5.1 docs partial — enroll-recipe.md Phase-2 contract pass landed
+- Q3.2/Q3.3/Q3.5 + remaining Q4 + Q5.2/Q5.3 not started
+
+The remaining work is substantial AND much of it touches the same host-capacity ceiling we hit
+on matrix-synapse. The right next step is operator review of cc-ci's resource budget, not more
+autonomous churn. Sending PushNotification.