M10 finding: Docker Hub rate limit blocks lasuite-docs upgrade — A1 registry creds needed (5/6 green)

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

JOURNAL.md

@@ -708,3 +708,15 @@ Fired !testme on all 6 recipe PRs (capacity=1, sequential). Results (real PR-tri
 So the real-!testme path + the upgrade fixes (upstream tags + `upgrade -o`) work across simple, DB,
 DB+media, workflow, and stateful recipes. lasuite-docs (the object-storage/S3 category, required)
 needs its upgrade to pass on the real path for the 6/6 D10 proof.
+
+---
+## 2026-05-27 — M10: 5/6 real-!testme green; lasuite-docs blocked on Docker Hub rate limit (A1)
+
+lasuite-docs #88/#92 upgrade failed "deploy failed" → diagnosed: node disk at 90% (2.7G free) — a
+9-service rolling upgrade couldn't converge. Pruned 30 unused images (reclaimed 12GB → 15G free).
+Retry #93: got further (5/8 services up) but redis task Rejected "No such image: redis:8.2.6" →
+`docker pull redis:8.2.6` on the node = `toomanyrequests: unauthenticated pull rate limit`. So the
+prune fixed disk but forced re-pulls that hit Docker Hub's anonymous limit (A1 registry-creds
+finding, §1.5/§4.4). Recorded in STATUS ## Blocked + DECISIONS; surfaced to operator (provide Docker
+Hub creds). 5/6 recipes green via real !testme; lasuite install+backup green, upgrade gated.
+Pivoting to M9 (docs/reproducibility, unblocked) while the limit resets / creds arrive.