@axiom-lattice/protocols 4.5.0 → 4.6.0

package/.turbo/turbo-build.log

@@ -1,5 +1,5 @@
 
-> @axiom-lattice/protocols@4.5.0 build /home/runner/work/agentic/agentic/packages/protocols
+> @axiom-lattice/protocols@4.6.0 build /home/runner/work/agentic/agentic/packages/protocols
 > tsup src/index.ts --format cjs,esm --dts --sourcemap
 
 CLI Building entry: src/index.ts
@@ -8,13 +8,13 @@
 CLI Target: es2020
 CJS Build start
 ESM Build start
-CJS dist/index.js     45.77 KB
-CJS dist/index.js.map 166.43 KB
-CJS ⚡️ Build success in 496ms
-ESM dist/index.mjs     41.17 KB
-ESM dist/index.mjs.map 162.75 KB
-ESM ⚡️ Build success in 519ms
+CJS dist/index.js     46.24 KB
+CJS dist/index.js.map 187.63 KB
+CJS ⚡️ Build success in 270ms
+ESM dist/index.mjs     41.58 KB
+ESM dist/index.mjs.map 183.90 KB
+ESM ⚡️ Build success in 270ms
 DTS Build start
-DTS ⚡️ Build success in 12748ms
-DTS dist/index.d.ts  221.93 KB
-DTS dist/index.d.mts 221.93 KB
+DTS ⚡️ Build success in 7655ms
+DTS dist/index.d.ts  243.17 KB
+DTS dist/index.d.mts 243.17 KB

package/CHANGELOG.md

@@ -1,5 +1,58 @@
 # @axiom-lattice/protocols
 
+## 4.6.0
+
+### Minor Changes
+
+- 6e07f01: Add a tenant-scoped model provider catalog.
+
+  Model lists were a process-wide in-memory registry: every model lived under
+  `models:default:{key}`, nothing was persisted, and `GET /api/models` returned
+  each model's `apiKey` in plaintext to any caller.
+
+  A tenant owner/admin can now register an upstream provider (base URL + API key),
+  run discovery against `{baseURL}/v1/models`, and see a tenant-isolated model
+  catalog. See ADR-138 for the full decision record.
+
+  Key points:
+
+  - **`modelKey` is `${providerId}/${modelId}`.** The same upstream model id
+    offered by two providers is two independent models — the real case being a
+    tenant running OpenAI direct and Azure OpenAI side by side. The provider id is
+    immutable, so renaming a provider never invalidates a key already stored in
+    agent or eval configuration.
+  - **Credentials never leave the server.** The API key is stored AES-256-GCM
+    encrypted and responses carry only `hasApiKey` / `apiKeyHint`. An omitted or
+    empty `apiKey` on update keeps the stored value.
+  - **Tenant scope comes from the authenticated session only**, never from the
+    request body, and writes require a tenant owner/admin role. A provider
+    belonging to another tenant is indistinguishable from a missing one (404).
+  - **Upstream URLs are validated** before any outbound request: http(s) only, no
+    embedded credentials, and private/loopback/link-local/CGNAT addresses are
+    rejected. Discovery does not follow redirects, times out after 8s, and never
+    echoes the upstream body in an error.
+  - **Discovery is explicit.** `POST /api/model-providers/:id/discover` refreshes a
+    persisted snapshot; the catalog endpoints never make outbound calls, so an
+    upstream outage leaves the list intact.
+
+  Phase 1 registers discovered models for execution only for the `default` tenant,
+  whose registry keys are byte-identical to the previous key-only API. Other
+  tenants get the catalog but their models report `executable: false`. Registering
+  them would let one tenant's model silently overwrite another's, sending the
+  second tenant's agents to the first tenant's upstream with the first tenant's
+  credentials.
+
+  **Contract changes on the legacy endpoints** (breaking for any consumer of
+  `GET /api/models`):
+
+  - `GET /api/models` no longer returns `apiKey`; it returns `hasApiKey` instead,
+    and is now scoped to the `default` tenant rather than enumerating all of them.
+  - `PUT /api/models` treats an empty `apiKey` as "keep the existing key". Without
+    this, the first save after the change above would clear every stored key.
+
+  The console UI ships the matching change, so a react-sdk built from this version
+  must be deployed together with this gateway.
+
 ## 4.5.0
 
 ### Minor Changes