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

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

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: mammoth-cli
-Version: 2.0.13
+Version: 2.0.15
 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.5
+Requires-Dist: mammoth-io<0.8,>=0.7.7
 Requires-Dist: platformdirs<5,>=4.10
 Requires-Dist: pydantic<3,>=2.13
 Requires-Dist: pyyaml<7,>=6

{mammoth_cli-2.0.13 → mammoth_cli-2.0.15}/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.13"
+__version__ = "2.0.15"
 
 # The versioned machine output envelope contract.
 SCHEMA_VERSION = 1

{mammoth_cli-2.0.13 → mammoth_cli-2.0.15}/mammoth_cli/bundled_skill/mammoth-cli/SKILL.md

@@ -65,6 +65,9 @@ the result.
 - **Import, resources, transforms, pipelines, dashboards, exports, or cleanup:**
   [recipes](references/recipes/index.md) and [operations](references/operations.md)
 - **A known command family or exact command:** [command catalog](references/command-index.md)
+- **Whether a route is proven, known-blocked, or untried on release:**
+  [capabilities](references/capabilities.md) — read it before promising a
+  deliverable or reporting a failure as a backend fault
 - **Pause or transfer to another agent:** [handoff](references/handoff.md)
 
 ## Handoff checklist

mammoth_cli-2.0.15/mammoth_cli/bundled_skill/mammoth-cli/references/capabilities.md

