@anchrd/intel-api 0.13.0 → 0.15.0

package/dist/model-catalog/model-catalog.js

@@ -1,99 +0,0 @@
-/**
- * The figures this package knows without asking anybody, and the ONLY place they are written down.
- *
- * ⚠️ It moved here out of `packages/ui` with #257, and the move is the point rather than the
- * tidying. The comment it used to carry accused itself correctly — *"it is a copy and it ages
- * silently"* — and named the reason it stayed a copy: the Cloudflare endpoint needs a token, and a
- * token does not belong in a SPA. It belongs here. What the browser gets is the answer, never the
- * credential, and the Workers AI half of this table is overwritten by the live one on every read.
- *
- * ⚠️ The Anthropic entries have no live source and will not get one. Cloudflare resells those models
- * through Unified Billing and publishes no price list for them, so they stay `builtin` even on a
- * perfectly healthy read — which is exactly why `source` is per entry and not per response.
- *
- * ⚠️ Workers AI models without `function_calling` are deliberately absent from the live merge. An
- * agent is a tool loop; a model that cannot call a tool cannot run one.
- *
- * Collected 2026-08-06 from `GET /accounts/{id}/ai/models/search` and from Anthropic's model list.
- */
-const builtin = [
-    entry("anthropic", "claude-opus-5", "Opus 5", 1_000_000, 5, 25),
-    entry("anthropic", "claude-sonnet-5", "Sonnet 5", 1_000_000, 3, 15),
-    entry("anthropic", "claude-sonnet-4", "Sonnet 4", 200_000, 3, 15),
-    entry("anthropic", "claude-haiku-4-5", "Haiku 4.5", 200_000, 1, 5),
-    entry("workers-ai", "@cf/openai/gpt-oss-120b", "GPT-OSS 120B", 128_000, 0.35, 0.75),
-    entry("workers-ai", "@cf/openai/gpt-oss-20b", "GPT-OSS 20B", 128_000, 0.2, 0.3),
-    entry("workers-ai", "@cf/moonshotai/kimi-k2.6", "Kimi K2.6", 262_144, 0.95, 4),
-    entry("workers-ai", "@cf/moonshotai/kimi-k2.7-code", "Kimi K2.7 Code", 262_144, 0.95, 4),
-    entry("workers-ai", "@cf/zai-org/glm-5.2", "GLM 5.2", 262_144, 1.4, 4.4),
-    entry("workers-ai", "@cf/zai-org/glm-4.7-flash", "GLM 4.7 Flash", 131_072, 0.0605, 0.4),
-    entry("workers-ai", "@cf/google/gemma-4-26b-a4b-it", "Gemma 4 26B", 256_000, 0.1, 0.3),
-    entry("workers-ai", "@cf/nvidia/nemotron-3-120b-a12b", "Nemotron 3 120B", 256_000, 0.5, 1.5),
-    entry("workers-ai", "@cf/meta/llama-4-scout-17b-16e-instruct", "Llama 4 Scout", 131_000, 0.27, 0.85),
-    entry("workers-ai", "@cf/meta/llama-3.3-70b-instruct-fp8-fast", "Llama 3.3 70B Fast", 24_000, 0.293, 2.253),
-    entry("workers-ai", "@cf/mistralai/mistral-small-3.1-24b-instruct", "Small 3.1 24B", 128_000, 0.351, 0.555),
-    entry("workers-ai", "@cf/ibm-granite/granite-4.0-h-micro", "Granite 4.0 Micro", 131_000, 0.017, 0.112),
-    entry("workers-ai", "@cf/qwen/qwen3-30b-a3b-fp8", "Qwen3 30B", 32_768, 0.0509, 0.335),
-];
-function entry(provider, model, name, contextTokens, inputPerMillion, outputPerMillion) {
-    return {
-        provider,
-        model,
-        name,
-        contextTokens,
-        price: { inputPerMillion, outputPerMillion },
-        source: "builtin",
-    };
-}
-/**
- * The model's own name, taken from its id rather than invented.
- *
- * A live Workers AI model that is not in the table above has no written-out name anywhere, and
- * "@cf/qwen/qwen3-30b-a3b-fp8" prettified by any rule short enough to write here comes out wrong —
- * so the last segment of the id is used as it stands. A raw name is easier to recognise as raw than
- * a wrong one is to recognise as wrong.
- */
-function nameFromId(model) {
-    const segments = model.split("/");
-    return segments[segments.length - 1] ?? model;
-}
-export function createModelCatalog(deps) {
-    return {
-        async list() {
-            if (!deps.cloudflare)
-                return { entries: builtin, liveStatus: "not_configured" };
-            try {
-                const live = await deps.cloudflare.workersAiModels();
-                const merged = new Map(builtin.map((known) => [`${known.provider}:${known.model}`, known]));
-                for (const model of live) {
-                    // ⚠️ A model that cannot call a tool is skipped rather than listed without figures. It
-                    // would be an offer that produces a broken agent for whoever took it.
-                    if (!model.functionCalling)
-                        continue;
-                    const key = `workers-ai:${model.name}`;
-                    const known = merged.get(key);
-                    merged.set(key, {
-                        provider: "workers-ai",
-                        model: model.name,
-                        name: known?.name ?? nameFromId(model.name),
-                        // ⚠️ The live figure wins, and a live figure that is MISSING wins too — falling back to
-                        // the table for one of the two halves would produce an entry that is half fresh and
-                        // half years old, labelled fresh. Either the account answered for this model or it did
-                        // not.
-                        contextTokens: model.contextTokens,
-                        price: model.price,
-                        source: "cloudflare",
-                    });
-                }
-                return { entries: [...merged.values()], liveStatus: "read" };
-            }
-            catch {
-                // ⚠️ Named, not thrown. The select has to render either way — an agent whose model cannot be
-                // chosen is an agent nobody can repair from that screen — and the alternative to a stale
-                // price here is no price at all, which helps nobody choose. What the caller gets is the
-                // table plus the reason it is the table, and the screen says so.
-                return { entries: builtin, liveStatus: "unreadable" };
-            }
-        },
-    };
-}

