@remixmate/cli 0.9.72 → 0.9.73

package/dist/auth/environment.d.ts

@@ -1,38 +0,0 @@
-/**
- * Pure environment predicates that gate the auto device-login feature.
- *
- * Everything here is synchronous, side-effect free, never touches the network
- * and never reads a PrivToken. The conservative bias is: when in doubt, treat
- * the environment as headless so we fail fast rather than pop a useless browser.
- *
- * See .kiro/specs/cli-auto-device-login/design.md (Requirement 1.4–1.7).
- */
-/** Total kill switch: hosts can force-disable auto auth and fall back to fail-fast. */
-export declare function autoAuthDisabled(): boolean;
-/**
- * Whether the process is likely running without a desktop session capable of
- * opening a browser.
- *
- *   - CI environments are always treated as headless.
- *   - On Linux a browser needs an X11 / Wayland display; absence → headless.
- *   - macOS / Windows are assumed to have a GUI session available.
- */
-export declare function isHeadless(): boolean;
-/**
- * Master gate for auto authorization. Only true when auto auth is not disabled
- * AND the environment can plausibly open a browser for the user.
- */
-export declare function canAutoAuth(): boolean;
-/**
- * Whether the CLI is being driven by an agent host (Claude Code / Codex /
- * ab-agent) rather than typed by a human at a terminal.
- *
- * Used to decide (a) whether to emit the machine-readable AUTH_REQUIRED block
- * alongside the human text, and (b) whether an interactive `login` may block
- * for the device code's full lifetime — an agent's tool call is time-bounded,
- * so it must get a bounded, resumable wait instead.
- *
- * Detection is deliberately loose: a piped stdout is the reliable signal, the
- * env markers just make the intent explicit for hosts that allocate a pty.
- */
-export declare function isAgentHost(): boolean;

package/dist/auth/pending-store.d.ts

@@ -1,33 +0,0 @@
-/**
- * Pending device-authorization state, at ~/.config/remixmate/pending.json.
- *
- * Exists so authorization can outlive a single process. `login --start` requests
- * a device code, persists it and returns immediately; `login --wait` picks it up
- * and polls with a bounded window, as many times as needed. That split is what
- * makes authorization workable from an agent host, whose tool calls are
- * time-bounded and cannot sit on a 10-minute blocking poll.
- *
- * The device_code IS a short-lived bearer secret (it can be exchanged for the
- * PrivToken until it expires or is used), so the file is written 0600 like the
- * credential store, and is deleted as soon as it is redeemed or found expired.
- */
-export declare const PENDING_FILE: string;
-export interface PendingAuth {
-    apiBaseUrl: string;
-    deviceCode: string;
-    userCode: string;
-    verificationUri: string;
-    verificationUriComplete?: string;
-    /** Poll interval in seconds, as instructed by the backend. */
-    interval: number;
-    /** Absolute epoch-ms deadline after which the device code is dead. */
-    expiresAt: number;
-}
-export declare function setPending(pending: PendingAuth): Promise<void>;
-/**
- * Read the pending authorization for `apiBaseUrl`. Returns null when absent,
- * unreadable, bound to a different backend, or already expired — callers then
- * tell the user to run `login --start` again.
- */
-export declare function getPending(apiBaseUrl: string): Promise<PendingAuth | null>;
-export declare function clearPending(): Promise<void>;

package/dist/auth/resolve.d.ts