@@ -0,0 +1,274 @@
+# 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.
+
+Status meanings:
+
+- **verified**: one bounded live run on release returned a success envelope (single path; variants and error paths are usually untested).
+- **not supported**: the backend refuses the route on release; the note says why and what to use instead.
+- **observed blocker**: the last run hit an error; the note quotes it. Re-check before relying on the route, and do not retry the same input.
+- **CLI defect fixed, untried since**: the failure was on the CLI side and this release repairs it; nobody has re-run the route yet.
+- Commands not listed under a family are untried.
+
+The typed `view transform *` commands all submit through `view.task.add`; its row below carries the transformations proven end to end (filter, fill-missing, join, pivot with an exported summary). A transformation not named there has the same untried status as any other command.
+
+## Coverage by family
+
+| 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 |
+| `connector` | 22 | 2 | 0 | 20 |
+| `workspace` | 19 | 6 | 0 | 13 |
+| `project` | 17 | 11 | 0 | 6 |
+| `workflow` | 16 | 5 | 0 | 11 |
+| `dataset` | 15 | 10 | 0 | 5 |
+| `parameter` | 14 | 2 | 0 | 12 |
+| `data-app` | 12 | 1 | 0 | 11 |
+| `folder` | 8 | 7 | 0 | 1 |
+| `snippet` | 8 | 1 | 0 | 7 |
+| `automation` | 7 | 1 | 0 | 6 |
+| `user` | 7 | 2 | 0 | 5 |
+| `webhook` | 7 | 0 | 0 | 7 |
+| `addon` | 6 | 0 | 0 | 6 |
+| `batch` | 6 | 4 | 0 | 2 |
+| `file` | 6 | 5 | 0 | 1 |
+| `agent` | 5 | 1 | 0 | 4 |
+| `ai` | 5 | 1 | 0 | 4 |
+| `annotation` | 5 | 1 | 0 | 4 |
+| `client-app` | 5 | 0 | 0 | 5 |
+| `notification` | 5 | 1 | 0 | 4 |
+| `schedule` | 5 | 0 | 0 | 5 |
+| `template` | 5 | 0 | 0 | 5 |
+| `browse` | 4 | 2 | 0 | 2 |
+| `external-key` | 4 | 0 | 0 | 4 |
+| `trash` | 3 | 3 | 0 | 0 |
+| `activity` | 2 | 1 | 0 | 1 |
+| `job` | 2 | 2 | 0 | 0 |
+| `report` | 1 | 1 | 0 | 0 |
+
+## `activity`
+
+Verified: `activity.list`
+
+| Command | State | Note |
+|---|---|---|
+| `activity.export` | observed blocker | server_error: see sweep report |
+
+## `agent`
+
+Verified: `agent.session.list`
+
+## `ai`
+
+Verified: `ai.condition.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)) |
+
+## `annotation`
+
+Verified: `annotation.list`
+
+## `automation`
+
+Verified: `automation.list`
+
+## `batch`
+
+Verified: `batch.bulk-delete`, `batch.delete`, `batch.get`, `batch.list`
+
+| 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) |
+
+## `browse`
+
+Verified: `browse.project`, `browse.workspace`
+
+| Command | State | Note |
+|---|---|---|
+| `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 |
+
+## `connector`
+
+Verified: `connector.active`, `connector.list`
+
+| Command | State | Note |
+|---|---|---|
+| `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.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`
+
+| Command | State | Note |
+|---|---|---|
+| `dashboard.create` | not supported | Not supported on release: backend returns HTTP 409 4DASH012 DASHBOARD_LEGACY_CREATION_RETIRED (legacy dashboard creation retired). Use dashboard.create-blank or dashboard.v3.generate. Dashboard sweep 2026-09-18, CLI 2.0.12. |
+| `dashboard.pdf.export` | not supported | Not supported from the CLI on release: backend HTTP 400 4GENR001 requires params.data to be the browser-hydrated DashboardData map and states it cannot rebuild it from stored descriptors (dashboard sweep and Haiku e2e, 2026-09-18). The route works only with a client render pass. |
+| `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.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.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`
+
+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`
+
+| 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) |
+
+## `external-key`
+
+| Command | State | Note |
+|---|---|---|
+| `external-key.list` | observed blocker | cli_error: not_authenticated although the same session authenticated elsewhere |
+
+## `file`
+
+Verified: `file.bulk-delete`, `file.delete`, `file.get`, `file.list`, `file.upload`
+
+| Command | State | Note |
+|---|---|---|
+| `file.update` | observed blocker | backend_error: CLI accepted the typed patch and submitted job 314 (handle_file on /workspaces/4/projects/21/files/50), then correctly reported timeout after 60s with recovery_comma |
+
+## `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}]}) |
+
+## `job`
+
+Verified: `job.get`, `job.get-many`
+
+## `notification`
+
+Verified: `notification.list`
+
+## `parameter`
+
+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`
+
+| 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`
+
+Verified: `report.list`
+
+## `schedule`
+
+| Command | State | Note |
+|---|---|---|
+| `schedule.list` | observed blocker | validation_error: HTTP 400 with message 'Not implemented' |
+
+## `snippet`
+
+Verified: `snippet.list`
+
+## `template`
+
+| Command | State | Note |
+|---|---|---|
+| `template.list` | observed blocker | cli_error: backend returned HTTP 200 but the CLI raised api_error (envelope mismatch) |
+
+## `trash`
+
+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) |
+
+## `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`
+
+| 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.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.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)) |
+
+## `webhook`
+
+| Command | State | Note |
+|---|---|---|
+| `webhook.list` | observed blocker | cli_error: api_error with no HTTP status recorded |
+
+## `workflow`
+
+Verified: `workflow.graph`, `workflow.list`, `workflow.workspace-datasets`, `workflow.workspace-exports`, `workflow.workspace-sources`
+
+## `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 |
+
+Evidence version: CLI mammoth-cli 1.1.11; mammoth-io 0.7.1. Details: `docs/capability-evidence/` in the repository.

{mammoth_cli-2.0.13 → mammoth_cli-2.0.15}/mammoth_cli/bundled_skill/mammoth-cli/references/commands/ai.md

@@ -28,7 +28,7 @@ Expected success: `AiRetentionConditionResult` in the standard JSON envelope; mu
 
 Run: `mammoth ai sql generate`. Exact input fields: `mammoth schema get ai.sql.generate --output json --no-input`.
 
-Example: `mammoth ai sql generate 'Summarize revenue by region' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
+Example: `mammoth ai sql generate 'Summarize revenue by region' --input '{"dataset_id": 456}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
 
 Expected success: `AiSqlGenerateResult` 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.
 
@@ -36,6 +36,6 @@ Expected success: `AiSqlGenerateResult` in the standard JSON envelope; mutation
 
 Run: `mammoth ai suggestion list`. Exact input fields: `mammoth schema get ai.suggestion.list --output json --no-input`.
 
-Example: `mammoth ai suggestion list --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
+Example: `mammoth ai suggestion list --input '{"suggestion_type": "generate_task", "params": {"prompt": "Filter rows where Price > 100"}, "dataset_id": 456, "dataview_id": 123}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
 
 Expected success: `AiSuggestionListResult` 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.