package/dist/model-catalog/model-catalog.types.d.ts

@@ -1,15 +0,0 @@
-import type { ModelCatalog } from "@anchrd/intel-contract";
-import type { CloudflareAccountApi } from "../adapters/cloudflare-api/cloudflare-api.types.js";
-export interface ModelCatalogDeps {
-    /** Absent where the deployment configured no Cloudflare read token. A named state, not an error. */
-    cloudflare?: Pick<CloudflareAccountApi, "workersAiModels">;
-}
-export interface ModelCatalogService {
-    /**
-     * ⚠️ The answer shape lives in `@anchrd/intel-contract`, because the select in the browser parses
-     * it. Its `source` field is per ENTRY on purpose: Cloudflare publishes figures for the models it
-     * serves itself and none for the Anthropic models it resells, so a healthy read still leaves half
-     * the list on a written-out table (#257).
-     */
-    list(): Promise<ModelCatalog>;
-}

package/dist/model-catalog/model-catalog.types.js

@@ -1 +0,0 @@
-export {};

package/dist/nodes/board/board.d.ts

@@ -1,59 +0,0 @@
-import { type BoardDocument } from "@anchrd/intel-contract";
-import type { BoardDeps, BoardOperations } from "./board.types.js";
-/**
- * A stored board brought up to the current schema, before it is validated.
- *
- * ⚠️ It runs before `BoardDocument.parse`, on `unknown`, because after that parse a missing field or
- * a repeated id is already a refusal — and `parseStoredBoard` is deliberately loud
- * (`board_unreadable`), so an un-upgraded board would not read as "old", it would read as corrupt.
- *
- * The upgrade is persisted by the next write of any kind, because every write serialises the whole
- * document. Nothing has to be migrated ahead of time and nothing has to be re-migrated.
- */
-export declare function upgradeStoredBoard(parsed: unknown): unknown;
-/**
- * The first id a board document uses for two different things (anchrd/intel#321).
- *
- * ⚠️ Deliberately NOT a rule on `BoardDocument`, and that is the whole decision. A schema rule would
- * reach every parse of a stored body — `parseStoredBoard`, `indexing.ts`, the link reader — and a
- * board imported before this existed would stop answering with `board_unreadable`: the whole board
- * gone over something that costs one view. It is the trap #311 walked into, and #318 walked into
- * from the other side.
- *
- * ⚠️ And NOT folded in `upgradeStoredBoard` either, which is where the sibling rules of #318 went. A
- * repeated `dependsOn`, label or reference carries no information, so dropping the second mention
- * loses nothing. Two tasks under one id are two whole tasks — titles, dates, descriptions — and a
- * fold on the READ is written back by the next save of any kind, because every write serialises the
- * whole document. That is one task gone for good, for every board, without anybody having asked.
- * The UI folds the same pair for a DRAWING (`orderedTasks`), which costs nothing: the document keeps
- * both, and repairing the pair brings the second card back.
- *
- * ⚠️ What this does NOT rescue, and it is worth knowing: `replaced` matches a task by id, so the
- * first `board_task_update` against such a pair writes the SAME task into both entries. The stored
- * board is then two identical tasks rather than two different ones. That is a consequence of
- * addressing a board by task id at all (#285) and predates this rule; the reason the rule is at the
- * import is to stop the pair from existing, not to make it survivable.
- *
- * So it is asked exactly where there is a caller to answer: the bundle import, the one door a board
- * document written elsewhere comes in through. Everything else mints task ids itself (`deps.id()`)
- * and takes its status list through `ConfigureBoardInput`, which has demanded distinct ids since
- * #285.
- */
-export declare function repeatedBoardId(document: BoardDocument): {
-    list: "statuses" | "tasks";
-    id: string;
-} | null;
-/**
- * Every board operation, applied to the document rather than to the file (#285).
- *
- * ⚠️ This module is where a board's rules live, and it is deliberately pure: it takes a document
- * and gives back the next one. The version, R2 and the retry against a racing write are the
- * service's business (`nodes.ts`), and the surfaces have no rules of their own — HTTP, MCP and the
- * UI all arrive here. A second implementation of "may this task depend on that one" is the thing
- * this shape exists to prevent.
- *
- * ⚠️ What it does NOT check is anything that needs the tree: whether a `references` id names a node
- * the writer may see, and whether an `agent` assignee is really an agent. Those are reads against
- * D1 and the ACL, so they happen in the service before the document is touched at all.
- */
-export declare function createBoard(deps: BoardDeps): BoardOperations;