@@ -1,30 +0,0 @@
-/**
- * Single source of truth for PrivToken resolution precedence, shared by the
- * CLI commands and the HTTP layer (src/http.ts wires this in — Wave 2 task 4.3).
- *
- * Precedence (high → low), per requirements 7.1–7.4:
- *   1. explicit --token flag (caller override)
- *   2. PRIV_TOKEN environment variable  (CI / agent-embedded hosts)
- *   3. Credential_Store entry for the active API base URL (written by `login`)
- *
- * A value that is empty after trimming whitespace is treated as ABSENT, so an
- * exported-but-empty `PRIV_TOKEN=""` falls through to the credential store
- * rather than masking it.
- */
-export type CredentialSource = 'flag' | 'env' | 'credential-store';
-export interface ResolvedToken {
-    privToken: string;
-    source: CredentialSource;
-    /** Present only for the credential-store source. */
-    userLabel?: string;
-}
-/**
- * Resolve the PrivToken following the documented precedence. Returns null when
- * no source yields a token (callers render the not-authenticated message).
- */
-export declare function resolvePrivToken(opts: {
-    flag?: string;
-    apiBaseUrl: string;
-}): Promise<ResolvedToken | null>;
-/** Human-readable hint shown when resolution fails (no token echoed). */
-export declare const NOT_AUTHENTICATED_HINT = "\u274C not authenticated \u2014 run `remixmate login`, set PRIV_TOKEN, or pass --token";

package/dist/billing.d.ts

@@ -1,44 +0,0 @@
-/**
- * Billing capture — makes credit consumption visible to whoever ran the skill.
- *
- * Credits are deducted server-side and used to be invisible here: a run printed
- * its image/video URL and nothing else, so the first time a user noticed the
- * credit system at all was the `insufficient_credits` error after the balance
- * had already run out. ab-api now attaches a `billing` object to the envelope of
- * every response that charged something (see core.Success / credits_billing.go);
- * this module accumulates those across all the calls a single skill run makes —
- * a gen-image run polls, a gen-video run polls, and each may charge once — and
- * renders one footer at the end.
- *
- * Two outputs, two audiences, both on stdout:
- *   - a human-readable footer, which is what the agent relays to the user.
- *   - one `__progress__` line (phase `billing`) — the existing machine protocol,
- *     already parsed by ab-agent's executor and skipped by the line-scanning
- *     parsers in render_video.py, so a nested pipeline caller can aggregate a
- *     whole run's spend without a new stdout contract.
- *
- * Both go to stdout rather than stderr (where the auth footer lives) because
- * ab-agent hands the LLM `result.stdout || result.stderr` (mcp-tools.ts) — a
- * stderr-only footer would be invisible in the hosted agent, visible only when
- * a local host like codex shows both streams. Adding stdout lines is safe:
- * emitProgress already writes NDJSON there, so no consumer can be treating
- * stdout as a single JSON document.
- */
-export interface BillingItem {
-    credits: number;
-    bizType?: string;
-    detail?: string;
-}
-/** The `billing` object ab-api attaches to a charged response. */
-export interface Billing {
-    credits: number;
-    balance: number;
-    items?: BillingItem[];
-}
-/** Accumulate one response's billing object; no-ops on responses that charged nothing. */
-export declare function recordBilling(billing: Billing | undefined | null): void;
-/** Everything charged so far in this process, or null when nothing was. */
-export declare function billingSummary(): Billing | null;
-export declare function emitBillingFooter(): void;
-/** Test seam — resets the accumulator between runs in-process. */
-export declare function resetBilling(): void;

package/dist/capabilities.d.ts

