@spunto/build 0.4.0 → 0.4.1

package/README.md

@@ -163,10 +163,11 @@ installed on its behalf. Import `./spec` without zod and resolution fails loudly
 right trade for not taxing every other entry point.
 
 Concretely: **no platform I/O**. No database, no Docker socket, no WebSocket. This package produces
-strings and parses strings; its only network call is outbound HTTP to a public extension registry,
-with no platform credential attached. Configuration arrives as function parameters — never read from
-the environment — so that one control plane can scope a setting per organization and another per
-process without either shape leaking in here.
+strings and parses strings. Its only network calls are outbound HTTP on the caller's behalf — a
+public extension registry, and a model vendor's catalogue endpoint when you hand
+`resolveContextWindow` a credential — and it holds no credential of its own. Configuration arrives
+as function parameters, never read from the environment, so that one control plane can scope a
+setting per organization and another per process without either shape leaking in here.
 
 That rule is what makes the package testable, safe to import from a node agent as well as from an
 API, and the reason it can't simply be folded into the design system: a script generator needs

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@spunto/build",
-  "version": "0.4.0",
+  "version": "0.4.1",
   "description": "Spunto's shared Build engine \u2014 the devcontainer image protocol and VS Code extension registry clients, with no database, no HTTP framework and no UI.",
   "type": "module",
   "license": "MIT",

package/src/agent-stream/index.ts

@@ -39,4 +39,16 @@ export type {
   UsageInput,
 } from "./agent-stream"
 
-export { contextWindowOf } from "./model-window"
+// Model context windows. `liveContextWindow`/`resolveContextWindow` take a credential as a
+// *parameter* and ask the model vendor's own API — the package still reads no environment and
+// holds no key of its own, but it is the one place here that talks to something other than a
+// public registry, and it does so on the caller's behalf. `resetModelWindowCache` exists for
+// tests: the lookup memoises per process.
+export {
+  apiModelId,
+  contextWindowOf,
+  liveContextWindow,
+  resetModelWindowCache,
+  resolveContextWindow,
+} from "./model-window"
+export type { ModelCredential } from "./model-window"