openclaw/docs
openclaw/docs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore(sync): mirror docs from openclaw/openclaw@5531502cb0

Browse Source
This commit is contained in:
openclaw-docs-sync[bot] 2026-04-27 17:13:03 +00:00
parent f33d231bde
commit a286393216
2 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
.openclaw-sync/source.json
View File

@ -1,5 +1,5 @@
{
"repository": "openclaw/openclaw",
"sha": "efc3a52947e9f0909569bf23dc9c5d1544f6aec3",
"syncedAt": "2026-04-27T16:43:24.967Z"
"sha": "5531502cb00986ffc63558a1f40900171472c075",
"syncedAt": "2026-04-27T17:11:34.610Z"
}

2
docs/plugins/architecture.md
View File

@ -151,6 +151,8 @@ Gateway startup builds one `PluginMetadataSnapshot` for the current config snaps
Plugin-aware config validation, startup auto-enable, and Gateway plugin bootstrap consume that snapshot instead of rebuilding manifest/index metadata independently. `PluginLookUpTable` is derived from the same snapshot and adds the startup plugin plan for the current runtime config.
After startup, Gateway keeps the current metadata snapshot as a replaceable runtime product. Repeated runtime provider discovery can borrow that snapshot instead of reconstructing the installed index and manifest registry for each provider-catalog pass. The snapshot is cleared or replaced on Gateway shutdown, config/plugin inventory changes, and installed index writes; callers fall back to the cold manifest/index path when no compatible current snapshot exists. Compatibility checks must include plugin discovery roots such as `plugins.load.paths` and the default agent workspace, because workspace plugins are part of the metadata scope.
The snapshot and lookup table keep repeated startup decisions on the fast path:
- channel ownership