@@ -1,63 +0,0 @@
-/**
- * Model capabilities client.
- *
- * The model roster — internal model ids, friendly aliases, defaults, and each
- * model's parameter constraints (aspect ratios / resolutions / durations /
- * reference-image caps / Seedream size presets) — is owned by ab-api and served
- * from POST /model/capabilities (public, no auth). The CLI fetches it at runtime
- * instead of hardcoding it, so this npm package never ships the internal model
- * matrix or provider details, and validation can't drift from the backend.
- *
- * Fetched once per process and memoized; the catalog is static server-side.
- */
-export interface ModelConstraints {
-    aspectRatios?: string[];
-    resolutions?: string[];
-    durations?: number[];
-    durationMin?: number;
-    durationMax?: number;
-    durationDefault?: number;
-    refImageMax?: number;
-    /** Omni-modal reference caps (Seedance 2.0): videos and audio clips per request. */
-    refVideoMax?: number;
-    refAudioMax?: number;
-    sizes?: string[];
-    /** aspect-ratio → [width, height] pixel preset (Seedream). Per model: the same
-     *  ratio maps to different pixels on different Seedream variants. */
-    sizePresets?: Record<string, [number, number]>;
-    /** total-pixel bounds (width × height); the backend rescales sizes outside them. */
-    pixelMin?: number;
-    pixelMax?: number;
-}
-export interface ModelDescriptor {
-    id: string;
-    label: string;
-    aliases?: string[];
-    default?: boolean;
-    constraints: ModelConstraints;
-}
-export interface VoiceCapabilities {
-    provider: string;
-    defaultVoiceId: string;
-    speedMin: number;
-    speedMax: number;
-}
-export interface DigitalHumanCapabilities {
-    sources: string[];
-    defaultVoiceId: string;
-}
-export interface ModelCapabilities {
-    image: ModelDescriptor[];
-    video: ModelDescriptor[];
-    voice: VoiceCapabilities;
-    digitalHuman: DigitalHumanCapabilities;
-}
-/** Fetch (and memoize) the model capabilities catalog from ab-api. */
-export declare function getCapabilities(apiBaseUrl?: string): Promise<ModelCapabilities>;
-/**
- * Resolve a user-supplied model (friendly alias or full id) against a model
- * list. Returns the matched descriptor, or null when nothing matches.
- */
-export declare function matchModel(list: ModelDescriptor[], input: string): ModelDescriptor | null;
-/** The descriptor flagged `default` in a list, falling back to the first entry. */
-export declare function defaultModel(list: ModelDescriptor[]): ModelDescriptor | undefined;

package/dist/cli.d.ts

@@ -1,13 +0,0 @@
-#!/usr/bin/env node
-/**
- * remixmate CLI entrypoint.
- *
- *   remixmate --list                          list registered skills
- *   remixmate <name> --help                   forward --help to underlying skill
- *   remixmate <name> [--flag value ...]       invoke the skill
- *
- * For python skills (entry.type === 'python') we spawn the script and inherit
- * its stdio so progress / errors flow through unchanged.
- * For http / builtin skills we dispatch in-process to handlers/.
- */
-export {};

package/dist/diagnostics.d.ts

@@ -1,24 +0,0 @@
-export declare function traceHeaders(): Record<string, string>;
-/**
- * Redact a string for anything that leaves this process (diagnostic lines,
- * execution traces).
- *
- * Kept in lockstep with ab-agent's `lib/telemetry.cleanText` — the two feed the
- * same `media_chat_turn_trace` table, and a table whose rows were sanitized by
- * two different rulesets is a table nobody can reason about. ANSI stripping,
- * e-mail and phone redaction were added here to close that gap.
- *
- * `max` caps the result in BYTES, keeping the head. Callers that need the tail
- * (a command's decisive line is its last one) slice before calling.
- */
-export declare function cleanDiagnosticText(value: string, max?: number): string;
-/**
- * Exit code → the outcome vocabulary of the logging contract.
- *
- * Exported because the execution trace (project/trace.ts) reports the same
- * verdict for the same run: two mappings would let a run be `failure` in the
- * diagnostic line and `success` in the database.
- */
-export declare function outcomeOf(exitCode: number): 'success' | 'cancelled' | 'rejected' | 'failure';
-/** Opt-in line framing for hosts; stdout is exclusively the existing skill protocol. */
-export declare function diagnostic(exitCode: number, durationMs: number, error?: unknown): void;

package/dist/doctor.d.ts

@@ -1,22 +0,0 @@
-/**
- * `remixmate doctor` — one command that answers "why isn't this working?".
- *
- * The failure modes this package actually produces in the field are: no
- * credential, a credential bound to a different backend, a missing python3, a
- * missing Playwright, and an unreachable backend. Each of those used to surface
- * only as a downstream error from whichever skill happened to be run first, in
- * that skill's own wording. Checking them up front, in one place, turns a
- * scavenger hunt into a list.
- *
- * Also exports the one-line status shown under `--list` / `--help`, so a first
- * run says "you are not logged in" instead of leaving the user to find out by
- * invoking a skill.
- */
-/**
- * Short auth status suitable for a footer. Never performs network I/O — a
- * listing command must stay instant and work offline.
- */
-export declare function authStatusLine(): Promise<string>;
-export declare function runDoctor(opts?: {
-    skipNetwork?: boolean;
-}): Promise<number>;

