@combycode/llm-sdk 2.2.2 → 3.0.0

package/dist/wire/mcp-specs.d.ts

@@ -0,0 +1,13 @@
+/** The MCP Streamable-HTTP spec family.
+ *
+ *  A sibling of the provider families, loaded separately for the same reason: an
+ *  application that never talks to an MCP server should not carry these, and the
+ *  generated `registry.ts` imports everything.
+ *
+ *  MCP is the case that shows the spec format is about NETWORKING rather than about
+ *  LLM providers — a JSON-RPC envelope, era-dependent routing headers and a
+ *  long-lived stream are described by the same six constructs a chat request uses.
+ */
+import type { WireSpec } from './interpreter';
+/** Resolve an MCP spec by id, flattening its `extends` chain. */
+export declare function mcpSpec(id: string): WireSpec;

package/dist/wire/media-specs.d.ts

@@ -0,0 +1,20 @@
+/** The media wire specs the RUNTIME loads, resolved and memoised.
+ *
+ *  A sibling of `chat-specs.ts` and separate from it for the same reason that file
+ *  is separate from `registry.ts`: the generated index imports all 71 specs, so any
+ *  adapter reaching for it pulls in every family whether or not anything runs them.
+ *  The runtime loads one family at a time, as each is migrated, so what ships is
+ *  what executes.
+ *
+ *  Only the leaves are exported — the `*.base` specs exist to be inherited from and
+ *  are never built directly, so naming one is a mistake worth catching.
+ */
+import type { WireSpec } from './interpreter';
+/** The media spec for `id`, with its inheritance chain applied.
+ *
+ *  Throws on an unknown or abstract id rather than substituting something
+ *  plausible: a quietly wrong endpoint is the failure mode the specs exist to end. */
+export declare function mediaSpec(id: string): WireSpec;
+/** Buildable media spec ids — asserted by the tests so this list and the shipped
+ *  spec files cannot drift apart unnoticed. */
+export declare const MEDIA_SPEC_IDS: readonly string[];

package/dist/wire/pins.d.ts

@@ -0,0 +1,34 @@
+/** Which spec builds a model's request when the catalog has no pin for it.
+ *
+ *  Every catalogued model carries an explicit `wireSpec`, so this only decides for
+ *  the models the catalog does not know: one released after this build, or an
+ *  engine running without a catalog at all. That case is not an edge — it is how
+ *  the SDK works on the day a provider ships something new — so it keeps a real
+ *  answer rather than a guess.
+ *
+ *  It is DATA, not code, for the same reason the specs are: the Python and Rust
+ *  ports read this file instead of each re-implementing version arithmetic and
+ *  drifting from it. Two versions of that arithmetic is exactly how the 2.2.1
+ *  regression happened.
+ *
+ *  Rules are ordered and the first match wins; `default` answers everything else.
+ */
+export interface PinRule {
+    /** Anchored regular expression, matched against the model id. */
+    match: string;
+    spec: string;
+    /** Why this band exists. Read by humans, not by the resolver. */
+    why?: string;
+}
+export interface ModelPins {
+    id: string;
+    rules?: PinRule[];
+    default: string;
+}
+/** The spec id for `model`, from an ordered rule table.
+ *
+ *  The id is lower-cased and stripped of a `provider/` prefix first, because a
+ *  caller may legitimately pass either form and a band must not depend on which. */
+export declare function pinFor(model: string, pins: ModelPins): string;
+export declare const ANTHROPIC_MESSAGE_PINS: ModelPins;
+export declare const GOOGLE_GENERATE_PINS: ModelPins;

package/dist/wire/registry.d.ts

@@ -0,0 +1,20 @@
+/** Every wire spec the SDK ships, indexed by id.
+ *
+ *  A spec says HOW to talk to a provider API: field names, enum values, defaults,
+ *  which shape a model version takes. It is deliberately DATA, so the same file
+ *  is consumed by this SDK and by the Python and Rust ports, and a provider
+ *  change is one reviewable diff rather than three code changes.
+ *
+ *  GENERATED by scripts/gen-wire-registry.ts — do not hand-edit. Add a spec by
+ *  dropping the JSON into src/wire/specs/ and running `bun run gen:registry`.
+ *
+ *  This index is what the chain tests and the coverage audit enumerate. The
+ *  ADAPTERS do not read it: each family has its own loader (chat-specs,
+ *  media-specs, service-specs, retrieval-specs) so a chat call does not drag
+ *  every batch and media spec into the bundle.
+ */
+import type { SpecDelta } from './inherit';
+/** All shipped specs, keyed by `provider/api@version` id. */
+export declare const WIRE_SPECS: ReadonlyMap<string, SpecDelta>;
+/** Resolve a spec id to its flattened form, walking `extends`. */
+export declare function getWireSpec(id: string): SpecDelta;

