/**
 * Hand-curated JSON Schemas for the operations-profile MCP tools.
 *
 * Why hand-curated: Harper's server-side validators are Joi, which doesn't
 * round-trip cleanly to JSON Schema. The MCP spec requires draft-07-ish
 * JSON Schema for tool inputSchema. Authoring these directly keeps the
 * schemas readable, easy to tweak per the LLM ergonomics we want, and
 * decoupled from server-side validation evolution.
 *
 * Each schema follows MCP convention: `type: 'object'` at the top, with
 * `properties` declared and a small `required` list when applicable.
 * Optional fields are listed but not required, so an LLM can call the
 * minimum-viable form.
 *
 * Coverage matches the v1 conservative `allow` default in the design
 * (#465 → Operations MCP). When operators expand `mcp.operations.allow`
 * beyond this list, ops without an entry here fall back to a permissive
 * `{ type: 'object' }` schema and a runtime-validates-as-it-goes posture
 * — better than silently dropping them from the tool surface.
 */
/** Permissive default for any opted-in operation that doesn't have a hand-curated schema yet. */
export declare const PERMISSIVE_SCHEMA: object;
/**
 * Map of operation name → input schema. Lookup misses fall back to
 * `PERMISSIVE_SCHEMA`. Keys mirror `OPERATIONS_ENUM` values.
 */
export declare const OPERATION_INPUT_SCHEMAS: Record<string, object>;