package/dist/errors.d.ts

@@ -1,29 +0,0 @@
-/**
- * Process-wide error type and exit-code contract.
- *
- * Extracted from http.ts so the auth gateway (auth/ensure.ts) can throw the same
- * error type without creating an import cycle (http.ts → ensure.ts → http.ts).
- * `SkillError` is still re-exported from http.ts, so existing imports are unchanged.
- *
- * Exit codes are a CONTRACT with hosts (Claude Code / Codex / ab-agent): an agent
- * reads the code to decide whether to guide the user through authorization, retry
- * later, or surface a hard failure. Never reuse a code for a different meaning.
- */
-export declare const EXIT: {
-    /** Success. */
-    readonly OK: 0;
-    /** Generic runtime failure. */
-    readonly ERROR: 1;
-    /** Usage error — unknown skill / unknown option. */
-    readonly USAGE: 2;
-    /** No usable credential, or the credential was rejected. Host should offer to authorize. */
-    readonly NOT_AUTHENTICATED: 4;
-    /** Backend unreachable / timed out. Distinct from 4 so "log in" isn't suggested for an outage. */
-    readonly BACKEND_UNREACHABLE: 5;
-    /** Failed to spawn the underlying interpreter. */
-    readonly SPAWN_FAILED: 127;
-};
-export declare class SkillError extends Error {
-    readonly exitCode: number;
-    constructor(message: string, exitCode?: number);
-}

package/dist/exec.d.ts

@@ -1,18 +0,0 @@
-/**
- * `remixmate exec -- <command> [args...]`
- *
- * Runs an arbitrary command with the resolved credential injected into its
- * environment (`PRIV_TOKEN` + `MM_API_BASE_URL`), using the same gateway that
- * skill dispatch uses.
- *
- * This is the general form of the invariant the auth rework establishes: Node
- * is the only thing that reads the credential store / keychain / device flow,
- * and every child process receives the result through its environment. Without
- * it, maintenance scripts that import `registry_loader` directly (e.g.
- * scripts/test-template-pipeline.py) would have to re-implement credential
- * lookup — which is exactly the duplication, and the cross-origin token leak,
- * that was just removed.
- *
- * The token is never printed; it only ever reaches the child's environment.
- */
-export declare function runExec(argv: string[]): Promise<number>;

package/dist/handlers/gen-digital-human.d.ts

@@ -1,17 +0,0 @@
-/**
- * gen-digital-human handler — talking-head video + custom avatars, five modes:
- *   --list-avatars true                          → POST /digital-human/avatar/page (list)
- *   --clone --clone-url <url> --name <n>         → POST /digital-human/avatar/clone, then poll clone-status
- *   --clone-status --avatar-id <id>              → POST /digital-human/avatar/clone-status (one-shot)
- *   --check-status --generation-id <id>          → POST /digital-human/video/status (one-shot)
- *   default (--avatar-id <id> ...)               → generate: resolve avatar → submit → poll
- *
- * Ported from `scripts/gen_digital_human_video.py` (python → http) so it shares
- * auth / base-URL / business-code handling with the other generators via
- * http.ts. Endpoints and payloads match the backend DigitalHuman* DTOs.
- *
- * Avatar ids are the backend's opaque uids (`dh_...`); legacy numeric ids are
- * still accepted as strings.
- */
-import type { HandlerContext, HandlerInput } from './index.js';
-export declare function genDigitalHuman(input: HandlerInput, ctxIn: HandlerContext): Promise<void>;

package/dist/handlers/gen-image.d.ts

