import type { ContentState } from "../model/ContentState.js";
import type { LifecycleMode } from "../model/ManifestGrammar.js";
/**
 * Per-Schema lifecycle state machine. Each Schema declares
 * `spec.lifecycle: 'publishing' | 'operational'` (default `'publishing'`);
 * this module translates that into allowed state transitions.
 *
 * Pure functions — no env, no DB. Feeds the dispatcher's
 * requestPublish branching and runtime state-transition validation.
 */
/**
 * Structural shape of a Schema manifest as far as the state machine
 * cares — just `spec.lifecycle?`. The full `SchemaManifest` type
 * lives in `domain/model/ManifestGrammar.ts` and conforms to this
 * structurally, so callers can pass either one.
 */
export interface LifecycleSchemaLike {
    readonly spec: {
        readonly lifecycle?: LifecycleMode;
    };
}
export declare function resolveLifecycle(schema: LifecycleSchemaLike | undefined): LifecycleMode;
/**
 * Allowed status transitions per lifecycle. Used by the MCP handler
 * and admin endpoints to gate operations. Unknown transitions return
 * `false` and the caller should reject with `CONFLICT`.
 *
 * Publishing lifecycle:
 *   draft → published, draft → archived
 *   published → archived, published → draft (unpublish-as-edit)
 *   archived → draft
 */
export declare function canTransition(schema: LifecycleSchemaLike | undefined, from: ContentState, to: ContentState): boolean;
//# sourceMappingURL=LifecycleStateMachine.d.ts.map