feat(generated): SSO (batch 16283437)

[workos-sdk-automation]

Summary

Regenerated SDK from spec changes.

Triggered by workos/openapi-spec@c7b7769

[greptile-apps]

Greptile Summary

This regeneration removes the SSO Connection callback endpoint and clarifies SAML prompt behavior.

• Removes callbackEndpoint from the Connection DTO, deserialization, and serialization.
• Updates Connection fixtures to match the reduced response shape.
• Clarifies that prompt=login only affects supported SAML providers.
• Updates generation metadata and adds a pending changelog entry.

Confidence Score: 3/5

This PR should not merge until the public Connection field removal is classified and released as a breaking SDK change.

Removing the exported property and named constructor parameter can break existing consumer code, but the pending changelog currently presents the change as an ordinary fix.

Files Needing Attention: lib/Resource/Connection.php and .changelog-pending/2026-07-28T20-32-59-c7b77690a4486560659df08d947039af4cd52055.md

Important Files Changed

Filename	Overview
lib/Resource/Connection.php	Removes a public resource property and its array mappings, creating a breaking SDK surface change that is not classified accordingly.
.changelog-pending/2026-07-28T20-32-59-c7b77690a4486560659df08d947039af4cd52055.md	Documents the field removal as a fix despite its breaking effect on existing consumers.
lib/Service/SSO.php	Changes only the prompt parameter documentation and does not alter runtime behavior.

Prompt To Fix All With AI

### Issue 1
.changelog-pending/2026-07-28T20-32-59-c7b77690a4486560659df08d947039af4cd52055.md:1
**Breaking removal classified as fix**

When consumers upgrade within the version range selected for fixes, removing the public `Connection::$callbackEndpoint` property and named constructor parameter causes undefined-property access or `Unknown named parameter $callbackEndpoint` errors, despite the changelog presenting this SDK surface break as an ordinary fix.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

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

[greptile-apps]

Breaking removal classified as fix

When consumers upgrade within the version range selected for fixes, removing the public Connection::$callbackEndpoint property and named constructor parameter causes undefined-property access or Unknown named parameter $callbackEndpoint errors, despite the changelog presenting this SDK surface break as an ordinary fix.

Knowledge Base Used: SSO and User Management authentication flows

Prompt To Fix With AI

This is a comment left during a code review.
Path: .changelog-pending/2026-07-28T20-32-59-c7b77690a4486560659df08d947039af4cd52055.md
Line: 1

Comment:
**Breaking removal classified as fix**

When consumers upgrade within the version range selected for fixes, removing the public `Connection::$callbackEndpoint` property and named constructor parameter causes undefined-property access or `Unknown named parameter $callbackEndpoint` errors, despite the changelog presenting this SDK surface break as an ordinary fix.

**Knowledge Base Used:** [SSO and User Management authentication flows](https://app.greptile.com/workos/-/custom-context/knowledge-base/workos/workos-php/-/docs/sso-and-user-management.md)

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!