@@ -1,20 +0,0 @@
-/**
- * gen-image handler — POST ab-api /model/genImg.
- *
- * Thin forwarder: the model roster, defaults, size presets and reference-image
- * caps all come from ab-api's capabilities catalog (see capabilities.ts), not
- * from this package. Behavior:
- *   - --model accepts a friendly alias or a full id; resolved against the catalog
- *     (ab-api also resolves aliases server-side, so an unknown value still passes
- *     through and is validated by the backend).
- *   - --size accepts a WxH string (→ width/height) or an aspect-ratio preset key
- *     (→ aspectRatio; for Seedream models ab-api maps the preset to pixels).
- *   - --resolution is accepted but inert: it only ever fed the Gemini `size` tier,
- *     and Gemini is not wired up on the gateway, so we no longer send it.
- *   - Reference images: HTTPS URLs and data: URIs pass through; local paths are
- *     read and base64-encoded into a data: URI.
- *   - Async response (generationId + status:'generating'/'pending') is polled
- *     against /model/getImgStatus until completed/failed/timeout.
- */
-import type { HandlerContext, HandlerInput } from './index.js';
-export declare function genImage(input: HandlerInput, ctxIn: HandlerContext): Promise<void>;

package/dist/handlers/gen-post.d.ts

@@ -1,22 +0,0 @@
-/**
- * gen-post handler — POST ab-api /publish/caption/generate.
- *
- * Generates the text of a social post — per-platform title / description / tags —
- * for a finished video (the video itself is not touched or uploaded): the same endpoint and prompts the web studio's 「发布文案」
- * panel uses. Prompt wording, compliance rules and the platform roster all live
- * in ab-api (publish_prompts.go + the user's saved prompt overrides); this
- * handler only collects context and forwards it.
- *
- * Behavior:
- *   - --platform is repeatable and/or comma-separated; `all` (the default) expands
- *     to the three platforms the web panel shows. Each platform is one backend
- *     call (one LLM run, billed separately), issued concurrently.
- *   - --render-id links the result to a studio take so it shows up in the web
- *     panel; without it the backend generates without persisting anything.
- *   - --instruction is the user's "how should it read" request. With a draft
- *     (--title / --description / --tag) it rewrites that caption — single platform
- *     only, since the draft belongs to one platform. Without a draft it is an extra
- *     requirement applied to a fresh generation on every requested platform.
- */
-import type { HandlerContext, HandlerInput } from './index.js';
-export declare function genPost(input: HandlerInput, ctxIn: HandlerContext): Promise<void>;

package/dist/handlers/gen-video.d.ts

@@ -1,19 +0,0 @@
-/**
- * gen-video handler — POST ab-api /model/genVideo, then poll /model/getVideoStatus.
- *
- * Thin forwarder: the model roster, friendly aliases, defaults and per-model
- * constraints (aspect ratios / resolutions / durations / reference-image caps)
- * come from ab-api's capabilities catalog (see capabilities.ts), not from this
- * package. Pre-flight validation here is purely data-driven from that catalog —
- * the CLI carries no model matrix — and ab-api re-validates authoritatively.
- *
- * --model accepts a friendly alias or a full id; ab-api also resolves aliases
- * server-side, so an unknown value still passes through to the backend.
- *
- * Local image paths for first/last/reference frames are read and base64-encoded
- * into a data: URI; https / data: URIs pass through unchanged. Reference videos
- * and audio are the exception — they must already be public URLs, see
- * `requirePublicUrls`.
- */
-import type { HandlerContext, HandlerInput } from './index.js';
-export declare function genVideo(input: HandlerInput, ctxIn: HandlerContext): Promise<void>;

package/dist/handlers/gen-voice.d.ts

