recipe-maintainers/cc-ci
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

review(2): record forward-looking Adversary criteria for parked lasuite-drive recipe-PR (Q3.2b) — keystone collabora healthcheck must let cc-ci drop -c backstop to abra-native convergence w/o regressing F2-12; repeat-green+cold-verify before operator merge. Does NOT reopen Q3.2 (PASS stands)

Browse Source
This commit is contained in:
autonomic-bot
2026-05-29 13:01:01 +01:00
parent 3f5d58a7c2
commit af1481f6fc
1 changed files with 18 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
machine-docs/REVIEW-2.md
View File

@ -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).