/**
 * Result of a version check against npm registry
 */
export interface VersionCheckResult {
    /** Currently installed version */
    currentVersion: string;
    /** Latest version available on npm */
    latestVersion: string;
    /** True if a newer version is available */
    updateAvailable: boolean;
    /** Command to update the package */
    updateCommand: string;
}
/**
 * Check for updates to a package by querying the npm registry
 *
 * @param packageName - The npm package name to check (e.g., '@skillsmith/mcp-server')
 * @param currentVersion - The currently installed version
 * @returns Version check result, or null if check failed (network error, timeout, etc.)
 *
 * @example
 * ```typescript
 * const result = await checkForUpdates('@skillsmith/mcp-server', '0.3.0')
 * if (result?.updateAvailable) {
 *   console.log(`Update available: ${result.latestVersion}`)
 * }
 * ```
 */
export declare function checkForUpdates(packageName: string, currentVersion: string): Promise<VersionCheckResult | null>;
/**
 * Format update notification message for stderr output
 *
 * SMI-5893 Wave 10 (GH#2368 C-06/C-07/C-22): upgrading the npm package alone
 * never refreshes on-disk onboarding artifacts (hooks.json, the bundled
 * slash-command skill's SKILL.md, agent-pack hook scripts) — those are only
 * (re)written when the corresponding install command actually runs. Before
 * this change the message assumed Claude Code and said nothing about this,
 * so a Cursor (or any non-Claude-Code) user who upgraded the package still
 * saw stale hooks/SKILL.md content with no indication why.
 *
 * Verified against current command behavior, not assumed:
 *  - `skillsmith setup --client <client>` installs the bundled slash-command
 *    skill but SKIPS an already-present install unless `--force` is passed
 *    (`install-skill.ts`) — so `--force` is required here to actually refresh
 *    it, and `--client` IS supported (per-client target path).
 *  - `skillsmith agent install` (hooks, MCP registration, agent-pack SKILL.md)
 *    always re-writes Skillsmith-owned artifacts on every run, with or
 *    without `--force` — that flag only controls whether a FOREIGN
 *    conflicting entry gets overwritten (`agent.ts`'s own `--force` help
 *    text). It has NO `--client` flag — it auto-detects and installs into
 *    every present harness, so `client` is threaded only into the `setup`
 *    line below, not this one.
 *
 * Code-review finding (real regression): an earlier draft of this message
 * dropped `result.updateCommand` (the actual "how do I get the new npm
 * version" instruction) entirely, replacing it solely with the on-disk-
 * artifact-refresh commands above — which run against the STILL-OLD
 * installed binary and never upgrade anything. Both instructions are
 * necessary and address different problems; neither substitutes the other.
 *
 * @param result - Version check result with update available
 * @param client - Resolved client ID (e.g. via {@link resolveUpdateNotificationClient}),
 *   if available. When omitted, the message stays generic rather than
 *   guessing a client.
 * @returns Formatted message string
 */
export declare function formatUpdateNotification(result: VersionCheckResult, client?: string): string;
/**
 * Canonical "refresh hooks/MCP registration" remediation command — the
 * single source of truth for this exact string, shared by
 * {@link formatUpdateNotification} (version-bump-triggered, fires only
 * inside a running MCP server — structurally unreachable when the server
 * never spawns at all, e.g. GH#2368 V3's "zero MCP tools" report) and
 * {@link checkCursorMcpArtifact} (on-disk-content-triggered, SMI-6279
 * Wave 9 — reachable from `skillsmith diagnose` even when no server is
 * running) so the two never drift into differently-worded instructions for
 * the same underlying fix.
 */
export declare function agentInstallRemediationCommand(): string;
/**
 * Resolve `SKILLSMITH_CLIENT` for {@link formatUpdateNotification}'s
 * optional `client` parameter, without ever throwing (code-review finding,
 * SMI-5893 Wave 10): the only production call site (`mcp-server/src/index.ts`)
 * awaits this inside a `.then()` whose trailing `.catch()` is empty — an
 * uncaught throw from `resolveClientId` on an invalid env value would
 * silently drop the ENTIRE update notification, not just degrade to the
 * generic message this function's own contract promises.
 *
 * Also deliberately does NOT call `resolveClientId(undefined)` when `raw`
 * is unset — that would return `'claude-code'` (its documented default),
 * which is actively wrong here: of the 9 client harnesses this repo
 * supports, only Cursor's own generated MCP config ever sets
 * `SKILLSMITH_CLIENT` (confirmed via `packages/cli/src/templates/mcp-server.template.snippets.ts` —
 * the claude-code/copilot/windsurf/agents/codex/opencode/hermes/grok/
 * antigravity snippets never set it). Defaulting to claude-code would tell
 * a Windsurf/Copilot/etc. user to `setup --force --client claude-code`,
 * pointing them at `~/.claude/skills` instead of their actual client's
 * directory. Staying `undefined` here keeps the message client-neutral for
 * everyone this env var was never meant to identify.
 *
 * @param raw - `process.env.SKILLSMITH_CLIENT`, or any other raw string.
 * @returns the resolved client id, or `undefined` if `raw` is unset/empty
 *   or does not resolve to a known client.
 */
export declare function resolveUpdateNotificationClient(raw: string | undefined): string | undefined;
/**
 * Result of inspecting one `.cursor/mcp.json` file for the GH#2368 V3
 * staleness signature (SMI-6279 Wave 9).
 */
export interface CursorMcpArtifactCheck {
    /** Absolute path checked. */
    path: string;
    /** Whether the file exists on disk at all. */
    exists: boolean;
    /**
     * A Skillsmith MCP server entry was found under either the current key
     * (`CURSOR_MCP_ENTRY_KEY`) or the pre-SMI-6279 legacy key
     * (`LEGACY_MCP_ENTRY_KEY`) — see `agent-pack-installer.entry.ts`.
     */
    entryFound: boolean;
    /** The JSON key the entry was found under, when `entryFound` is true. */
    entryKey?: string;
    /**
     * True when the entry's `command` is the broken `npx` form
     * (`buildAgentMcpEntryValue()`'s shape) — two independent live UAT passes
     * proved this ENOENTs inside Cursor's bundled Node (GH#2368 C-01).
     */
    usesNpxForm: boolean;
    /** True when `env.SKILLSMITH_CLIENT === 'cursor'` is present on the entry. */
    hasClientEnv: boolean;
    /**
     * True when this artifact needs a `agent install` refresh — an entry was
     * found and either `usesNpxForm` or NOT `hasClientEnv` (or both; the
     * GH#2368 V3 repro found the real broken installer output had both
     * problems at once). `false` when no entry was found at all — Cursor
     * simply not being configured yet is not a staleness signal.
     */
    stale: boolean;
    /** Present only when `stale` is true — the exact remediation command. */
    remediation?: string;
}
/**
 * Inspect one `.cursor/mcp.json` file (global `~/.cursor/mcp.json` or a
 * project-scoped `<workspace>/.cursor/mcp.json` — the GH#2368 V3 tester's
 * actual broken config was project-scoped, and nothing before this checked
 * that location at all) for the exact staleness signature
 * {@link agentInstallRemediationCommand} fixes: the `npx` command form, and/or
 * a missing `SKILLSMITH_CLIENT` env var.
 *
 * Read-only, never throws — an unreadable or unparsable file is reported as
 * "not found" (nothing we can confidently flag) rather than surfaced as an
 * error; `skillsmith diagnose` is a best-effort diagnostic, not a validator.
 */
export declare function checkCursorMcpArtifact(path: string): CursorMcpArtifactCheck;
//# sourceMappingURL=version-check.d.ts.map