claim(prevb): M2 — discourse PR#4 !testme GREEN in real CI (Drone 717, all 5 tiers, head=official 3.5.3); 3 spot-checks green under dynamic base

machine-docs/JOURNAL-prevb.md

@@ -132,3 +132,20 @@ test_head_runs_official_image_not_bitnamilegacy + test_sidekiq_service_dropped_b
 teardown (no discourse stacks). This is the M2 headline: the migration is REALLY tested in real CI.
 
 Launching hedgedoc #1 as the 3rd spot-check (cryptpad #5 + keycloak #3 already green). Then reconcile + claim M2.
+
+## 2026-06-17T01:40Z — hedgedoc spot-check green; CLAIMING M2
+
+hedgedoc #1 (3rd spot-check): kind=ref main-tip 09bf4d54; install:pass upgrade:pass; clean teardown.
+3 spot-checks now green under dynamic base (cryptpad/keycloak/hedgedoc), all main-tip — no regression.
+
+discourse 717 results.json level=4/5. The 5th level is capped by the discourse *recipe* lint rung (R011)
+— a rung not a gate, and a recipe-level nit on the PR head (not cc-ci/prevb). The run is GREEN (bridge
+"✅ passed", all 5 functional tiers junit 0-fail). Not fixing the recipe's R011 here (recipe defect → not
+our test to weaken; out of prevb scope).
+
+Records reconciliation: 717's artifacts (results.json/junit/badge/summary/screenshot) are durable at
+/var/lib/cc-ci-runs/717/ (host-shared, Adversary-readable); the bridge mirrored the outcome to PR#4.
+No warm canonicals to reconcile (none exist). Pre-existing warm-keycloak orphan left untouched (not prevb).
+
+Claiming M2. Adversary cold-verifies (re-read 717 junit / re-trigger !testme / re-run a spot-check); then
+I write ## DONE once REVIEW-prevb shows fresh M1+M2 PASS with no VETO.