{mammoth_cli-2.0.13 → mammoth_cli-2.0.15}/mammoth_cli/bundled_skill/mammoth-cli/references/commands/connector.md

@@ -164,7 +164,7 @@ Expected success: `ConnectorListResult` in the standard JSON envelope; mutation
 
 Run: `mammoth connector query generate`. Exact input fields: `mammoth schema get connector.query.generate --output json --no-input`.
 
-Example: `mammoth connector query generate sample sample --input '{"prompt": "Summarize revenue by region"}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
+Example: `mammoth connector query generate sample sample --input '{"query": "Total sales for January"}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
 
 Expected success: `ConnectorQueryGenerateResult` 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.
 

{mammoth_cli-2.0.13 → mammoth_cli-2.0.15}/mammoth_cli/bundled_skill/mammoth-cli/references/commands/dashboard.md

@@ -148,7 +148,7 @@ Expected success: `DashboardCreateBlankResult` in the standard JSON envelope; mu
 
 Run: `mammoth dashboard data draft`. Exact input fields: `mammoth schema get dashboard.data.draft --output json --no-input`.
 
-Example: `mammoth dashboard data draft 123 --input '{"sql": "SELECT region, SUM(revenue) FROM data GROUP BY region"}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
+Example: `mammoth dashboard data draft 123 --input '{"widget_id": "550e8400-e29b-41d4-a716-446655440000"}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
 
 Expected success: `DashboardDataDraftResult` 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.
 
@@ -156,7 +156,7 @@ Expected success: `DashboardDataDraftResult` in the standard JSON envelope; muta
 
 Run: `mammoth dashboard data published`. Exact input fields: `mammoth schema get dashboard.data.published --output json --no-input`.
 
-Example: `mammoth dashboard data published 123 --input '{"sql": "SELECT region, SUM(revenue) FROM data GROUP BY region"}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
+Example: `mammoth dashboard data published 123 --input '{"widget_id": "550e8400-e29b-41d4-a716-446655440000"}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
 
 Expected success: `DashboardDataPublishedResult` 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.
 
@@ -460,7 +460,7 @@ Expected success: `DashboardQaSettingsSetResult` in the standard JSON envelope;
 
 Run: `mammoth dashboard query`. Exact input fields: `mammoth schema get dashboard.query --output json --no-input`.
 
-Example: `mammoth dashboard query 123 --input '{"body": {"params": {"descriptor": {}}}}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
+Example: `mammoth dashboard query 123 --input '{"body": {"params": {"descriptor": {"kind": "scalar", "agg": "count"}}}}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
 
 Expected success: `DashboardQueryResult` in the standard JSON envelope; mutation `benign_mutation`, confirmation `none`, 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.
 
@@ -788,7 +788,7 @@ Expected success: `DashboardTrashResult` in the standard JSON envelope; mutation
 
 Run: `mammoth dashboard update`. Exact input fields: `mammoth schema get dashboard.update --output json --no-input`.
 
-Example: `mammoth dashboard update 123 --input '{"patch": [{"op": "add", "path": "intent", "value": "sample"}]}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
+Example: `mammoth dashboard update 123 --input '{"patch": [{"op": "replace", "path": "title", "value": "Renamed dashboard"}]}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
 
 Expected success: `DashboardUpdateResult` 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.13 → mammoth_cli-2.0.15}/mammoth_cli/bundled_skill/mammoth-cli/references/commands/dataset.md

@@ -12,7 +12,7 @@ Expected success: `DatasetBatchDataResult` in the standard JSON envelope; mutati
 
 Run: `mammoth dataset bulk-delete`. Exact input fields: `mammoth schema get dataset.bulk-delete --output json --no-input`.
 
-Example: `mammoth dataset bulk-delete --output json --no-input`. Illustrative only: append `--yes` after observing an owned target.
+Example: `mammoth dataset bulk-delete --input '{"dataset_ids": [456, 457]}' --output json --no-input`. Illustrative only: append `--yes` after observing an owned target.
 
 Expected success: `DatasetBulkDeleteResult` in the standard JSON envelope; mutation `destructive`, confirmation `prompt_or_yes`, 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.
 

{mammoth_cli-2.0.13 → mammoth_cli-2.0.15}/mammoth_cli/bundled_skill/mammoth-cli/references/commands/folder.md

