/**
 * Lightweight helper to check whether a specific package version exists in the
 * public npm registry. Used by `ensureSquadStateMcpPinned` to avoid pinning a
 * `squad_state` MCP launch spec to a version that `npx` cannot resolve
 * (which would cause an ETARGET at session start and leave the bridge unwired).
 *
 * The result is cached per-process to avoid repeated lookups across the
 * multi-pass upgrade flow. Network failures and non-200 responses are
 * conservatively treated as "version not published" so that we fall back to
 * the locally-installed binary rather than pinning a bad spec.
 *
 * See `.squad/files/validation/MCP-LOADER-ROOT-CAUSE.md` (data-15 Option A).
 */
/** Reset the cache (test-only helper). */
export declare function _resetNpmRegistryCache(): void;
/**
 * Returns true if `@bradygaster/squad-cli@<version>` is reachable on the npm
 * registry, false on any network failure / 404 / non-publishable response.
 *
 * Uses Node's built-in `https` so we don't pull in extra deps. Total budget
 * is bounded by `timeoutMs` (default 2s) so a slow / offline registry can
 * never block CLI startup.
 */
export declare function isSquadCliVersionPublished(version: string, timeoutMs?: number): Promise<boolean>;
//# sourceMappingURL=npm-registry.d.ts.map