@sema-agent/sdk 11.2.1 → 12.0.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sema-agent/sdk",
-  "version": "11.2.1",
+  "version": "12.0.0",
   "description": "Typed, zero-runtime-dependency SDK for the Sema agent fleet usage plane. The shared substrate for all doors (CC/Codex MCP façade + web). Server-side only — tokens never enter the browser.",
   "type": "module",
   "license": "BUSL-1.1",
@@ -52,6 +52,6 @@
     "prepublishOnly": "rm -f tsconfig.tsbuildinfo && npm run build && npm run typecheck --workspaces=false --prefix ../.. && npm test --workspaces=false --prefix ../.."
   },
   "devDependencies": {
-    "@sema-agent/registry-core": "^0.17.1"
+    "@sema-agent/settings-schema": "^5.0.0"
   }
 }

package/registry-openapi.yaml

@@ -4,7 +4,8 @@ info:
   version: "0.1.0"
   description: >
     ⚠️ AUTHORITY POSTURE (read first): the registry SERVER lives in the sema-registry repo (web AI);
-    the machine contract single-source is `@sema-agent/registry-core` (zod schemas + path constants —
+    the machine contract single-source is `@sema-agent/settings-schema` (renamed from
+    `@sema-agent/registry-core` at 1.0.0, 2026-08-26; zod schemas + path constants —
     AUTH_V1_PATHS/SCOPES_V1_PATHS etc.; the SDK keeps value-copies with same-source anchor tests).
     THIS file documents the surface the SDK's registry subpath actually calls, so a consumer generating
     a client from spec sees the full face — it mirrors, it does not rule. Backfilled 2026-07-28 from
@@ -12,7 +13,7 @@ info:
     `registry-spec-path-gate.test.ts` (reflective: every /api path the SDK hits must be here, zero baseline).
     USER-PLANE paths carry real request/response shapes; the ADMIN family (RegistryAdmin, user-JWT
     role-gated — "admin" is a registry-side ROLE, not a separate credential) is documented loose
-    (operator tooling; shapes live in registry-core/zod and the registry server).
+    (operator tooling; shapes live in settings-schema/zod and the registry server).
   x-sdk-subpath: "@sema-agent/sdk/registry"
 paths:
   /api/healthz:
@@ -27,7 +28,7 @@ paths:
     post:
       operationId: registryDeviceCode
       summary: Start the device-authorization flow (requestDeviceCode).
-      requestBody: { required: false, content: { application/json: { schema: { type: object, additionalProperties: true, description: 'registry-core DeviceCodeRequest (open: client metadata).' } } } }
+      requestBody: { required: false, content: { application/json: { schema: { type: object, additionalProperties: true, description: 'settings-schema DeviceCodeRequest (open: client metadata).' } } } }
       responses:
         '200':
           description: '{device_code, user_code, verification_uri(_complete)?, interval, expires_in}.'
@@ -36,7 +37,7 @@ paths:
     post:
       operationId: registryDeviceToken
       summary: Poll the device flow (pollUntilApproved's leg).
-      requestBody: { required: true, content: { application/json: { schema: { type: object, required: [grant_type, device_code], properties: { grant_type: { type: string, description: 'The RFC 8628 device grant type constant (registry-core DEVICE_GRANT_TYPE).' }, device_code: { type: string } } } } } }
+      requestBody: { required: true, content: { application/json: { schema: { type: object, required: [grant_type, device_code], properties: { grant_type: { type: string, description: 'The RFC 8628 device grant type constant (settings-schema DEVICE_GRANT_TYPE).' }, device_code: { type: string } } } } } }
       description: >
         OAuth device-token semantics: `authorization_pending` keeps the interval, `slow_down` adds +5s,
         `access_denied`/`expired_token` are terminal (typed errors in the SDK). Success = the token pair.
@@ -85,7 +86,7 @@ paths:
       operationId: registryScopesList
       summary: List the caller's scopes (listScopes; `?counts=` optional).
       responses:
-        '200': { description: 'ScopesListResponse (registry-core schema).', content: { application/json: { schema: { type: object, additionalProperties: true } } } }
+        '200': { description: 'ScopesListResponse (settings-schema schema).', content: { application/json: { schema: { type: object, additionalProperties: true } } } }
     post:
       operationId: registryScopesCreate
       summary: 'ADMIN: create a scope/space.'