@@ -1152,22 +1152,22 @@ Some pre-runtime plugin metadata intentionally lives in `package.json` under the
1152115211531153Important examples:
115411541155-| Field | What it means |
1156-| ----------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
1157-| `openclaw.extensions` | Declares native plugin entrypoints. Must stay inside the plugin package directory. |
1158-| `openclaw.runtimeExtensions` | Declares built JavaScript runtime entrypoints for installed packages. Must stay inside the plugin package directory. |
1159-| `openclaw.setupEntry` | Lightweight setup-only entrypoint used during onboarding, deferred channel startup, and read-only channel status/SecretRef discovery. Must stay inside the plugin package directory. |
1160-| `openclaw.runtimeSetupEntry` | Declares the built JavaScript setup entrypoint for installed packages. Requires `setupEntry`, must exist, and must stay inside the plugin package directory. |
1161-| `openclaw.channel` | Cheap channel catalog metadata like labels, docs paths, aliases, and selection copy. |
1162-| `openclaw.channel.commands` | Static native command and native skill auto-default metadata used by config, audit, and command-list surfaces before channel runtime loads. |
1163-| `openclaw.channel.configuredState` | Lightweight configured-state checker metadata that can answer "does env-only setup already exist?" without loading the full channel runtime. |
1164-| `openclaw.channel.persistedAuthState` | Lightweight persisted-auth checker metadata that can answer "is anything already signed in?" without loading the full channel runtime. |
1165-| `openclaw.install.npmSpec` / `openclaw.install.localPath` | Install/update hints for bundled and externally published plugins. |
1166-| `openclaw.install.defaultChoice` | Preferred install path when multiple install sources are available. |
1167-| `openclaw.install.minHostVersion` | Minimum supported OpenClaw host version, using a semver floor like `>=2026.3.22` or `>=2026.5.1-beta.1`. |
1168-| `openclaw.install.expectedIntegrity` | Expected npm dist integrity string such as `sha512-...`; install and update flows verify the fetched artifact against it. |
1169-| `openclaw.install.allowInvalidConfigRecovery` | Allows a narrow bundled-plugin reinstall recovery path when config is invalid. |
1170-| `openclaw.startup.deferConfiguredChannelFullLoadUntilAfterListen` | Lets setup-only channel surfaces load before the full channel plugin during startup. |
1155+| Field | What it means |
1156+| ------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
1157+| `openclaw.extensions` | Declares native plugin entrypoints. Must stay inside the plugin package directory. |
1158+| `openclaw.runtimeExtensions` | Declares built JavaScript runtime entrypoints for installed packages. Must stay inside the plugin package directory. |
1159+| `openclaw.setupEntry` | Lightweight setup-only entrypoint used during onboarding, deferred channel startup, and read-only channel status/SecretRef discovery. Must stay inside the plugin package directory. |
1160+| `openclaw.runtimeSetupEntry` | Declares the built JavaScript setup entrypoint for installed packages. Requires `setupEntry`, must exist, and must stay inside the plugin package directory. |
1161+| `openclaw.channel` | Cheap channel catalog metadata like labels, docs paths, aliases, and selection copy. |
1162+| `openclaw.channel.commands` | Static native command and native skill auto-default metadata used by config, audit, and command-list surfaces before channel runtime loads. |
1163+| `openclaw.channel.configuredState` | Lightweight configured-state checker metadata that can answer "does env-only setup already exist?" without loading the full channel runtime. |
1164+| `openclaw.channel.persistedAuthState` | Lightweight persisted-auth checker metadata that can answer "is anything already signed in?" without loading the full channel runtime. |
1165+| `openclaw.install.clawhubSpec` / `openclaw.install.npmSpec` / `openclaw.install.localPath` | Install/update hints for bundled and externally published plugins. |
1166+| `openclaw.install.defaultChoice` | Preferred install path when multiple install sources are available. |
1167+| `openclaw.install.minHostVersion` | Minimum supported OpenClaw host version, using a semver floor like `>=2026.3.22` or `>=2026.5.1-beta.1`. |
1168+| `openclaw.install.expectedIntegrity` | Expected npm dist integrity string such as `sha512-...`; install and update flows verify the fetched artifact against it. |
1169+| `openclaw.install.allowInvalidConfigRecovery` | Allows a narrow bundled-plugin reinstall recovery path when config is invalid. |
1170+| `openclaw.startup.deferConfiguredChannelFullLoadUntilAfterListen` | Lets setup-only channel surfaces load before the full channel plugin during startup. |
1171117111721172Manifest metadata decides which provider/channel/setup choices appear in
11731173onboarding before runtime loads. `package.json#openclaw.install` tells
@@ -1179,6 +1179,11 @@ registry loading for non-bundled plugin sources. Invalid values are rejected;
11791179newer-but-valid values skip external plugins on older hosts. Bundled source
11801180plugins are assumed to be co-versioned with the host checkout.
118111811182+Official install-on-demand metadata should use `clawhubSpec` when the plugin is
1183+published on ClawHub; onboarding treats that as the preferred remote source and
1184+records ClawHub artifact facts after install. `npmSpec` remains the compatibility
1185+fallback for packages that have not moved to ClawHub yet.
1186+11821187Exact npm version pinning already lives in `npmSpec`, for example
11831188`"npmSpec": "@wecom/wecom-openclaw-plugin@1.2.3"`. Official external catalog
11841189entries should pair exact specs with `expectedIntegrity` so update flows fail
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。