@aisa-one/cli 0.6.8 → 0.6.10

package/dist/commands/mcp.d.ts

@@ -1,47 +1,19 @@
-/**
- * `aisa mcp setup` — write real, per-client MCP entries from the live manifest.
- *
- * Three rules, each one a lesson from the version this replaces:
- *
- * 1. The server list comes from the platform's discovery manifest at setup
- *    time, never from this file. Servers ship without a CLI release.
- * 2. Nothing is written unless the manifest was actually fetched. The old
- *    command wrote first and verified never, which is how a dead hostname
- *    sat in users' configs across releases.
- * 3. Each client gets the shape it executes: `{url}` for clients that dial
- *    HTTP themselves, an `npx mcp-remote` stdio bridge for the ones that only
- *    spawn processes. One shape for all three was the old bug.
- *
- * Auth is a choice the user already made: with an API key configured, entries
- * carry it as a Bearer header (zero-interaction, but the key lands in each
- * client's config file); without one, entries carry no credentials and the
- * server's 401 challenge drives the client through the Clerk OAuth flow.
- */
+/** Configure the unified Router MCP. Existing client entries are preserved. */
 export interface LiveServer {
     slug: string;
     name: string;
     endpoint: string;
-    toolCount: number;
-    /** One-paragraph capability description from the manifest — the single
-     *  source of truth for what a server does; rendered on the connect page. */
+    toolCount?: number;
+    /** Capability description rendered on the connect page. */
     description: string;
     category: string;
 }
 export declare const stripped: (name: string) => string;
