Update API specifications with fern api update

[github-actions]

Update API specifications by running fern api update.

---

Note

Medium Risk
Medium risk because it changes public API contracts (new OAuth/session fields, pagination params/response shapes, and new Share Link update endpoint), which can affect generated SDKs and existing clients expecting old schemas or error codes.

Overview
Updates openapi.json with several contract additions/changes: introduces OAuth auditing/types (new oauth-consent-grant/oauth-consent-deny actions, OAuthScope, OAuth session fields like clientId/landscapeId/scopes, and performedByClientId on actions) plus new org controls (aiModel selection and oauthLandscapeWriteEnabled).

Expands multiple APIs: adds cursor pagination (cursor/limit, nextCursor, and x-fern-pagination) to ModelObjects/ModelConnections list endpoints, enhances diagram export and AI description generation inputs (maxWidth, filtering by modelObjectIds), and extends Share Links (new adrs/model-viewer modes, adrId option, and a PATCH update operation distinct from DELETE).

Also tightens/adjusts schemas and responses: makes catalog technology status nullable to allow “private”, adds ADR content, disallows additional properties on import payload schemas, updates import hierarchy rules for parentId, and adds 403 Forbidden responses across many endpoints.

^{Reviewed by Cursor Bugbot for commit d148d26. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit d148d26. Configure here.}

[cursor]

Expand key and response property naming mismatch

Medium Severity

The new flows value in ModelObjectExpandKey doesn't match its corresponding response property flowsExpanded in ModelObjectExpanded. All other expand keys (domain, tags, technologies) map directly to identically-named properties in the response. This breaks the established naming convention and will likely confuse SDK consumers who expect flows in the response after passing flows as the expand parameter.

Additional Locations (1)

• openapi.json#L13311-L13312

 

^{Reviewed by Cursor Bugbot for commit d148d26. Configure here.}