package/dist/wire/retrieval-specs.d.ts

@@ -0,0 +1,14 @@
+/** The hosted-retrieval spec family: vector stores, file search stores, collections.
+ *
+ *  A sibling of `chat-specs.ts`, `media-specs.ts` and `service-specs.ts`, split for
+ *  the same reason: the generated `registry.ts` imports all 118 specs, so anything
+ *  reaching for it drags every family into the bundle. An application that never
+ *  builds a corpus should not carry these.
+ *
+ *  Only leaves are buildable. The base specs exist to be inherited from — they
+ *  carry auth and content-type and produce no endpoint of their own — so naming
+ *  one is a mistake to catch, not a request to send.
+ */
+import type { WireSpec } from './interpreter';
+/** Resolve a retrieval spec by id, flattening its `extends` chain. */
+export declare function retrievalSpec(id: string): WireSpec;

package/dist/wire/service-specs.d.ts

@@ -0,0 +1,18 @@
+/** The remaining runtime spec families: embeddings, realtime, batch, files, and
+ *  the media adapters that had no builder seam until now.
+ *
+ *  A sibling of `chat-specs.ts` and `media-specs.ts`, split for the same reason:
+ *  the generated `registry.ts` imports all 71 specs, so an adapter reaching for it
+ *  drags every family into the bundle whether or not anything executes them. Each
+ *  file here loads exactly what its adapters run.
+ *
+ *  Only leaves are buildable. The `*.base` specs exist to be inherited from and
+ *  produce no endpoint of their own, so naming one is a mistake to catch rather
+ *  than a request to send.
+ */
+import type { WireSpec } from './interpreter';
+/** The service spec for `id`, with its inheritance chain applied. Throws on an
+ *  unknown or abstract id rather than substituting something plausible. */
+export declare function serviceSpec(id: string): WireSpec;
+/** Buildable ids, asserted by the tests so this list cannot drift from the files. */
+export declare const SERVICE_SPEC_IDS: readonly string[];

package/dist/wire/utility-specs.d.ts

@@ -0,0 +1,10 @@
+/** The utility spec family: exact token counting, live model listing, file
+ *  content retrieval, and the provenance check.
+ *
+ *  Four small surfaces that share nothing except being requests. They are loaded
+ *  together because each is a handful of specs and no consumer reaches one without
+ *  reaching the layer that owns it.
+ */
+import type { WireSpec } from './interpreter';
+/** Resolve a utility spec by id, flattening its `extends` chain. */
+export declare function utilitySpec(id: string): WireSpec;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@combycode/llm-sdk",
-  "version": "2.2.2",
+  "version": "3.0.0",
   "description": "Unified, pluggable AI SDK for accessing the LLMs of every major provider (Anthropic, OpenAI, Google, xAI, OpenRouter) through one API. Cross-environment: Node, Bun, and the browser.",
   "type": "module",
   "main": "./dist/index.js",
@@ -43,9 +43,12 @@
     "format": "biome format --write src tests",
     "check": "biome check src tests",
     "check:fix": "biome check --write src tests",
-    "gate": "node ../../quality-gate/gate.mjs",
+    "gen:registry": "bun run scripts/gen-wire-registry.ts",
+    "gate": "bun run scripts/gate.ts",
     "gate:selftest": "node ../../quality-gate/selftest.mjs",
-    "gate:snapshot": "node ../../quality-gate/gate.mjs --only api-snapshot --update"
+    "record:responses": "bun run scripts/record-responses.ts",
+    "derive:shapes": "bun run scripts/derive-response-shapes.ts",
+    "gate:snapshot": "bun run scripts/gate.ts --only api-snapshot --update"
   },
   "devDependencies": {
     "@biomejs/biome": "^2.4.13",