plugin

Overview ¶

Package plugin carries the fleet's build-time PROJECTIONS into the host: what each subsystem serves, known without running it.

Both are a function of the plugin's own router and typed-op registry, so both are known when the plugin is BUILT: `<app> describe plugin/<app>` writes mcp.json and openapi.json from one mount of one router (describe.go). This package embeds those files. The tool lists go to zip as Plugin.Tools, which is what lets the host answer tools/list for all 113 subsystems without starting a single one; the specs are what the host weaves into the fleet document it serves at /v1/openapi.json. Same invariant, two consumers: MCPTools() and the router are in-process, and a host cannot ask a plugin that is not running.

It exists as its own leaf package for one reason: go:embed cannot reach outside its own directory, so the bytes must be embedded from HERE, and cmd/cloud must stay light. This file imports embed and nothing else — no apps, no cloud root — so `go list -deps ./cmd/cloud` gains exactly one package and still links no subsystem.

The catalogue can only be INCOMPLETE, never wrong: the child's own registry answers the call, so a name the host still lists but the child no longer serves yields that child's -32602 rather than a mis-dispatch.