@github/copilot-sdk-darwin-arm64 1.0.16 → 1.0.17-preview.1

package/schemas/session-events.schema.json

@@ -3070,6 +3070,10 @@
           "type": "string",
           "description": "Server-provided reason for falling back, when available"
         },
+        "selectionReason": {
+          "type": "string",
+          "description": "Short human-readable sentence from the routing service explaining why this model was chosen, for display alongside the model. Present only when the service supplied one: it is omitted for on-device selections, when the service did not provide an explanation, and when a replayed decision made no routing call. The text is display-only and drawn from a fixed catalogue; several distinct routing categories share identical wording, so it cannot be used to recover the category or keyed on programmatically."
+        },
         "stickyOverride": {
           "type": "boolean",
           "description": "Whether a sticky model choice overrode the router result"
@@ -9775,7 +9779,7 @@
         "managedKeys"
       ],
       "additionalProperties": false,
-      "description": "Enterprise managed-settings resolution: the effective managed settings the session applied and which channels contributed, so SDK clients can show users what is enterprise-managed. Fires whenever managed policy is (re)applied — at session start, on resume, and on account switch. This is an ephemeral live snapshot (delivered to subscribers but not persisted to the session event log), because at session start it resolves before `session.start` is emitted. Device values take precedence over server values, then the policy helper, per ordinary key, while permissions compose restrictively across device, server, policy-helper, and SDK-client layers. The account-scoped `getManagedSettings()` API does not include session-local client injection. Marked experimental while the managed-settings surface stabilizes.",
+      "description": "Effective enterprise managed settings and contributing channels. Session events report applied policy; sessionless resolve reports an account/device snapshot, and compose reports a non-applying preview of candidate documents. Device values take precedence over server values, then the policy helper, per ordinary key, while permissions compose restrictively. Session-local SDK-client policy is included only in session results. Marked experimental while the managed-settings surface stabilizes.",
       "title": "ManagedSettingsResolvedData",
       "stability": "experimental"
     },
@@ -9820,7 +9824,7 @@
         },
         "data": {
           "$ref": "#/definitions/ManagedSettingsResolvedData",
-          "description": "Enterprise managed-settings resolution: the effective managed settings the session applied and which channels contributed, so SDK clients can show users what is enterprise-managed. Fires whenever managed policy is (re)applied — at session start, on resume, and on account switch. This is an ephemeral live snapshot (delivered to subscribers but not persisted to the session event log), because at session start it resolves before `session.start` is emitted. Device values take precedence over server values, then the policy helper, per ordinary key, while permissions compose restrictively across device, server, policy-helper, and SDK-client layers. The account-scoped `getManagedSettings()` API does not include session-local client injection. Marked experimental while the managed-settings surface stabilizes."
+          "description": "Effective enterprise managed settings applied to the session and their contributing channels. Emitted whenever managed policy is applied or reapplied, including session start, resume, and account switch. This ephemeral live snapshot is delivered to subscribers but not persisted to the session event log; initial resolution occurs before session.start."
         }
       },
       "required": [
@@ -9832,7 +9836,7 @@
         "data"
       ],
       "additionalProperties": false,
-      "description": "Session event \"session.managed_settings_resolved\". Enterprise managed-settings resolution: the effective managed settings the session applied and which channels contributed, so SDK clients can show users what is enterprise-managed. Fires whenever managed policy is (re)applied — at session start, on resume, and on account switch. This is an ephemeral live snapshot (delivered to subscribers but not persisted to the session event log), because at session start it resolves before `session.start` is emitted. Device values take precedence over server values, then the policy helper, per ordinary key, while permissions compose restrictively across device, server, policy-helper, and SDK-client layers. The account-scoped `getManagedSettings()` API does not include session-local client injection. Marked experimental while the managed-settings surface stabilizes.",
+      "description": "Session event \"session.managed_settings_resolved\". Effective enterprise managed settings applied to the session and their contributing channels. Emitted whenever managed policy is applied or reapplied, including session start, resume, and account switch. This ephemeral live snapshot is delivered to subscribers but not persisted to the session event log; initial resolution occurs before session.start.",
       "title": "ManagedSettingsResolvedEvent",
       "stability": "experimental"
     },
@@ -10966,7 +10970,7 @@
         },
         "configSource": {
           "type": "string",
-          "description": "Runtime configuration provenance for a failed connection, or unknown when unavailable. Additional string values may be introduced."
+          "description": "Runtime configuration provenance for a connected or failed server, or unknown when unavailable. Additional string values may be introduced."
         }
       },
       "required": [
@@ -15725,6 +15729,15 @@
           "description": "Raw names of tools redefined since the prior call, restricted because a tool name can be user-authored",
           "visibility": "internal"
         },
+        "toolsRedefinedParts": {
+          "type": "array",
+          "items": {
+            "type": "string"
+          },
+          "default": [],
+          "description": "Changed definition parts of redefined tools, as `tool:part` entries; property-level parts only for telemetry-safe tools, whose other names are hashed",
+          "visibility": "internal"
+        },
         "toolsReordered": {
           "type": "boolean",
           "default": false,
@@ -18092,7 +18105,7 @@
         },
         {
           "$ref": "#/definitions/ManagedSettingsResolvedEvent",
-          "description": "Session event \"session.managed_settings_resolved\". Enterprise managed-settings resolution: the effective managed settings the session applied and which channels contributed, so SDK clients can show users what is enterprise-managed. Fires whenever managed policy is (re)applied — at session start, on resume, and on account switch. This is an ephemeral live snapshot (delivered to subscribers but not persisted to the session event log), because at session start it resolves before `session.start` is emitted. Device values take precedence over server values, then the policy helper, per ordinary key, while permissions compose restrictively across device, server, policy-helper, and SDK-client layers. The account-scoped `getManagedSettings()` API does not include session-local client injection. Marked experimental while the managed-settings surface stabilizes."
+          "description": "Session event \"session.managed_settings_resolved\". Effective enterprise managed settings applied to the session and their contributing channels. Emitted whenever managed policy is applied or reapplied, including session start, resume, and account switch. This ephemeral live snapshot is delivered to subscribers but not persisted to the session event log; initial resolution occurs before session.start."
         },
         {
           "$ref": "#/definitions/ManagedSettingsEnforcedEvent",
@@ -22097,6 +22110,11 @@
         "progressMessage": {
           "type": "string",
           "description": "Human-readable progress status message (e.g., from an MCP server)"
+        },
+        "structuredContent": {
+          "description": "Client-only structured progress metadata. Not model-facing tool output.",
+          "x-opaque-json": true,
+          "stability": "experimental"
         }
       },
       "required": [