-/**
- * Which servers exist, asked of the host that runs them.
- *
- * The index is preferred and the manifest is the fallback, in that order for
- * one reason: the manifest is a snapshot committed by hand, and on 2026-08-25
- * it was three servers and 72 tools behind what the host was actually serving.
- * Anything derived from a running process cannot drift that way.
- *
- * The fallback is not defensive padding — the index is newer than some
- * deployments, and a self-hosted gateway configured through `baseUrl` may
- * never grow one. A user in either case should still get a working setup from
- * a slightly stale list rather than an error.
- */
-export declare function fetchLiveServers(): Promise<LiveServer[]>;
+/** Router's fixed public MCP contract, independent of the legacy module catalog. */
+export declare function unifiedMcpServer(): LiveServer;
+export declare function isUnifiedMcpSelection(servers: LiveServer[]): boolean;
+/** The unified entry is fixed; setup does not depend on a directory service. */
+export declare function getMcpServers(): LiveServer[];
 /** One config entry in the shape the client actually executes. */
 export declare function buildEntry(shape: "url" | "stdio", endpoint: string, key: string | undefined): Record<string, unknown>;
 export type WriteResult = {
@@ -51,12 +23,7 @@ export type WriteResult = {
     ok: false;
     reason: string;
 };
-/**
- * Write the chosen servers (plus the docs server) into one client's config
- * file. Shared by `aisa mcp setup` and `aisa connect` so the two entry points
- * cannot drift in how they treat existing files: unparseable JSON is refused,
- * never replaced, and only the known-dead legacy entry is cleaned up.
- */
+/** Add the unified entry without deleting old AIsa, docs, or unrelated entries. */
 export declare function writeClientConfig(agent: string, chosen: LiveServer[], key: string | undefined): WriteResult;
 export declare function mcpSetupAction(options: {
     agent?: string;

package/dist/commands/mcp.js

@@ -2,57 +2,27 @@ import { existsSync, readFileSync, writeFileSync } from "node:fs";
 import chalk from "chalk";
 import { success, error, info, hint } from "../utils/display.js";
 import { expandHome, ensureDir } from "../utils/file.js";
-import { MCP_CONFIGS, MCP_MANIFEST_URL, MCP_CATALOG_URL, DOCS_MCP_URL, MCP_DEFAULT_SLUGS } from "../constants.js";
-import { httpFetch, MAX_ATTEMPTS } from "../utils/http.js";
+import { MCP_CONFIGS, MCP_URL } from "../constants.js";
+import { httpFetch } from "../utils/http.js";
 import { getAccessToken } from "../config.js";
+import { clientConfigKey } from "../utils/client-key.js";
 import { detectClients } from "./connect.js";
 import { join } from "node:path";
 export const stripped = (name) => name.replace(/^AIsa\s+/i, "");
-function toLive(servers) {
-    return servers
-        .filter((s) => s.status === "live" && s.slug && s.transport?.endpoint)
-        .map((s) => ({
-        slug: s.slug,
-        name: s.name ?? s.slug,
-        endpoint: s.transport.endpoint,
-        toolCount: s.toolCount ?? s.tools?.length ?? 0,
-        description: s.description ?? "",
-        category: s.category ?? "Other",
-    }));
+/** Router's fixed public MCP contract, independent of the legacy module catalog. */
+export function unifiedMcpServer() {
+    return {
+        slug: "router", name: "AIsa Router", endpoint: MCP_URL,
+        description: "One AIsa connection to discover and use tools through the Router.",
+        category: "AIsa",
+    };
 }
-async function readSource(url, attempts) {
-    const res = await httpFetch(url, { idempotent: true, maxAttempts: attempts, timeoutMs: 15_000 });
-    if (!res.ok)
-        throw new Error(`${url} answered HTTP ${res.status}`);
-    const doc = (await res.json());
-    const live = toLive(doc.servers ?? []);
-    if (live.length === 0)
-        throw new Error(`${url} lists no live servers`);
-    return live;
+export function isUnifiedMcpSelection(servers) {
+    return servers.length === 1 && servers[0].slug === "router" && servers[0].endpoint === MCP_URL;
 }
-/**
- * Which servers exist, asked of the host that runs them.
- *
- * The index is preferred and the manifest is the fallback, in that order for
- * one reason: the manifest is a snapshot committed by hand, and on 2026-08-25
- * it was three servers and 72 tools behind what the host was actually serving.
- * Anything derived from a running process cannot drift that way.
- *
- * The fallback is not defensive padding — the index is newer than some
- * deployments, and a self-hosted gateway configured through `baseUrl` may
- * never grow one. A user in either case should still get a working setup from
- * a slightly stale list rather than an error.
- */
-export async function fetchLiveServers() {
-    try {
-        // One attempt only: there is somewhere else to go, so spending a retry
-        // budget here just delays the fallback. The manifest is the last resort
-        // and gets the full three.
-        return await readSource(MCP_CATALOG_URL, 1);
-    }
-    catch {
-        return await readSource(MCP_MANIFEST_URL, MAX_ATTEMPTS);
-    }
+/** The unified entry is fixed; setup does not depend on a directory service. */
+export function getMcpServers() {
+    return [unifiedMcpServer()];
 }
 /** One config entry in the shape the client actually executes. */
 export function buildEntry(shape, endpoint, key) {
@@ -69,15 +39,10 @@ export function buildEntry(shape, endpoint, key) {
     args.push("--transport", "http-only");
     return { command: "npx", args };
 }
-/** The dead entry every pre-v0.3 setup wrote. Remove it on sight. */
-const DEAD_URL = "https://docs.aisa.one/mcp";
-/**
- * Write the chosen servers (plus the docs server) into one client's config
- * file. Shared by `aisa mcp setup` and `aisa connect` so the two entry points
- * cannot drift in how they treat existing files: unparseable JSON is refused,
- * never replaced, and only the known-dead legacy entry is cleaned up.
- */
+/** Add the unified entry without deleting old AIsa, docs, or unrelated entries. */
 export function writeClientConfig(agent, chosen, key) {
+    if (!isUnifiedMcpSelection(chosen))
+        return { ok: false, reason: "Only the unified AIsa Router MCP can be configured" };
     const config = MCP_CONFIGS[agent];
     if (!config)
         return { ok: false, reason: `unknown client "${agent}"` };
@@ -97,20 +62,12 @@ export function writeClientConfig(agent, chosen, key) {
         ensureDir(join(filePath, ".."));
     }
     const entries = existing[config.key] || {};
-    // Clean up the dead entry earlier releases wrote, and only that one: an
-    // "aisa" entry the user pointed somewhere else on purpose stays.
-    const stale = entries["aisa"];
-    if (stale?.url === DEAD_URL)
-        delete entries["aisa"];
     for (const s of chosen) {
         entries[`aisa-${s.slug}`] = buildEntry(config.shape, s.endpoint, key);
     }
-    // The docs-search MCP is tiny, unauthenticated, and answers "how do I call
-    // this" questions — always included.
-    entries["aisa-docs"] = buildEntry(config.shape, DOCS_MCP_URL, undefined);
     existing[config.key] = entries;
     writeFileSync(filePath, JSON.stringify(existing, null, 2) + "\n", "utf-8");
-    return { ok: true, written: chosen.length + 1 };
+    return { ok: true, written: chosen.length };
 }
 export async function mcpSetupAction(options) {
     const requested = options.agent && options.agent !== "all" ? [options.agent] : Object.keys(MCP_CONFIGS);
@@ -137,24 +94,12 @@ export async function mcpSetupAction(options) {
         process.exitCode = 1;
         return;
     }
-    // Fetch before touching any file: a setup that cannot see the manifest has
-    // nothing true to write.
-    let servers;
-    try {
-        servers = await fetchLiveServers();
-    }
-    catch (e) {
-        error(`Could not read the MCP manifest at ${MCP_MANIFEST_URL}: ${e.message}`);
-        hint("Nothing was written. Check your network and try again.");
-        process.exitCode = 1;
-        return;
-    }
-    const chosen = options.all
-        ? servers
-        : servers.filter((s) => MCP_DEFAULT_SLUGS.includes(s.slug));
-    const skipped = servers.length - chosen.length;
-    const key = await getAccessToken();
-    if (key) {
+    const servers = getMcpServers();
+    // --all remains accepted for existing scripts; there is only one entry.
+    const chosen = servers;
+    info("Adds aisa-router only. Existing MCP entries are preserved; remove old domain entries manually.");
+    const credential = await getAccessToken();
+    if (credential) {
         info("Using your configured API key (Bearer). It will be written into each client's config file.");
     }
     else {
@@ -171,11 +116,23 @@ export async function mcpSetupAction(options) {
             console.log(`  ${chalk.cyan(MCP_CONFIGS[agent].path)}  (${agent}, ${MCP_CONFIGS[agent].shape})`);
         }
         for (const s of chosen) {
-            console.log(`    ${chalk.gray(`aisa-${s.slug}`)}  ${stripped(s.name)} (${s.toolCount} tools)`);
+            console.log(`    ${chalk.gray(`aisa-${s.slug}`)}  ${stripped(s.name)}`);
         }
         hint("Nothing was written. Re-run with --yes to apply, or use `aisa connect` to choose interactively.");
         return;
     }
+    // A client config never refreshes an OAuth token, so it gets the durable
+    // key instead — otherwise every entry stops working a day from now.
+    let key;
+    try {
+        key = credential ? await clientConfigKey(credential) : undefined;
+    }
+    catch (e) {
+        error(e.message);
+        hint("Nothing was written.");
+        process.exitCode = 1;
+        return;
+    }
     for (const agent of targets) {
         const config = MCP_CONFIGS[agent];
         const result = writeClientConfig(agent, chosen, key);
@@ -186,12 +143,10 @@ export async function mcpSetupAction(options) {
         }
         console.log(`  ${chalk.green("✓")} ${agent}: ${result.written} servers (${config.shape}) → ${config.path}`);
     }
-    success(`Configured ${chosen.length} live servers plus docs search for ${targets.length} client(s)`);
+    success(`Configured the unified AIsa Router MCP for ${targets.length} client(s)`);
     for (const s of chosen) {
-        console.log(`    ${chalk.cyan(`aisa-${s.slug}`)}  ${stripped(s.name)} (${s.toolCount} tools)`);
+        console.log(`    ${chalk.cyan(`aisa-${s.slug}`)}  ${stripped(s.name)}`);
     }
-    if (skipped > 0)
-        hint(`${skipped} more live servers available — run with --all to configure every one`);
     hint("Restart your agent/editor to activate");
 }
 /**
@@ -223,10 +178,18 @@ export async function mcpStatusAction() {
             console.log(`  ${chalk.gray("○")} ${agent}: not configured`);
             continue;
         }
-        console.log(`  ${chalk.green("✓")} ${agent}: ${ours.length} entries`);
+        const unified = ours.filter(([, entry]) => {
+            const e = entry;
+            return (e.url ?? e.args?.find((a) => a.startsWith("http"))) === MCP_URL;
+        }).length;
+        console.log(`  ${unified ? chalk.green("✓") : chalk.yellow("!")} ${agent}: ${unified} unified, ${ours.length - unified} other AIsa entries (not checked)`);
         for (const [name, entry] of ours) {
             const e = entry;
             const endpoint = e.url ?? e.args?.find((a) => a.startsWith("http"));
+            if (endpoint && endpoint !== MCP_URL) {
+                console.log(`    ${name}: ${endpoint} — existing entry preserved (not checked); remove manually from ${filePath} if no longer needed`);
+                continue;
+            }
             if (endpoint) {
                 const users = endpoints.get(endpoint) ?? [];
                 users.push(`${agent}/${name}`);

package/dist/commands/oauth-login.js

@@ -307,7 +307,7 @@ Default: open a browser this person can actually use (SSH/CI/no display skip the
 
 If this process already timed out, or the URL/code is from an older run, start a fresh aisa login and use the new URL and its result. Do not reuse a stale paste.
 
-No browser and no TTY: this CLI cannot complete OAuth here. Normal setup is native MCP OAuth at https://tools.aisa.one/mcp.
+No browser and no TTY: this CLI cannot complete OAuth here. Normal setup is native MCP OAuth at https://mcp.aisa.one/mcp.
 
 Do not report connected unless login stored credentials and the following balance check succeeded. aisa whoami and stored local credentials are not proof. Scripts/CI: AISA_API_KEY or --key.
 `;

package/dist/completion.js

@@ -7,7 +7,7 @@ export function isShell(value) {
 }
 // ── Dynamic candidates, all cache-only ───────────────────────────────────────
 function cachedProviders() {
-    return readCache(`catalog/${cacheScope()}/category.json`)?.data.apis || [];
+    return readCache(`catalog-v2/${cacheScope()}/category.json`)?.data.apis || [];
 }
 function providerIds() {
     return cachedProviders().map((p) => ({

package/dist/constants.d.ts

@@ -1,42 +1,11 @@
-export declare const VERSION = "0.6.8";
+export declare const VERSION = "0.6.10";
 /** Default for chat when no model is configured or supplied explicitly. */
 export declare const DEFAULT_CHAT_MODEL = "deepseek-v4.1-flash";
 /** Root of the platform. Per-surface bases are derived in api.ts#resolveBases. */
 export declare const BASE_URL = "https://api.aisa.one";
 export declare const ENV_VAR_NAME = "AISA_API_KEY";
-/**
- * The MCP discovery manifest — the single source of truth for which servers
- * exist and where they live. The CLI deliberately knows no server list of its
- * own: servers ship and retire on the platform side, and reading the manifest
- * at setup time means a new server works without a CLI release (the same
- * philosophy as live catalog/MCP discovery, applied to the fast-moving side).
- *
- * History: until v0.2.4 this file hardcoded MCP_URL = "https://docs.aisa.one/mcp",
- * a host that does not resolve — every `aisa mcp setup` wrote a dead entry into
- * users' configs, and nothing noticed because the command had no tests.
- */
-export declare const MCP_MANIFEST_URL = "https://aisa.one/.well-known/mcp.json";
-/**
- * The live server index, served by the MCP host itself.
- *
- * Preferred over the manifest above, which is generated offline and committed
- * by hand: being a snapshot it drifts. Measured 2026-08-25 it named 11 servers
- * and 188 tools while mcp.aisa.one was serving 14 and 260 — agentmail (49
- * tools), seo (21) and creator-discovery (2) missing outright, so every user
- * of this CLI was offered 72 fewer tools than exist.
- *
- * It is also 12 KB against the manifest's 137 KB. Most of that difference is
- * tool names, of which this CLI uses exactly one thing: `tools.length`, to
- * print a count. The index carries `toolCount` instead; a client that wants
- * the names is about to connect anyway, and `tools/list` is authoritative.
- *
- * The manifest stays as the fallback — this endpoint is newer than some
- * deployments — and as the public document for readers who want the roadmap
- * of planned servers, which a running process cannot honestly report.
- */
-export declare const MCP_CATALOG_URL = "https://mcp.aisa.one/servers";
-/** Mintlify's docs-search MCP (3 tools: search/read/feedback). Unauthenticated. */
-export declare const DOCS_MCP_URL = "https://aisa.one/docs/mcp";
+/** The only business MCP resource configured by this CLI. */
+export declare const MCP_URL = "https://mcp.aisa.one/mcp";
 /** Where credit is added. Payment always finishes in a browser — Stripe's
  *  hosted page owns the card details, and 3-D Secure needs one. */
 /** The account surface. Printed where someone can act on it, not linked. */
@@ -50,22 +19,6 @@ export declare const LLM_RESPONSES_BASE_URL = "https://api.aisa.one/v1";
 /** The provider name written into Codex's config.toml. Frozen: renaming it
  *  orphans the block we would otherwise remove cleanly. */
 export declare const AISA_PROVIDER_ID = "aisa";
-/**
- * Servers configured by default. Eleven entries per client is a lot of config;
- * these five cover the broadest agent needs, and `--all` configures everything
- * the manifest lists as live.
- */
-export declare const MCP_DEFAULT_SLUGS: readonly string[];
-/**
- * Why one and not five.
- *
- * Each server is its own OAuth resource — the authorization URL carries
- * `resource=https://mcp.aisa.one/<slug>/mcp` (RFC 8707) — so a keyless
- * install authorises once per server. Defaulting to five meant five browser
- * round trips before anything worked, observed 2026-08-20. Web search is the
- * one every agent reaches for; the rest are one tick away, and a configured
- * API key skips authorization for all of them anyway.
- */
 export declare const AGENT_DIRS: Record<string, string>;
 /**
  * Per-client config shape. This is the part v0.2.4 got wrong even apart from

package/dist/constants.js

@@ -1,42 +1,11 @@
-export const VERSION = "0.6.8";
+export const VERSION = "0.6.10";
 /** Default for chat when no model is configured or supplied explicitly. */
 export const DEFAULT_CHAT_MODEL = "deepseek-v4.1-flash";
 /** Root of the platform. Per-surface bases are derived in api.ts#resolveBases. */
 export const BASE_URL = "https://api.aisa.one";
 export const ENV_VAR_NAME = "AISA_API_KEY";
-/**
- * The MCP discovery manifest — the single source of truth for which servers
- * exist and where they live. The CLI deliberately knows no server list of its
- * own: servers ship and retire on the platform side, and reading the manifest
- * at setup time means a new server works without a CLI release (the same
- * philosophy as live catalog/MCP discovery, applied to the fast-moving side).
- *
- * History: until v0.2.4 this file hardcoded MCP_URL = "https://docs.aisa.one/mcp",
- * a host that does not resolve — every `aisa mcp setup` wrote a dead entry into
- * users' configs, and nothing noticed because the command had no tests.
- */
-export const MCP_MANIFEST_URL = "https://aisa.one/.well-known/mcp.json";
-/**
- * The live server index, served by the MCP host itself.
- *
- * Preferred over the manifest above, which is generated offline and committed
- * by hand: being a snapshot it drifts. Measured 2026-08-25 it named 11 servers
- * and 188 tools while mcp.aisa.one was serving 14 and 260 — agentmail (49
- * tools), seo (21) and creator-discovery (2) missing outright, so every user
- * of this CLI was offered 72 fewer tools than exist.
- *
- * It is also 12 KB against the manifest's 137 KB. Most of that difference is
- * tool names, of which this CLI uses exactly one thing: `tools.length`, to
- * print a count. The index carries `toolCount` instead; a client that wants
- * the names is about to connect anyway, and `tools/list` is authoritative.
- *
- * The manifest stays as the fallback — this endpoint is newer than some
- * deployments — and as the public document for readers who want the roadmap
- * of planned servers, which a running process cannot honestly report.
- */
-export const MCP_CATALOG_URL = "https://mcp.aisa.one/servers";
-/** Mintlify's docs-search MCP (3 tools: search/read/feedback). Unauthenticated. */
-export const DOCS_MCP_URL = "https://aisa.one/docs/mcp";
+/** The only business MCP resource configured by this CLI. */
+export const MCP_URL = "https://mcp.aisa.one/mcp";
 /** Where credit is added. Payment always finishes in a browser — Stripe's
  *  hosted page owns the card details, and 3-D Secure needs one. */
 /** The account surface. Printed where someone can act on it, not linked. */
@@ -50,22 +19,6 @@ export const LLM_RESPONSES_BASE_URL = "https://api.aisa.one/v1";
 /** The provider name written into Codex's config.toml. Frozen: renaming it
  *  orphans the block we would otherwise remove cleanly. */
 export const AISA_PROVIDER_ID = "aisa";
-/**
- * Servers configured by default. Eleven entries per client is a lot of config;
- * these five cover the broadest agent needs, and `--all` configures everything
- * the manifest lists as live.
- */
-export const MCP_DEFAULT_SLUGS = ["web-search"];
-/**
- * Why one and not five.
- *
- * Each server is its own OAuth resource — the authorization URL carries
- * `resource=https://mcp.aisa.one/<slug>/mcp` (RFC 8707) — so a keyless
- * install authorises once per server. Defaulting to five meant five browser
- * round trips before anything worked, observed 2026-08-20. Web search is the
- * one every agent reaches for; the rest are one tick away, and a configured
- * API key skips authorization for all of them anyway.
- */
 export const AGENT_DIRS = {
     claude: "~/.claude/skills/",
     cursor: "~/.cursor/skills/",

package/dist/index.js

@@ -229,7 +229,7 @@ skills
 // Top-level so the zero-install one-liner works: `npx @aisa-one/cli connect`.
 program
     .command("connect")
-    .description("Connect AIsa MCP servers to your local coding agents via a one-shot local page")
+    .description("Connect the unified AIsa Router MCP and models to your coding agents")
     .option("--no-open", "Print the URL instead of opening the browser")
     .option("--port <port>", "Bind a specific port (default: random)")
     .option("--dry-run", "Show what would be configured without writing anything")
@@ -248,9 +248,9 @@ program
 const mcp = program.command("mcp").description("MCP server integration");
 mcp
     .command("setup")
-    .description("Configure AIsa MCP servers (from the live manifest) for AI agents")
+    .description("Configure the unified AIsa Router MCP for AI agents")
     .option("--agent <agent>", "Target agent: cursor, claude-desktop, all")
-    .option("--all", "Configure every live server, not just the default set")
+    .option("--all", "Compatibility option: configures the single AIsa Router MCP")
     .option("--yes", "Write the files. Without it, print what would change and stop")
     .action(wrap(mcpSetupAction));
 mcp

package/dist/utils/client-key.d.ts

@@ -0,0 +1 @@
+export declare function clientConfigKey(credential: string): Promise<string>;

package/dist/utils/client-key.js

@@ -0,0 +1,36 @@
+import { BASE_URL } from "../constants.js";
+import { httpFetch } from "./http.js";
+/**
+ * The credential a third-party client config gets.
+ *
+ * Since 0.6.0 browser login stores an OAuth session: this CLI refreshes the
+ * access token, but a token copied into Claude Code, Codex or Cursor stays
+ * the snapshot it was — and expires in 24 hours, taking every MCP entry and
+ * model provider with it the next day. Those configs need an API key, so an
+ * OAuth access token is traded for the durable "aisa cli" key at
+ * /v1/keys/mint. The server returns the same managed key on every call, so
+ * nothing piles up; the CLI's own session is left as it is.
+ *
+ * A static key (`login --key`, AISA_API_KEY) already is one and passes
+ * through untouched — the mint endpoint refuses API keys anyway.
+ */
+const MINT_URL = `${BASE_URL}/v1/keys/mint`;
+export async function clientConfigKey(credential) {
+    if (credential.startsWith("sk-"))
+        return credential;
+    const res = await httpFetch(MINT_URL, {
+        method: "POST",
+        headers: { Authorization: `Bearer ${credential}`, "Content-Type": "application/json" },
+        // Named explicitly; no body means the same thing to the server.
+        body: JSON.stringify({ client: "cli" }),
+        timeoutMs: 20_000,
+    });
+    if (res.status === 404) {
+        throw new Error("this deployment cannot issue CLI keys — copy one from https://console.aisa.one/api-keys and run: aisa login --key <key>");
+    }
+    const minted = (await res.json().catch(() => ({})));
+    if (!res.ok || !minted.key) {
+        throw new Error(`could not issue a key for your clients: ${minted.error ?? `HTTP ${res.status}`}`);
+    }
+    return minted.key;
+}

package/dist/utils/update-check.js

@@ -5,11 +5,9 @@ import { httpFetch } from "./http.js";
 /**
  * Throttled, best-effort check for a newer published version.
  *
- * `connect` already makes a network call before it does anything else
- * (fetchLiveServers), so piggybacking one more cheap lookup costs nothing —
- * but only once a day: the npm-registry hit is cached like the API catalog
- * and skills index (see cache.ts), so every other run within the window
- * reads the last answer off disk instead of asking again.
+ * The npm-registry lookup is cached once a day like the API catalog
+ * and skills index (see cache.ts), so runs within the window
+ * read the last answer off disk instead of asking again.
  *
  * Never throws and never blocks longer than FETCH_TIMEOUT_MS. Offline, a
  * timeout, or a non-200 all resolve to "nothing to report" rather than an

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@aisa-one/cli",
-  "version": "0.6.8",
+  "version": "0.6.10",
   "description": "CLI for the AIsa unified AI infrastructure platform - one API key for 80+ LLMs and 900+ endpoints across finance, search, social, and video APIs",
   "type": "module",
   "main": "dist/index.js",