@sema-agent/sdk 9.1.0 → 9.2.0

package/openapi.yaml

@@ -2652,16 +2652,20 @@ paths:
             `POST /v1/assistant/tasks/{taskId}/resume`. Retrying the same body never succeeds.
             SEVENTH group (server >= 7.69.0 / S-185, the PARKED WORKFLOW-CHILD lane): `decide.workflow_host_unknown`
             and `decide.workflow_host_not_parked`. The pending belongs to a workflow child that parked on an
-            approval gate, and the deployment could not hand the decision to that workflow's HOST session (the
-            engine's only deployment-facing channel for a parked workflow ordinal is a resume of the host, which
-            then re-invokes `Workflow({resumeFromRunId})`). Both bodies carry `runId` (the WORKFLOW run) and NO
-            `taskId`. NOTHING was consumed: the child's checkpoint stays PENDING and the card is still listable
-            and re-decidable. `_host_not_parked` = the host is not currently parked awaiting this run (it may
-            have been interrupted, taking an already-delivered decision with it — the decision is not persisted
-            anywhere) → retry once it parks again, or resume that `runId` yourself. `_host_unknown` = the run
-            carries no originating session at all (a directly started `runWorkflow`, not a Workflow tool call) →
-            NO retry value, a person resumes that `runId`. SDK → DecideWorkflowHostError (`.errorCode` splits the
-            two recovery verbs, `.runId` is the handle).
+            approval gate, and the deployment could not hand the decision to that workflow's HOST session. Both
+            bodies carry `runId` (the WORKFLOW run) and NO `taskId`. NOTHING was consumed: the child's checkpoint
+            stays PENDING and the card is still listable and re-decidable. SDK → DecideWorkflowHostError (`.runId`
+            is the handle). `_host_unknown` = the run carries no originating session at all (a directly started
+            `runWorkflow`, not a Workflow tool call) → NO retry value, a person resumes that `runId`.
+            `_host_not_parked` = the host is not currently parked awaiting this run. ⚰️ RETIRED at server 7.72.0,
+            no alias, but this SDK still maps it: `SUPPORTED_SERVER_FLOOR` is 3.0.0 and this code was introduced
+            at 7.69.0, so a still-supported server in the [7.69.0, 7.72.0) window can genuinely send it, and for
+            that window the old contract holds — retry once it parks again, or resume that `runId` yourself. A
+            server >= 7.72.0 will never send this code again: that version replaced the dead end with a SECOND
+            leg that instead mints a fresh run on the same host session, so against a current server the SAME
+            decide either resumes the parked host or starts that new run (both land on the byte-identical
+            acceptance shape) — a host session already busy with another run instead answers the ordinary 409
+            `conflict.session_active_run`.
             SIXTH group (A-075.10, TIME-BASED retry-later pair): `resume.usage_window_exhausted` (#449 G1,
             core 5.60.1 — the deployment governance window on this run's ledger key is full; NOTHING was
             consumed or unpinned, the SAME token with the SAME decision redeems once the window slides) and
@@ -8812,9 +8816,16 @@ components:
         lane's 200 DO mean the engine committed the decision — one sentence ("approved and in effect") cannot be
         used for both lanes.
         (2) delivery can still be LOST: if the host run is interrupted before it re-invokes `Workflow`, the
-        decision goes with that invocation (it is not persisted anywhere) and a retry answers 409
-        `decide.workflow_host_not_parked`. Because the card was pending throughout, nothing is forged and the
-        approval can be re-decided once the host parks again.
+        decision goes with that invocation (it is not persisted anywhere); because the card was pending
+        throughout, nothing is forged. Against a server >= 7.72.0 a retry of the SAME decide succeeds — that
+        version gave this lane a second leg that mints a fresh run on the same host session when the host is not
+        currently parked, so the retry either resumes the parked host or starts that new run (byte-identical
+        acceptance shape either way; a host session already busy with another run instead answers the existing
+        `conflict.session_active_run` 409). Against a still-supported server in the [7.69.0, 7.72.0) window
+        (`SUPPORTED_SERVER_FLOOR` is 3.0.0) the retry instead answers 409 `decide.workflow_host_not_parked` —
+        retry once the host parks again, or resume that `runId` yourself. ⚰️ That code is RETIRED at 7.72.0, no
+        alias, and a current server will not send it again — but it remains a live, supported response from an
+        older server in that window, so the SDK still maps it (see `DecideWorkflowHostError`).
         The durable approval-queue projection is UNCHANGED — no key marks the workflow origin on any read face.
       required: []
       additionalProperties: false
