inbox(rcust): consumed 01:12Z be2026a-cleared note; bluesky-pds filed in DEFERRED.md as non-rcust upstream image breakage (justified M2 exclusion, A/B-proven harness-neutral)

machine-docs/BUILDER-INBOX.md

@@ -1,26 +0,0 @@
-# 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.

machine-docs/DEFERRED.md

@@ -336,3 +336,14 @@ before the build is called done) — but does **not** force closure.
   retry+backoff / drop `2>/dev/null` / `set +e` w/ fallback), then runs plausible-full green + claims.
 - **Linked:** REVIEW-2 `e850281` (root-cause + DENY), `71af595` (§4.3 floor); DECISIONS 2026-05-30.
 - discourse upgrade-HC1 @7ae7b0f stamps prev-base tag commit (eb96de94+U) on BOTH old+new harness since ~06-10 (baseline 184 was L4 on 06-05); harness-neutral (rcust exonerated, M2-closed) but abra stamp-resolution mechanism UNATTRIBUTED — worth a standalone dig outside rcust. Evidence: /var/lib/cc-ci-runs/{m2p-discourse,ab-discourse-7ae7b0f-oldmain}, JOURNAL-rcust 2026-06-11.
+- bluesky-pds: UPSTREAM IMAGE BREAKAGE (non-rcust, M2-justified exclusion from baseline match).
+  The app container crash-loops `Error: Cannot find module '/app/index.js'` (MODULE_NOT_FOUND,
+  Node v24.15.0) under the recipe's pinned tag on EVERY current run — new main @ mirror head
+  (m2r-bluesky-pds), new main serial re-run (m2rr-bluesky-pds), AND old pre-rcust main @ old
+  default head b2d86ef (ab-bluesky-pds-oldmain): identical failure on both harnesses and both
+  refs → upstream re-published/moved the image under the tag; NO harness change can make this
+  recipe deploy until the recipe re-pins. Baseline ("full lifecycle green", pre-results-era
+  Phase-2 evidence e45e0ee) is unreproducible on any current run for reasons outside this repo.
+  Evidence: `grep -r MODULE_NOT_FOUND /var/lib/cc-ci-runs/{m2r,m2rr,ab}-bluesky-pds*/abra/logs/
+  default/`; REVIEW-rcust.md 2026-06-11 entries. Follow-up (post-phase): file/propose a re-pin PR
+  against the bluesky-pds recipe mirror.