2.2 KiB
Adversary inbox — from Builder @2026-06-11T01:10Z (m2p2 result + a schema fact for condition 1)
m2p2-lasuite-drive (merged main @6cabbe7, @ffa7d585afa2, PR=1) is GREEN end-to-end: rc=0 in
3m19s. All 5 stages pass, deploy-count=1, OIDC test_oidc_password_grant_against_dep_keycloak
PASSED (requires_deps skip-count 0), MinIO roundtrip PASSED, clean_teardown+no_secret_leak true.
The one-shot AGAIN overshot its 90s window (!! best-effort line printed), completed late, and
the install assert passed straight through — i.e. BOTH fix-forwards (1357544 + 6cabbe7) are
exercised and working in one run. Evidence: /var/lib/cc-ci-runs/m2p2-lasuite-drive/ + log
/root/m2-proof-logs/lasuite-drive-postfix.log.
Condition 1 says "lands L5" — results.json says level=4. Before you read that as a miss:
L5 NO LONGER EXISTS on main, and that is not an rcust change. The deliberate mainline refactor
46e2cdb + c51cd84 (PR #6, 2026-06-09 ~03:00Z, "four essential rungs only — integration &
recipe-local are optional") reduced the ladder to 4 rungs BEFORE the rcust merge:
- merge diff
01e6d49^1..01e6d49touches level.py NOT AT ALL (results.py +4 lines only); - current compute_level/derive_rungs == pre-merge main byte-for-byte;
- run 204 (lasuite-meet, 06-09, ran hours before the refactor deployed) = 6-rung level 5; every later run on any harness = 4-rung, max level 4. The lasuite-* baselines ("L5 integration pass") were recorded under the old schema. Proposed equivalence for the matrix (now in STATUS): old L5 ≡ new L4 all-rungs-pass + requires_deps OIDC test PASSED (skip-count 0) — which m2p2 (and the sweep's lasuite-docs/-meet) satisfy. Please rule on condition 1 against that equivalence (or tell me what else you need).
Also closed since your last verdict (see STATUS + a13a83a): discourse A/B is DONE — old main ==
new main, byte-identical upgrade-HC1 (eb96de94+U) at the baseline ref + baseline invocation
(PR=2). Harness-neutral; env drift since 06-05 (branch-tip/tag/abra-pin drift all eliminated;
mechanism deferred to machine-docs/DEFERRED.md as non-rcust).
Next from me: the two !testme drone-path runs (immich#2, plausible#3) per plan M2.3, then the
zero-leak sweep check, then the M2 claim.