fix(openapi): preserve typed default errors

[flemzord]

Summary

• keep the global Speakeasy error policy on default only
• prevent generic 4XX/5XX matchers from shadowing typed default error schemas in generated SDKs
• update the OpenAPI build invariant to reject a reintroduction of range matchers

Root cause

The 4XX and 5XX matchers introduced in v3.2.9 run before each operation's typed default error response in generated SDKs. Structured API errors are therefore converted into generic SDK errors, and explicit error statuses can disappear from generated response models.

Validation

• nix develop --impure --command bash -c 'just generate-composition-overlay && speakeasy run -s all --skip-upload-spec --auto-yes && just validate-openapi'
• OpenAPI lint: 0 errors
• generated policy: ["default"]
• normalized v3.2.9 and candidate documents are byte-identical after removing paths.x-speakeasy-errors (ac36525febc56af5e96654b57a70824625137631053f19c71481375364681b3e)
• git diff --check

Release

This is intended for Stack v3.2.10. SDKs should regenerate from the v3.2.10 Registry revision before any generated PR is merged.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 9f07ef39-4860-4ebc-bb46-b240e9cd3f25

📥 Commits

Reviewing files that changed from the base of the PR and between 5eeed11 and ea49852.

⛔ Files ignored due to path filters (1)

• releases/overlays/shared.overlay.yaml is excluded by !**/*.yaml

📒 Files selected for processing (1)

• Justfile

---

Walkthrough

The validate-openapi target now requires the generated error path to expose only the "default" response status code.

Changes

OpenAPI validation

Layer / File(s)	Summary
Validate default error response Justfile	The OpenAPI validation assertion now requires only the typed "default" error response instead of "4XX", "5XX", and "default" responses.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Suggested reviewers: gfyrag

Poem

A rabbit checks the schema bright,
Finds one default response right.
The extra codes now fade away,
Validation hops through clean today.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly states that the OpenAPI change preserves typed default errors.
Description check	✅ Passed	The description directly explains the OpenAPI error-handling change, root cause, validation, and release impact.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/openapi-typed-error-responses

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[NumaryBot]

✅ Approve — automated review

The change consistently limits the global Speakeasy error policy to default and updates the validation invariant accordingly. No regressions or actionable defects were found.

No findings.