M6.5: lasuite-docs (recipe #5, multi-service+S3) full 3-stage green; TIMEOUT fix; Drone #57 in flight

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

JOURNAL.md

@@ -588,3 +588,25 @@ backups too). Triggering the canonical Drone recipe-ci run.
 4 of 6 D10 recipes now green: custom-html (simple), keycloak (SSO/DB), cryptpad (stateful/no-DB),
 matrix-synapse (DB+media/large-volume). Remaining categories: multi-service+S3 (lasuite-docs) and
 TLS-passthrough (bluesky-pds).
+
+---
+## 2026-05-27 — M6.5: lasuite-docs (recipe #5, multi-service + S3/MinIO) full 3-stage green
+
+Enrolled lasuite-docs (the object-storage/S3 + multi-service D10 category): a 9-service stack
+(frontend app + Django backend + celery + y-provider + docspec + postgres + redis + minio + nginx).
+Host runs (cc-ci-run): install **2 passed** (~2.5m; SPA served + Playwright), upgrade **1 passed**
+(~3m; postgres marker survives previous→current, incl. cold-pulling the older images), backup
+**1 passed** (~2.3m; pg_backup.sh dump/restore). Clean teardown.
+
+Root-caused the initial deploy timeout: cold-pulling ~9 large images (impress frontend/backend,
+minio, postgres18, docspec, y-provider, redis) exceeds abra's default 300s convergence TIMEOUT →
+`FATA deploy timed out 🟠`. A manual deploy confirmed the stack converges 9/9 once images are pulled.
+Fix: bump the recipe TIMEOUT to 900 via the generic EXTRA_ENV mechanism (no harness surgery). OIDC is
+config-only (Django `manage.py check` validates but doesn't fetch), so the stack starts healthy with
+placeholder OIDC; login isn't exercised in CI (documented in recipe_meta). Data-survival uses a
+postgres marker (docs/docs) via the pg_backup hook.
+
+5 of 6 D10 recipes green: custom-html (simple), keycloak (SSO/DB), cryptpad (stateful/no-DB),
+matrix-synapse (DB+media/large-volume), lasuite-docs (multi-service + S3/MinIO). Remaining: a
+TLS-passthrough recipe (bluesky-pds) for the 6th, which needs cc-ci Traefik passthrough config
+(plan §4.0 caveat) — the hardest infra-wise.