mammoth-cli 2.0.15__tar.gz → 2.0.16__tar.gz

{mammoth_cli-2.0.15 → mammoth_cli-2.0.16}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: mammoth-cli
-Version: 2.0.15
+Version: 2.0.16
 Summary: Command-line interface for the Mammoth Analytics platform
 Project-URL: homepage, https://mammoth.io
 Project-URL: repository, https://github.com/EdgeMetric/mammothsdk
@@ -17,7 +17,7 @@ Classifier: Topic :: Software Development :: Libraries :: Python Modules
 Requires-Python: <3.15,>=3.12
 Requires-Dist: jsonschema>=4.20
 Requires-Dist: keyring<26,>=25.7
-Requires-Dist: mammoth-io<0.8,>=0.7.7
+Requires-Dist: mammoth-io<0.8,>=0.7.8
 Requires-Dist: platformdirs<5,>=4.10
 Requires-Dist: pydantic<3,>=2.13
 Requires-Dist: pyyaml<7,>=6

{mammoth_cli-2.0.15 → mammoth_cli-2.0.16}/mammoth_cli/__init__.py

@@ -6,7 +6,7 @@ not implement a second HTTP client and does not call private SDK members.
 
 from __future__ import annotations
 
-__version__ = "2.0.15"
+__version__ = "2.0.16"
 
 # The versioned machine output envelope contract.
 SCHEMA_VERSION = 1

{mammoth_cli-2.0.15 → mammoth_cli-2.0.16}/mammoth_cli/bundled_skill/mammoth-cli/references/capabilities.md

@@ -1,7 +1,7 @@
 # What is proven on release
 
 Generated from `docs/release-capability-matrix.json`; do not edit by hand.
-455 API operations have a CLI command. 193 were exercised successfully on release, 2 are not supported there, and the rest are untried. Untried is not broken: discover the contract with `mammoth schema get COMMAND_ID --output json --no-input`, run it, and treat the structured error envelope as the answer.
+455 API operations have a CLI command. 225 were exercised successfully on release, 2 are not supported there, and the rest are untried. Untried is not broken: discover the contract with `mammoth schema get COMMAND_ID --output json --no-input`, run it, and treat the structured error envelope as the answer.
 
 Status meanings:
 
@@ -17,27 +17,27 @@ The typed `view transform *` commands all submit through `view.task.add`; its ro
 
 | Family | Commands | Verified | Not supported | Untried |
 |---|---|---|---|---|
-| `dashboard` | 104 | 80 | 2 | 22 |
-| `view` | 62 | 43 | 0 | 19 |
-| `support` | 45 | 0 | 0 | 45 |
-| `billing` | 23 | 0 | 0 | 23 |
+| `dashboard` | 104 | 81 | 2 | 21 |
+| `view` | 62 | 50 | 0 | 12 |
+| `support` | 45 | 9 | 0 | 36 |
+| `billing` | 23 | 4 | 0 | 19 |
 | `connector` | 22 | 2 | 0 | 20 |
-| `workspace` | 19 | 6 | 0 | 13 |
-| `project` | 17 | 11 | 0 | 6 |
+| `workspace` | 19 | 7 | 0 | 12 |
+| `project` | 17 | 15 | 0 | 2 |
 | `workflow` | 16 | 5 | 0 | 11 |
-| `dataset` | 15 | 10 | 0 | 5 |
+| `dataset` | 15 | 12 | 0 | 3 |
 | `parameter` | 14 | 2 | 0 | 12 |
 | `data-app` | 12 | 1 | 0 | 11 |
-| `folder` | 8 | 7 | 0 | 1 |
+| `folder` | 8 | 8 | 0 | 0 |
 | `snippet` | 8 | 1 | 0 | 7 |
 | `automation` | 7 | 1 | 0 | 6 |
-| `user` | 7 | 2 | 0 | 5 |
+| `user` | 7 | 3 | 0 | 4 |
 | `webhook` | 7 | 0 | 0 | 7 |
 | `addon` | 6 | 0 | 0 | 6 |
-| `batch` | 6 | 4 | 0 | 2 |
+| `batch` | 6 | 5 | 0 | 1 |
 | `file` | 6 | 5 | 0 | 1 |
 | `agent` | 5 | 1 | 0 | 4 |
-| `ai` | 5 | 1 | 0 | 4 |
+| `ai` | 5 | 2 | 0 | 3 |
 | `annotation` | 5 | 1 | 0 | 4 |
 | `client-app` | 5 | 0 | 0 | 5 |
 | `notification` | 5 | 1 | 0 | 4 |
@@ -64,14 +64,13 @@ Verified: `agent.session.list`
 
 ## `ai`
 
-Verified: `ai.condition.generate`
+Verified: `ai.condition.generate`, `ai.expression.generate`
 
 | Command | State | Note |
 |---|---|---|
