Tool-schema rows in the Context browser carry a best-effort source tag for the registering plugin, recovered without a harness change: - a harness-logged `plugin` field passes through verbatim (future-proof); - MCP-proxied tools resolve `mcp:<server>` from their public names; - shipped first-party tools resolve from a pinned package map; - a live `tools.register()` hook (cordis `internal/get` reader slot, with a caller-package stack fallback for local-link installs) tags third-party, agent-scoped, and dynamic registrations, and peels a prior incarnation's wrapper on reload; - tools already registered when the plugin mounts render a localized "unknown plugin" tag explaining the boot-order gap. Priority: `mcp:<server>` > live record > pinned map > unknown. The chip rides the shared tag frame tinted with the brand badge tokens. Rebased onto v0.35.0 with maintainer review fixes; the attribution priority and reload-safety rework and the chip theming are described in the PR review comment. Co-authored-by: Nwflower <1679659@qq.com> Co-authored-by: bowenliang123 <liang.bowen.123@qq.com>
6 lines
89 B
JSON
6 lines
89 B
JSON
{
|
|
"name": "local-plugin",
|
|
"version": "0.0.0",
|
|
"private": true,
|
|
"type": "module"
|
|
} |