From af1481f6fc579e768fb639a6e710190a63f487db Mon Sep 17 00:00:00 2001 From: autonomic-bot Date: Fri, 29 May 2026 13:01:01 +0100 Subject: [PATCH] =?UTF-8?q?review(2):=20record=20forward-looking=20Adversa?= =?UTF-8?q?ry=20criteria=20for=20parked=20lasuite-drive=20recipe-PR=20(Q3.?= =?UTF-8?q?2b)=20=E2=80=94=20keystone=20collabora=20healthcheck=20must=20l?= =?UTF-8?q?et=20cc-ci=20drop=20-c=20backstop=20to=20abra-native=20converge?= =?UTF-8?q?nce=20w/o=20regressing=20F2-12;=20repeat-green+cold-verify=20be?= =?UTF-8?q?fore=20operator=20merge.=20Does=20NOT=20reopen=20Q3.2=20(PASS?= =?UTF-8?q?=20stands)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- machine-docs/REVIEW-2.md | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/machine-docs/REVIEW-2.md b/machine-docs/REVIEW-2.md index f1b62dd..e0b6de4 100644 --- a/machine-docs/REVIEW-2.md +++ b/machine-docs/REVIEW-2.md @@ -947,3 +947,21 @@ canonical volumes intact. deploy-count=1 (HC1 in-place upgrade, not a 2nd instal **Verdict: Q3.2 PASS. F2-12 CLOSED.** No `## VETO`. Anti-anchoring honored (verdict from plan + code + my own run; did not read JOURNAL first). Remaining open Adversary item: cryptpad F2-9 create-pad (separate cold-verify pending — Builder's `05d0dc1` test + its full-suite run). + +## @2026-05-29 — (forward-looking, NOT active) Adversary criteria for lasuite-drive recipe-PR (Q3.2b) +Orchestrator queued `cc-ci-plan/plan-lasuite-drive-recipe-pr.md` — a recipe-maintainer PR fixing +lasuite-drive at the SOURCE: (1) **collabora healthcheck + start_period [KEYSTONE]** — makes abra's OWN +convergence wait correct, fixing F2-12 at source so cc-ci can DROP the `-c`/READY_PROBE backstop and +return to abra-native convergence; (2) backend retry/wait for collabora WOPI; (3) gunicorn-perms +startup-race fix; (4) lazy/retrying OIDC discovery. Explicitly **PARKED behind my current Q3.2 work — +not active now.** Recording the bar I will enforce when it IS claimed: +- **Merge rule (operator):** the recipe PR is "working" ONLY when cc-ci runs the **FULL suite (incl. + the upgrade tier) on that PR, repeatedly GREEN + Adversary cold-verified** — then the operator merges. + So I require repeat-green on the PR + my own cold re-run reading the assertions (same bar as Q3.2). +- **Post-merge revert check:** after merge, the lasuite-drive `-c`/READY_PROBE workaround must be + **reverted to abra-native convergence** (per the §9 guardrail: prefer abra's own checks; the backstop + was only because abra didn't fit). I will verify the upgrade tier stays GREEN under abra-native + convergence once the keystone healthcheck lands — i.e. the `-c` removal doesn't regress F2-12. +- Real-abra-only still applies; the keystone is a recipe `compose.yml` healthcheck (real), not a CI patch. +This does NOT reopen Q3.2 (PASS stands, F2-12 CLOSED) — it's a separate future gate (Builder parked it +as Q3.2b @ ac241d4).