@@ -52,7 +52,7 @@ Expected success: `FolderListResult` in the standard JSON envelope; mutation `re
 
 Run: `mammoth folder move`. Exact input fields: `mammoth schema get folder.move --output json --no-input`.
 
-Example: `mammoth folder move --input '{"resource_ids": ["resource-123"]}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
+Example: `mammoth folder move --input '{"resource_ids": [8024], "target_folder_resource_id": "root"}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
 
 Expected success: `FolderMoveResult` 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.13 → mammoth_cli-2.0.15}/mammoth_cli/bundled_skill/mammoth-cli/references/commands/project.md

@@ -12,7 +12,7 @@ Expected success: `ProjectBulkDeleteResult` in the standard JSON envelope; mutat
 
 Run: `mammoth project bulk-update`. Exact input fields: `mammoth schema get project.bulk-update --output json --no-input`.
 
-Example: `mammoth project bulk-update --input '{"patch_data": {"sample_key": "Status"}}' --output json --no-input`. Illustrative only: append `--yes --confirm <EXACT_TARGET>` after observing the target.
+Example: `mammoth project bulk-update --input '{"patch_data": {"patches": [{"op": "add", "path": "role", "value": [{"project_id": 456, "user_roles": [{"user_id": 123, "role": "project_analyst"}]}]}]}}' --output json --no-input`. Illustrative only: append `--yes --confirm <EXACT_TARGET>` after observing the target.
 
 Expected success: `ProjectBulkUpdateResult` in the standard JSON envelope; mutation `high_impact`, confirmation `confirm_target`, 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.
 
@@ -116,7 +116,7 @@ Expected success: `ProjectSampleFlowResult` in the standard JSON envelope; mutat
 
 Run: `mammoth project update`. Exact input fields: `mammoth schema get project.update --output json --no-input`.
 
-Example: `mammoth project update 123 --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
+Example: `mammoth project update 123 --input '{"name": "Renamed project"}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
 
 Expected success: `ProjectUpdateResult` in the standard JSON envelope; mutation `benign_mutation`, confirmation `none`, 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.
 
@@ -124,7 +124,7 @@ Expected success: `ProjectUpdateResult` in the standard JSON envelope; mutation
 
 Run: `mammoth project user add`. Exact input fields: `mammoth schema get project.user.add --output json --no-input`.
 
-Example: `mammoth project user add 123 --input '{"user_ids": ["resource-123"]}' --output json --no-input`. Illustrative only: append `--yes --confirm <EXACT_TARGET>` after observing the target.
+Example: `mammoth project user add 123 --input '{"user_ids": [123], "role": "project_analyst"}' --output json --no-input`. Illustrative only: append `--yes --confirm <EXACT_TARGET>` after observing the target.
 
 Expected success: `ProjectUserAddResult` in the standard JSON envelope; mutation `high_impact`, confirmation `confirm_target`, 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.
 

{mammoth_cli-2.0.13 → mammoth_cli-2.0.15}/mammoth_cli/bundled_skill/mammoth-cli/references/commands/user.md

@@ -54,11 +54,9 @@ Expected success: `UserPreferenceGetResult` in the standard JSON envelope; mutat
 
 Run: `mammoth user preference update`. Exact input fields: `mammoth schema get user.preference.update --output json --no-input`.
 
-Example: `mammoth user preference update --output json --no-input`. Discovery only: this command is fail-closed and must not dispatch a request.
+Example: `mammoth user preference update --input '{"patch": [{"op": "replace", "path": "GLOBAL.PREFERENCES.TOP_TABS", "value": []}]}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
 
-Execution is unavailable for the current contract and returns `unsupported_contract`. Do not infer request fields or retry it; use only a separately typed alternative.
-
-Known restriction: BLOCKED[B17 VARIADIC_INPUT_UNTYPED]: **prefs is unconstrained; reserved, not registered.
+Expected success: `UserPreferenceUpdateResult` in the standard JSON envelope; mutation `benign_mutation`, confirmation `none`, 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.
 
 ### `user.update`
 

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

@@ -36,7 +36,7 @@ Expected success: `ViewAiGenerationInfoResult` in the standard JSON envelope; mu
 
 Run: `mammoth view ai profile`. Exact input fields: `mammoth schema get view.ai.profile --output json --no-input`.
 
-Example: `mammoth view ai profile 123 --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
+Example: `mammoth view ai profile 123 --input '{"dataset_id": 456, "action": "insights"}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
 
 Expected success: `ViewAiProfileResult` in the standard JSON envelope; mutation `benign_mutation`, 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.
 
