Update app-server protocol schema fixtures

codex-rs/app-server-protocol/schema/json/DynamicToolCallParams.json

@@ -30,4 +30,4 @@
   ],
   "title": "DynamicToolCallParams",
   "type": "object"
-}
+}

codex-rs/app-server-protocol/schema/json/ServerNotification.json

@@ -4053,7 +4053,7 @@
           "type": "string"
         },
         "items": {
-          "description": "Populated on history-bearing responses such as `thread/resume` and `thread/fork`. The `turn/completed` notification also includes the terminal turn items when they are still available from the live thread listener. Other responses and notifications may still return an empty list to keep payloads small.",
+          "description": "Populated on history-bearing responses such as `thread/resume` and `thread/fork`. The `turn/completed` notification may also include a compact terminal turn snapshot when it is still available from the live thread listener. Bulky command/tool outputs may be elided there to avoid replaying large payloads on the terminal notification.",
           "items": {
             "$ref": "#/definitions/ThreadItem"
           },

codex-rs/app-server-protocol/schema/json/codex_app_server_protocol.schemas.json

@@ -14099,8 +14099,8 @@
               },
               "namespace": {
                 "type": [
-                  "null",
-                  "string"
+                  "string",
+                  "null"
                 ]
               },
               "status": {
@@ -15812,7 +15812,7 @@
             "type": "string"
           },
           "items": {
-            "description": "Populated on history-bearing responses such as `thread/resume` and `thread/fork`. The `turn/completed` notification also includes the terminal turn items when they are still available from the live thread listener. Other responses and notifications may still return an empty list to keep payloads small.",
+            "description": "Populated on history-bearing responses such as `thread/resume` and `thread/fork`. The `turn/completed` notification may also include a compact terminal turn snapshot when it is still available from the live thread listener. Bulky command/tool outputs may be elided there to avoid replaying large payloads on the terminal notification.",
             "items": {
               "$ref": "#/definitions/v2/ThreadItem"
             },
@@ -16612,4 +16612,4 @@
   },
   "title": "CodexAppServerProtocol",
   "type": "object"
-}
+}

codex-rs/app-server-protocol/schema/json/codex_app_server_protocol.v2.schemas.json

