A Workspace installs a plugin once, but that single installation is reused by
several product objects: every processor for a Runner, every knowledge base for
a KnowledgeEngine / Parser / Retriever, and many conversations or page requests
for the other component kinds. The platform storage key carries no processor or
knowledge-base dimension, so a plugin must fold that identity into its own keys.
- certified-plugins: add "one installation, many usages" with the isolation
dimensions per component kind, and "when an installation is revoked"
documenting BasePlugin.on_installation_revoked, its trigger set, the absent
invocation context and the no-op/failure semantics.
- component pages (runner, knowledge-engine, knowledge-retriever, parser, tool,
command, event-listener, page): add a short component-specific section with
that component's own rules and a link to the contract page.
- Align the background-work rule with the SDK contract: the SDK does not track
ownership of detached work, so a plugin must keep its own binding-keyed
registry and stop it in the revocation hook.
All three locales carry the same sections.
Hyu