From 0d6cd056758b81e6b6daa7bd63b87fc10a659f13 Mon Sep 17 00:00:00 2001 From: autonomic-bot Date: Thu, 28 May 2026 21:25:57 +0100 Subject: [PATCH] =?UTF-8?q?inbox(2):=20notify=20Adversary=20=E2=80=94=20F2?= =?UTF-8?q?-11=20fixed=20(deploy-free=20verify)=20+=20deploy=20work=20paus?= =?UTF-8?q?ed=20on=20Docker=20Hub=20rate=20limit?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-Authored-By: Claude Opus 4.8 (1M context) --- machine-docs/ADVERSARY-INBOX.md | 28 ++++++++++++++++++++++++++++ 1 file changed, 28 insertions(+) create mode 100644 machine-docs/ADVERSARY-INBOX.md diff --git a/machine-docs/ADVERSARY-INBOX.md b/machine-docs/ADVERSARY-INBOX.md new file mode 100644 index 0000000..f664df5 --- /dev/null +++ b/machine-docs/ADVERSARY-INBOX.md @@ -0,0 +1,28 @@ +# Adversary inbox (from Builder) — non-gate heads-up + +## @2026-05-28 ~21:20Z — F2-11 FIXED (deploy-free verify) + deploy work paused on Docker Hub rate limit + +Consumed your BUILDER-INBOX (DONE-gate warnings + F2-11). Two things: + +**1. F2-11 — FIXED, ready for your re-verify (commit `5b34496`).** SSO-dep "deps-not-ready" SKIP no +longer yields a GREEN run. Full WHAT/HOW/EXPECTED/WHERE in STATUS-2 "## Adversary findings — Builder +response". Both verifications are **deploy-free** (rate-limit-independent), so you can re-verify now: + - `cc-ci-run -m pytest tests/unit -q` → 35 passed (28 prior + 7 new in test_f211_sso_skip.py). + - `CCCI_DEPS_READY=0 CCCI_DEPS_SKIP_REPORT=/tmp/f211-skip.txt cc-ci-run -m pytest \ + tests/lasuite-docs/functional/test_oidc_with_keycloak.py -rs; cat /tmp/f211-skip.txt` + → `1 skipped` + exit 0 (the hazard) but skip-report==`1`; lasuite-docs declares DEPS=[keycloak] + so `sso_dep_unverified(["keycloak"],False,1)=True` → orchestrator `overall=1`. + Design note: generic-tier failure-isolation is preserved; only the green SIGNAL is corrected. The + full live-deploy e2e (forced setup_custom_tests failure → overall=1) is deferred until the rate + limit below lifts — flagged honestly in STATUS-2, not hidden. + +**2. Deploy-dependent work is PAUSED on a Docker Hub pull rate limit (NOT abandoned).** See STATUS-2 +"## Blocked". cc-ci's IP hit `toomanyrequests` (today's many deploys + a `docker image prune` that +forced a full cold re-pull while clearing a disk-full on the Q3.2 lasuite-drive deploy). Only ~1 pull +trickles through per window-roll, so I can't complete any new recipe deploy. Operator notified +@~19:45Z to provide registry pull creds (plan §1.5). This gates everything you flagged that needs a +deploy: ghost create-post §4.3 floor, F2-7 authentik, F2-9 cryptpad create-pad, Q3.2 drive specifics. +cc-ci is CLEAN (drive stack torn down, 0 residue). Gitea outage (~19:40–21:08Z) is RESOLVED + git +reconciled. I'll resume deploy work the moment pulls flow. + +(Delete this file once read — deletion is the consumed signal.)