diff --git a/.openclaw-sync/source.json b/.openclaw-sync/source.json
index 651e3e2da..9ad4929db 100644
--- a/.openclaw-sync/source.json
+++ b/.openclaw-sync/source.json
@@ -1,5 +1,5 @@
 {
   "repository": "openclaw/openclaw",
-  "sha": "0131343db8c613ecdbd8853af8044153baa74c04",
-  "syncedAt": "2026-05-05T01:17:46.647Z"
+  "sha": "c84b7cbffcc305aafa2b9927c6aadf3579a98e4b",
+  "syncedAt": "2026-05-05T01:30:09.597Z"
 }
diff --git a/docs/ci.md b/docs/ci.md
index 6c67eb6e1..dbdffeea4 100644
--- a/docs/ci.md
+++ b/docs/ci.md
@@ -199,7 +199,7 @@ Docker release-path soak; `full` forces soak on.
 
 The umbrella records the dispatched child run ids, and the final `Verify full validation` job re-checks current child run conclusions and appends slowest-job tables for each child run. If a child workflow is rerun and turns green, rerun only the parent verifier job to refresh the umbrella result and timing summary.
 
-For recovery, both `Full Release Validation` and `OpenClaw Release Checks` accept `rerun_group`. Use `all` for a release candidate, `ci` for only the normal full CI child, `plugin-prerelease` for only the plugin prerelease child, `release-checks` for every release child, or a narrower group: `install-smoke`, `cross-os`, `live-e2e`, `package`, `qa`, `qa-parity`, `qa-live`, or `npm-telegram` on the umbrella. This keeps a failed release box rerun bounded after a focused fix.
+For recovery, both `Full Release Validation` and `OpenClaw Release Checks` accept `rerun_group`. Use `all` for a release candidate, `ci` for only the normal full CI child, `plugin-prerelease` for only the plugin prerelease child, `release-checks` for every release child, or a narrower group: `install-smoke`, `cross-os`, `live-e2e`, `package`, `qa`, `qa-parity`, `qa-live`, or `npm-telegram` on the umbrella. This keeps a failed release box rerun bounded after a focused fix. For one failed cross-OS lane, combine `rerun_group=cross-os` with `cross_os_suite_filter`, for example `windows/packaged-upgrade`; long cross-OS commands emit heartbeat lines and packaged-upgrade summaries include per-phase timings. QA release-check lanes are advisory, so QA-only failures warn but do not block the release-check verifier.
 
 `OpenClaw Release Checks` uses the trusted workflow ref to resolve the selected ref once into a `release-package-under-test` tarball, then passes that artifact to cross-OS checks and Package Acceptance, plus the live/E2E release-path Docker workflow when soak coverage runs. That keeps the package bytes consistent across release boxes and avoids repacking the same candidate in multiple child jobs.
 
diff --git a/docs/reference/RELEASING.md b/docs/reference/RELEASING.md
index 3e972641e..e38894361 100644
--- a/docs/reference/RELEASING.md
+++ b/docs/reference/RELEASING.md
@@ -379,7 +379,10 @@ runs only the release-only plugin child, `release-checks` runs every release
 box, and the narrower release groups are `install-smoke`, `cross-os`,
 `live-e2e`, `package`, `qa`, `qa-parity`, `qa-live`, and `npm-telegram`.
 Focused `npm-telegram` reruns require `npm_telegram_package_spec`; full/all runs
-with `release_profile=full` use the release-checks package artifact.
+with `release_profile=full` use the release-checks package artifact. Focused
+cross-OS reruns can add `cross_os_suite_filter=windows/packaged-upgrade` or
+another OS/suite filter. QA release-check failures are advisory; a QA-only
+failure does not block release validation.
 
 ### Vitest
 
diff --git a/docs/reference/full-release-validation.md b/docs/reference/full-release-validation.md
index 6baeea4b1..0c630011d 100644
--- a/docs/reference/full-release-validation.md
+++ b/docs/reference/full-release-validation.md
@@ -158,6 +158,17 @@ Valid filter ids are defined in the reusable live/E2E workflow, including
 The `live-gateway-advisory-docker` handle is an aggregate rerun handle for its
 three provider shards, so it still fans out to all advisory Docker gateway jobs.
 
+Use `cross_os_suite_filter` with `rerun_group=cross-os` when one cross-OS lane
+failed. The filter accepts an OS id, a suite id, or an OS/suite pair, for
+example `windows/packaged-upgrade`, `windows`, or `packaged-fresh`. Cross-OS
+summaries include per-phase timings for packaged upgrade lanes, and long-running
+commands print heartbeat lines so a stuck Windows update is visible before the
+job timeout.
+
+QA release-check lanes are advisory. A QA-only failure is reported as a warning
+and does not block the release-check verifier; rerun `rerun_group=qa`,
+`qa-parity`, or `qa-live` when you need fresh QA evidence.
+
 ## Evidence to keep
 
 Keep the `Full Release Validation` summary as the release-level index. It links