feat: add missing auth methods

[stacurry]

Description

Some of the authentication methods that the API supports were not included in the types here; adding them

Documentation

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

[ ] Yes

If yes, link a related docs PR and add a docs maintainer as a reviewer. Their approval is required.

[greptile-apps]

Greptile Summary

This PR adds missing authentication method literals to two type union definitions in the user-management interfaces. It extends AuthenticationMethod in authentication-response.interface.ts with 7 new values (DiscordOAuth, IntuitOAuth, SlackOAuth, VercelMarketplaceOAuth, XeroOAuth, ExternalAuth, MigratedSession) and adds the missing 'cross_app_auth' literal to AuthMethod in session.interface.ts.

Key observations:

• Changes are purely additive type-only additions with no logic changes, making them safe to merge.
• AuthenticationMethod (PascalCase) and AuthMethod (snake_case) intentionally use different naming conventions to reflect the serialized vs. deserialized representations of API fields.
• The newly added values are consistent: ExternalAuth/MigratedSession in AuthenticationMethod correspond to pre-existing external_auth/migrated_session in AuthMethod; similarly, cross_app_auth added to AuthMethod mirrors the pre-existing CrossAppAuth in AuthenticationMethod.
• One pre-existing (not introduced by this PR) minor inconsistency: 'unknown' exists in AuthMethod but has no PascalCase counterpart in AuthenticationMethod.

Confidence Score: 5/5

• This PR is safe to merge — it only adds missing string literals to TypeScript union types with no logic changes.
• The changes are purely additive type-level additions. No runtime logic, no API calls, no security-sensitive code, and no breaking changes to existing consumers (new union members are fully backwards compatible). The additions are consistent with the existing conventions used in each file.
• No files require special attention.

Important Files Changed

Filename	Overview
src/user-management/interfaces/authentication-response.interface.ts	Adds 7 new string literals to the AuthenticationMethod union type: DiscordOAuth, IntuitOAuth, SlackOAuth, VercelMarketplaceOAuth, XeroOAuth, ExternalAuth, and MigratedSession. No logic changes.
src/user-management/interfaces/session.interface.ts	Adds the missing 'cross_app_auth' literal to the AuthMethod union type, aligning it with the pre-existing 'CrossAppAuth' value already present in AuthenticationMethod.

Class Diagram

%%{init: {'theme': 'neutral'}}%%
classDiagram
    class AuthenticationMethod {
        <<union type>>
        SSO
        Password
        Passkey
        AppleOAuth
        BitbucketOAuth
        DiscordOAuth ✨
        GitHubOAuth
        GitLabOAuth
        GoogleOAuth
        IntuitOAuth ✨
        LinkedInOAuth
        MicrosoftOAuth
        SalesforceOAuth
        SlackOAuth ✨
        VercelMarketplaceOAuth ✨
        VercelOAuth
        XeroOAuth ✨
        MagicAuth
        CrossAppAuth
        ExternalAuth ✨
        MigratedSession ✨
        Impersonation
    }

    class AuthMethod {
        <<union type>>
        cross_app_auth ✨
        external_auth
        impersonation
        magic_code
        migrated_session
        oauth
        passkey
        password
        sso
        unknown
    }

    class AuthenticationResponse {
        +User user
        +string organizationId?
        +string accessToken
        +string refreshToken
        +Impersonator impersonator?
        +AuthenticationMethod authenticationMethod?
        +string sealedSession?
        +OauthTokens oauthTokens?
    }

    class Session {
        +string id
        +string userId
        +AuthMethod authMethod
        +SessionStatus status
        +string expiresAt
    }

    AuthenticationResponse --> AuthenticationMethod
    Session --> AuthMethod

Loading

_{Last reviewed commit: 6d614c1}

[greptile-apps]

_{2 files reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}

[nicknisi]

LGTM but to fix CI you'll need to rename the title of this PR to be prefixed with feat:. See this for more info on the labels and when to use them.

This is to automate the creation of release PRs.