defect in YAML: the same member field "id" declared twice in inheritance between ComputerToolCallOutput and ComputerToolCallOutputResource

    ComputerToolCallOutput:
      type: object
      title: Computer tool call output
      description: |
        The output of a computer tool call.
      properties:
        type:
          type: string
          description: >
            The type of the computer tool call output. Always
            `computer_call_output`.
          enum:
            - computer_call_output
          default: computer_call_output
          x-stainless-const: true
        id:
          type: string
          description: |
            The ID of the computer tool call output.

......

    ComputerToolCallOutputResource:
      allOf:
        - $ref: "#/components/schemas/ComputerToolCallOutput"
        - type: object
          properties:
            id:
              type: string
              description: |
                The unique ID of the computer call tool output.
          required:
            - id

The only difference is, in derived class ComputerToolCallOutputResource, "id" becomes required.

A decent IDE or compiler will warn about such defect in OO inheritance, though the defect may be intentional.

Start by inspecting the ComputerToolCallOutput and ComputerToolCallOutputResource schema definitions in the YAML shown in the issue, focusing on their allOf relationship and repeated id member. Determine whether the repeated declaration is intentional, then resolve the schema inconsistency and validate that the OpenAPI specification no longer reports the duplicate inheritance field.