v0.4.0

Compare with previous release

Added

• Every MCP tool now publishes a result schema (outputSchema) next to its argument schema in tools/list, and the whole contract ships as the machine-readable snapshot docs/v1/tools.json in every release archive and as a standalone checksummed release asset; clients can validate requests and results against the published member names.
• Tool descriptions are specific, unique, and validated at startup, so a client can show what each tool observes without guessing.
• A backend result that fails its tool's published schema fails the call with a response_shape issue instead of returning an unvalidated payload.

Changed

• Argument validation derives from the tool's input schema: malformed or unrelated arguments now fail with invalid_arguments before any backend contact.
• get_hostlens_info is available to health-role tokens whose holder has the hostlens audit grant (previously the diagnostics role).
• The diagnostics backend IPC now carries typed tool arguments; MCP clients are unaffected because the gateway owns the client-facing envelope.
• Audit and Docker tool failure paths return schema-valid empty payloads instead of bare empty data objects; issue codes and isError behavior are unchanged.