fix(plugins): rename bundled allowlist discovery policy

docs/gateway/configuration-reference.md

@@ -166,7 +166,7 @@ See [MCP](/cli/mcp#openclaw-as-an-mcp-client-registry) and
   plugins: {
     enabled: true,
     allow: ["voice-call"],
-    bundledMode: "compat",
+    bundledDiscovery: "compat",
     deny: [],
     load: {
       paths: ["~/Projects/oss/voice-call-plugin"],
@@ -188,8 +188,8 @@ See [MCP](/cli/mcp#openclaw-as-an-mcp-client-registry) and
 - Discovery accepts native OpenClaw plugins plus compatible Codex bundles and Claude bundles, including manifestless Claude default-layout bundles.
 - **Config changes require a gateway restart.**
 - `allow`: optional allowlist (only listed plugins load). `deny` wins.
-- `bundledMode`: defaults to `"compat"` for legacy bundled provider activation.
-  Use `"respect-allow"` when a non-empty `plugins.allow` should also gate
+- `bundledDiscovery`: defaults to `"compat"` for legacy bundled provider activation.
+  Use `"allowlist"` when a non-empty `plugins.allow` should also gate
   bundled provider plugins, including web-search runtime providers.
 - `plugins.entries.<id>.apiKey`: plugin-level API key convenience field (when supported by the plugin).
 - `plugins.entries.<id>.env`: plugin-scoped env var map.

docs/gateway/doctor.md

@@ -169,7 +169,9 @@ That stages grounded durable candidates into the short-term dreaming store while
     Doctor also warns when `plugins.allow` is non-empty and tool policy uses
     wildcard or plugin-owned tool entries. `tools.allow: ["*"]` only matches tools
     from plugins that actually load; it does not bypass the exclusive plugin
-    allowlist.
+    allowlist. If bundled provider discovery is still in legacy compatibility
+    mode, doctor also points to the stricter `plugins.bundledDiscovery:
+    "allowlist"` setting.
 
   </Accordion>
   <Accordion title="2. Legacy config key migrations">