@@ -141,6 +141,7 @@ or npm install metadata. Those belong in your plugin code and `package.json`.
|
141 | 141 | | `kind` | No | `"memory"` \| `"context-engine"` | Declares an exclusive plugin kind used by `plugins.slots.*`. | |
142 | 142 | | `channels` | No | `string[]` | Channel ids owned by this plugin. Used for discovery and config validation. | |
143 | 143 | | `providers` | No | `string[]` | Provider ids owned by this plugin. | |
| 144 | +| `providerDiscoveryEntry` | No | `string` | Lightweight provider-discovery module path, relative to the plugin root, for manifest-scoped provider catalog metadata that can be loaded without activating the full plugin runtime. | |
144 | 145 | | `modelSupport` | No | `object` | Manifest-owned shorthand model-family metadata used to auto-load the plugin before runtime. | |
145 | 146 | | `providerEndpoints` | No | `object[]` | Manifest-owned endpoint host/baseUrl metadata for provider routes that core must classify before provider runtime loads. | |
146 | 147 | | `cliBackends` | No | `string[]` | CLI inference backend ids owned by this plugin. Used for startup auto-activation from explicit config refs. | |
@@ -681,6 +682,7 @@ See [Configuration reference](/gateway/configuration) for the full `plugins.*` s
|
681 | 682 | - Native manifests are parsed with JSON5, so comments, trailing commas, and unquoted keys are accepted as long as the final value is still an object. |
682 | 683 | - Only documented manifest fields are read by the manifest loader. Avoid custom top-level keys. |
683 | 684 | - `channels`, `providers`, `cliBackends`, and `skills` can all be omitted when a plugin does not need them. |
| 685 | +- `providerDiscoveryEntry` must stay lightweight and should not import broad runtime code; use it for static provider catalog metadata or narrow discovery descriptors, not request-time execution. |
684 | 686 | - Exclusive plugin kinds are selected through `plugins.slots.*`: `kind: "memory"` via `plugins.slots.memory`, `kind: "context-engine"` via `plugins.slots.contextEngine` (default `legacy`). |
685 | 687 | - Env-var metadata (`providerAuthEnvVars`, `channelEnvVars`) is declarative only. Status, audit, cron delivery validation, and other read-only surfaces still apply plugin trust and effective activation policy before treating an env var as configured. |
686 | 688 | - For runtime wizard metadata that requires provider code, see [Provider runtime hooks](/plugins/architecture-internals#provider-runtime-hooks). |
|