Non-existent properties are defined as required

Hey there,

As of today there are a few places in the schema components that specify property names as required but those properties are not actually specified in their corresponding sets of properties.

• For example: LocalShellToolCallOutput -> call_id here is not specified in properties:

LocalShellToolCallOutput:
  type: object
  title: Local shell call output
  description: |
    The output of a local shell tool call.
  properties:
    type:
      type: string
      ...
    id:
      type: string
      ...
    output:
      type: string
      ...
    status:
      anyOf:
        - type: string
          ...
        - type: 'null'
  required:
    - id
    - type
    - call_id
    - output

• Another example: MCPApprovalResponse -> request_id (marked as required) is not one of the available properties.

MCPApprovalResponse:
  type: object
  title: MCP approval response
  description: |
    A response to an MCP approval request.
  properties:
    type:
      type: string
      ...
    id:
      anyOf:
        - type: string
          ...
        - type: 'null'
    approval_request_id:
      type: string
      ...
    approve:
      type: boolean
      ...
    reason:
      anyOf:
        - type: string
         ...
        - type: 'null'
  required:
    - type
    - request_id
    - approve
    - approval_request_id

Further examples:

• MCPApprovalResponseResource -> request_id
• ResponseAudioDoneEvent -> response_id
• ResponseAudioTranscriptDeltaEvent -> response_id
• ResponseAudioTranscriptDoneEvent -> response_id
• UsageCodeInterpreterSessionsResult -> sessions

Start with the OpenAPI schema components named in the issue, including LocalShellToolCallOutput and MCPApprovalResponse, and compare each required list with its properties map. Check all listed examples and confirm that every required name has a corresponding property; the schema should validate without these mismatches.