Files
wizardchen fb63c70022 docs: point builtin integration registration at the builtin plugin package
The extension point, data source, IM and web search pages still said the
builtin web search providers, data source connectors and IM adapters are
registered in container.go (registerWebSearchProviders,
initConnectorRegistry, registerIMAdapterFactories). They are registered
in internal/plugin/builtin/implementations.go now, which the container
only calls.

The plugin page and the RAG pipeline page also describe the fixed plugin
behavior: kubernetes plugins have the abilities of remote ones,
chat.answered comes from IM channels and the MCP ask tool too, the
pipeline hooks' place in the chain and the fallback when filterResults
drops everything, webhook-only plugin IM channels that follow upgrades,
OAuth tokens in plugin MCP headers, and workspace config forms usable
before the plugin is enabled.
2026-09-26 22:00:35 +08:00
..