@@ -1,26 +0,0 @@
-/**
- * gen-voice handler — Minimax TTS via ab-api unified /tool/tts (provider=minimax).
- *
- * Operations:
- *   --list-voices true                 → GET available voice IDs from /voice/page (live)
- *   --list-voices true --local true    → print the built-in language-tagged
- *                                        fallback catalog (offline, no API call).
- *                                        **CLI-only escape hatch for offline dev.**
- *   default                            → synthesize text into an MP3 URL
- *
- * `local` is deliberately absent from `skills/gen-voice/skill.json`'s
- * `parameters`, which is what ab-agent turns into the model-facing tool schema.
- * A model asked to check a voice id would reach for `local: true`, get a
- * two-entry hardcoded list back, and conclude that a perfectly valid voice does
- * not exist — which is exactly what happened on the hosted web agent
- * ("本地回退列表中没有该音色"). The remote catalog is the only authority on
- * which voices exist; the local list is a developer convenience for working
- * without a token, and it is only reachable by typing the flag yourself.
- *
- * The previous Python script also offered `--download` to write the MP3 to
- * disk. That's intentionally dropped here: the agent flow never used it (the
- * audio URL is persisted in cloud) and removing local file I/O keeps the
- * handler stateless.
- */
-import type { HandlerContext, HandlerInput } from './index.js';
-export declare function genVoice(input: HandlerInput, ctxIn: HandlerContext): Promise<void>;

package/dist/handlers/index.d.ts

@@ -1,20 +0,0 @@
-/**
- * Handler registry — maps `entry.handler` strings to their implementation.
- *
- * Only `entry.type` in ('http' | 'builtin') uses this registry; python
- * skills go through spawn() in runner.ts and bypass handlers entirely.
- */
-import type { AuthPreflight } from '../auth/ensure.js';
-export type HandlerInput = Record<string, unknown>;
-export interface HandlerContext {
-    /** ISO-style skill name from the registry (e.g. `gen-image`). Used for x-invoke-skill. */
-    skillName: string;
-    /**
-     * Credential resolved by the dispatcher's preflight (runner.ts). Handlers pass
-     * `auth.token` into resolveHttpContext so the device flow can't run twice for
-     * a single invocation.
-     */
-    auth?: AuthPreflight;
-}
-export type SkillHandler = (input: HandlerInput, ctx: HandlerContext) => Promise<void>;
-export declare const HANDLERS: Record<string, SkillHandler>;

package/dist/handlers/shared.d.ts

@@ -1,26 +0,0 @@
-/**
- * Shared helpers for TS skill handlers.
- *
- * These were previously copy-pasted across gen-image / gen-video /
- * gen-digital-human / gen-voice. Centralizing them keeps argument coercion and
- * image-input resolution identical across every atomic generator.
- *
- * Lives under handlers/ (not src/ root) so the compiled `dist/handlers/shared.js`
- * travels with the rest of the handler bundle when ab-agent copies `dist/`.
- */
-/** Truthy check tolerant of CLI string values (`--flag` → true, `--flag true` → 'true'). */
-export declare function isTrue(value: unknown): boolean;
-/**
- * Coerce a flag value into a finite number, or `undefined` when absent/empty.
- * Throws SkillError on a non-numeric value so callers fail fast with a clear msg.
- */
-export declare function toNumber(value: unknown, name: string): number | undefined;
-/** Coerce a repeatable flag (string | string[] | undefined) into a string array. */
-export declare function toStringArray(value: unknown): string[];
-/**
- * Resolve an image reference into a value the backend accepts:
- *   - http(s) URLs and data: URIs pass through unchanged
- *   - local file paths are read and base64-encoded into a `data:<mime>;base64,…` URI
- * Throws SkillError when a local path does not exist or is not a file.
- */
-export declare function resolveImageInput(pathOrUrl: string): string;

package/dist/handlers/template-init.d.ts

@@ -1,10 +0,0 @@
-/**
- * template-authoring skill → `remixmate template init`.
- *
- * Agent hosts call skills as `remixmate template-authoring --dir X [--force]`;
- * this handler is a thin adapter so both entry points share one implementation.
- * Purely local (auth: none): fetches the starter via npm, no ab-api calls.
- */
-import type { HandlerContext, HandlerInput } from './index.js';
-export declare function templateInit(input: HandlerInput, _ctx: HandlerContext): Promise<void>;
-export default templateInit;

