/**
 * The ONE strategy-status vocabulary (H7 / D-10).
 *
 * The platform's status strings are read in two places that used to keep private copies of the same
 * sets: `senpi deploy`'s reconcile and `installRuntimeCore`'s wallet gate. They had already drifted
 * — the install gate's terminal set was missing `TERMINATED` and `CLOSING_DONE`, so both fell
 * through to a generic "only ACTIVE strategies can run a runtime" hint that told the user nothing
 * about the strategy actually being gone. One producer per set, one producer for the hint.
 *
 * The deploy sets are canonical; the install gate now reads them.
 */
/**
 * Statuses a wallet passes through on its way to ACTIVE. ONLY these are worth waiting on: they
 * resolve on their own, so a bounded poll is the right response.
 */
export declare const INITIALIZING_STATUSES: readonly string[];
/** Statuses that mean a teardown is under way — not dead yet, so never a candidate to create beside. */
export declare const CLOSING_STATUSES: readonly string[];
/** Statuses that mean a strategy is gone — never adopted, never ambiguous. */
export declare const DEAD_STATUSES: readonly string[];
export declare function isInitializing(status: string): boolean;
export declare function isClosing(status: string): boolean;
export declare function isDead(status: string): boolean;
/**
 * The install gate's hint for a non-ACTIVE wallet — one producer for all four branches.
 *
 * A strategy that is closing and one that is already closed get the same advice (create a new
 * strategy), which is why they share a branch; what matters is that neither falls to the generic
 * arm, where the user learns only that ACTIVE is required and not that this wallet is finished.
 */
export declare function buildWalletStatusHint(status: string): string;
//# sourceMappingURL=strategy-status.d.ts.map