-| `ai.retention.condition` | observed blocker | backend_error: HTTP 403 4PERM001 PERMISSION_UNDEFINED: "Permissions have not been set correctly for this API, please contact Mammoth Help to report this error" on POST /workspaces/ |
-| `ai.expression.generate` | CLI defect fixed, untried since | 2.0.15 (SDK-side argument rejections (e.g. mode not math/metric) surface as invalid_arguments with the SDK message instead of an empty api_error) |
-| `ai.sql.generate` | CLI defect fixed, untried since | 2.0.15 (dataset_id is required and sent as the query parameter |
-| `ai.suggestion.list` | CLI defect fixed, untried since | 2.0.15 (command takes the release UnifiedPromptSpec (suggestion_type + params, optional dataset_id/dataview_id)) |
+| `ai.retention.condition` | observed blocker | permission: POST /workspaces/4/projects/24/sql_generation/retention_policy -> HTTP 403 4PERM001 PERMISSION_UNDEFINED, error_object {code:76,message:'Permissions have not been set c |
+| `ai.sql.generate` | observed blocker | backend_error: Fix held (dataset_id required and sent as query param -- request reached backend and got a domain-specific conflict, not an empty api_error) |
+| `ai.suggestion.list` | observed blocker | backend_error: Fix held: release UnifiedPromptSpec (suggestion_type + params, optional dataset_id/dataview_id) shape accepted and dispatched to a real job (id 381), which failed fo |
 
 ## `annotation`
 
@@ -83,12 +82,24 @@ Verified: `automation.list`
 
 ## `batch`
 
-Verified: `batch.bulk-delete`, `batch.delete`, `batch.get`, `batch.list`
+Verified: `batch.bulk-delete`, `batch.delete`, `batch.get`, `batch.list`, `batch.update`
 
 | Command | State | Note |
 |---|---|---|
-| `batch.create` | CLI defect fixed, untried since | 2.0.15 (mapping is sent as the release list of {source_c_name,destination_c_name} items and body keys match BatchesPostRequest) |
-| `batch.update` | CLI defect fixed, untried since | 2.0.15 (SDK-side argument rejections (patch ops must be replace/remove) surface as invalid_arguments with the SDK message instead of an empty api_error) |
+| `batch.create` | CLI defect fixed, untried since | 2.0.16 (mapping items carry expected_destination_c_type (TEXT/NUMERIC/DATE) |
+
+## `billing`
+
+Verified: `billing.stripe.history`, `billing.stripe.payment-method.list`, `billing.stripe.status`, `billing.subscription.get`
+
+| Command | State | Note |
+|---|---|---|
+| `billing.chargebee-plan` | observed blocker | backend_error: The CLI gates this GET behind --yes --confirm WORKSPACE_ID; with confirmation: HTTP 400 4SUBS014 'Chargebee plan not found for the given workspace' (workspace 4 is n |
+| `billing.invoice.get` | observed blocker | blocked_missing_fixture: The CLI gates this GET behind --yes --confirm WORKSPACE_ID; with confirmation: billing invoice list answered HTTP 500, so no invoice id was observed |
+| `billing.invoice.list` | observed blocker | backend_error: The CLI gates this GET behind --yes --confirm WORKSPACE_ID; with confirmation: HTTP 500 with empty body on GET /workspaces/4/subscription_v1/invoices |
+| `billing.stripe.preview-invoice` | observed blocker | backend_error: The CLI gates this GET behind --yes --confirm WORKSPACE_ID; with confirmation: HTTP 400 4SUBS037 'Failed to perform subscription operation' |
+| `billing.stripe.upcoming-invoice` | observed blocker | backend_error: The CLI gates this GET behind --yes --confirm WORKSPACE_ID; with confirmation: HTTP 400 4SUBS074 'Upcoming invoice not found' (no active Stripe subscription on works |
+| `billing.stripe.usage` | observed blocker | backend_error: The CLI gates this GET behind --yes --confirm WORKSPACE_ID; with confirmation: HTTP 400 5GENR010 UNKNOWN_ERROR 'Unknown error occurred |
 
 ## `browse`
 
@@ -99,6 +110,12 @@ Verified: `browse.project`, `browse.workspace`
 | `browse.folder` | observed blocker | cli_error: rejects folder id 0 although folder.root reports id 0 as the root |
 | `browse.root` | observed blocker | server_error: see sweep report |
 
+## `client-app`
+
+| Command | State | Note |
+|---|---|---|
+| `client-app.list` | observed blocker | forbidden: backend_code=4GENR012 INVALID_TOKEN_FOR_CLIENT_APPS: 'Cannot access this API with API-tokens' on GET /workspaces/4/clientapps |
+
 ## `connector`
 
 Verified: `connector.active`, `connector.list`
@@ -108,12 +125,12 @@ Verified: `connector.active`, `connector.list`
 | `connector.ai.session.list` | observed blocker | cli_error: backend returned HTTP 200 but the CLI raised api_error (envelope mismatch) |
 | `connector.connection.list` | observed blocker | server_error: see sweep report |
 | `connector.get` | observed blocker | validation_error: HTTP 400 'Invalid connector key' for a key returned by connector.list |
+| `connector.query.generate` | observed blocker | blocked_missing_fixture: No real connector connection exists in workspace 4 (connector.list shows all is_added:false; connector.active returns []), matching the documented capabili |
 | `connector.query.status` | observed blocker | blocked_missing_fixture: No real connector connection exists in workspace 4 (connector list shows all is_added:false; connector active returns []) and creating one requires externa |
-| `connector.query.generate` | CLI defect fixed, untried since | 2.0.15 (input field is query (release Intent body) instead of prompt) |
 
 ## `dashboard`
 
-Verified: `dashboard.action`, `dashboard.analytics`, `dashboard.archive`, `dashboard.cancel-generation`, `dashboard.canvas.get`, `dashboard.canvas.restore`, `dashboard.canvas.save`, `dashboard.chat.edit`, `dashboard.chat.history`, `dashboard.context.create`, `dashboard.context.delete`, `dashboard.context.extract`, `dashboard.context.list`, `dashboard.context.update`, `dashboard.create-blank`, `dashboard.delete`, `dashboard.descriptor-data`, `dashboard.duplicate`, `dashboard.exemplar.extract`, `dashboard.figure-intent`, `dashboard.get`, `dashboard.get-by-url`, `dashboard.job-by-url`, `dashboard.list`, `dashboard.page.plan`, `dashboard.pages.add`, `dashboard.published.canvas`, `dashboard.published.share-page`, `dashboard.qa.ask`, `dashboard.qa.comment.create`, `dashboard.qa.comment.delete`, `dashboard.qa.feedback`, `dashboard.qa.session.create`, `dashboard.qa.session.delete`, `dashboard.qa.session.fork`, `dashboard.qa.session.get`, `dashboard.qa.session.list`, `dashboard.qa.session.rename`, `dashboard.qa.session.set-visibility`, `dashboard.qa.settings.get`, `dashboard.qa.settings.set`, `dashboard.query`, `dashboard.restore`, `dashboard.rls.assignment.list`, `dashboard.rls.assignment.set`, `dashboard.rls.column.list`, `dashboard.rls.value.list`, `dashboard.share`, `dashboard.signature.create`, `dashboard.signature.delete`, `dashboard.signature.list`, `dashboard.signature.update`, `dashboard.style.custom.create`, `dashboard.style.custom.delete`, `dashboard.style.custom.list`, `dashboard.style.custom.update`, `dashboard.style.default.get`, `dashboard.style.default.set`, `dashboard.style.derive`, `dashboard.style.extract-brand`, `dashboard.style.preset.list`, `dashboard.style.token.list`, `dashboard.suggestion.list`, `dashboard.swap-data`, `dashboard.tags.delete`, `dashboard.tags.list`, `dashboard.tags.merge`, `dashboard.tags.rename`, `dashboard.tags.set`, `dashboard.template.apply`, `dashboard.template.fit`, `dashboard.template.get`, `dashboard.template.list`, `dashboard.template.preview`, `dashboard.template.resolve-mapping`, `dashboard.templates.pending`, `dashboard.trash`, `dashboard.update`, `dashboard.v3.generate`, `dashboard.video-state`
+Verified: `dashboard.action`, `dashboard.analytics`, `dashboard.archive`, `dashboard.cancel-generation`, `dashboard.canvas.get`, `dashboard.canvas.restore`, `dashboard.canvas.save`, `dashboard.chat.edit`, `dashboard.chat.history`, `dashboard.context.create`, `dashboard.context.delete`, `dashboard.context.extract`, `dashboard.context.list`, `dashboard.context.update`, `dashboard.create-blank`, `dashboard.delete`, `dashboard.descriptor-data`, `dashboard.duplicate`, `dashboard.exemplar.extract`, `dashboard.figure-intent`, `dashboard.get`, `dashboard.get-by-url`, `dashboard.job-by-url`, `dashboard.list`, `dashboard.og-card`, `dashboard.page.plan`, `dashboard.pages.add`, `dashboard.published.canvas`, `dashboard.published.share-page`, `dashboard.qa.ask`, `dashboard.qa.comment.create`, `dashboard.qa.comment.delete`, `dashboard.qa.feedback`, `dashboard.qa.session.create`, `dashboard.qa.session.delete`, `dashboard.qa.session.fork`, `dashboard.qa.session.get`, `dashboard.qa.session.list`, `dashboard.qa.session.rename`, `dashboard.qa.session.set-visibility`, `dashboard.qa.settings.get`, `dashboard.qa.settings.set`, `dashboard.query`, `dashboard.restore`, `dashboard.rls.assignment.list`, `dashboard.rls.assignment.set`, `dashboard.rls.column.list`, `dashboard.rls.value.list`, `dashboard.share`, `dashboard.signature.create`, `dashboard.signature.delete`, `dashboard.signature.list`, `dashboard.signature.update`, `dashboard.style.custom.create`, `dashboard.style.custom.delete`, `dashboard.style.custom.list`, `dashboard.style.custom.update`, `dashboard.style.default.get`, `dashboard.style.default.set`, `dashboard.style.derive`, `dashboard.style.extract-brand`, `dashboard.style.preset.list`, `dashboard.style.token.list`, `dashboard.suggestion.list`, `dashboard.swap-data`, `dashboard.tags.delete`, `dashboard.tags.list`, `dashboard.tags.merge`, `dashboard.tags.rename`, `dashboard.tags.set`, `dashboard.template.apply`, `dashboard.template.fit`, `dashboard.template.get`, `dashboard.template.list`, `dashboard.template.preview`, `dashboard.template.resolve-mapping`, `dashboard.templates.pending`, `dashboard.trash`, `dashboard.update`, `dashboard.v3.generate`, `dashboard.video-state`
 
 | Command | State | Note |
 |---|---|---|
@@ -122,18 +139,17 @@ Verified: `dashboard.action`, `dashboard.analytics`, `dashboard.archive`, `dashb
 | `dashboard.data.draft` | observed blocker | blocked_missing_fixture: Dashboard 56 (create-blank/v3 engine) has no widgets in its canvas and getDraftData rejects with backend_code 4DASH004 DASHBOARD_WRONG_ENGINE: "This dashbo |
 | `dashboard.data.published` | observed blocker | blocked_missing_fixture: Same as dashboard.data.draft: backend_code 4DASH004 DASHBOARD_WRONG_ENGINE on /dashboards/56/getPublishData |
 | `dashboard.published-data-by-url` | observed blocker | blocked_missing_fixture: backend_code 4DASH004 DASHBOARD_WRONG_ENGINE on /dashboards/url/IuZl5tk5KcEHJWTy4tnhrA/getPublishData, same class of blocker as widget-data: this v3 dashbo |
+| `dashboard.published.data` | observed blocker | blocked_missing_fixture: Could not publish dashboard 59 to reach a live published state: `dashboard action 59 {action:publish-presentation}` failed twice with HTTP 500 outcome_unkn |
 | `dashboard.published.pdf-artifact` | observed blocker | blocked_missing_fixture: Same as dashboard.pdf-artifact: no real pdf job available; used job 313 (descriptor-data job) as the only real job id in hand and got backend_code 4DASH001 |
 | `dashboard.published.pdf.export` | observed blocker | backend_error: Got backend_code 4PERM002 PERMISSION_ERROR, "User lacks permission to perform given action" on POST /dashboards/url/IuZl5tk5KcEHJWTy4tnhrA/pdf (403), envelope: {"err |
 | `dashboard.published.video.export` | observed blocker | backend_error: backend_code 4PERM002 PERMISSION_ERROR, "User lacks permission to perform given action" on POST /dashboards/url/IuZl5tk5KcEHJWTy4tnhrA/video (403) |
 | `dashboard.source.list` | observed blocker | blocker; still broken, not one of the 11 CLI-fixed commands |
-| `dashboard.template.create` | observed blocker | backend_error: Both attempts (2/2) returned the same outcome_unknown envelope: {"error":{"code":"outcome_unknown","details":{"endpoint":"/dashboards/v3/templates","method":"POST"," |
+| `dashboard.template.create` | observed blocker | backend: POST /dashboards/v3/templates -> HTTP 500, empty response_body, request_id:null, code:outcome_unknown |
 | `dashboard.template.delete` | observed blocker | blocked_missing_fixture: dashboard.template.create never produced an owned template (HTTP 500 both attempts, reconciled as not-committed via template list) |
 | `dashboard.templates.use` | observed blocker | skipped_out_of_scope: BRIEF instructs running templates.use "on that template" (i.e |
 | `dashboard.video.export` | observed blocker | backend_error: After publishing dashboard 56 (dashboard.share public + dashboard.action publish-presentation), the previously-documented "publish the dashboard before exporting a v |
 | `dashboard.widget-data` | observed blocker | blocked_missing_fixture: backend_code 4DASH004 DASHBOARD_WRONG_ENGINE, "This dashboard uses a different rendering engine -- use the matching endpoints", on POST /dashboards/56/widg |
 | `dashboard.widget-data-by-url` | observed blocker | blocked_missing_fixture: Same backend_code 4DASH004 DASHBOARD_WRONG_ENGINE, on POST /dashboards/url/IuZl5tk5KcEHJWTy4tnhrA/widgets/data |
-| `dashboard.og-card` | CLI defect fixed, untried since | SDK 0.7.5 returns a described binary body |
-| `dashboard.published.data` | CLI defect fixed, untried since | 2.0.15 (published-dashboard jobs are polled through the URL-scoped job route) |
 
 ## `data-app`
 
@@ -141,14 +157,12 @@ Verified: `data-app.list`
 
 ## `dataset`
 
-Verified: `dataset.batch-data`, `dataset.create`, `dataset.data`, `dataset.delete`, `dataset.file-settings.get`, `dataset.file-settings.update`, `dataset.get`, `dataset.list`, `dataset.restore`, `dataset.trash`
+Verified: `dataset.batch-data`, `dataset.bulk-delete`, `dataset.create`, `dataset.data`, `dataset.delete`, `dataset.file-settings.get`, `dataset.file-settings.undo`, `dataset.file-settings.update`, `dataset.get`, `dataset.list`, `dataset.restore`, `dataset.trash`
 
 | Command | State | Note |
 |---|---|---|
 | `dataset.bulk-update` | observed blocker | cli_error: Schema preconditions already flag this as BLOCKED[B07 DATASET_PATCH_UNTYPED]; reserved, not registered -- confirmed live |
-| `dataset.create-from-pdf` | observed blocker | backend_error: Attempt 1 (file_name only) -> HTTP 400 4DSET053 MUST_PROVIDE_TABLE_LIST_OR_PREVIEW: "Either 'table_list' or 'is_preview_needed' must be provided." (clear, actionable |
-| `dataset.bulk-delete` | CLI defect fixed, untried since | 2.0.15 (dataset_ids is required, confirmation names the ids, and ids are sent as the ids query parameter) |
-| `dataset.file-settings.undo` | CLI defect fixed, untried since | 2.0.15 (2xx non-object bodies are reported as success instead of outcome_unknown) |
+| `dataset.create-from-pdf` | observed blocker | backend: POST /workspaces/4/projects/24/datasets-from-pdf |
 
 ## `external-key`
 
@@ -166,11 +180,7 @@ Verified: `file.bulk-delete`, `file.delete`, `file.get`, `file.list`, `file.uplo
 
 ## `folder`
 
-Verified: `folder.bulk-delete`, `folder.create`, `folder.delete`, `folder.get`, `folder.list`, `folder.trash`, `folder.update`
-
-| Command | State | Note |
-|---|---|---|
-| `folder.move` | CLI defect fixed, untried since | 2.0.15 (SDK now sends {patch:[{op:move,from:[ids],path:destination/root}]}) |
+Verified: `folder.bulk-delete`, `folder.create`, `folder.delete`, `folder.get`, `folder.list`, `folder.move`, `folder.trash`, `folder.update`
 
 ## `job`
 
@@ -186,15 +196,11 @@ Verified: `parameter.group.list`, `parameter.list`
 
 ## `project`
 
-Verified: `project.bulk-delete`, `project.checkpoint.list`, `project.create`, `project.data-check.list`, `project.list`, `project.pending-changes`, `project.publish-credentials`, `project.resource-dependencies`, `project.resource-dependencies.update`, `project.resource-status`, `project.sample-flow`
+Verified: `project.bulk-delete`, `project.bulk-update`, `project.checkpoint.list`, `project.create`, `project.data-check.list`, `project.delete`, `project.list`, `project.pending-changes`, `project.publish-credentials`, `project.resource-dependencies`, `project.resource-dependencies.update`, `project.resource-status`, `project.sample-flow`, `project.update`, `project.user.add`
 
 | Command | State | Note |
 |---|---|---|
 | `project.user.update` | observed blocker | backend_error: HTTP 400 4PROJ010 ROLE_ALREADY_ASSIGNED: "Role already assigned to the user" -- targeted our own user (id 5, already project_admin as project owner) |
-| `project.bulk-update` | CLI defect fixed, untried since | 2.0.15 (body must be a ProjectsPatch naming project_id in every value item and the confirmation lists those projects) |
-| `project.delete` | CLI defect fixed, untried since | 2.0.15 (2xx non-object bodies such as 202 Accepted are reported as success instead of outcome_unknown) |
-| `project.update` | CLI defect fixed, untried since | 2.0.15 (SDK now sends the release ProjectPatch {patches:[{op:replace,path:name/properties,...}]} body) |
-| `project.user.add` | CLI defect fixed, untried since | 2.0.15 (SDK now sends {users:[{user_id,role}]} with numeric user ids) |
 
 ## `report`
 
@@ -204,12 +210,17 @@ Verified: `report.list`
 
 | Command | State | Note |
 |---|---|---|
-| `schedule.list` | observed blocker | validation_error: HTTP 400 with message 'Not implemented' |
+| `schedule.get` | observed blocker | blocked_missing_fixture: Not run: id source schedule.list failed with backend_error (5GENR011 NOT_IMPLEMENTED, HTTP 400), so no schedule_id was observed to use |
+| `schedule.list` | observed blocker | backend_error: backend_code=5GENR011 NOT_IMPLEMENTED: 'Not implemented' on GET /workspaces/4/projects/3/schedules |
 
 ## `snippet`
 
 Verified: `snippet.list`
 
+## `support`
+
+Verified: `support.connector-profile.list`, `support.connector.list`, `support.feature-profile.list`, `support.feature.list`, `support.plan.chargebee-list`, `support.plan.list`, `support.plan.self-serve-list`, `support.user.list-all`, `support.workspace.list`
+
 ## `template`
 
 | Command | State | Note |
@@ -222,36 +233,25 @@ Verified: `trash.add`, `trash.list`, `trash.restore`
 
 ## `user`
 
-Verified: `user.get`, `user.preference.get`
-
-| Command | State | Note |
-|---|---|---|
-| `user.preference.update` | CLI defect fixed, untried since | 2.0.15 (command takes the release {patch:[...]} list instead of free keyword fields) |
+Verified: `user.get`, `user.preference.get`, `user.preference.update`
 
 ## `view`
 
-Verified: `view.active-user.list`, `view.active-user.mark`, `view.ai.generate-data`, `view.bulk-delete`, `view.checkpoint.create`, `view.checkpoint.list`, `view.conditional-format.list`, `view.conditional-format.update`, `view.create`, `view.data-check.create`, `view.data-check.get`, `view.data-check.list`, `view.data.get`, `view.data.query`, `view.delete`, `view.derivative.create`, `view.derivative.list`, `view.draft.command`, `view.export.delete`, `view.export.get`, `view.export.list`, `view.export.publish-db`, `view.export.update`, `view.exportable-config.get`, `view.get`, `view.list`, `view.parameter-context`, `view.pipeline.get`, `view.pipeline.items`, `view.pipeline.rerun`, `view.preview`, `view.restore`, `view.task.add`, `view.task.delete`, `view.task.get`, `view.task.list`, `view.trash`, `view.version.apply`, `view.version.delete`, `view.version.get`, `view.version.list`, `view.version.update`
+Verified: `view.active-user.list`, `view.active-user.mark`, `view.ai.generate-data`, `view.ai.profile`, `view.bulk-delete`, `view.checkpoint.create`, `view.checkpoint.delete`, `view.checkpoint.list`, `view.conditional-format.list`, `view.conditional-format.update`, `view.create`, `view.data-check.create`, `view.data-check.delete`, `view.data-check.get`, `view.data-check.list`, `view.data.get`, `view.data.query`, `view.delete`, `view.derivative.create`, `view.derivative.delete`, `view.derivative.list`, `view.derivative.update`, `view.draft.command`, `view.export.delete`, `view.export.get`, `view.export.list`, `view.export.publish-db`, `view.export.update`, `view.exportable-config.get`, `view.get`, `view.list`, `view.parameter-context`, `view.pipeline.edit`, `view.pipeline.get`, `view.pipeline.items`, `view.pipeline.rerun`, `view.preview`, `view.restore`, `view.task.add`, `view.task.delete`, `view.task.get`, `view.task.list`, `view.task.update`, `view.trash`, `view.version.apply`, `view.version.delete`, `view.version.get`, `view.version.list`, `view.version.update`
 
 | Command | State | Note |
 |---|---|---|
-| `view.ai.generation-info` | observed blocker | backend_error: HTTP 400 5GENR011 NOT_IMPLEMENTED: "Not implemented" -- matches known capabilities.md observed blocker for this route (backend-side, not CLI) |
-| `view.checkpoint.get` | observed blocker | backend_error: HTTP 500 on GET /workspaces/4/projects/21/datasets/48/dataviews/73/pipeline/checkpoints/1 with empty response_body:{}, reproduced twice (2s apart) right after checkp |
+| `view.ai.generation-info` | observed blocker | backend: GET /workspaces/4/projects/24/datasets/54/dataviews/76/data/generate -> HTTP 400 5GENR011 NOT_IMPLEMENTED 'Not implemented', request_id:null |
+| `view.checkpoint.get` | observed blocker | backend: GET /workspaces/4/projects/24/datasets/54/dataviews/76/pipeline/checkpoints/2 -> HTTP 500, empty response_body:{}, request_id:null, backend code: none surfaced (generic ap |
+| `view.checkpoint.update` | observed blocker | backend_error: CLI-side fix (payload now carries value:null as required) held: the correctly-shaped request was dispatched and the backend returned HTTP 500 (not a CLI-side crash): |
 | `view.conditional-format.create` | observed blocker | cli_error: Skill doc (view.md) claims this route is 'fail-closed and must not dispatch a request' (BLOCKED B09 DATAVIEW_INPUT_UNTYPED) -- but live it DOES dispatch: HTTP 400 4GENR0 |
-| `view.data-check.update` | observed blocker | backend_error: PATCH .../pipeline/data-checks/1 -> HTTP 500, empty response_body, CLI correctly reported outcome_unknown (exit 7) rather than a false success |
-| `view.derivative.data` | observed blocker | backend_error: HTTP 500 on POST .../dataviews/73/derivatives/2/data, empty response_body |
-| `view.export.create` | observed blocker | cli_error: Both attempts return exit 0 with a job accepted (334, then 335 after adding target_properties.destination:local), but the job itself always fails: job get shows status:e |
+| `view.data-check.update` | observed blocker | backend: PATCH .../pipeline/data-checks/3 -> HTTP 500, empty response_body, request_id:null, code:outcome_unknown |
+| `view.derivative.data` | observed blocker | backend: POST .../derivatives/4/data -> HTTP 500, empty response_body, request_id:null, code:outcome_unknown |
+| `view.export.create` | observed blocker | backend: CLI accepts the request (exit 0, job 358 accepted on POST /dataviews/76/actions), but job get 358 -> status:error, response:{"error":{"message":"'destination'"}} (a raw Py |
 | `view.exportable-config.apply` | observed blocker | cli_error: Schema's own runnable_example (config:{tasks:[]}) fails: job_failed, response:{reason:(quote)dependencies(quote)} -- a raw Python KeyError, not a structured validation m |
-| `view.task.preview` | observed blocker | cli_error: Schema's own runnable_example (COPY:{}) fails: HTTP 400 5GENR010 UNKNOWN_ERROR "Unknown error occurred |
-| `view.ai.profile` | CLI defect fixed, untried since | 2.0.15 (SDK sends the release ProfileGenerationSpec {params:{action}} body (action defaults to insights)) |
-| `view.checkpoint.delete` | CLI defect fixed, untried since | 2.0.15 (2xx non-object bodies such as 202 Accepted are reported as success instead of outcome_unknown) |
-| `view.checkpoint.update` | CLI defect fixed, untried since | 2.0.15 (example now carries value:null as the backend requires |
-| `view.conditional-format.delete-all` | CLI defect fixed, untried since | 2.0.15 (rule_id is required and sent as the query parameter) |
-| `view.data-check.delete` | CLI defect fixed, untried since | 2.0.15 (2xx non-object bodies such as 202 Accepted are reported as success instead of outcome_unknown) |
-| `view.derivative.delete` | CLI defect fixed, untried since | 2.0.15 (2xx non-object bodies such as 202 Accepted are reported as success instead of outcome_unknown) |
-| `view.derivative.update` | CLI defect fixed, untried since | 2.0.15 (2xx non-object bodies such as 202 Accepted are reported as success instead of outcome_unknown) |
-| `view.export.publish-db-update` | CLI defect fixed, untried since | 2.0.15 (example now shows the only accepted patch path (credentials -> postgres/bigquery)) |
-| `view.pipeline.edit` | CLI defect fixed, untried since | 2.0.15 (example now shows a valid patch (path auto_run with a bool value) |
-| `view.task.update` | CLI defect fixed, untried since | 2.0.15 (SDK now sends {patches:[{op:replace,path:params,value:task_spec}]} (or caller-supplied patches)) |
+| `view.conditional-format.delete-all` | CLI defect fixed, untried since | 2.0.16 (the handler now forwards rule_id from --input (2.0.15 accepted the field but dropped it before the SDK call)) |
+| `view.export.publish-db-update` | CLI defect fixed, untried since | 2.0.16 (example value is the documented {"odbc_type": "postgres"} object (a bare string is rejected)) |
+| `view.task.preview` | CLI defect fixed, untried since | 2.0.16 (example now uses the backend COPY param-template shape: list of {SOURCE, AS{COLUMN,TYPE,INTERNAL_NAME}}, VERSION 2 |
 
 ## `webhook`
 
@@ -265,10 +265,6 @@ Verified: `workflow.graph`, `workflow.list`, `workflow.workspace-datasets`, `wor
 
 ## `workspace`
 
-Verified: `workspace.app-usage`, `workspace.get`, `workspace.list`, `workspace.segment.list`, `workspace.storage-breakdown`, `workspace.user.list`
-
-| Command | State | Note |
-|---|---|---|
-| `workspace.segment.update` | CLI defect fixed, untried since | 2.0.15 (2xx non-object bodies are reported as success instead of outcome_unknown |
+Verified: `workspace.app-usage`, `workspace.get`, `workspace.list`, `workspace.segment.list`, `workspace.segment.update`, `workspace.storage-breakdown`, `workspace.user.list`
 
 Evidence version: CLI mammoth-cli 1.1.11; mammoth-io 0.7.1. Details: `docs/capability-evidence/` in the repository.

{mammoth_cli-2.0.15 → mammoth_cli-2.0.16}/mammoth_cli/bundled_skill/mammoth-cli/references/commands/batch.md

@@ -12,7 +12,7 @@ Expected success: `BatchBulkDeleteResult` in the standard JSON envelope; mutatio
 
 Run: `mammoth batch create`. Exact input fields: `mammoth schema get batch.create --output json --no-input`.
 
-Example: `mammoth batch create 123 123 --input '{"mapping": {"sample_key": "Status"}}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
+Example: `mammoth batch create 123 123 --input '{"mapping": [{"source_c_name": "column_1", "destination_c_name": "column_1", "expected_destination_c_type": "TEXT"}]}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
 
 Expected success: `BatchCreateResult` in the standard JSON envelope; mutation `benign_mutation`, confirmation `none`, wait policy `returns_job`. On nonzero exit, inspect the JSON error envelope and its `recovery_commands`; do not guess request fields. See [representative envelopes](../machine-output.md) for concrete success/error shapes.
 

{mammoth_cli-2.0.15 → mammoth_cli-2.0.16}/mammoth_cli/bundled_skill/mammoth-cli/references/commands/view.md

@@ -446,7 +446,7 @@ Expected success: `ViewExportPublishDbResult` in the standard JSON envelope; mut
 
 Run: `mammoth view export publish-db-update`. Exact input fields: `mammoth schema get view.export.publish-db-update --output json --no-input`.
 
-Example: `mammoth view export publish-db-update 123 --input '{"patch": [{"op": "replace", "path": "credentials", "value": "postgres"}]}' --output json --no-input`. Illustrative only: append `--yes` after observing an owned target.
+Example: `mammoth view export publish-db-update 123 --input '{"patch": [{"op": "replace", "path": "credentials", "value": {"odbc_type": "postgres"}}]}' --output json --no-input`. Illustrative only: append `--yes` after observing an owned target.
 
 Expected success: `ViewExportPublishDbUpdateResult` in the standard JSON envelope; mutation `external_effect`, confirmation `yes_always`, wait policy `not_async`. On nonzero exit, inspect the JSON error envelope and its `recovery_commands`; do not guess request fields. See [representative envelopes](../machine-output.md) for concrete success/error shapes.
 
@@ -612,7 +612,7 @@ Expected success: `ViewRestoreResult` in the standard JSON envelope; mutation `b
 
 Run: `mammoth view task add`. Exact input fields: `mammoth schema get view.task.add --output json --no-input`.
 
-Example: `mammoth view task add 123 --input '{"task_spec": {"DATAVIEW_ID": 123, "SEQUENCE_NUMBER": 1, "COPY": {}}}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
+Example: `mammoth view task add 123 --input '{"task_spec": {"DATAVIEW_ID": 123, "SEQUENCE_NUMBER": 1, "COPY": [{"SOURCE": "column_1", "AS": {"COLUMN": "Copy of column 1", "TYPE": "TEXT", "INTERNAL_NAME": "column_9"}}], "VERSION": 2}}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
 
 Expected success: `ViewTaskAddResult` in the standard JSON envelope; mutation `reversible_pipeline`, confirmation `none`, wait policy `always_wait`. On nonzero exit, inspect the JSON error envelope and its `recovery_commands`; do not guess request fields. See [representative envelopes](../machine-output.md) for concrete success/error shapes.
 
@@ -644,7 +644,7 @@ Expected success: `ViewTaskListResult` in the standard JSON envelope; mutation `
 
 Run: `mammoth view task preview`. Exact input fields: `mammoth schema get view.task.preview --output json --no-input`.
 
-Example: `mammoth view task preview 123 --input '{"task_spec": {"DATAVIEW_ID": 123, "SEQUENCE_NUMBER": 1, "COPY": {}}}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
+Example: `mammoth view task preview 123 --input '{"task_spec": {"DATAVIEW_ID": 123, "SEQUENCE_NUMBER": 1, "COPY": [{"SOURCE": "column_1", "AS": {"COLUMN": "Copy of column 1", "TYPE": "TEXT", "INTERNAL_NAME": "column_9"}}], "VERSION": 2}}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
 
 Expected success: `ViewTaskPreviewResult` in the standard JSON envelope; mutation `read`, confirmation `none`, wait policy `always_wait`. On nonzero exit, inspect the JSON error envelope and its `recovery_commands`; do not guess request fields. See [representative envelopes](../machine-output.md) for concrete success/error shapes.
 
@@ -652,7 +652,7 @@ Expected success: `ViewTaskPreviewResult` in the standard JSON envelope; mutatio
 
 Run: `mammoth view task update`. Exact input fields: `mammoth schema get view.task.update --output json --no-input`.
 
-Example: `mammoth view task update 123 123 --input '{"task_spec": {"DATAVIEW_ID": 123, "SEQUENCE_NUMBER": 1, "COPY": {}}, "dataset_id": 456}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
+Example: `mammoth view task update 123 123 --input '{"task_spec": {"DATAVIEW_ID": 123, "SEQUENCE_NUMBER": 1, "COPY": [{"SOURCE": "column_1", "AS": {"COLUMN": "Copy of column 1", "TYPE": "TEXT", "INTERNAL_NAME": "column_9"}}], "VERSION": 2}, "dataset_id": 456}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
 
 Expected success: `ViewTaskUpdateResult` in the standard JSON envelope; mutation `reversible_pipeline`, confirmation `none`, wait policy `always_wait`. On nonzero exit, inspect the JSON error envelope and its `recovery_commands`; do not guess request fields. See [representative envelopes](../machine-output.md) for concrete success/error shapes.
 

{mammoth_cli-2.0.15 → mammoth_cli-2.0.16}/mammoth_cli/bundled_skill/mammoth-cli/references/recipes/transforms.md

@@ -81,8 +81,12 @@ free-form lists. Observed shapes:
   `reorder`, `null` for commands). Prefer `view draft *` for submit/discard.
 - `view task update VIEW_ID TASK_ID --input '{"dataset_id":DATASET_ID,"task_spec":{...}}'`
   sends `{"patches":[{"op":"replace","path":"params","value":task_spec}]}`;
-  pass `patches` directly for other paths. `view task preview` needs the
-  task's internal column names (`view columns`), not display names.
+  pass `patches` directly for other paths. Raw `task_spec` bodies use the
+  backend param-template shape with internal column names, e.g. COPY is
+  `{"COPY":[{"SOURCE":"column_1","AS":{"COLUMN":"Copy","TYPE":"TEXT","INTERNAL_NAME":"column_9"}}],"VERSION":2,...}`;
+  prefer the typed `view transform *` commands, which build these for you.
+  `view task preview` currently fails on the backend for views with a DATE
+  column (`datetime is not JSON serializable`), so do not rely on it.
 - `view checkpoint update` sends `{"patches":[{"op":"command","path":"approve","value":null}]}`;
   the release backend answered HTTP 500 to that shape, so treat checkpoint
   approval as unavailable until `checkpoint get` succeeds again.

{mammoth_cli-2.0.15 → mammoth_cli-2.0.16}/mammoth_cli/commands/schema.py

@@ -452,8 +452,25 @@ def runnable_example(
         "view.task.update": ["mammoth", "view", "task", "update", "123", "123"],
     }
     if record["command_id"] in task_examples:
+        # COPY follows the backend param template (a list of SOURCE/AS items
+        # with VERSION 2); the former ``COPY: {}`` placeholder was rejected
+        # with backend code 720.
         task_input: dict[str, Any] = {
-            "task_spec": {"DATAVIEW_ID": 123, "SEQUENCE_NUMBER": 1, "COPY": {}}
+            "task_spec": {
+                "DATAVIEW_ID": 123,
+                "SEQUENCE_NUMBER": 1,
+                "COPY": [
+                    {
+                        "SOURCE": "column_1",
+                        "AS": {
+                            "COLUMN": "Copy of column 1",
+                            "TYPE": "TEXT",
+                            "INTERNAL_NAME": "column_9",
+                        },
+                    }
+                ],
+                "VERSION": 2,
+            }
         }
         if record["command_id"] == "view.task.update":
             task_input["dataset_id"] = 456

{mammoth_cli-2.0.15 → mammoth_cli-2.0.16}/mammoth_cli/commands/view.py

@@ -625,14 +625,27 @@ def view_conditional_format_create(invocation: Invocation) -> HandlerResult:
 
 
 def view_conditional_format_delete_all(invocation: Invocation) -> HandlerResult:
-    """Delete all conditional-format rules on a dataview. Prompt or ``--yes``."""
+    """Delete a conditional-format rule on a dataview. Prompt or ``--yes``.
+
+    The release route deletes one rule per call and requires ``rule_id`` as a
+    query parameter (``view conditional-format list`` shows the ids).
+    """
     project_id = require_project(invocation)
     dataview_id = _require_int_positional_at(invocation, 0, "view id")
     document = invocation.load_input() or {}
+    rule_id = document.get("rule_id")
+    if rule_id is None:
+        raise CliError(
+            code=CODE_MISSING_FIELD,
+            message="This command requires the 'rule_id' input field.",
+            exit_status=EXIT_USAGE,
+            hint="List rules with 'view conditional-format list VIEW_ID', then pass "
+            "--input '{\"rule_id\": ...}'.",
+        )
     enforce_confirmation(
         invocation,
         policy=POLICY_PROMPT_OR_YES,
-        action=f"delete all conditional-format rules on view {dataview_id}",
+        action=f"delete conditional-format rule {rule_id} on view {dataview_id}",
     )
     with open_service(invocation) as (service, auth):
         dataset_id = _resolve_dataset_id(service, invocation, dataview_id, document)
@@ -640,6 +653,7 @@ def view_conditional_format_delete_all(invocation: Invocation) -> HandlerResult:
             _symbol(invocation),
             dataset_id=dataset_id,
             dataview_id=dataview_id,
+            rule_id=rule_id,
             project_id=project_id,
         )
     return data, _meta(invocation, auth.workspace_id, project_id)

{mammoth_cli-2.0.15 → mammoth_cli-2.0.16}/mammoth_cli/services/input_fields.py

@@ -204,7 +204,18 @@ _EXAMPLE_INPUT_HINTS: dict[str, dict[str, Any]] = {
         "patches": [{"op": "replace", "path": "auto_run", "value": True}],
     },
     "view.export.publish-db-update": {
-        "patch": [{"op": "replace", "path": "credentials", "value": "postgres"}],
+        "patch": [{"op": "replace", "path": "credentials", "value": {"odbc_type": "postgres"}}],
+    },
+    # BatchesPostRequest: every ColumnNameMapping item carries the expected
+    # destination type; a bare {src: dst} map cannot satisfy the route.
+    "batch.create": {
+        "mapping": [
+            {
+                "source_c_name": "column_1",
+                "destination_c_name": "column_1",
+                "expected_destination_c_type": "TEXT",
+            }
+        ]
     },
     "view.checkpoint.update": {
         "body": {"patches": [{"op": "command", "path": "approve", "value": None}]},

{mammoth_cli-2.0.15 → mammoth_cli-2.0.16}/pyproject.toml

@@ -1,13 +1,13 @@
 [project]
 name = "mammoth-cli"
-version = "2.0.15"
+version = "2.0.16"
 description = "Command-line interface for the Mammoth Analytics platform"
 authors = [{name = "Mammoth Analytics", email = "support@mammoth.io"}]
 readme = "README.md"
 license = "LicenseRef-Proprietary"
 requires-python = ">=3.12,<3.15"
 dependencies = [
-    "mammoth-io (>=0.7.7,<0.8)",
+    "mammoth-io (>=0.7.8,<0.8)",
     "typer (>=0.27,<0.28)",
     "rich (>=15,<16)",
     "platformdirs (>=4.10,<5)",

{mammoth_cli-2.0.15 → mammoth_cli-2.0.16}/spec/manifests/commands/batch.yaml

@@ -75,8 +75,8 @@ commands:
   required_fixture_guard: null
   secret_fields: []
   human_example: mammoth batch create DATASET_ID SOURCE_ID --help
-  agent_example: 'mammoth batch create 123 123 --input ''{"mapping": {"sample_key": "Status"}}'' --output
-    json --no-input'
+  agent_example: 'mammoth batch create 123 123 --input ''{"mapping": [{"source_c_name": "column_1", "destination_c_name":
+    "column_1", "expected_destination_c_type": "TEXT"}]}'' --output json --no-input'
   unit_tests:
   - UT-BATCH-CREATE
   contract_tests:

{mammoth_cli-2.0.15 → mammoth_cli-2.0.16}/spec/manifests/commands/view.yaml

@@ -2499,7 +2499,7 @@ commands:
   secret_fields: []
   human_example: mammoth view export publish-db-update DATAVIEW_ID --help
   agent_example: 'mammoth view export publish-db-update 123 --input ''{"patch": [{"op": "replace", "path":
-    "credentials", "value": "postgres"}]}'' --output json --no-input'
+    "credentials", "value": {"odbc_type": "postgres"}}]}'' --output json --no-input'
   unit_tests:
   - UT-VIEW-EXPORT-PUBLISH-DB-UPDATE
   contract_tests:
@@ -3394,7 +3394,8 @@ commands:
   secret_fields: []
   human_example: mammoth view task add DATAVIEW_ID --help
   agent_example: 'mammoth view task add 123 --input ''{"task_spec": {"DATAVIEW_ID": 123, "SEQUENCE_NUMBER":
-    1, "COPY": {}}}'' --output json --no-input'
+    1, "COPY": [{"SOURCE": "column_1", "AS": {"COLUMN": "Copy of column 1", "TYPE": "TEXT", "INTERNAL_NAME":
+    "column_9"}}], "VERSION": 2}}'' --output json --no-input'
   unit_tests:
   - UT-VIEW-TASK-ADD
   contract_tests:
@@ -3569,7 +3570,8 @@ commands:
   secret_fields: []
   human_example: mammoth view task preview DATAVIEW_ID --help
   agent_example: 'mammoth view task preview 123 --input ''{"task_spec": {"DATAVIEW_ID": 123, "SEQUENCE_NUMBER":
-    1, "COPY": {}}}'' --output json --no-input'
+    1, "COPY": [{"SOURCE": "column_1", "AS": {"COLUMN": "Copy of column 1", "TYPE": "TEXT", "INTERNAL_NAME":
+    "column_9"}}], "VERSION": 2}}'' --output json --no-input'
   unit_tests:
   - UT-VIEW-TASK-PREVIEW
   contract_tests:
@@ -3616,7 +3618,8 @@ commands:
   secret_fields: []
   human_example: mammoth view task update DATAVIEW_ID TASK_ID --help
   agent_example: 'mammoth view task update 123 123 --input ''{"task_spec": {"DATAVIEW_ID": 123, "SEQUENCE_NUMBER":
-    1, "COPY": {}}, "dataset_id": 456}'' --output json --no-input'
+    1, "COPY": [{"SOURCE": "column_1", "AS": {"COLUMN": "Copy of column 1", "TYPE": "TEXT", "INTERNAL_NAME":
+    "column_9"}}], "VERSION": 2}, "dataset_id": 456}'' --output json --no-input'
   unit_tests:
   - UT-VIEW-TASK-UPDATE
   contract_tests:

{mammoth_cli-2.0.15 → mammoth_cli-2.0.16}/spec/manifests/sdk-methods.yaml

@@ -881,7 +881,7 @@ methods:
   reviewed_by: primary
 - sdk_symbol: mammoth.api.batches.BatchesAPI.create
   implementation_origin: mammoth.api.batches.BatchesAPI.create
-  signature: 'create(self, dataset_id: ''int'', source_id: ''int'', mapping: ''dict[str, str] | _list[dict[str, Any]]'', project_id: ''int | None'' = None, new_ds_params: ''dict[str, Any] | None'' = None, is_validation_required: ''bool | None'' = None, change_map: ''dict[str, Any] | None'' = None, delete_source_ds: ''bool'' = False) -> ''dict[str, Any]'''
+  signature: 'create(self, dataset_id: ''int'', source_id: ''int'', mapping: ''dict[str, str] | _list[dict[str, Any]]'', project_id: ''int | None'' = None, new_ds_params: ''dict[str, Any] | None'' = None, is_validation_required: ''bool | None'' = None, change_map: ''dict[str, Any] | None'' = None, delete_source_ds: ''bool'' = False, expected_destination_c_type: ''str'' = ''TEXT'') -> ''dict[str, Any]'''
   openapi_operation_ids: []
   canonical_command: batch.create
   alias_of: null