/**
 * Period close tools for the Frihet MCP server — D4-B megasprint (3 tools).
 *
 * Tools:
 *   1. period_close_status — get the current or selected fiscal-year state
 *   2. period_close        — close a monthly or quarterly period (TRUST AREA)
 *   3. period_reopen       — reopen a closed period with required reason (TRUST AREA)
 *
 * REST surface: /v1/periods/current, /v1/periods/{id}, /v1/periods/close, /v1/periods/{id}/reopen
 *
 * STATE OF THE WORLD (verified against erp-main functions/src/publicApi/families/
 * periods.ts): only the READ route is implemented. Both WRITE routes answer
 * HTTP 501 NOT_IMPLEMENTED — "deferred to the upcoming fiscal-write wave (Trust,
 * serialized). Use year-end closing in the app for now." Nothing is frozen, and
 * there is no idempotent no-op to rely on, because there is no handler at all.
 *
 * The descriptions below therefore state the 501 in the present tense. Do not
 * restore aspirational prose about freezing or idempotency until a handler exists
 * — GAP-13 was exactly that: an agent planning a year-end close read a mechanism
 * the backend never had.
 *
 * `withBackendGuard` converts 404 only (backend-availability.ts isBackendNotFound),
 * so a 501 surfaces through the generic error path as isError with the backend's
 * own NOT_IMPLEMENTED message — an honest failure, not a fake success.
 */
import type { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
import type { IFrihetClient } from "../client-interface.js";
export declare function registerAccountingCloseTools(server: McpServer, client: IFrihetClient): void;
//# sourceMappingURL=accountingClose.d.ts.map