fix(openapi): handle ZodVoid responses as 204 No Content

[kentwilliam]

This was causing 500s.

Context

This avoids crashes for these endpoints:

• DELETE /api/account/device-connections/{connectionId}
• DELETE /api/orgs/{orgName}/postman-credentials
• DELETE /api/orgs/{orgName}/vcs-app
• DELETE /api/orgs/{orgName}/projects/{projectName}
• DELETE /api/orgs/{orgName}/pending-projects/{projectName}
• DELETE /api/orgs/{orgName}/projects/{projectName}/sdk-requests
• DELETE /api/orgs/{orgName}/projects/{projectName}/sdks/{language}
• DELETE /api/docs-sites/{docsSiteId}/domains/{domainId}
• DELETE /api/users/{userId}/tutorial-modals/{modalType}

[Copilot]

Pull request overview

Updates the Stainless OpenAPI spec generator to correctly represent endpoints whose response schema defaults to z.void() by emitting a 204 No Content response instead of attempting to serialize a ZodVoid schema (which crashes GET /api/openapi).

Changes:

• Detect ZodVoid response schemas during OpenAPI generation.
• Emit 204 No Content responses (no body) for ZodVoid endpoints; otherwise keep existing 200 application/json behavior.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[dgellow]

Seems to relate to #110 🤔
I would need to check what was the context for that change, I remember doing it when handling an incident

Edit: sorry, I meant this one #108. Though that also relates to #110, incidentally.
There is more context in that PR

[dgellow]

LGTM