From 6856d0764d97d287e260d336ec0214fb966792a7 Mon Sep 17 00:00:00 2001 From: "openclaw-docs-sync[bot]" Date: Sun, 3 May 2026 12:46:27 +0000 Subject: [PATCH] chore(sync): mirror docs from openclaw/openclaw@baf8b8effec58257110c750e5b6567548540f775 --- .openclaw-sync/source.json | 4 ++-- docs/gateway/configuration.md | 2 +- docs/gateway/protocol.md | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/.openclaw-sync/source.json b/.openclaw-sync/source.json index 0e9003ced..017dc7712 100644 --- a/.openclaw-sync/source.json +++ b/.openclaw-sync/source.json @@ -1,5 +1,5 @@ { "repository": "openclaw/openclaw", - "sha": "ca69917153a8745675d8492f57e504bab86cd29d", - "syncedAt": "2026-05-03T12:26:51.600Z" + "sha": "baf8b8effec58257110c750e5b6567548540f775", + "syncedAt": "2026-05-03T12:44:38.828Z" } diff --git a/docs/gateway/configuration.md b/docs/gateway/configuration.md index 3dd3b67af..6be45bb97 100644 --- a/docs/gateway/configuration.md +++ b/docs/gateway/configuration.md @@ -609,7 +609,7 @@ For tooling that writes config over the gateway API, prefer this flow: - `config.patch` for partial updates (JSON merge patch: objects merge, `null` deletes, arrays replace) - `config.apply` only when you intend to replace the entire config -- `update.run` for explicit self-update plus restart +- `update.run` for explicit self-update plus restart; include `continuationMessage` when the post-restart session should run one follow-up turn - `update.status` to inspect the latest update restart sentinel and verify the running version after a restart Agents should treat `config.schema.lookup` as the first stop for exact diff --git a/docs/gateway/protocol.md b/docs/gateway/protocol.md index b15ee802b..d57afd029 100644 --- a/docs/gateway/protocol.md +++ b/docs/gateway/protocol.md @@ -381,7 +381,7 @@ enumeration of `src/gateway/server-methods/*.ts`. - `config.apply` validates + replaces the full config payload. - `config.schema` returns the live config schema payload used by Control UI and CLI tooling: schema, `uiHints`, version, and generation metadata, including plugin + channel schema metadata when the runtime can load it. The schema includes field `title` / `description` metadata derived from the same labels and help text used by the UI, including nested object, wildcard, array-item, and `anyOf` / `oneOf` / `allOf` composition branches when matching field documentation exists. - `config.schema.lookup` returns a path-scoped lookup payload for one config path: normalized path, a shallow schema node, matched hint + `hintPath`, and immediate child summaries for UI/CLI drill-down. Lookup schema nodes keep the user-facing docs and common validation fields (`title`, `description`, `type`, `enum`, `const`, `format`, `pattern`, numeric/string/array/object bounds, and flags like `additionalProperties`, `deprecated`, `readOnly`, `writeOnly`). Child summaries expose `key`, normalized `path`, `type`, `required`, `hasChildren`, plus the matched `hint` / `hintPath`. - - `update.run` runs the gateway update flow and schedules a restart only when the update itself succeeded. Package-manager updates force a non-deferred, no-cooldown update restart after the package swap so the old Gateway process does not keep lazy-loading from a replaced `dist` tree. + - `update.run` runs the gateway update flow and schedules a restart only when the update itself succeeded; callers with a session can include `continuationMessage` so startup resumes one follow-up agent turn through the restart continuation queue. Package-manager updates force a non-deferred, no-cooldown update restart after the package swap so the old Gateway process does not keep lazy-loading from a replaced `dist` tree. - `update.status` returns the latest cached update restart sentinel, including the post-restart running version when available. - `wizard.start`, `wizard.next`, `wizard.status`, and `wizard.cancel` expose the onboarding wizard over WS RPC.