docs(release): refine beta validation guidance

.agents/skills/openclaw-release-maintainer/SKILL.md

@@ -86,10 +86,11 @@ Use this skill for release and publish-time workflow. Keep ordinary development
   parallel, publish npm from the successful npm preflight, then start published
   npm install/update, Docker, and Parallels verification while mac artifacts
   continue.
-- After a beta is published, run the expensive Docker, Parallels, and QA-Lab
-  release rosters in parallel instead of serializing them. Use selective reruns
-  after failures or fixes, but keep proof that Docker, Parallels, and QA-Lab
-  each passed at least once before stable/latest promotion.
+- After a beta is published, overlap remote/manual release rosters where useful,
+  but avoid piling local Docker, Parallels, and QA-Lab work onto the same host
+  when it would create system-load noise. Use selective reruns after failures or
+  fixes, but keep proof that Docker, Parallels, and QA-Lab each passed at least
+  once before stable/latest promotion.
 - Mac packaging may be built from a slight release-branch variation of the
   tagged commit when the delta is mac packaging, signing, workflow, or
   validation-only release machinery. If mac packaging needs release-branch-only
@@ -558,9 +559,10 @@ node --import tsx scripts/openclaw-npm-postpublish-verify.ts <published-version>
     the next beta if the fix must change the already-published package. If any
     lane fails after the beta tag/package is pushed or published, fix,
     commit/push/pull, increment to the next beta tag, and rerun the affected
-    beta evidence. Start Docker, Parallels, and QA-Lab in parallel once the
-    beta is live. Ensure the full expensive roster has passed at least once
-    before stable/latest promotion. The roster includes the manual Actions >
+    beta evidence. Once the beta is live, start remote/manual rosters where they
+    can overlap safely, but keep local Docker and Parallels load controlled.
+    Ensure the full expensive roster has passed at least once before
+    stable/latest promotion. The roster includes the manual Actions >
     `NPM Telegram Beta E2E` workflow against the exact published beta package.
     If a pre-npm lane fails before any tag/package leaves the machine, fix and
     rerun the same intended beta attempt. Repeat up to the operator's

docs/.generated/config-baseline.sha256

@@ -1,4 +1,4 @@
-d8e7866e0c3f633222f75a35defed3c3a03d849f4aa4f70871e3436e80074e76  config-baseline.json
+7fa6e35bb9f9d3096d6281f141488be0dcfe15de40dc4f5c0305eb1ff2bc60b6  config-baseline.json
 5f5fb87fd46f9cbb84d8af17e00ae3c4b74062e8ad517bc2260ba83da2e9014f  config-baseline.core.json
 7cd9c908f066c143eab2a201efbc9640f483ab28bba92ddeca1d18cc2b528bc3  config-baseline.channel.json
-a5479c182ec987bb21e814b8a4e7b3bda7190ae5c2b35fd5ca403dfa48afa115  config-baseline.plugin.json
+f9e0174988718959fe1923a54496ec5b9262721fe1e7306f32ccb1316d9d9c3f  config-baseline.plugin.json

docs/.generated/plugin-sdk-api-baseline.sha256

@@ -1,2 +1,2 @@
-947221d62a0eb0b66250fba2b011ca28a11cb1058bc542b9c155d55479f15935  plugin-sdk-api-baseline.json
-0d750f785adbe4d90f209842ed9297476669dd62f7be81fa41e06b6736cc2aaf  plugin-sdk-api-baseline.jsonl
+21b0bd88e0d2fcaefaeaa9ab59d73853aa38badee88d0242d3fe3311a24217e1  plugin-sdk-api-baseline.json
+7f85f52c0bc54e8b860b115bec205ecb8d66e20f62dd1971c660eb7a4b136799  plugin-sdk-api-baseline.jsonl