Generate clients

[herber]

Note

Medium Risk
Large generated diff with breaking callback client shapes and removed endpoints; SDK integrators must migrate call sites even though runtime logic is mostly thin HTTP wrappers.

Overview
Regenerates the magnetar Python client under metorial/_generated/magnetar to match a newer API surface: new endpoint modules and type/mapper export lists, with matching updates across dashboard, management, and instance-scoped variants.

Callbacks (breaking for SDK callers): The integration-provider model replaces deployment-centric setup. callbacks create/update now take integration_id / integration_provider_id (optional name) and drop provider_deployment_id, destinations, triggers, and poll overrides; delete is documented as disabling callbacks on the provider. Nested clients for destinations, notifications, and callback-scoped events/instances are removed. Callback events and callback instances are new top-level read APIs (callback-events, callback-instances) with richer filters.

New product areas: A full chat stack (connections, instances, workspaces, chats, channels, messages, reactions, threads, DMs, typing, events). Consumer read APIs for agents, identity credentials, session connections, and tool calls. Skills merge requests (comments, events, resolve/perform/rollback), imports, fork syncs, and share. Organization event destinations/listeners, events, outposts (credentials/access), and webhook events. Documents edit-token fetch.

Note: Typed wrapper code such as _magnetar_sdk.py may still reference removed callback submodules unless updated in the same release.

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

[cursor]

Cursor Bugbot has reviewed your changes using default effort 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 df4e51b. Configure here.}

[cursor]

DM open omits request body

High Severity

open POSTs with no body even though DashboardInstanceChatsDmsOpenBody is imported and the method is documented as opening a DM with one or more users. Callers cannot pass user IDs or other body fields, so the request cannot identify who the DM is for. The same gap is in the dashboard and management variants.

Additional Locations (2)

• src/metorial/_generated/magnetar/endpoints/dashboard_instance_chats_dms.py#L10-L23
• src/metorial/_generated/magnetar/endpoints/management_instance_chats_dms.py#L10-L23

 

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