v0.8.0

Agents can now manage the servers MCPHub runs

Until now an agent that needed Kodi's tools while Kodi's server was stopped could only report them missing. Agents connected to the proxy can now operate the managed servers themselves through mcphub__* tools — off by default, and switched on under Settings → Agent management.

Tool	Does
mcphub__list_services	Every managed server with its install state, versions, run state and port
mcphub__start / stop / restart	Drive a server and wait for it to report healthy (wait_seconds, default 30)
mcphub__install	Install a server that is not installed, from its latest GitHub release; start: true brings it up
mcphub__update	Check for a newer release and install it, preserving config and restarting the server if it was running; force: true reinstalls
mcphub__check_service_updates	Check GitHub for one server or all of them, installing nothing
mcphub__check_hub_update	Compare the running MCPHub with its newest release — MCPHub never replaces itself, so the agent is told to hand you the release page URL

• Gated in layers. One master switch grants mcphub__list_services; three capability switches beneath it grant control (start/stop/restart), install/update, and update checks. They persist as soon as they are toggled and are enforced as proxy tool authorization, so a disabled tool vanishes from the tool list and is refused on call immediately — no restart.
• Headless overrides. MCPHUB_AGENT_MANAGEMENT_ENABLED, _CONTROL, _INSTALL and _UPDATE_CHECKS pin each switch from the environment (true/false, 1/0, yes/no, on/off); the Settings page shows a pinned checkbox locked and names the variable.
• Config and logs stay yours. No tool reads or returns a server's config files, install paths or logs. If a server will not start, the agent is told to ask you.
• Servers are addressed by proxy key (kodi), product name (KodiMCPSharp) or display name. Operations on one server are serialised, and every agent-driven action is written to that server's log so the Logs page shows who did what. The proxy's MCP instructions describe the granted capabilities on connect, so an agent knows it can start a stopped server instead of giving up.
• For embedders, MCPHub.Proxy gains CompositeToolAuthorization for stacking independent feature policies in front of one ProxyHandlers, and IServiceManager raises ServiceChanged so a UI can follow changes an agent makes.

222 tests pass (25 new, including an end-to-end MCP-over-HTTP run); the solution builds with no warnings.

Full Changelog: v0.7.0...v0.8.0