journal(redfix): M2 mumble VERIFIED (4/6); bluesky force-chaos verification plan

machine-docs/JOURNAL-redfix.md

@@ -420,3 +420,24 @@ warm-canon-keycloak for WARM_DOMAINS recipes; WARM_CANONICAL=True). RESULT: all
 - warm-canon-keycloak = 404 now = CORRECT idle state (data-warm canonical undeployed, volume kept).
 So keycloak is now a full data-warm canonical with zero risk to the live SSO. **FIXED + verified.**
 3/6 verified: mattermost-lts, discourse, keycloak. Doing mumble next (harness, tractable).
+
+## 2026-06-18T03:50Z — M2 mumble VERIFIED (stabilization); 4/6 done
+
+Ran mumble from branch checkout (handshake budget attempts=36/180s). ALL tiers PASS incl
+test_handshake_completes_with_channel_presence; promote succeeded (canonical 1.0.0+v1.6.870-0 idle).
+The longer budget is active + non-regressing. NOTE: mumble is green in isolation regardless of budget
+(the 60s sufficed in isolation); the budget matters UNDER LOAD, which is hard to reproduce
+deterministically — so this verifies the stabilization is applied + sound + non-weakening, not a literal
+load-flake repro. (M1 already established green-isolation/red-under-canon-load; the fix gives the
+handshake 3x the readiness window.) **Stabilization fix verified.** 4/6: mattermost, discourse,
+keycloak, mumble. Remaining: bluesky (force-chaos verify of the rename), gitea (rework).
+
+## 2026-06-18T03:52Z — M2 bluesky force-chaos verification approach
+
+bluesky's rename can't deploy via the normal path (annotated tag -> non-chaos -> abra checks out the
+tag, reverting the rename). In PRODUCTION post-merge the new tag would carry the rename (non-chaos
+deploys it fine). For PRE-merge verification I force chaos via a temporary tests/bluesky-pds/
+compose.ccci.yml scaffold on the branch (has_ccci_overlay -> deploy_app uses chaos -> deploys my
+renamed checkout). Then cold goes green (service pds + branch exec-refs) and the promote deploys the
+renamed recipe at warm-bluesky-pds via chaos -> caddy resolves the unique `pds` -> expect 200 (vs M1
+000). The overlay is a verification scaffold (NOT part of recipe PR #4); removed after.