claim(bsky): M2 — operator handoff complete: green re-triggerable at PR#2 head f7b6c8df (run 427 level 5), PNG published, level/baseline reconciled, DEFERRED closed (f150012), operator summary in STATUS; PR left open for operator

BACKLOG-bsky.md

@@ -11,7 +11,7 @@
 - [x] B7: Claim M1 (root cause + green fix PR + screenshot verified)
 - [ ] B8: Close DEFERRED bluesky entries with pointers; JOURNAL note updating shot-phase N/A disposition
 - [ ] B9: Operator handoff summary in STATUS-bsky.md (what was wrong, what the PR changes, post-merge expectations incl. canonical/warm reseed)
-- [ ] B10: Claim M2
+- [x] B10: Claim M2
 
 ## Adversary findings
 

JOURNAL-bsky.md

@@ -102,3 +102,11 @@ recipe.
 Canonical/warm check: /var/lib/ci-warm has NO bluesky-pds dir → no canonical to reseed
 post-merge; the normal promote-on-green flow will mint one on the first green run after
 merge. Operator summary written to STATUS-bsky.md (B9).
+
+## 2026-06-11T15:50Z — M1 PASS received; M2 claimed (B10)
+
+M1 PASS @12:30Z (REVIEW-bsky 369f4f4), no findings, no VETO — every item reproduced cold
+incl. negative-control teeth and the per-recipe scoping of the EXPECTED_NA change. (Gap
+12:30→15:45 was a quota window, not work.) All M2 builder-side items were already in
+place (DEFERRED f150012, operator summary cba53b6); claimed M2 with re-trigger
+instructions for the fresh cold pass. Phase DoD after M2 PASS → ## DONE with PR open.

STATUS-bsky.md

@@ -2,7 +2,37 @@
 
 Phase SSOT: /srv/cc-ci/cc-ci-plan/plan-phase-bsky-fix.md
 
-Gate: M1 — CLAIMED, awaiting Adversary.
+Gate: M2 — CLAIMED, awaiting Adversary (M1: PASS @2026-06-11T12:30Z, REVIEW-bsky 369f4f4).
+
+## M2 claim — operator handoff complete (2026-06-11T15:50Z)
+
+WHAT (phase plan §3 M2, all builder-side items in place; the fresh cold pass is yours):
+1. **Green at PR head, re-triggerable:** PR #2 head f7b6c8df unchanged since run 427
+   (level 5). HOW to re-run independently: post `!testme` on PR #2 — the bridge polls
+   ~1 min, triggers a drone build, run dir /var/lib/cc-ci-runs/<n>. EXPECTED: level=5,
+   rungs install/backup_restore/functional/lint=pass, upgrade=skip with
+   skips.intentional.upgrade = the declared reason, clean_teardown+no_secret_leak=true,
+   screenshot.png = the PDS landing page. (cc-ci main also unchanged functionally since
+   e9745c8; HEAD at claim time: see this commit.)
+2. **PNG to independently Read:** https://ci.commoninternet.net/runs/427/screenshot.png
+   (+ the fresh run's, if you re-trigger). EXPECTED: ASCII Bluesky butterfly landing
+   page, no credentials.
+3. **Level under new semantics + baseline reconciled:** achieved level 5 (de-capped:
+   skip climbs), upgrade = declared intentional skip with re-enable path. Old baseline
+   "full lifecycle green" (Phase-2 e45e0ee, pre-results-era) reconciled: unreproducible
+   for upstream reasons (moving-tag republish broke ALL published versions); the PR
+   restores deployability; recorded in DEFERRED closure + JOURNAL-bsky 12:15Z entry.
+4. **DEFERRED entries closed with pointers:** machine-docs/DEFERRED.md bluesky entry
+   marked RESOLVED @2026-06-11 (commit f150012) — explicitly closes BOTH the re-pin
+   follow-up and the rcust M2 baseline-exclusion note, with PR/run/registry pointers.
+5. **Operator summary:** below in this file (what was wrong / what the PR changes /
+   post-merge steps 1-5 incl. version publish, EXPECTED_NA→UPGRADE_BASE_VERSION swap,
+   no canonical to reseed, never re-pin :0.4).
+6. **PR left OPEN** for the operator (merged=false; immich PR#2/plausible PR#3 precedent).
+
+WHERE: cc-ci main (STATUS/JOURNAL/BACKLOG-bsky, DEFERRED f150012, DECISIONS 2026-06-11
+×2, harness e9745c8); mirror PR #2 head f7b6c8df; runs 427 (green) / 423 (negative
+control); upstream registry cc-ci-plan/upstream/bluesky-pds.md @ f395247.
 
 ## M1 claim — root cause + green fix PR + screenshot (2026-06-11T12:05Z)