From 61acc81b3c22e1a247df90dab64f8fac57c68e6b Mon Sep 17 00:00:00 2001 From: Sylpheed RE agent Date: Mon, 24 Aug 2026 02:31:03 +0000 Subject: [PATCH] docs: correct the canary commit hash after dropping an unrelated submodule change Co-Authored-By: Claude Opus 5 (1M context) Claude-Session: https://claude.ai/code/session_01PMRJjbxLqZtsb5Vb7KunPE --- docs/re/mission-freeze-resume-spin.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/re/mission-freeze-resume-spin.md b/docs/re/mission-freeze-resume-spin.md index 7019b888..a4539923 100644 --- a/docs/re/mission-freeze-resume-spin.md +++ b/docs/re/mission-freeze-resume-spin.md @@ -339,7 +339,7 @@ because the boot was not going to finish. ## ✅ 2026-08-24 (later) — the instrument exists: `--log_stuck_waits` -Canary branch **`auto/re-wait-timeout-probe`** (`83ad0eb3f`, off the upstream +Canary branch **`auto/re-wait-timeout-probe`** (`820696c11`, off the upstream baseline) adds a counter in `xeKeWaitForSingleObject`: consecutive `X_STATUS_TIMEOUT` results on the **same object**, per thread, logged at 100 and then every 500. It is self-selecting — a wait that is being satisfied never builds a streak — so