@vedmalex/ai-connect 0.6.0 → 0.7.0

package/README.md

@@ -425,7 +425,9 @@ A `cli` route exposes the same management interfaces as other providers — `dis
 - **`static`** — build the catalog from the account's configured `models[]` (+ `contextWindow`). This is the default for a preset-less custom CLI that declares `models[]` (it previously reported `not_supported`); opt out with `discovery: { via: "none" }`.
 - **`none`** — no discovery.
 
-**Configured context window (GAP-A).** A model entry's `contextLength` is surfaced from the route's configured `contextWindow` only when discovery did not already report one (monotonic — a live discovered value always wins). Such entries are tagged `metadata.contextWindowSource: "configured"`. A consumer mapping `catalog.contextLength` into `resolveModelContextWindow`'s `discovered` slot should gate on `metadata.contextWindowSource !== "configured"` (otherwise feed it as the `configured` input) so the documented precedence `discovered > reference > configured > default` stays honest.
+**Configured context window (GAP-A).** A model entry's `contextLength` is surfaced from the route's configured `contextWindow` only when discovery did not already report one (monotonic — a live discovered value always wins). Provenance is exposed on the typed field `ModelInfo.contextWindowSource`: `"discovered"` (read from a live API/cli list-command record), `"configured"` (surfaced from the route's `contextWindow`), or `undefined` (unknown). A consumer mapping `catalog.contextLength` into `resolveModelContextWindow`'s `discovered` slot should do so ONLY when `contextWindowSource === "discovered"` — treat `"configured"` as the `configured` input and `undefined` as unknown (do not promote it to the `discovered` slot) — so the precedence `discovered > reference > configured > default` stays honest. (`metadata.contextWindowSource: "configured"` is retained as a back-compat alias on the configured-fill path.)
+
+**Discovery diagnostics.** A model-discovery route report (and its catalog) may carry a `warnings: string[]`. In particular, a cli `discovery.via: "command"` route whose list command fails/times out/returns nothing and falls back to its static `models[]` catalog records a warning there, so a degraded fallback is distinguishable from a healthy static catalog.
 
 Current local transport scope:
 

package/dist/browser/index.js

@@ -1980,6 +1980,8 @@ function fillConfiguredContextLength(route, models) {
     return {
       ...entry,
       contextLength: configured,
+      // FT-002: typed provenance (canonical) + metadata alias (back-compat).
+      contextWindowSource: "configured",
       metadata: { ...entry.metadata ?? {}, contextWindowSource: "configured" }
     };
   });
@@ -3309,7 +3311,8 @@ function createClient(configOrInput, options = {}) {
           ...catalog.canonicalModelId ? { canonicalModelId: catalog.canonicalModelId } : {},
           ...catalog.resolvedModelId ? { resolvedModelId: catalog.resolvedModelId } : {},
           ...catalog.currentModelId ? { currentModelId: catalog.currentModelId } : {},
-          availableModels: catalog.availableModels
+          availableModels: catalog.availableModels,
+          ...catalog.warnings?.length ? { warnings: catalog.warnings } : {}
         });
         wideAttempts.push({
           index: wideAttempts.length + 1,
@@ -5012,7 +5015,7 @@ function parseOpenAiModelCatalog(route, payload) {
         modelId: entry.id,
         name: typeof entry.display_name === "string" ? entry.display_name : typeof entry.name === "string" ? entry.name : entry.id,
         ...typeof entry.description === "string" ? { description: entry.description } : {},
-        ...contextLength !== void 0 ? { contextLength } : {},
+        ...contextLength !== void 0 ? { contextLength, contextWindowSource: "discovered" } : {},
         ...pricing ? { pricing } : {},
         ...free ? { free } : {},
         ...metadata ? {