/**
 * gsk-mesh native-binary manifest — pinned version, CDN layout, platform
 * detection, and the sha256 floor table for first-run downloads.
 *
 * ─── CONTRACT (gen-spark#32059) ──────────────────────────────────────────
 * The platform strings produced by `currentTarget()` (and the keys of
 * CHECKSUMS) MUST match, byte-for-byte, the platforms registered in the
 * backend at:
 *   backend/voice/update_model.py :: APP_REGISTRY["gsk-mesh"].platforms
 * The backend builds its manifest filename as `{channel}-{platform}.yml` and
 * looks it up against the CLI-supplied `target` string verbatim, so any drift
 * (e.g. "mac-arm64" vs "darwin-arm64", or channel "prerelease" vs "beta")
 * surfaces as a silent 404 / "no update" rather than a typed error.
 *
 *   Five targets : darwin-arm64 / darwin-x64 / linux-x64 / linux-arm64 / win-x64
 *   Channels     : stable / beta  (the CLI `--prerelease` flag maps to `beta`)
 * ─────────────────────────────────────────────────────────────────────────
 *
 * PINNED_VERSION + CHECKSUMS are the FLOOR — the version `gsk mesh` pulls on
 * first use. Routine version bumps after npm publish are handled at runtime by
 * `gsk mesh upgrade` (and the autorun check) against the backend endpoint, so
 * we do NOT re-publish @genspark/cli for every gsk-mesh release.
 */
export declare const PINNED_VERSION = "0.1.10";
export declare const CDN_BASE = "https://cdn1.genspark.ai/user-upload-image/client/gsk-mesh";
export type MeshTarget = 'darwin-arm64' | 'darwin-x64' | 'linux-x64' | 'linux-arm64' | 'win-x64';
/**
 * Map process.platform / process.arch to a gsk-mesh target string.
 * Throws for any platform/arch combination gsk-mesh does not publish.
 */
export declare function currentTarget(): MeshTarget;
/** `.exe` on Windows, empty elsewhere. */
export declare function binExt(target: string): string;
/** Full CDN download URL for a given version + target. */
export declare function cdnUrl(version: string, target: string): string;
/**
 * sha256 of each target's binary at PINNED_VERSION. Populated by hand from
 * the gsk-mesh release's published `.sha256` sidecars at
 *   <CDN_BASE>/v<VERSION>/gsk-mesh-<VERSION>-<target>[.exe].sha256
 * A mismatch fails closed: the downloader refuses to install the binary.
 *
 * The KEYS here are the contract surface with the backend (see top-of-file).
 */
export declare const CHECKSUMS: Record<MeshTarget, string>;
//# sourceMappingURL=manifest.d.ts.map