feat(generated): OrganizationMembership (batch 4a353f07)

[workos-sdk-automation]

Summary

Regenerated SDK from spec changes.

Triggered by workos/openapi-spec@053f61e

[greptile-apps]

Greptile Summary

This PR regenerates SDK models from the latest spec. The main changes are:

• Adds roles to organization membership models and fixtures.
• Updates generated package re-exports for common and organization-domain models.
• Moves organization-domain round-trip coverage to the shared OrganizationDomain alias.

Confidence Score: 3/5

The generated membership deserializer can reject successful responses that still use the legacy singular role shape.

• Current roles-array fixtures and updated generated imports execute successfully.
• The remaining concern is backward compatibility for existing organization membership payloads or mocks that still provide role instead of roles, which can surface as an SDK exception during model construction.

src/workos/organization_membership/models/organization_membership.py

T-Rex Logs

What T-Rex did

• Ran trex_org_membership_contract.py against the base version to validate the organization membership roles contract; the run failed with KeyError: 'roles'.
• Ran trex_org_membership_contract.py against the head version after the PR; the run completed with EXIT_CODE: 0 and status=200 OK for organization_membership.json and user_organization_membership.json, including the first list fixture item and the updated imports for common.OrganizationDomain and organization_domains.models.OrganizationDomain.

_{Ran code and verified through T-Rex}

Prompt To Fix All With AI

Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 1
src/workos/organization_membership/models/organization_membership.py:65-68
**Legacy Role Payloads Fail**

When an existing membership response or mock payload still has only `role`, this required `data["roles"]` lookup raises during `from_dict`. The membership resource methods deserialize successful API responses through this path, so callers can receive an unexpected SDK error instead of an `OrganizationMembership` model.

_{Reviews (1): Last reviewed commit: "chore(generated): add release notes frag..." | Re-trigger Greptile}

[greptile-apps]

Legacy Role Payloads Fail

When an existing membership response or mock payload still has only role, this required data["roles"] lookup raises during from_dict. The membership resource methods deserialize successful API responses through this path, so callers can receive an unexpected SDK error instead of an OrganizationMembership model.

Prompt To Fix With AI

This is a comment left during a code review.
Path: src/workos/organization_membership/models/organization_membership.py
Line: 65-68

Comment:
**Legacy Role Payloads Fail**

When an existing membership response or mock payload still has only `role`, this required `data["roles"]` lookup raises during `from_dict`. The membership resource methods deserialize successful API responses through this path, so callers can receive an unexpected SDK error instead of an `OrganizationMembership` model.

How can I resolve this? If you propose a fix, please make it concise.