@anchrd/intel-api 0.14.0 → 0.16.0

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,61 +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. A board that already holds
- * one is repaired by `repairTaskIds` below — asked for, never done on the quiet — and the refusal
- * here names it, because "your file is wrong" without a way out is where anchrd/intel#341 started.
- *
- * 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;