chore(sync): mirror docs from openclaw/openclaw@422d139ba0

This commit is contained in:
openclaw-docs-sync[bot] 2026-04-29 09:11:20 +00:00
parent 6988707509
commit 10d0fc37fd
2 changed files with 7 additions and 3 deletions

View File

@ -1,5 +1,5 @@
{
"repository": "openclaw/openclaw",
"sha": "68ba1e7180a6393fdc7d61b71a11fc514502d1b3",
"syncedAt": "2026-04-29T08:43:57.503Z"
"sha": "422d139ba0f4952948e6700ab3258b6f257b18f9",
"syncedAt": "2026-04-29T09:09:46.195Z"
}

View File

@ -424,7 +424,11 @@ box first. The sanity check fails fast when required root files such as
tracked deletions. That usually means the remote sync state is not a trustworthy
copy of the PR. Stop that box and warm a fresh one instead of debugging the
product test failure. For intentional large deletion PRs, set
`OPENCLAW_TESTBOX_ALLOW_MASS_DELETIONS=1` for that sanity run.
`OPENCLAW_TESTBOX_ALLOW_MASS_DELETIONS=1` for that sanity run. `pnpm
testbox:run` also terminates a local Blacksmith CLI invocation that stays in the
sync phase for more than five minutes without post-sync output. Set
`OPENCLAW_TESTBOX_SYNC_TIMEOUT_MS=0` to disable that guard, or use a larger
millisecond value for unusually large local diffs.
Manual CI dispatches run `checks-node-compat-node22` as broad compatibility coverage. Android is opt-in for standalone manual CI through `include_android=true` and always enabled for `Full Release Validation`. `Plugin Prerelease` is more expensive product/package coverage, so it is a separate workflow dispatched by `Full Release Validation` or by an explicit operator. Normal pull requests, `main` pushes, and standalone manual CI dispatches keep that suite off.