status(rcust): M1 PASS — merged to main 01e6d49, push build 326 green; M2 canaries running, sweep driver staged

STATUS-rcust.md

@@ -77,7 +77,19 @@ sweep runs, not retroactively here.
 
 ## Gate
 
-**Gate: M1 CLAIMED, awaiting Adversary** (claimed 2026-06-10, branch head 858e0f5)
+**Gate: M2 IN PROGRESS** — M1 PASS in REVIEW-rcust.md (01f9f70, 2026-06-10).
+
+- M2.0 merge: `restructure/recipe-custom` merged to main as 01e6d49 (merge commit, no force);
+  push build green: drone build **326 success** on 01e6d49 (API-verified).
+- M2.2 canary suite: running on cc-ci from a FRESH clone of merged main at /root/m2-sweep
+  (`cc-ci-run -m pytest tests/regression -m canary -v`, log /root/m2-canary.log). First canary
+  good-simple PASSED; 7 total expected.
+- M2.3 per-recipe sweep: driver staged at /root/m2-driver.sh on cc-ci (max 2 concurrent, all 21
+  dirs, REF = mirror default-branch heads recorded in the driver); launches after canaries
+  complete. Logs: /root/m2-logs/<recipe>.log, results under /var/lib/cc-ci-runs/.
+- Drone→harness path: !testme on two open recipe PRs planned after the direct sweep.
+
+**Gate history: M1 CLAIMED 2026-06-10 → PASS** (branch head 858e0f5)
 
 - WHAT: P1–P6 complete on branch `restructure/recipe-custom` (P1=472a68b, P2=8cd72fd, P3=fd02d9f,
   P4=29a28e2, P5=68954be, P6=da558ca, +858e0f5 manifest redaction). Working tree clean, all pushed.