/**
 * v2.1 Phase 4i — Bot-relay protocol version.
 *
 * Distinct from the package version (src/version.ts). The package version
 * bumps on every ship (patches, docs, release hygiene). The protocol version
 * bumps only when the tool *surface* or wire semantics change.
 *
 * SemVer for the protocol:
 *   MAJOR — breaking: tool removed, required arg added, response shape
 *           narrowed. Old clients cannot work.
 *   MINOR — additive: new tool, new optional arg, new response field.
 *           Old clients ignore the new stuff; still work.
 *   PATCH — behavior fix without surface change. Rare.
 *
 * Change history:
 *   2.0.0  — v2.0 npm release baseline (22 tools, session_id, channels, etc.)
 *   2.1.0  — v2.1 sweep (Stop hook, legacy migration bypass, backup/restore,
 *            dashboard auth, webhook hardening fields, spawn token
 *            passthrough, etc.). All additive — no breaking changes.
 *   2.1.1  — v2.1.3 (I6): agent_status enum widened from
 *            (online|busy|away|offline) to (idle|working|blocked|waiting_user|
 *            stale|offline). Legacy input values still accepted and mapped.
 *            New error codes: SENDER_NOT_REGISTERED, NAME_COLLISION_ACTIVE.
 *            Additive — old clients that hardcode the 4 old values on the
 *            output side will need to widen their pattern-matches.
 *   2.1.3  — v2.1.6 inbox hygiene: new additive tool `get_messages_summary`
 *            (lightweight inbox preview with 100-char content_preview + same
 *            since/status filters as get_messages). `get_messages` gains
 *            optional `since` arg (default "24h"; "all" or explicit null
 *            preserves pre-v2.1.6 unlimited behavior).
 *   2.2.0  — v2.2.0 core dashboard observability. Additive: `register_agent`
 *            accepts optional `terminal_title_ref` (dashboard click-to-focus
 *            key), `discover_agents` + `/api/snapshot` surface the field,
 *            new HTTP endpoints `POST /api/focus-terminal` + WebSocket
 *            `/dashboard/ws`, new `content_preview` / `description_preview`
 *            / `result_preview` fields on `/api/snapshot`. No breaking
 *            changes — old clients ignore the new surface.
 *   2.2.1  — v2.2.1 bug sweep + dashboard polish. Additive: `register_agent`
 *            gains optional `force` boolean (default false — escape hatch
 *            for the new active-name collision gate); `get_messages`
 *            response gains optional `hint` field; new MCP tool
 *            `set_dashboard_theme({mode, custom_json?})`; new HTTP
 *            endpoints `POST /api/send-message` / `/api/kill-agent` /
 *            `/api/set-status`; `/api/snapshot` surfaces
 *            `dashboard_prefs`. All additive — no breaking changes.
 *
 * Surfaced via `register_agent` + `health_check` response payloads so any
 * client can introspect compatibility before issuing tool calls. The relay
 * REPORTS the version; it does NOT enforce client-side checks.
 *
 * Update rule: modify this string ONLY when a new release changes the tool
 * surface. Bump MAJOR for breaking changes, MINOR for additive, PATCH rarely.
 * This file is intentionally the sole authoritative source — the drift-grep
 * in scripts/pre-publish-check.sh allowlists it alongside src/version.ts.
 */
export declare const PROTOCOL_VERSION: string;
//# sourceMappingURL=protocol.d.ts.map