/** The published npm package this binary is released as. */ export declare const PACKAGE_NAME = "teamshare-bridge"; /** Live package version (dist/lib -> ../../package.json) - never drifts. */ export declare function currentVersion(): string; /** * Parses `1.2.3` into numeric components. Anything non-numeric (a `v` prefix * is tolerated, pre-release/build suffixes are dropped) yields null so a * malformed registry answer can never be treated as an upgrade. */ export declare function parseVersion(raw: string | null | undefined): number[] | null; /** Standard semver-ish ordering: -1 older, 0 equal, 1 newer, null = incomparable. */ export declare function compareVersions(a: string, b: string): number | null; /** True only when `latest` is strictly newer than `current`. */ export declare function isNewer(latest: string, current: string): boolean; /** * Newest published version from the npm registry (dist-tag `latest`). * Returns null when unreachable/undecodable - callers treat that as "no * upgrade available", never as an error worth retrying aggressively. */ export declare function fetchLatestVersion(timeoutMs?: number): Promise; /** * The `upgrade --check` verdict as ONE consistent pair of answers (2026-11). * * `updatable` answers **"can this machine upgrade RIGHT NOW"**, not "is this a * replaceable install". It used to print `updatable: yes` next to * `status: up to date`, which reads as a contradiction and sends a human * looking for a newer version that does not exist. The capability itself * (`updatableInstall`) still has its own surface - `auto-upgrade status` prints * it as `applicable:` - where "yes" means exactly that question. */ export declare function describeUpgradeCheck(installed: string, published: string | null, install: { ok: boolean; reason?: string; }): { status: string; updatable: string; }; /** * Can `npm i -g @latest` safely replace THIS install? * * A source checkout (npm link, git clone, local dev build) is never replaced: * the global install command would delete the developer's working tree. The * npm tarball ships only dist/skills/templates/tools/README, so the presence * of project files marks a checkout. */ export declare function updatableInstall(): { ok: boolean; reason?: string; };