package/dist/http.d.ts

@@ -1,72 +0,0 @@
-/**
- * Shared HTTP helpers for ab-api endpoints.
- *
- * Centralizes the auth contract (X-Priv-Token + x-invoke-skill / x-invoke-agent /
- * x-conversation-id), business-code error handling (result.code != 0), and the
- * env var resolution order that every Python skill used to duplicate.
- *
- * Token resolution order (high → low), shared with the CLI auth commands via
- * src/auth/resolve.ts:
- *   1. opts.privateToken              — caller override (maps to --token/--priv-token)
- *   2. process.env.PRIV_TOKEN         — process env (CI / agent-embedded hosts)
- *   3. Credential_Store[apiBaseUrl]   — written by `remixmate login`
- *   (none) → throws SkillError        — non-interactive failure
- *
- * Base URL resolution:
- *   1. opts.apiBaseUrl                  — caller override
- *   2. process.env.MM_API_BASE_URL      — process env (point at local/staging here)
- *   3. process.env.MM_BACKEND_API_URL   — ab-agent's convention (back-compat)
- *   4. https://api.remixmate.ai/api    — production default (zero-config)
- */
-import { type Billing } from './billing.js';
-export { SkillError, EXIT } from './errors.js';
-/**
- * Resolve the ab-api base URL the same way for authenticated and device-flow calls.
- *
- * `MM_BACKEND_API_URL` is honored because several Python skills already fall back
- * to it (registry_loader, render_job_client, _vod_polling). Since runner.ts now
- * injects the resolved base URL into those child processes, leaving it out here
- * would let a prod default silently override an ab-agent-injected backend.
- */
-export declare function resolveApiBaseUrl(flag?: string): string;
-export interface HttpContext {
-    apiBaseUrl: string;
-    privateToken: string;
-    skillName: string;
-    agentName?: string;
-    conversationId?: string;
-}
-export declare function resolveHttpContext(skillName: string, opts?: {
-    apiBaseUrl?: string;
-    privateToken?: string;
-    /**
-     * Token already resolved by the dispatcher's auth preflight (runner.ts).
-     * Reusing it avoids a second credential-store read — and, more importantly,
-     * a second device-flow attempt — per skill invocation.
-     */
-    preflightToken?: string;
-}): Promise<HttpContext>;
-export interface MmResponse<T = unknown> {
-    code: number;
-    msg?: string;
-    data?: T;
-    /** Present only on responses that charged credits — see billing.ts. */
-    billing?: Billing;
-}
-/**
- * POST JSON to ab-api and return the parsed business payload.
- * Throws SkillError on HTTP errors or business code != 0.
- */
-export declare function mmPost<T = unknown>(ctx: HttpContext, pathOrUrl: string, body: unknown, opts?: {
-    timeoutMs?: number;
-}): Promise<T>;
-/**
- * Generic polling helper. Invokes `probe()` immediately, then every
- * `intervalMs`, until it returns a non-null value or `timeoutMs` elapses.
- * Probing first (rather than sleeping first) avoids a wasted initial interval
- * when the backend job is already complete.
- */
-export declare function pollUntil<T>(probe: () => Promise<T | null>, opts?: {
-    intervalMs?: number;
-    timeoutMs?: number;
-}): Promise<T>;

package/dist/index.d.ts

@@ -1,9 +0,0 @@
-/**
- * remixmate — public library exports.
- *
- * The CLI entrypoint lives in `cli.ts` (`bin: remixmate`). This file is the
- * library surface for type-sharing consumers; the published npm package
- * exposes it via `main: dist/index.js` / `types: dist/index.d.ts`.
- */
-export { loadSkills, findSkill, SKILLS_DIR } from './registry.js';
-export type { SkillDef, SkillEntry } from './registry.js';

package/dist/install.d.ts