@@ -9155,6 +9166,21 @@ components:
             one-off question. The value comes WHOLE from core (`summarizeCheckpoint` echoes it only when the
             cause is a member of the engine's set), so the server neither recomputes nor re-screens it. See
             ClassifierUnavailable for the open-`cause` rule and the three shapes absence covers.
+            RETIRED: server >= 7.72.0 (core 7.14.0 #688) never mints this key on any of the three faces; its
+            successor is `disposition.cause` on the gate record (`unavailable` / `parse_error` — a different
+            question, so an old switch does not port). Kept for servers in [7.69.0, 7.72.0) only (sdk 9.2.0).
+        ruleStoreUnreadable:
+          type: string
+          enum: [store, call]
+          description: >-
+            server >= 7.72.0 (core 7.14.0 #688 C3), ADDITIVE — WHICH HALF of the rule lane could not be read.
+            Present iff `origin === "rule_store_unavailable"`: `store` = the wired rule store could not be read
+            (look at the store / network); `call` = the store was read but THIS command could not be read against
+            the person's deny/ask rows (look at the command spelling). One `origin` word covers both facts, and
+            their recovery verbs live in different places (ops vs prompt). Carried on the live `tool_approval`
+            frame and the inbox row; the `card_json` card deliberately does NOT carry it (it travels with `origin`,
+            which is not on the card). Absence = `origin` is not that word — NOT an assertion that the rule store
+            is healthy.
 
     InboxList:
       type: object
@@ -10227,6 +10253,18 @@ components:
           properties:
             kind: { const: denied }
             deniedBy: { $ref: '#/components/schemas/DeniedBy' }
+            cause:
+              type: string
+              description: >-
+                server >= 7.72.0 (core 7.14.0 #688 C-a) — the SHAPE of this deny when the auto-mode classifier was
+                the refusing layer: `unavailable` (that classifier round could not run: threw / refused / over cap)
+                or `parse_error` (it ran but answered outside the verdict contract, so the call was stopped to be
+                safe). Successor seat of the retired `classifierUnavailable` key (minted once by the engine, carried
+                on both `tool_end.gate` and `permissionDenied.gate`) — but NOT the same question as the old `cause`
+                (`error` / `timeout` answered WHY it was unavailable), so an old switch does not port. The
+                vocabulary's owner is the engine (`CLASSIFIER_DENY_CAUSES`); the server passes it through verbatim
+                — branch the two known words and keep a default arm. Absent = this deny was not a classifier-fault
+                shape (policy / person / rule refused); never read absence as "classifier healthy".
 
     GateOutcome:
       type: object
@@ -10265,7 +10303,7 @@ components:
             #   服务对缺陷记录是整条不上帧 ⇒ 词表外的值在这条 wire 上到不了消费端。审批帧那一面不判成员,
             #   所以 `AskOrigin` 本体保持真开(见该 schema 的长注)。这张 enum 是本 spec 里该词表的**唯一**
             #   执法点;core 加词时改这一处。
-            - enum: [content_question, unresolvable, org_unavailable, org_rule, rule_store_unavailable, hook, ask_rule, denial_limit_fallback, shell_gate_tighten, safety_tighten, policy]
+            - enum: [content_question, ancestor_marked, org_unavailable, org_rule, rule_store_unavailable, hook, ask_rule, denial_limit_fallback, shell_gate_tighten, safety_tighten, policy]
           description: >
             WHO ASKED. Same-present/same-absent as `settlement` (I1). CLOSED here (and only here) — see the
             enum note above.
@@ -10833,16 +10871,19 @@ components:
     Event_tool_roster_delta:
       type: object
       description: >
-        LIVE stream only (server >= 7.70.0, core 7.8.0) — a RUN-TIME roster change.
+        A RUN-TIME roster change (server >= 7.70.0, core 7.8.0; live-only until 7.71.0, see below).
         `wiring_manifest.tools` is the snapshot taken when this leg started; this frame is the increment after
         it: one refresh that actually changed the roster emits EXACTLY one frame (ordered after the manifest and
         before that refresh's own `tool_end`).
         🔴 A `delta.fromDigest` that does not match what the consumer holds is NOT a rejection: `delta.roster`
         is the new state regardless — record a skew and re-sync from the whole roster (only `delta.summary`
         becomes unusable). 🔴 Half a roster never reaches the wire: the service drops the WHOLE frame when
-        core's own typebox check rejects the payload. 🔴 Neither durable leg appends it, so it never replays on
-        GET /v1/runs/{id}/events — after a reconnect re-sync from the `wiring_manifest.tools` snapshot instead
-        of waiting for a replacement delta.
+        core's own typebox check rejects the payload. 🔴 Durable legs (server >= 7.71.0, S-212): BOTH durable legs
+        append it too (the three legs share one mint point), so the raw replay `GET /v1/runs/{id}/events`
+        (`runs.events()`, `AgentEvent`) DOES carry it after a reconnect. What still never carries it is the
+        projected trace stream `GET /v1/tasks/{id}/stream` (`trace.stream()`, `TraceStreamEvent`, `mapTraceEvent`
+        drops it with `wiring_manifest` / `human_input`) — consumers on THAT leg keep re-syncing from the
+        `wiring_manifest.tools` snapshot. (Before 7.71.0 the frame was live-only.)
       allOf: [{ $ref: '#/components/schemas/EventIdentity' }]
       additionalProperties: false   # 封闭 + identity 本地镜像:见 Event_reasoning 处的长注
       required: [type, delta]
@@ -11701,6 +11742,21 @@ components:
             server >= 7.69.0 (core 7.10.0 #616), ADDITIVE, present only when the classifier was consulted and
             could not run — WHY this ask reached a human. See ClassifierUnavailable for the open-`cause` rule and
             the three shapes absence covers.
+            RETIRED: server >= 7.72.0 (core 7.14.0 #688) never mints this key on any of the three faces; its
+            successor is `disposition.cause` on the gate record (`unavailable` / `parse_error` — a different
+            question, so an old switch does not port). Kept for servers in [7.69.0, 7.72.0) only (sdk 9.2.0).
+        ruleStoreUnreadable:
+          type: string
+          enum: [store, call]
+          description: >-
+            server >= 7.72.0 (core 7.14.0 #688 C3), ADDITIVE — WHICH HALF of the rule lane could not be read.
+            Present iff `origin === "rule_store_unavailable"`: `store` = the wired rule store could not be read
+            (look at the store / network); `call` = the store was read but THIS command could not be read against
+            the person's deny/ask rows (look at the command spelling). One `origin` word covers both facts, and
+            their recovery verbs live in different places (ops vs prompt). Carried on the live `tool_approval`
+            frame and the inbox row; the `card_json` card deliberately does NOT carry it (it travels with `origin`,
+            which is not on the card). Absence = `origin` is not that word — NOT an assertion that the rule store
+            is healthy.
     ApprovalRequestFrame:
       type: object
       description: >
@@ -11839,6 +11895,9 @@ components:
             server >= 7.69.0 (core 7.10.0 #616), ADDITIVE — WHY this ask reached a human. Frame and card carry
             the SAME value (one narrow-read function server-side). See ClassifierUnavailable for the open-`cause`
             rule and the three shapes absence covers.
+            RETIRED: server >= 7.72.0 (core 7.14.0 #688) never mints this key on any of the three faces; its
+            successor is `disposition.cause` on the gate record (`unavailable` / `parse_error` — a different
+            question, so an old switch does not port). Kept for servers in [7.69.0, 7.72.0) only (sdk 9.2.0).
 
     RuleSuggestion:
       type: object

package/package.json

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