import { type Subscription } from "@uptimizr/schema";
/**
 * `uptimizr subscriptions …` — the operator's offline half of the subscriptions
 * API (#311, ADR 0051 §6).
 *
 * The offline sibling of `/api/v1/subscriptions`, and an **operator** command in
 * the same sense as `new-key` and `regions set`: it takes no API key and opens
 * the store directly, because store access is already strictly more than any
 * capability grants. It is the path a self-hoster uses to put a subscription
 * under version control — `sub.json` in a repo, applied by a deploy step —
 * rather than clicking one together.
 *
 * `test` deliberately **never delivers**. A dry run from a shell should not be
 * able to page anyone; proving a webhook receiver works is
 * `POST /api/v1/subscriptions/:id/test?deliver=true`, which needs an `annotate`
 * key and is auditable.
 *
 * Human progress goes to stderr, machine-readable JSON to stdout — the same
 * split the rest of `cli.ts` uses, so `uptimizr subscriptions list | jq` works.
 */
/** Read and validate a declaration file (a bare object or a `{ subscription }` envelope). */
export declare function readSubscriptionFile(file: string): Subscription;
/** `uptimizr subscriptions list` — every subscription of `projectId`. */
export declare function cmdSubscriptionsList(projectId: string): Promise<void>;
/** `uptimizr subscriptions add --file sub.json` — store a new declaration. */
export declare function cmdSubscriptionsAdd(projectId: string, file: string): Promise<void>;
/** `uptimizr subscriptions remove <id>` — delete a subscription and its firings. */
export declare function cmdSubscriptionsRemove(projectId: string, id: string): Promise<void>;
/**
 * `uptimizr subscriptions test <id>` — evaluate once, now, delivering nothing.
 *
 * Answers with the evaluation, including why it did not fire, which is what
 * makes a subscription tunable rather than mysterious.
 */
export declare function cmdSubscriptionsTest(projectId: string, id: string): Promise<void>;
//# sourceMappingURL=cli.d.ts.map