review(prevb): M1 e2e GREEN confirmed cold (head=official 3.5.3, sidekiq dropped, clean teardown); break-it re-launched after SIGTERM

machine-docs/REVIEW-prevb.md

@@ -64,8 +64,18 @@ Done so far (cold):
 - CONCURRENCY observed: a Builder keycloak spot-check (PR#3) runs simultaneously in `/root/prevb-deploy`. My
   discourse run's janitor saw the keycloak lock and LEFT IT (`live concurrent run, leaving it`) — per-run
   ABRA_DIR isolation holding. Watching for memory-pressure false-failures on the shared 7GB node.
-STILL TO CONFIRM: head ran official `discourse/discourse:3.5.3` (not bitnamilegacy) + sidekiq gone + upgrade GREEN
-+ clean teardown; then a deliberately-broken-head BREAK-IT probe → upgrade RED.
+UPDATE 2026-06-17T01:00Z (post-reboot, cold re-check of completed run):
+- e2e `manual-1344943` COMPLETED **GREEN** (read full log /root/cc-ci-adv-prevb-e2e.log): `upgrade base:
+  kind=ref ref=f87c612d71b4 (target-branch (main) tip)`; `upgrade→PR-head head_ref=ae5a8180`;
+  generic `test_upgrade_reconverges` PASSED; discourse `test_head_runs_official_image_not_bitnamilegacy`
+  PASSED + `test_sidekiq_service_dropped_by_head` PASSED; RUN SUMMARY deploy-count=1 (expect 1),
+  install:pass upgrade:pass, level=2/5. Matches STATUS EXPECTED exactly.
+- TEARDOWN clean: `docker stack ls` shows NO discourse stack; no discourse secrets/volumes. (warm-keycloak
+  stack present = Builder's concurrent spot-check, not mine.)
+- BREAK-IT: my first probe (`manual-1357729`, broken-head ref 94ebaaa = head image
+  `discourse/discourse:99.99.99-adversary-broken`) was SIGTERM-killed mid-base-deploy by MY reboot — INCOMPLETE.
+  RE-LAUNCHED as `manual-1360025` (same broken head, base resolving to main-tip f87c612d as expected). In flight.
+STILL TO CONFIRM: break-it `manual-1360025` → upgrade tier RED (broken head not papered over).
 
 ## Verdicts
 (none yet — M1 cold acceptance in flight)