@@ -84,7 +84,7 @@ Expected success: `ViewCheckpointListResult` in the standard JSON envelope; muta
 
 Run: `mammoth view checkpoint update`. Exact input fields: `mammoth schema get view.checkpoint.update --output json --no-input`.
 
-Example: `mammoth view checkpoint update 123 123 123 --input '{"body": {"patches": [{"op": "replace", "path": "approve"}]}}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
+Example: `mammoth view checkpoint update 123 123 123 --input '{"body": {"patches": [{"op": "command", "path": "approve", "value": null}]}}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
 
 Expected success: `ViewCheckpointUpdateResult` in the standard JSON envelope; mutation `benign_mutation`, confirmation `none`, 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.
 
@@ -92,17 +92,15 @@ Expected success: `ViewCheckpointUpdateResult` in the standard JSON envelope; mu
 
 Run: `mammoth view conditional-format create`. Exact input fields: `mammoth schema get view.conditional-format.create --output json --no-input`.
 
-Example: `mammoth view conditional-format create 123 123 --input '{"rule": {"sample_key": "Status"}}' --output json --no-input`. Discovery only: this command is fail-closed and must not dispatch a request.
+Example: `mammoth view conditional-format create 123 123 --input '{"rule": {"sample_key": "Status"}}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
 
-Execution is unavailable for the current contract and returns `unsupported_contract`. Do not infer request fields or retry it; use only a separately typed alternative.
-
-Known restriction: BLOCKED[B09 DATAVIEW_INPUT_UNTYPED]: rule is an arbitrary dictionary; reserved, not registered.
+Expected success: `ViewConditionalFormatCreateResult` in the standard JSON envelope; mutation `benign_mutation`, confirmation `none`, 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.
 
 ### `view.conditional-format.delete-all`
 
 Run: `mammoth view conditional-format delete-all`. Exact input fields: `mammoth schema get view.conditional-format.delete-all --output json --no-input`.
 
-Example: `mammoth view conditional-format delete-all 123 123 --output json --no-input`. Illustrative only: append `--yes` after observing an owned target.
+Example: `mammoth view conditional-format delete-all 123 123 --input '{"rule_id": "rule-1"}' --output json --no-input`. Illustrative only: append `--yes` after observing an owned target.
 
 Expected success: `ViewConditionalFormatDeleteAllResult` in the standard JSON envelope; mutation `destructive`, confirmation `prompt_or_yes`, 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.
 
@@ -448,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": [{"sample_key": "Status"}]}' --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": "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.
 
@@ -550,7 +548,7 @@ Expected success: `ViewParameterContextResult` in the standard JSON envelope; mu
 
 Run: `mammoth view pipeline edit`. Exact input fields: `mammoth schema get view.pipeline.edit --output json --no-input`.
 
-Example: `mammoth view pipeline edit 123 --input '{"patches": [{"sample_key": "Status"}]}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
+Example: `mammoth view pipeline edit 123 --input '{"patches": [{"op": "replace", "path": "auto_run", "value": true}]}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
 
 Expected success: `ViewPipelineEditResult` in the standard JSON envelope; mutation `benign_mutation`, 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/bundled_skill/mammoth-cli/references/recipes/dashboards.md

@@ -0,0 +1,73 @@
+# Dashboards
+
+Dashboard inputs are generated and release-dependent:
+
+```bash
+mammoth schema find "dashboard create" --output json --no-input
+mammoth schema find "dashboard source" --output json --no-input
+mammoth schema get dashboard.create-blank --output json --no-input
+mammoth dashboard create-blank --input INPUT_JSON --project PROJECT_ID --output json --no-input --yes
+mammoth dashboard get DASHBOARD_ID --output json --no-input
+mammoth dashboard source list --output json --no-input
+```
+
+Discover page/widget/publish routes and verify source binding, draft/published
+data and terminal jobs. Use only returned IDs and schema confirmation policy;
+do not invent dashboard JSON or opaque task specs.
+
+Expected create-blank input is currently typed as
+`{"params":{"dataview_id":VIEW_ID,"title":"TITLE"}}`; confirm with
+`schema get dashboard.create-blank` first. If the dashboard is requested as a
+deliverable, preserve the dashboard ID actually named in the returned `data`
+object and do not clean it up. Otherwise, classify it explicitly as
+temporary/intermediate before authorizing deletion. Then run:
+
+```bash
+mammoth dashboard get DASHBOARD_ID --output json --no-input
+mammoth dashboard source list --output json --no-input
+mammoth schema find "dashboard page" --output json --no-input
+mammoth schema find "dashboard" --output json --no-input
+```
+
+Page/widget schemas vary by release. Read each schema, use returned IDs, and
+verify dashboard source plus draft/published data after every mutation. A
+creation response alone is not proof of a usable published view.
+
+## Canvas, widget data and PDF
+
+Never save an invented canvas. Read it, change it, write it back:
+
+```bash
+mammoth dashboard canvas get DASHBOARD_ID --output json --no-input   # data.canvas incl. style_tokens
+mammoth dashboard canvas save DASHBOARD_ID --input '{"body":{"params":{"canvas":CANVAS_FROM_GET}}}' --output json --no-input
+```
+
+`canvas save` with `{"canvas": {}}` fails (`dataset` and other fields are
+required); the object returned by `canvas get` is the only known-good shape.
+Widget ids for `dashboard data draft` / `dashboard data published` come from
+that canvas: `--input '{"widget_id": "WIDGET_UUID"}'` (optional
+`global_filters` / `drilldown_filters` objects). `dashboard query` needs a
+descriptor with a `kind` (`scalar`, `group`, `rate`, `detail`, `options`,
+`range`); `{"kind":"scalar","agg":"count"}` is the smallest that runs.
+
+`dashboard pdf export` and `dashboard video export` cannot be completed from
+the CLI: the backend requires the browser-hydrated `DashboardData` map
+(pre-rendered widget results) in `params.data` and refuses to rebuild it. Report
+this as a known limitation instead of retrying with `{}`. `dashboard create`
+(legacy engine) is retired on release (HTTP 409 `4DASH012`); use
+`create-blank` or `v3 generate`.
+
+## Publishing and the url routes
+
+`dashboard share DASHBOARD_ID --input '{"type_of_auth":"public"}'` alone does
+not publish: `was_published` stays false until you also run
+`dashboard action DASHBOARD_ID --input '{"action":"publish-presentation"}'`.
+`share` returns `data: null`; read the url slug back with `dashboard get`.
+Only then do `dashboard published canvas URL`, `published data URL`,
+`job-by-url URL JOB_ID` and the other `/dashboards/url/...` routes answer;
+before that they return 404 `DASHBOARD_NOT_FOUND`. Legacy widget routes
+(`widget-data`, `widget-data-by-url`, `published-data-by-url`, `data draft`,
+`data published`) answer 409 `DASHBOARD_WRONG_ENGINE` on a v3 dashboard.
+`video export` needs a motion-story dashboard. Revert the share
+(`type_of_auth: "mammoth"`) before trashing a temporary dashboard.
+

{mammoth_cli-2.0.13 → mammoth_cli-2.0.15}/mammoth_cli/bundled_skill/mammoth-cli/references/recipes/exports.md

@@ -21,3 +21,12 @@ returns `job_id`, read it until terminal success before inspecting the artifact.
 If `schema get view.export.csv` rejects requested fields, preserve the
 structured error and discover another declared export route rather than using
 raw HTTP.
+
+## Generic export routes
+
+`view export csv` and the typed destination commands are the proven path. The
+generic `view export create` accepts a raw `export_spec`; for `handler_type`
+`csv_file` the release job failed with a bare `'destination'` key even when
+`target_properties.destination` was set, so do not use it for CSV. `view export
+publish-db-update` only rotates credentials: the body is
+`{"patch":[{"op":"replace","path":"credentials","value":"postgres"|"bigquery"}]}`.

{mammoth_cli-2.0.13 → mammoth_cli-2.0.15}/mammoth_cli/bundled_skill/mammoth-cli/references/recipes/resources.md

@@ -16,6 +16,10 @@ mammoth view list DATASET_ID --project PROJECT_ID --output json --no-input
 mammoth view get VIEW_ID --project PROJECT_ID --output json --no-input
 ```
 
+`file upload` takes the local path as its positional argument; there is no
+`--source`/`--file` option. `dataset delete` is asynchronous: re-read
+`dataset list` (the id disappears once the job completes) before reporting.
+
 Use display names from the exact view schema. For settings, folders and other
 families, use `schema find`/`schema get` first, then read back the exact parent
 and resource IDs. For example: