feat(pipes): expose connected account provenance

[dandorman]

Description

SDK counterpart to https://github.com/workos/workos/pull/74550 (PVIT-1003). Adds two optional fields to ConnectedAccount (and the provider-list connected-account type):

establishedByUserId?: string | null;                          // ← established_by_user_id
stateReason?: 'establishing_member_membership_ended' | null;  // ← state_reason

Both deserialize to null when an older API response omits them. establishedByUserId: null + stateReason: 'establishing_member_membership_ended' means the member who established an organization-owned connection left the organization; state is unchanged (needs_reauthorization).

Generated with oagen from the workos PR's spec. The diff is only the delta between generating from main's spec and the PR's spec, so unrelated spec drift is not included. docs/PIPES_COMPATIBILITY.md gets a short provenance note. Additive, so no breaking change. Keep this as a draft until the API PR merges and openapi-spec syncs.

npx tsc --noEmit, jest src/pipes (125 passing), prettier, and eslint on src/pipes all pass.

Documentation

Does this require changes to the WorkOS Docs? E.g. the API Reference or code snippets need updates.

[x] Yes

API reference and narrative docs are regenerated in https://github.com/workos/workos/pull/74550.

Link to Devin session: https://app.devin.ai/sessions/36f3d8c7cd3444918fc616f9f6d332b2
Open in Devin Desktop: https://app.devin.ai/desktop/session/36f3d8c7cd3444918fc616f9f6d332b2?variant=devin
Requested by: @dandorman

[devin-ai-integration]

I'll fix CI failures and address comments from users with write access. I'll skip comments containing "(aside)".

• Disable automatic comment, CI, and merge conflict monitoring

---

Original prompt from dan

'Post-launch: expose Pipes connection establishment provenance in APIs and SDKs' (PVIT-1003)

User instruction: @devin please get cooking on a draft PR for this

[linear-code]

PVIT-1003