journal(redfix): M1 mumble isolation GREEN — load/timing flake confirmed

machine-docs/JOURNAL-redfix.md

@@ -95,3 +95,21 @@ restore__cc-ci__test_restore.xml.
 Tooling note: my background "waiter" loop `while pgrep -f run_recipe_ci.py` self-matched (its own
 cmdline contains the string) → never exited, falsely showed a run active. Use `pgrep -f
 "[r]un_recipe_ci.py"` or match the python invocation. Killed the stuck waiters; node confirmed free.
+
+## 2026-06-18T00:18Z — M1: mumble isolation run — GREEN (flake confirmed)
+
+Ran mumble ALONE (tag 1.0.0+v1.6.870-0, log /tmp/redfix-mumble.log). RESULT: **ALL tiers PASS**
+(install/upgrade/backup/restore/custom), including `custom/test_protocol_handshake.py::
+test_handshake_completes_with_channel_presence` PASSED. No orphan stacks. The canon sweep recorded
+this RED (`test_handshake…` failed under concurrent sweep load); it is GREEN here in isolation, and
+its canonical was already written green TODAY (1.0.0+v1.6.870-0 @20260617T180501Z) under the lighter
+nixenv sweep. → **load/timing FLAKE** on the control-channel handshake, NOT a recipe defect.
+
+The handshake test already retries (`retry_handshake(attempts=12, interval=5.0)` = 60s). So the flake
+is the voice server not completing the TLS+ServerSync handshake within ~60s under heavy concurrent
+node load (deploy contention). M2 fix = harness stabilization (stronger readiness gate before the
+custom tier / longer-or-smarter retry / serialize), based on the load failure mode. Classification:
+**FLAKE (load/concurrency)** → harness stabilization.
+
+Reproducibility: 1 green isolation run here + canonical green today + documented red under canon load.
+Will do 1–2 more isolation repeats before the M1 claim to firm "reproducibly green in isolation."