chore(sync): mirror docs from openclaw/openclaw@1bc50e0

Author: openclaw-docs-sync[bot]

.openclaw-sync/source.json

@@ -1,15 +1,15 @@
 {
   "repository": "openclaw/openclaw",
-  "sha": "3f5ace1fe14488b5dc9af60f441246dac49b018a",
+  "sha": "1bc50e0517adf5c4cb8bd025802d55208e9c6318",
   "sources": {
     "openclaw": {
       "repository": "openclaw/openclaw",
-      "sha": "3f5ace1fe14488b5dc9af60f441246dac49b018a"
+      "sha": "1bc50e0517adf5c4cb8bd025802d55208e9c6318"
     },
     "clawhub": {
       "repository": "openclaw/clawhub",
-      "sha": "2c592484445075688e06d67d37a98507e6c77a3a"
+      "sha": "6612f51b72bfa9a619388fce0c553d224fda19ca"
     }
   },
-  "syncedAt": "2026-11-09T03:37:44.578Z"
+  "syncedAt": "2026-11-09T04:23:33.582Z"
 }

docs/clawhub/cli.md

@@ -310,7 +310,7 @@ clawhub scan download @scope/demo --version 2.0.0 --kind plugin --output report.
 #### GitHub Actions
 
 ClawHub ships an official reusable workflow at
-[`/.github/workflows/skill-publish.yml`](https://github.com/openclaw/clawhub/blob/2c592484445075688e06d67d37a98507e6c77a3a/.github/workflows/skill-publish.yml)
+[`/.github/workflows/skill-publish.yml`](https://github.com/openclaw/clawhub/blob/6612f51b72bfa9a619388fce0c553d224fda19ca/.github/workflows/skill-publish.yml)
 for skill repos and catalog repos.
 
 Typical catalog setup:
@@ -844,7 +844,7 @@ Notes:
 #### GitHub Actions
 
 ClawHub also ships an official reusable workflow at
-[`/.github/workflows/package-publish.yml`](https://github.com/openclaw/clawhub/blob/2c592484445075688e06d67d37a98507e6c77a3a/.github/workflows/package-publish.yml)
+[`/.github/workflows/package-publish.yml`](https://github.com/openclaw/clawhub/blob/6612f51b72bfa9a619388fce0c553d224fda19ca/.github/workflows/package-publish.yml)
 for plugin repos.
 
 Typical caller setup:

docs/reference/scripts/pr-preparation.md

@@ -143,6 +143,26 @@ workflow binding, and hosted lease. The default source-review file is
 `.local/correction-review.json`; an explicit file lets the reviewer supply new
 source-review bytes without overwriting an older correction review.
 
+To credit additional verified contributors without rewriting the signed source,
+add `--coauthors <file>` to this explicit `--for-proof` invocation. The regular
+UTF-8 JSON file contains an array of `Name <email>` identities, for example:
+
+```json
+["Ada Example <ada@example.invalid>", "Renée Example <renee@example.invalid>"]
+```
+
+The file is snapshotted relative to the caller’s working directory before
+checkout or evidence retirement; use an absolute path across native handoffs.
+Names and addresses must be single-line values without control or Unicode line
+separators. Existing source trailers remain unchanged and first; additions are
+deduplicated by case-insensitive email, retaining the first requested spelling.
+The requested metadata is part of the signed baseline binding and candidate
+identity. Interrupted and completed retries must select the same metadata;
+changing the file cannot change the admitted transition. This is attribution,
+not approval: the new candidate still requires fresh exact-source review.
+Omitting the option preserves source-only credit. Other baseline commands do
+not accept it.
+
 For a previously published correction whose fresh incoming review has advanced
 but whose preparation context still names the earlier incoming head, also select
 `--incoming-head <hosted-SHA> --incoming-review <fresh-review-OID>