@@ -13710,7 +13710,7 @@
           "type": "string"
         },
         "items": {
-          "description": "Populated on history-bearing responses such as `thread/resume` and `thread/fork`. The `turn/completed` notification also includes the terminal turn items when they are still available from the live thread listener. Other responses and notifications may still return an empty list to keep payloads small.",
+          "description": "Populated on history-bearing responses such as `thread/resume` and `thread/fork`. The `turn/completed` notification may also include a compact terminal turn snapshot when it is still available from the live thread listener. Bulky command/tool outputs may be elided there to avoid replaying large payloads on the terminal notification.",
           "items": {
             "$ref": "#/definitions/ThreadItem"
           },

codex-rs/app-server-protocol/schema/json/v2/ReviewStartResponse.json

@@ -1323,7 +1323,7 @@
           "type": "string"
         },
         "items": {
-          "description": "Populated on history-bearing responses such as `thread/resume` and `thread/fork`. The `turn/completed` notification also includes the terminal turn items when they are still available from the live thread listener. Other responses and notifications may still return an empty list to keep payloads small.",
+          "description": "Populated on history-bearing responses such as `thread/resume` and `thread/fork`. The `turn/completed` notification may also include a compact terminal turn snapshot when it is still available from the live thread listener. Bulky command/tool outputs may be elided there to avoid replaying large payloads on the terminal notification.",
           "items": {
             "$ref": "#/definitions/ThreadItem"
           },

codex-rs/app-server-protocol/schema/json/v2/ThreadForkResponse.json

@@ -1912,7 +1912,7 @@
           "type": "string"
         },
         "items": {
-          "description": "Populated on history-bearing responses such as `thread/resume` and `thread/fork`. The `turn/completed` notification also includes the terminal turn items when they are still available from the live thread listener. Other responses and notifications may still return an empty list to keep payloads small.",
+          "description": "Populated on history-bearing responses such as `thread/resume` and `thread/fork`. The `turn/completed` notification may also include a compact terminal turn snapshot when it is still available from the live thread listener. Bulky command/tool outputs may be elided there to avoid replaying large payloads on the terminal notification.",
           "items": {
             "$ref": "#/definitions/ThreadItem"
           },

codex-rs/app-server-protocol/schema/json/v2/ThreadListResponse.json

@@ -1674,7 +1674,7 @@
           "type": "string"
         },
         "items": {
-          "description": "Populated on history-bearing responses such as `thread/resume` and `thread/fork`. The `turn/completed` notification also includes the terminal turn items when they are still available from the live thread listener. Other responses and notifications may still return an empty list to keep payloads small.",
+          "description": "Populated on history-bearing responses such as `thread/resume` and `thread/fork`. The `turn/completed` notification may also include a compact terminal turn snapshot when it is still available from the live thread listener. Bulky command/tool outputs may be elided there to avoid replaying large payloads on the terminal notification.",
           "items": {
             "$ref": "#/definitions/ThreadItem"
           },

codex-rs/app-server-protocol/schema/json/v2/ThreadMetadataUpdateResponse.json

@@ -1674,7 +1674,7 @@
           "type": "string"
         },
         "items": {
-          "description": "Populated on history-bearing responses such as `thread/resume` and `thread/fork`. The `turn/completed` notification also includes the terminal turn items when they are still available from the live thread listener. Other responses and notifications may still return an empty list to keep payloads small.",
+          "description": "Populated on history-bearing responses such as `thread/resume` and `thread/fork`. The `turn/completed` notification may also include a compact terminal turn snapshot when it is still available from the live thread listener. Bulky command/tool outputs may be elided there to avoid replaying large payloads on the terminal notification.",
           "items": {
             "$ref": "#/definitions/ThreadItem"
           },

codex-rs/app-server-protocol/schema/json/v2/ThreadReadResponse.json

@@ -1674,7 +1674,7 @@
           "type": "string"
         },
         "items": {
-          "description": "Populated on history-bearing responses such as `thread/resume` and `thread/fork`. The `turn/completed` notification also includes the terminal turn items when they are still available from the live thread listener. Other responses and notifications may still return an empty list to keep payloads small.",
+          "description": "Populated on history-bearing responses such as `thread/resume` and `thread/fork`. The `turn/completed` notification may also include a compact terminal turn snapshot when it is still available from the live thread listener. Bulky command/tool outputs may be elided there to avoid replaying large payloads on the terminal notification.",
           "items": {
             "$ref": "#/definitions/ThreadItem"
           },

codex-rs/app-server-protocol/schema/json/v2/ThreadResumeResponse.json

@@ -1912,7 +1912,7 @@
           "type": "string"
         },
         "items": {
-          "description": "Populated on history-bearing responses such as `thread/resume` and `thread/fork`. The `turn/completed` notification also includes the terminal turn items when they are still available from the live thread listener. Other responses and notifications may still return an empty list to keep payloads small.",
+          "description": "Populated on history-bearing responses such as `thread/resume` and `thread/fork`. The `turn/completed` notification may also include a compact terminal turn snapshot when it is still available from the live thread listener. Bulky command/tool outputs may be elided there to avoid replaying large payloads on the terminal notification.",
           "items": {
             "$ref": "#/definitions/ThreadItem"
           },

codex-rs/app-server-protocol/schema/json/v2/ThreadRollbackResponse.json

@@ -1674,7 +1674,7 @@
           "type": "string"
         },
         "items": {
-          "description": "Populated on history-bearing responses such as `thread/resume` and `thread/fork`. The `turn/completed` notification also includes the terminal turn items when they are still available from the live thread listener. Other responses and notifications may still return an empty list to keep payloads small.",
+          "description": "Populated on history-bearing responses such as `thread/resume` and `thread/fork`. The `turn/completed` notification may also include a compact terminal turn snapshot when it is still available from the live thread listener. Bulky command/tool outputs may be elided there to avoid replaying large payloads on the terminal notification.",
           "items": {
             "$ref": "#/definitions/ThreadItem"
           },

codex-rs/app-server-protocol/schema/json/v2/ThreadStartResponse.json

@@ -1912,7 +1912,7 @@
           "type": "string"
         },
         "items": {
-          "description": "Populated on history-bearing responses such as `thread/resume` and `thread/fork`. The `turn/completed` notification also includes the terminal turn items when they are still available from the live thread listener. Other responses and notifications may still return an empty list to keep payloads small.",
+          "description": "Populated on history-bearing responses such as `thread/resume` and `thread/fork`. The `turn/completed` notification may also include a compact terminal turn snapshot when it is still available from the live thread listener. Bulky command/tool outputs may be elided there to avoid replaying large payloads on the terminal notification.",
           "items": {
             "$ref": "#/definitions/ThreadItem"
           },

codex-rs/app-server-protocol/schema/json/v2/ThreadStartedNotification.json

@@ -1674,7 +1674,7 @@
           "type": "string"
         },
         "items": {
-          "description": "Populated on history-bearing responses such as `thread/resume` and `thread/fork`. The `turn/completed` notification also includes the terminal turn items when they are still available from the live thread listener. Other responses and notifications may still return an empty list to keep payloads small.",
+          "description": "Populated on history-bearing responses such as `thread/resume` and `thread/fork`. The `turn/completed` notification may also include a compact terminal turn snapshot when it is still available from the live thread listener. Bulky command/tool outputs may be elided there to avoid replaying large payloads on the terminal notification.",
           "items": {
             "$ref": "#/definitions/ThreadItem"
           },

codex-rs/app-server-protocol/schema/json/v2/ThreadTurnsListResponse.json

@@ -1323,7 +1323,7 @@
           "type": "string"
         },
         "items": {
-          "description": "Only populated on a `thread/resume` or `thread/fork` response. For all other responses and notifications returning a Turn, the items field will be an empty list.",
+          "description": "Populated on history-bearing responses such as `thread/resume` and `thread/fork`. The `turn/completed` notification may also include a compact terminal turn snapshot when it is still available from the live thread listener. Bulky command/tool outputs may be elided there to avoid replaying large payloads on the terminal notification.",
           "items": {
             "$ref": "#/definitions/ThreadItem"
           },

codex-rs/app-server-protocol/schema/json/v2/ThreadUnarchiveResponse.json

@@ -1674,7 +1674,7 @@
           "type": "string"
         },
         "items": {
-          "description": "Populated on history-bearing responses such as `thread/resume` and `thread/fork`. The `turn/completed` notification also includes the terminal turn items when they are still available from the live thread listener. Other responses and notifications may still return an empty list to keep payloads small.",
+          "description": "Populated on history-bearing responses such as `thread/resume` and `thread/fork`. The `turn/completed` notification may also include a compact terminal turn snapshot when it is still available from the live thread listener. Bulky command/tool outputs may be elided there to avoid replaying large payloads on the terminal notification.",
           "items": {
             "$ref": "#/definitions/ThreadItem"
           },

codex-rs/app-server-protocol/schema/json/v2/TurnCompletedNotification.json

@@ -1323,7 +1323,7 @@
           "type": "string"
         },
         "items": {
-          "description": "Populated on history-bearing responses such as `thread/resume` and `thread/fork`. The `turn/completed` notification also includes the terminal turn items when they are still available from the live thread listener. Other responses and notifications may still return an empty list to keep payloads small.",
+          "description": "Populated on history-bearing responses such as `thread/resume` and `thread/fork`. The `turn/completed` notification may also include a compact terminal turn snapshot when it is still available from the live thread listener. Bulky command/tool outputs may be elided there to avoid replaying large payloads on the terminal notification.",
           "items": {
             "$ref": "#/definitions/ThreadItem"
           },

codex-rs/app-server-protocol/schema/json/v2/TurnStartResponse.json

@@ -1323,7 +1323,7 @@
           "type": "string"
         },
         "items": {
-          "description": "Populated on history-bearing responses such as `thread/resume` and `thread/fork`. The `turn/completed` notification also includes the terminal turn items when they are still available from the live thread listener. Other responses and notifications may still return an empty list to keep payloads small.",
+          "description": "Populated on history-bearing responses such as `thread/resume` and `thread/fork`. The `turn/completed` notification may also include a compact terminal turn snapshot when it is still available from the live thread listener. Bulky command/tool outputs may be elided there to avoid replaying large payloads on the terminal notification.",
           "items": {
             "$ref": "#/definitions/ThreadItem"
           },

codex-rs/app-server-protocol/schema/json/v2/TurnStartedNotification.json

@@ -1323,7 +1323,7 @@
           "type": "string"
         },
         "items": {
-          "description": "Populated on history-bearing responses such as `thread/resume` and `thread/fork`. The `turn/completed` notification also includes the terminal turn items when they are still available from the live thread listener. Other responses and notifications may still return an empty list to keep payloads small.",
+          "description": "Populated on history-bearing responses such as `thread/resume` and `thread/fork`. The `turn/completed` notification may also include a compact terminal turn snapshot when it is still available from the live thread listener. Bulky command/tool outputs may be elided there to avoid replaying large payloads on the terminal notification.",
           "items": {
             "$ref": "#/definitions/ThreadItem"
           },

codex-rs/app-server-protocol/schema/typescript/v2/Turn.ts

@@ -8,9 +8,9 @@ import type { TurnStatus } from "./TurnStatus";
 export type Turn = { id: string,
 /**
  * Populated on history-bearing responses such as `thread/resume` and `thread/fork`.
- * The `turn/completed` notification also includes the terminal turn items when they are
- * still available from the live thread listener. Other responses and notifications may
- * still return an empty list to keep payloads small.
+ * The `turn/completed` notification may also include a compact terminal turn snapshot when
+ * it is still available from the live thread listener. Bulky command/tool outputs may be
+ * elided there to avoid replaying large payloads on the terminal notification.
  */
 items: Array<ThreadItem>, status: TurnStatus,
 /**