/**
 * Attach snapshot-mode lifecycle to the dev server.
 *
 * When `FUSION_SNAPSHOT_MODE=1` the pod runs as a one-shot job:
 *   - Dev server ready → clean npm cache → exit 0 (success)
 *   - SIGTERM          → exit 143 (standard signal code, treated as eviction)
 *   - Uncaught error   → exit 1 (failure)
 *
 * The service-side trigger handler (`handleSnapshotTrigger`) polls the pod
 * via the Kubernetes API and calls `executeSnapshotCallback` in-process once
 * the pod terminates, so no HTTP callback from the pod is required.
 */
export declare function attachSnapshotMode(onHttpOk: (cb: () => Promise<void>) => void): void;
