@sema-agent/sdk 0.0.119 → 0.0.120

package/openapi.yaml

@@ -2569,13 +2569,16 @@ components:
             the user wants only files reverted. Target = a user-message SessionTreeEntry.id.
         permissionMode:
           type: string
-          enum: [default, plan, acceptEdits, bypassPermissions]
+          enum: [default, plan, acceptEdits, bypassPermissions, auto]
           description: >
-            CC permission-mode INTENT. The frontend (TUI shell / web portal) carries the RAW mode; the SERVICE
-            INTERPRETS it (axis-aware, tighten-only): `plan` ⇒ mount present_plan (core enablePlanMode) + read-only
-            hands (handsReadOnly) = CC EnterPlanMode read-only research; `acceptEdits`/`bypassPermissions` are
-            loosening, not honorable remotely (coerced to default engine-side, enforced client-side). Carrying the
-            intent (not pre-interpreted core fields) = one interpretation across frontends + service-owned governance.
+            CC permission-mode INTENT (the five CC modes verbatim, post-[816]/[820]/[822]). The frontend (TUI shell /
+            web portal) carries the RAW mode; the SERVICE interprets it TIGHTEN-ONLY vs the deployment baseline:
+            `plan` ⇒ mount present_plan (core enablePlanMode) + read-only hands (CC EnterPlanMode research);
+            `default` adds the manual ask gate; `auto` = same ask gate with core's auto-mode classifier screening
+            asks upstream (entitlement-gated in core); `acceptEdits`/`bypassPermissions` are honored as
+            "add less/no mode-derived gating" — they can never subtract from the deployment/operator policy
+            (deny-wins). An unknown string coerces to `default` (the most-asking mode). Carrying the intent
+            (not pre-interpreted core fields) = one interpretation across frontends + service-owned governance.
         attachmentIds:
           type: array
           maxItems: 16
@@ -3186,7 +3189,7 @@ components:
         sessionDelete: { type: boolean, description: "Session delete verb." }
         sessionInit: { type: boolean, description: "Session pre-initialization verb." }
         sessionPolicy: { type: boolean, description: "E6 per-session operator-tightened tool rules are durable." }
-        usage: { type: boolean, description: "Usage analytics face." }
+        usage: { type: boolean, description: "QUOTA face wired (server costQuota dep — cost/token budget enforcement + per-principal accounting). NOT an analytics-availability probe ([1871] B15): per-turn analytics (turn_end.usage, model_usage frames) are engine-side and unconditional, and GET /v1/usage always answers 200 (with `enabled: false` when the quota face is off). Gate quota UI on this key; never gate analytics on it." }
         policy: { type: boolean, description: "`GET /v1/policy` (autonomy/permission READ side)." }
         permissionModeWrite: { type: boolean, description: "Runtime permission-mode WRITE. Advertised false by design — autonomy is CONFIG, not steer; the READ side is `policy`." }
         modelSelection: { type: boolean, description: "`model` accepted per request." }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sema-agent/sdk",
-  "version": "0.0.119",
+  "version": "0.0.120",
   "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",