@@ -1,71 +0,0 @@
-/**
- * `remixmate install` / `remixmate uninstall` — 把包内 skills/ 铺进 agent 宿主。
- *
- * 为什么需要一条命令，而不是让站点给出 `cp -R "$(npm root -g)/…/skills/." ~/.claude/skills/`：
- *
- *   1. 目标已经不止一个。Claude Code 与 Codex 现在用同一套 SKILL.md 格式
- *      （Codex 装到 $CODEX_HOME/skills/<name>），手工 cp 的心智成本直接翻倍。
- *   2. 拷贝出去的副本没有主人。`npm update -g` 之后包升了级、副本停在旧版；
- *      `npm uninstall -g` 之后副本原地变成孤儿。两种都是静默的 —— 本项目作者机器上
- *      就留着一批 5 月建的、指向早已不存在路径的 skill 目录，没有任何东西负责清理。
- *
- * 所以这里的安装是**受管**的：每个宿主的 skills 目录下写一份装机回执
- * (.remixmate-install.json)，记下版本、来源与这次铺下去的 skill 名单。升级照名单
- * 覆盖、卸载照名单删除、doctor 照名单比对版本 —— 三件事都不靠猜目录里哪些是我们的。
- *
- * 刻意不做的两件事：
- *   - 不挂 npm postinstall。`npm i -g` 时往 ~/.claude、~/.codex 写东西太越界，
- *     且 `--ignore-scripts` 下会静默失效。安装必须是用户显式发起的动作。
- *   - 不用软链。指向 $(npm root -g) 看着优雅，但 node 版本管理器一切换路径就变，
- *     全部断掉且极难排查。拷贝 + 回执 + doctor 漂移检查更稳。
- */
-export declare const INSTALL_VERB = "install";
-export declare const UNINSTALL_VERB = "uninstall";
-export type HostId = 'claude' | 'codex' | 'workbuddy' | 'codebuddy' | 'trae';
-interface Host {
-    id: HostId | 'custom';
-    label: string;
-    /** skill 的父目录 —— 安装写到 <skillsDir>/<skill-name>/。 */
-    skillsDir: string;
-}
-/** 已检测到、且**有用户级位置**的宿主。 */
-export declare function detectHosts(): Host[];
-/**
- * 检测到了、但只能项目级安装的宿主（当前只有 Trae）。
- *
- * 单独拎出来是为了别把它们**静默**跳过：用户装了 Trae 却在全局 install 的输出里
- * 完全看不到它，只会以为这个 CLI 不支持 —— 正是这次 WorkBuddy 的翻车方式。
- */
-export declare function projectOnlyHosts(): HostId[];
-export declare function packageVersion(): string;
-export declare function installUsage(): void;
-export declare function uninstallUsage(): void;
-export declare function runInstall(argv: string[]): number;
-export declare function runUninstall(argv: string[]): number;
-export interface InstallState {
-    label: string;
-    skillsDir: string;
-    /** 回执里的版本；null = 该宿主下没有本 CLI 的安装。 */
-    installedVersion: string | null;
-    /** 当前包的版本，供报告直接引用。 */
-    currentVersion: string;
-    /** 回执版本与当前包版本不一致。 */
-    drifted: boolean;
-}
-/**
- * 供 doctor 使用：每个宿主的安装状态。
- *
- * 漂移是这套方案唯一的静默失败模式 —— `npm update -g` 只动包，不动铺出去的副本，
- * 用户会拿着旧 SKILL.md 打新后端。doctor 是「为什么跑不起来」的统一入口，检查放这里。
- */
-export declare function installStates(): InstallState[];
-/**
- * 首次使用提示：检测到了宿主、但还没跑过 `remixmate install`（或装的是旧版）时返回一行提示，
- * 否则 null。
- *
- * 不用 postinstall 做这件事：npm 7+ 默认吞掉生命周期脚本的输出，而在安装期往用户家目录
- * 写文件太侵入。改为在用户/agent 一定会看到的地方（--list、--help 页脚、template init 的
- * 下一步、doctor）提示。纯本地读文件，不发网络请求。
- */
-export declare function skillInstallHint(states?: InstallState[]): string | null;
-export {};