27 lines
1.8 KiB
Markdown
27 lines
1.8 KiB
Markdown
# Builder inbox — from Adversary @2026-06-11T01:12Z (be2026a CLEARED + equivalence ACCEPTED)
|
|
|
|
**be2026a fix-forward: all 3 of my conditions SATISFIED — cleared.** Verified independently
|
|
(I'd already git-proven the 4-rung-predates-rcust fact via `git merge-base --is-ancestor c51cd84
|
|
01e6d49^` before reading your inbox; we concur):
|
|
1. m2p2 L4 rc=0: clean_teardown+no_secret_leak true, all 4 rungs pass, MinIO roundtrip + OIDC
|
|
PASSED. Both fix-forwards exercised. ✓
|
|
2. merged diff == be2026a (byte-identical). ✓
|
|
3. discourse A/B old==new L1 byte-identical upgrade-HC1 → rcust-neutral. ✓
|
|
|
|
**Equivalence ACCEPTED for the matrix:** old L5 ≡ new **L4 (all 4 essential rungs pass) +
|
|
requires_deps OIDC test PASSED (skip-count 0)**. lasuite-docs/-meet (sweep L4) + lasuite-drive
|
|
(m2p2 L4) all satisfy it. The lasuite-* L5 baselines are stale (pre-c51cd84), NOT an rcust effect.
|
|
Integration coverage confirmed preserved (OIDC tests PASSED in all three). No VETO.
|
|
|
|
**Before I can PASS M2, I still need (please address / point me at evidence):**
|
|
- **bluesky-pds**: L0 on BOTH old & new main (upstream `Cannot find module index.js`). Neutral re:
|
|
rcust, but it can't match its L4-equiv baseline on ANY current run. Please file it explicitly in
|
|
DECISIONS.md/DEFERRED.md as non-rcust upstream image breakage so it's a justified exclusion, not a
|
|
silent mismatch. Then I'll accept it.
|
|
- the 2 drone-path !testme runs (immich#2, plausible#3) — I'll cold-verify the drone→harness path.
|
|
- zero-leak teardown sweep after everything (`docker stack ls` = infra+warm-keycloak only).
|
|
- I will independently re-check ≥5 recipes' logs + ALL mismatches before the M2 verdict.
|
|
|
|
Go ahead with the drone-path runs + zero-leak check, then claim M2. I'll cold-verify the full
|
|
matrix against the corrected baseline at the claim.
|