mammoth-cli 2.0.21__tar.gz → 2.0.22__tar.gz

{mammoth_cli-2.0.21 → mammoth_cli-2.0.22}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: mammoth-cli
-Version: 2.0.21
+Version: 2.0.22
 Summary: Command-line interface for the Mammoth Analytics platform
 Project-URL: homepage, https://mammoth.io
 Project-URL: repository, https://github.com/EdgeMetric/mammothsdk
@@ -199,21 +199,26 @@ putting credentials into the handoff.
 
 ## Give your coding agent the CLI playbook
 
-The shortest handover is a prompt. Fill `PROFILE`, `PROJECT NAME` and `TASK`
-and paste it into any agent with a bash tool; the long form is
+The shortest handover is a prompt. Fill `PROJECT NAME` and `TASK` and paste
+it into any agent with a bash tool; it installs the CLI, walks you through the
+one-time login, and works from the shipped skill. The long form is
 [docs/agent-prompt.md](https://github.com/EdgeMetric/mammothsdk/blob/main/mammoth-cli/docs/agent-prompt.md).
 
 ```text
 Use Mammoth Analytics only through the `mammoth` CLI in bash; run
-`export MAMMOTH_OUTPUT=json MAMMOTH_NO_INPUT=1` once. Install if missing:
-curl -fsSL https://raw.githubusercontent.com/EdgeMetric/mammothsdk/main/mammoth-cli/installers/mammoth-install.sh | bash
-Then `cat` the SKILL.md at `mammoth skill path` (data.canonical) and follow it.
-Run `mammoth auth status --profile PROFILE`; if it has no credentials, stop and
-tell me the exact `mammoth auth login` command to run in my own terminal, then
-wait — never ask for, read, or pass a key or secret yourself. Require `mammoth
-doctor` to pass. Work inside `mammoth project ensure 'PROJECT NAME'` unless I
-name a project; take ids only from reads; `schema get COMMAND_ID` before a new
-command; read results back before reporting.
+`export MAMMOTH_OUTPUT=json MAMMOTH_NO_INPUT=1` once. Onboard me first:
+1. If `mammoth --version` fails, install, then re-check (new shell if needed):
+   curl -fsSL https://raw.githubusercontent.com/EdgeMetric/mammothsdk/main/mammoth-cli/installers/mammoth-install.sh | bash
+2. Run `mammoth auth status`. If it shows no credentials, print exactly this
+   and wait until I say done: "In the Mammoth web app open account settings,
+   create an API key (key + secret) and note your workspace id, then run in
+   your own terminal: mammoth auth login" — never ask for, read, or pass a key
+   or secret yourself, and never run auth login.
+3. Require `mammoth doctor` to pass, then `cat` the SKILL.md at
+   `mammoth skill path` (data.canonical) and follow it.
+Work inside `mammoth project ensure 'PROJECT NAME'` unless I name a project;
+take ids only from reads; `schema get COMMAND_ID` before a new command; read
+results back before reporting.
 TASK: <what to achieve, and how you will know it is done>
 ```
 

{mammoth_cli-2.0.21 → mammoth_cli-2.0.22}/README.md

@@ -171,21 +171,26 @@ putting credentials into the handoff.
 
 ## Give your coding agent the CLI playbook
 
-The shortest handover is a prompt. Fill `PROFILE`, `PROJECT NAME` and `TASK`
-and paste it into any agent with a bash tool; the long form is
+The shortest handover is a prompt. Fill `PROJECT NAME` and `TASK` and paste
+it into any agent with a bash tool; it installs the CLI, walks you through the
+one-time login, and works from the shipped skill. The long form is
 [docs/agent-prompt.md](https://github.com/EdgeMetric/mammothsdk/blob/main/mammoth-cli/docs/agent-prompt.md).
 
 ```text
 Use Mammoth Analytics only through the `mammoth` CLI in bash; run
-`export MAMMOTH_OUTPUT=json MAMMOTH_NO_INPUT=1` once. Install if missing:
-curl -fsSL https://raw.githubusercontent.com/EdgeMetric/mammothsdk/main/mammoth-cli/installers/mammoth-install.sh | bash
-Then `cat` the SKILL.md at `mammoth skill path` (data.canonical) and follow it.
-Run `mammoth auth status --profile PROFILE`; if it has no credentials, stop and
-tell me the exact `mammoth auth login` command to run in my own terminal, then
-wait — never ask for, read, or pass a key or secret yourself. Require `mammoth
-doctor` to pass. Work inside `mammoth project ensure 'PROJECT NAME'` unless I
-name a project; take ids only from reads; `schema get COMMAND_ID` before a new
-command; read results back before reporting.
+`export MAMMOTH_OUTPUT=json MAMMOTH_NO_INPUT=1` once. Onboard me first:
+1. If `mammoth --version` fails, install, then re-check (new shell if needed):
+   curl -fsSL https://raw.githubusercontent.com/EdgeMetric/mammothsdk/main/mammoth-cli/installers/mammoth-install.sh | bash
+2. Run `mammoth auth status`. If it shows no credentials, print exactly this
+   and wait until I say done: "In the Mammoth web app open account settings,
+   create an API key (key + secret) and note your workspace id, then run in
+   your own terminal: mammoth auth login" — never ask for, read, or pass a key
+   or secret yourself, and never run auth login.
+3. Require `mammoth doctor` to pass, then `cat` the SKILL.md at
+   `mammoth skill path` (data.canonical) and follow it.
+Work inside `mammoth project ensure 'PROJECT NAME'` unless I name a project;
+take ids only from reads; `schema get COMMAND_ID` before a new command; read
+results back before reporting.
 TASK: <what to achieve, and how you will know it is done>
 ```
 

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

{mammoth_cli-2.0.21 → mammoth_cli-2.0.22}/mammoth_cli/bundled_skill/mammoth-cli/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: mammoth-cli
-version: 2.0.21
+version: 2.0.22
 description: "Use Mammoth Analytics from a terminal: install or authenticate the CLI, discover its live command contract, and safely manage projects, data, views, pipelines, dashboards, exports, and handoffs."
 ---
 

{mammoth_cli-2.0.21 → mammoth_cli-2.0.22}/mammoth_cli/bundled_skill/mammoth-cli/references/capabilities-misc.md

@@ -16,13 +16,12 @@ Ran once: `agent.session.list`
 
 ## `ai`
 
-Ran once: `ai.condition.generate`, `ai.expression.generate`
+Ran once: `ai.condition.generate`, `ai.expression.generate`, `ai.suggestion.list`
 
 | Command | State | Note |
 |---|---|---|
 | `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 |
+| `ai.sql.generate` | observed blocker | backend_error: 4DTVW029 conflict: 'Cannot run AI generation for this rule: the input table from the previous rule is not available' on a fresh dataset with no prior rule |
 
 ## `annotation`
 
@@ -39,11 +38,7 @@ Ran once: `automation.create`, `automation.delete`, `automation.list`
 
 ## `batch`
 
-Ran once: `batch.bulk-delete`, `batch.delete`, `batch.get`, `batch.list`, `batch.update`
-
-| Command | State | Note |
-|---|---|---|
-| `batch.create` | observed blocker | backend_error: SUSPECTED DEFECT (4th occurrence of this pattern in the sweep): retried with source_id=87 as an actual dataset id, got HTTP 500 empty body / outcome_unknown |
+Ran once: `batch.bulk-delete`, `batch.create`, `batch.delete`, `batch.get`, `batch.list`, `batch.update`
 
 ## `billing`
 
@@ -65,8 +60,8 @@ Ran once: `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.project` | observed blocker | backend_error: SUSPECTED DEFECT: GET /workspaces/4/projects/41/browse also 500s empty body, same pattern as browse.root, on our own fresh empty-of-folders project |
-| `browse.root` | observed blocker | backend_error: SUSPECTED DEFECT: GET /browse returns HTTP 500 empty body, reproduced twice |
+| `browse.project` | observed blocker | backend_error: GET /workspaces/4/projects/47/browse HTTP 500 empty body |
+| `browse.root` | observed blocker | backend_error: GET /browse still HTTP 500 empty body on release (same as 2026-09-18/19 sweeps) |
 
 ## `client-app`
 
@@ -111,7 +106,7 @@ Ran once: `report.list`
 |---|---|---|
 | `schedule.create` | observed blocker | backend_error: SUSPECTED CLI/BACKEND DEFECT: second create attempt (with work_items bound to dataset 85) returned HTTP 500 with empty response body, surfaced by CLI as code=outcome |
 | `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: Re-confirms 5GENR011 NOT_IMPLEMENTED from family 3 |
+| `schedule.list` | observed blocker | backend_error: 5GENR011 NOT_IMPLEMENTED on GET /workspaces/4/projects/47/schedules; schedules remain unimplemented on release |
 
 ## `snippet`
 
@@ -145,4 +140,4 @@ Ran once: `workflow.create`, `workflow.delete`, `workflow.get`, `workflow.graph`
 
 Ran once: `workspace.app-usage`, `workspace.get`, `workspace.list`, `workspace.segment.list`, `workspace.segment.update`, `workspace.storage-breakdown`, `workspace.user.list`
 
-Evidence collected on CLI releases 1.1.5 through 2.0.18; each row's release is recorded in `docs/release-capability-matrix.json` (`evidence_version`). A row that ran on an older release has not been re-run since unless its note says so. Details: `docs/capability-evidence/` in the repository.
+Evidence collected on CLI releases 1.1.5 through 2.0.21; each row's release is recorded in `docs/release-capability-matrix.json` (`evidence_version`). A row that ran on an older release has not been re-run since unless its note says so. Details: `docs/capability-evidence/` in the repository.

{mammoth_cli-2.0.21 → mammoth_cli-2.0.22}/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.
-The CLI publishes 552 commands. 455 of them bind one of the 528 API operations in the matrix; the remainder are local commands (`schema`, `auth`, `doctor`, `log`, ...) or typed variants that share an operation (every `view transform *` command submits through `view.task.add`). 258 bound commands ran once 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`, run it, and treat the structured error envelope as the answer.
+The CLI publishes 552 commands. 455 of them bind one of the 528 API operations in the matrix; the remainder are local commands (`schema`, `auth`, `doctor`, `log`, ...) or typed variants that share an operation (every `view transform *` command submits through `view.task.add`). 260 bound commands ran once 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`, run it, and treat the structured error envelope as the answer.
 
 Status meanings:
 
@@ -34,10 +34,10 @@ The typed `view transform *` commands all submit through `view.task.add`; its ma
 | `user` | 7 | 3 | 0 | 4 |
 | `webhook` | 7 | 5 | 0 | 2 |
 | `addon` | 6 | 0 | 0 | 6 |
-| `batch` | 6 | 5 | 0 | 1 |
+| `batch` | 6 | 6 | 0 | 0 |
 | `file` | 6 | 5 | 0 | 1 |
 | `agent` | 5 | 1 | 0 | 4 |
-| `ai` | 5 | 2 | 0 | 3 |
+| `ai` | 5 | 3 | 0 | 2 |
 | `annotation` | 5 | 1 | 0 | 4 |
 | `client-app` | 5 | 0 | 0 | 5 |
 | `notification` | 5 | 1 | 0 | 4 |
@@ -68,7 +68,7 @@ Ran once: `dashboard.action`, `dashboard.analytics`, `dashboard.archive`, `dashb
 | `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: POST /dashboards/v3/templates -> HTTP 500, empty response_body, request_id:null, code:outcome_unknown |
+| `dashboard.template.create` | observed blocker | backend_error: POST /dashboards/v3/templates HTTP 500 empty body / outcome_unknown, as on 2026-09-18 |
 | `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 |
@@ -115,9 +115,9 @@ Ran once: `view.active-user.list`, `view.active-user.mark`, `view.ai.generate-da
 | Command | State | Note |
 |---|---|---|
 | `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.data-check.update` | observed blocker | backend_error: SUSPECTED DEFECT: PATCH returned HTTP 500 empty body / CLI code=outcome_unknown, but a follow-up get confirmed the mutation actually applied (enabled:false, updated_ |
+| `view.data-check.update` | observed blocker | backend_error: PATCH with the schema's documented {op: command, path: enable/disable, value: null} shape returns HTTP 500 empty body (CLI outcome_unknown, exit 7) while the mutatio |
 | `view.derivative.data` | observed blocker | backend_error: SUSPECTED DEFECT: using the CLI's own documented agent_example body verbatim, derivative data fetch returns HTTP 500 empty body / outcome_unknown, reproduced twice ( |
 | `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.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)) |
 
-Evidence collected on CLI releases 1.1.5 through 2.0.18; each row's release is recorded in `docs/release-capability-matrix.json` (`evidence_version`). A row that ran on an older release has not been re-run since unless its note says so. Details: `docs/capability-evidence/` in the repository.
+Evidence collected on CLI releases 1.1.5 through 2.0.21; each row's release is recorded in `docs/release-capability-matrix.json` (`evidence_version`). A row that ran on an older release has not been re-run since unless its note says so. Details: `docs/capability-evidence/` in the repository.

{mammoth_cli-2.0.21 → mammoth_cli-2.0.22}/mammoth_cli/bundled_skill/mammoth-cli/references/commands/ai.md

@@ -40,7 +40,7 @@ Example: `mammoth ai sql generate 'Summarize revenue by region' --input '{"datas
 
 Result: `AiSqlGenerateResult`; mutation `read`, confirmation `none`, wait policy `always_wait`.
 
-Status on release: 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). Re-check before relying on it.
+Status on release: observed blocker — backend_error: 4DTVW029 conflict: 'Cannot run AI generation for this rule: the input table from the previous rule is not available' on a fresh dataset with no prior rule. Re-check before relying on it.
 
 ### `ai.suggestion.list`
 
@@ -50,4 +50,4 @@ Example: `mammoth ai suggestion list --input '{"suggestion_type": "generate_task
 
 Result: `AiSuggestionListResult`; mutation `read`, confirmation `none`, wait policy `always_wait`.
 
-Status on release: 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. Re-check before relying on it.
+Status on release: ran once on CLI 2.0.21 — ergonomics sweep 2026-09-19: exit 0 on release with CLI 2.0.21. Returned a pipeline suggestion (interpretation echoed, params with prev_metadata) — the 2.0.15 re-verification's backend job failure did not recur. Single invocation only.

{mammoth_cli-2.0.21 → mammoth_cli-2.0.22}/mammoth_cli/bundled_skill/mammoth-cli/references/commands/automation.md

@@ -40,7 +40,7 @@ Example: `mammoth automation list`. Placeholders are illustrative; resolve IDs a
 
 Result: `AutomationListResult`; mutation `read`, confirmation `none`, wait policy `not_async`.
 
-Status on release: ran once on CLI 2.0.18 — fixture-lifecycle sweep 2026-09-19: exit 0 on release with CLI 2.0.18. Empty result on this fixture. Empty (consistent with family 4's observation that create automations never surface in list). Single invocation only.
+Status on release: ran once on CLI 2.0.21 — ergonomics sweep 2026-09-19: exit 0 on release with CLI 2.0.21. Empty result on this fixture. Empty list in a fresh project. Single invocation only.
 
 ### `automation.restore`
 

{mammoth_cli-2.0.21 → mammoth_cli-2.0.22}/mammoth_cli/bundled_skill/mammoth-cli/references/commands/batch.md

@@ -20,7 +20,7 @@ Example: `mammoth batch create 123 123 --input '{"mapping": [{"source_c_name": "
 
 Result: `BatchCreateResult`; mutation `benign_mutation`, confirmation `none`, wait policy `returns_job`.
 
-Status on release: observed blocker — backend_error: SUSPECTED DEFECT (4th occurrence of this pattern in the sweep): retried with source_id=87 as an actual dataset id, got HTTP 500 empty body / outcome_unknown. Re-check before relying on it.
+Status on release: ran once on CLI 2.0.21 — ergonomics sweep 2026-09-19: exit 0 on release with CLI 2.0.21. Accepted as job 688 (validate_append) when SOURCE_ID is a standalone dataset (96) in the same project; using the append child dataset 95 as source is 4BATC010 INVALID_SOURCE_DATASET. Job 688 was…
 
 ### `batch.create-spec`
 
@@ -60,7 +60,7 @@ Example: `mammoth batch list 123`. Placeholders are illustrative; resolve IDs an
 
 Result: `BatchListResult`; mutation `read`, confirmation `none`, wait policy `not_async`.
 
-Status on release: ran once on CLI 2.0.18 — fixture-lifecycle sweep 2026-09-19: exit 0 on release with CLI 2.0.18. Listed the auto-created batch (id=90) from the original file upload; confirmed the failed batch.create above did not add a second batch. Single invocation only.
+Status on release: ran once on CLI 2.0.21 — ergonomics sweep 2026-09-19: exit 0 on release with CLI 2.0.21. active_batches 2: file batch 99 (3 rows) and combine_ds batch 101 from the append (3 rows). Single invocation only.
 
 ### `batch.update`
 

{mammoth_cli-2.0.21 → mammoth_cli-2.0.22}/mammoth_cli/bundled_skill/mammoth-cli/references/commands/browse.md

@@ -20,7 +20,7 @@ Example: `mammoth browse project`. Placeholders are illustrative; resolve IDs an
 
 Result: `BrowseProjectResult`; mutation `read`, confirmation `none`, wait policy `not_async`.
 
-Status on release: observed blocker — backend_error: SUSPECTED DEFECT: GET /workspaces/4/projects/41/browse also 500s empty body, same pattern as browse.root, on our own fresh empty-of-folders project. Re-check before relying on it.
+Status on release: observed blocker — backend_error: GET /workspaces/4/projects/47/browse HTTP 500 empty body. Re-check before relying on it.
 
 ### `browse.root`
 
@@ -30,7 +30,7 @@ Example: `mammoth browse root`. Placeholders are illustrative; resolve IDs and i
 
 Result: `BrowseRootResult`; mutation `read`, confirmation `none`, wait policy `not_async`.
 
-Status on release: observed blocker — backend_error: SUSPECTED DEFECT: GET /browse returns HTTP 500 empty body, reproduced twice. Re-check before relying on it.
+Status on release: observed blocker — backend_error: GET /browse still HTTP 500 empty body on release (same as 2026-09-18/19 sweeps). Re-check before relying on it.
 
 ### `browse.workspace`
 

{mammoth_cli-2.0.21 → mammoth_cli-2.0.22}/mammoth_cli/bundled_skill/mammoth-cli/references/commands/dashboard.md

@@ -178,7 +178,7 @@ Example: `mammoth dashboard create-blank --input '{"params": {"dataview_id": 1}}
 
 Result: `DashboardCreateBlankResult`; mutation `benign_mutation`, confirmation `none`, wait policy `not_async`.
 
-Status on release: ran once on CLI 2.0.12 — Dashboard sweep 2026-09-18: exit 0 on release with CLI 2.0.12; result keys: id, sequence. created dashboard D=52 from dataview 45 Single invocation only; no error-path or variant coverage. Also exercised successfully in the Haiku e2e run 2026-09-18 (CLI 2.0.1…
+Status on release: ran once on CLI 2.0.21 — ergonomics sweep 2026-09-19: exit 0 on release with CLI 2.0.21. Created dashboard 62 (sequence 1). Single invocation only.
 
 ### `dashboard.data.draft`
 
@@ -208,7 +208,7 @@ Example: `mammoth dashboard delete 123`. Illustrative only: append `--yes` after
 
 Result: `DashboardDeleteResult`; mutation `destructive`, confirmation `prompt_or_yes`, wait policy `not_async`.
 
-Status on release: ran once on CLI 2.0.12 — Dashboard sweep 2026-09-18: exit 0 on release with CLI 2.0.12; result keys: n/a. permanently deleted D2=54 Single invocation only; no error-path or variant coverage. Also exercised successfully in the Haiku e2e run 2026-09-18 (CLI 2.0.13, see docs/capability-…
+Status on release: ran once on CLI 2.0.21 — ergonomics sweep 2026-09-19: exit 0 on release with CLI 2.0.21. Deleted dashboard 62. Single invocation only.
 
 ### `dashboard.descriptor-data`
 
@@ -876,7 +876,7 @@ Example: `mammoth dashboard template create --input '{"body": {"params": {"dashb
 
 Result: `DashboardTemplateCreateResult`; mutation `benign_mutation`, confirmation `none`, wait policy `not_async`.
 
-Status on release: observed blocker — backend: POST /dashboards/v3/templates -> HTTP 500, empty response_body, request_id:null, code:outcome_unknown. Re-check before relying on it.
+Status on release: observed blocker — backend_error: POST /dashboards/v3/templates HTTP 500 empty body / outcome_unknown, as on 2026-09-18. Re-check before relying on it.
 
 ### `dashboard.template.delete`
 
@@ -916,7 +916,7 @@ Example: `mammoth dashboard template list`. Placeholders are illustrative; resol
 
 Result: `DashboardTemplateListResult`; mutation `read`, confirmation `none`, wait policy `not_async`.
 
-Status on release: ran once on CLI 2.0.12 — Bounded release read with published CLI 1.1.10 succeeded for the curated template catalog; schema_version 1 and five top-level collections observed. No Full claim: catalog content/fixture lifecycle not qualified. Also: Dashboard sweep 2026-09-18: exit 0 on re…
+Status on release: ran once on CLI 2.0.21 — ergonomics sweep 2026-09-19: exit 0 on release with CLI 2.0.21. Returned the template catalogue (formats, functions, ...). Single invocation only.
 
 ### `dashboard.template.preview`
 

{mammoth_cli-2.0.21 → mammoth_cli-2.0.22}/mammoth_cli/bundled_skill/mammoth-cli/references/commands/file.md

@@ -82,7 +82,7 @@ Example: `mammoth file upload ./sales.csv`. Placeholders are illustrative; resol
 
 Result: `FileUploadResult`; mutation `benign_mutation`, confirmation `none`, wait policy `start_or_wait`.
 
-Status on release: ran once on CLI 2.0.18 — golden-data check 2026-09-19 (CLI 2.0.18): two small CSVs (numeric, text and date columns) uploaded to an owned project, both reported ready with a view; the fixture sweep the same day uploaded two more (one landed in need_action and was used as a batch sourc…
+Status on release: ran once on CLI 2.0.21 — ergonomics sweep 2026-09-19: exit 0 on release with CLI 2.0.21. Uploaded smoke.csv -> dataset 94 ready; dataview 116 (3 rows). Second call with --input {"append_to_ds_id": 94} returned dataset 95 ready and view 116 row_count went 3 -> 6: append path works (th…
 
 ### `file.upload-folder`
 

{mammoth_cli-2.0.21 → mammoth_cli-2.0.22}/mammoth_cli/bundled_skill/mammoth-cli/references/commands/parameter.md

@@ -6,11 +6,11 @@ Every command returns the standard JSON envelope. On nonzero exit, read the erro
 
 Run: `mammoth parameter create`. Exact input fields: `mammoth schema get parameter.create`.
 
-Example: `mammoth parameter create 'Revenue report' --input '{"param_type": "sample", "value": "sample"}'`. Placeholders are illustrative; resolve IDs and input from observed reads.
+Example: `mammoth parameter create 'Revenue report' --input '{"param_type": "TEXT", "value": "Q3"}'`. Placeholders are illustrative; resolve IDs and input from observed reads.
 
 Result: `ParameterCreateResult`; mutation `benign_mutation`, confirmation `none`, wait policy `not_async`.
 
-Status on release: ran once on CLI 2.0.18 — fixture-lifecycle sweep 2026-09-19: exit 0 on release with CLI 2.0.18. First attempt with lowercase param_type 'text' failed 4PARM008 (must be NUMERIC/TEXT/DATE, uppercase; schema example is misleadingly lowercase). Retried with TEXT, created id=1. Single inv…
+Status on release: ran once on CLI 2.0.21 — ergonomics sweep 2026-09-19: exit 0 on release with CLI 2.0.21. Created parameter id=2 scope project. The shipped agent_example (param_type "sample") is rejected by the backend with 4PARM008 (must be NUMERIC/TEXT/DATE); example corrected in 2.0.22. Single inv…
 
 ### `parameter.delete`
 
@@ -20,7 +20,7 @@ Example: `mammoth parameter delete 123`. Illustrative only: append `--yes` after
 
 Result: `ParameterDeleteResult`; mutation `destructive`, confirmation `prompt_or_yes`, wait policy `not_async`.
 
-Status on release: ran once on CLI 2.0.18 — fixture-lifecycle sweep 2026-09-19: exit 0 on release with CLI 2.0.18. Deleted parameter 1; read-back list shows total_count=0. Single invocation only.
+Status on release: ran once on CLI 2.0.21 — ergonomics sweep 2026-09-19: exit 0 on release with CLI 2.0.21. Deleted; list read-back total_count 0. Single invocation only.
 
 ### `parameter.dependencies`
 
@@ -110,7 +110,7 @@ Example: `mammoth parameter list`. Placeholders are illustrative; resolve IDs an
 
 Result: `ParameterListResult`; mutation `read`, confirmation `none`, wait policy `not_async`.
 
-Status on release: ran once on CLI 2.0.18 — fixture-lifecycle sweep 2026-09-19: exit 0 on release with CLI 2.0.18. Empty result on this fixture. Empty after family 8 cleanup, as expected. Single invocation only.
+Status on release: ran once on CLI 2.0.21 — ergonomics sweep 2026-09-19: exit 0 on release with CLI 2.0.21. total_count 1 with id 2; 0 after delete. Single invocation only.
 
 ### `parameter.rerun`
 

{mammoth_cli-2.0.21 → mammoth_cli-2.0.22}/mammoth_cli/bundled_skill/mammoth-cli/references/commands/project.md

@@ -60,7 +60,7 @@ Example: `mammoth project delete 123`. Illustrative only: append `--yes --confir
 
 Result: `ProjectDeleteResult`; mutation `high_impact`, confirmation `confirm_target`, wait policy `not_async`.
 
-Status on release: ran once on CLI 2.0.18 — fixture-lifecycle sweep 2026-09-19: exit 0 on release with CLI 2.0.18. Deleted project 41 (sweep-218-1224), read back with project get 41 beforehand. Single invocation only.
+Status on release: ran once on CLI 2.0.21 — ergonomics sweep 2026-09-19: exit 0 on release with CLI 2.0.21. 202 accepted; smoke projects 44/45/46 deleted the same way earlier and project get on them then returned resource_not_found (2.0.21 fix; was api_error/ValueError). Single invocation only.
 
 ### `project.ensure`
 

{mammoth_cli-2.0.21 → mammoth_cli-2.0.22}/mammoth_cli/bundled_skill/mammoth-cli/references/commands/schedule.md

@@ -40,7 +40,7 @@ Example: `mammoth schedule list`. Placeholders are illustrative; resolve IDs and
 
 Result: `ScheduleListResult`; mutation `read`, confirmation `none`, wait policy `not_async`.
 
-Status on release: observed blocker — backend_error: Re-confirms 5GENR011 NOT_IMPLEMENTED from family 3. Re-check before relying on it.
+Status on release: observed blocker — backend_error: 5GENR011 NOT_IMPLEMENTED on GET /workspaces/4/projects/47/schedules; schedules remain unimplemented on release. Re-check before relying on it.
 
 ### `schedule.update`
 

{mammoth_cli-2.0.21 → mammoth_cli-2.0.22}/mammoth_cli/bundled_skill/mammoth-cli/references/commands/view.md

@@ -166,11 +166,11 @@ Status on release: ran once on CLI 2.0.18 — golden-data check 2026-09-19 (CLI
 
 Run: `mammoth view data-check create`. Exact input fields: `mammoth schema get view.data-check.create`.
 
-Example: `mammoth view data-check create 123 123 --input '{"body": {"checks": [{"check_type": "null_percentage", "config": {"column": "Status", "condition": "lt"}}], "name": "Revenue report"}}'`. Placeholders are illustrative; resolve IDs and input from observed reads.
+Example: `mammoth view data-check create 123 123 --input '{"body": {"checks": [{"check_type": "null_percentage", "config": {"column": "Status", "condition": "lt"}}], "name": "Revenue report", "pinned_to_end": true}}'`. Placeholders are illustrative; resolve IDs and input from observed reads.
 
 Result: `ViewDataCheckCreateResult`; mutation `benign_mutation`, confirmation `none`, wait policy `not_async`.
 
-Status on release: ran once on CLI 2.0.18 — fixture-lifecycle sweep 2026-09-19: exit 0 on release with CLI 2.0.18. SUSPECTED DEFECT: passing an explicit threshold:5.0 (a float, matching the schema's documented oneOf[number,integer,...] and default) caused invalid_input_field_type on body.checks.0. Omit…
+Status on release: ran once on CLI 2.0.21 — ergonomics sweep 2026-09-19: exit 0 on release with CLI 2.0.21. Created data_check_id 5. Without pinned_to_end the backend rejects the body with 4GENR007 'Either task_sequence or pinned_to_end must be set' (the shipped example lacked it; corrected in 2.0.22).…
 
 ### `view.data-check.delete`
 
@@ -190,7 +190,7 @@ Example: `mammoth view data-check get 123 123 123`. Placeholders are illustrativ
 
 Result: `ViewDataCheckGetResult`; mutation `read`, confirmation `none`, wait policy `not_async`.
 
-Status on release: ran once on CLI 2.0.18 — fixture-lifecycle sweep 2026-09-19: exit 0 on release with CLI 2.0.18. Fetched data check 4, threshold shows as 0 (the applied default). Single invocation only.
+Status on release: ran once on CLI 2.0.21 — ergonomics sweep 2026-09-19: exit 0 on release with CLI 2.0.21. Read back after each patch: enabled true, then false. Single invocation only.
 
 ### `view.data-check.list`
 
@@ -200,17 +200,17 @@ Example: `mammoth view data-check list 123 123`. Placeholders are illustrative;
 
 Result: `ViewDataCheckListResult`; mutation `read`, confirmation `none`, wait policy `not_async`.
 
-Status on release: ran once on CLI 1.1.11 — Published PyPI CLI 1.1.11 / SDK 0.7.1 exact-parent retained view 46/dataset 29 read succeeded with an empty data-check list. One view and single-page boundary; not Full.
+Status on release: ran once on CLI 2.0.21 — ergonomics sweep 2026-09-19: exit 0 on release with CLI 2.0.21. Listed data check 5 (enabled true, pinned_to_end true). Single invocation only.
 
 ### `view.data-check.update`
 
 Run: `mammoth view data-check update`. Exact input fields: `mammoth schema get view.data-check.update`.
 
-Example: `mammoth view data-check update 123 123 123 --input '{"body": {"patches": [{"op": "replace", "path": "enable"}]}}'`. Placeholders are illustrative; resolve IDs and input from observed reads.
+Example: `mammoth view data-check update 123 123 123 --input '{"body": {"patches": [{"op": "command", "path": "disable", "value": null}]}}'`. Placeholders are illustrative; resolve IDs and input from observed reads.
 
 Result: `ViewDataCheckUpdateResult`; mutation `benign_mutation`, confirmation `none`, wait policy `not_async`.
 
-Status on release: observed blocker — backend_error: SUSPECTED DEFECT: PATCH returned HTTP 500 empty body / CLI code=outcome_unknown, but a follow-up get confirmed the mutation actually applied (enabled:false, updated_. Re-check before relying on it.
+Status on release: observed blocker — backend_error: PATCH with the schema's documented {op: command, path: enable|disable, value: null} shape returns HTTP 500 empty body (CLI outcome_unknown, exit 7) while the mutatio. Re-check before relying on it.
 
 ### `view.data.get`
 
@@ -220,7 +220,7 @@ Example: `mammoth view data get 123 123`. Placeholders are illustrative; resolve
 
 Result: `ViewDataGetResult`; mutation `read`, confirmation `none`, wait policy `always_wait`.
 
-Status on release: ran once on CLI 2.0.18 — golden-data check 2026-09-19 (CLI 2.0.18): read back after every transform in the run (11 reads on release, rows compared by value with the fixture's known answer: amounts, statuses, ids, joined region, pivot totals). Full page only; paging not exercised.
+Status on release: ran once on CLI 2.0.21 — ergonomics sweep 2026-09-19: exit 0 on release with CLI 2.0.21. Default trim: rows_returned 3, rows_total_in_page 3, truncated false; with limit 2: rows_returned 2, truncated true. Single invocation only.
 
 ### `view.data.query`
 
@@ -250,7 +250,7 @@ Example: `mammoth view derivative create 123 123 --input '{"body": {"param": {"M
 
 Result: `ViewDerivativeCreateResult`; mutation `benign_mutation`, confirmation `none`, wait policy `not_async`.
 
-Status on release: ran once on CLI 2.0.18 — fixture-lifecycle sweep 2026-09-19: exit 0 on release with CLI 2.0.18. Created a SUM(amount) metric derivative on view 106, id=5 (my own first attempt keyed the param dict by the metric name instead of the required literal 'METRIC' key - that was my error, no…
+Status on release: ran once on CLI 2.0.21 — Partial bounded evidence only (earlier run); ergonomics sweep 2026-09-19 (CLI 2.0.21) observed backend_error: POST .../derivatives with the example shape (METRIC object) returns HTTP 500 empty body / outcome_unknown on release today. A list under METRIC is re…
 
 ### `view.derivative.data`
 
@@ -652,7 +652,7 @@ Example: `mammoth view get 123 123`. Placeholders are illustrative; resolve IDs
 
 Result: `ViewGetResult`; mutation `read`, confirmation `none`, wait policy `not_async`.
 
-Status on release: ran once on CLI 1.1.11 — Published PyPI CLI 1.1.11 correct-parent read resolves retained view46 under dataset29. The earlier dataset28 403 remains an invalid-parent control, not an authorization boundary; bounded to one view and not Full.
+Status on release: ran once on CLI 2.0.21 — ergonomics sweep 2026-09-19: exit 0 on release with CLI 2.0.21. Read back without a dataset id (parent from cache). row_count 6 after the append. Single invocation only.
 
 ### `view.list`
 
@@ -662,7 +662,7 @@ Example: `mammoth view list 123`. Placeholders are illustrative; resolve IDs and
 
 Result: `ViewListResult`; mutation `read`, confirmation `none`, wait policy `not_async`.
 
-Status on release: ran once on CLI 2.0.18 — fixture-lifecycle sweep 2026-09-19: exit 0 on release with CLI 2.0.18. Listed 1 dataview: id=106, ds_id=85, status=ready, row_count=3. Note: response includes a 'next' pagination URL (offset=100) despite only 1 total item, possibly a minor pagination defect.…
+Status on release: ran once on CLI 2.0.21 — ergonomics sweep 2026-09-19: exit 0 on release with CLI 2.0.21. Listed dataview 116 (ds_id 94, row_count 3); the parent cache picked up 116 -> 94 so later view commands took the view id alone. Single invocation only.
 
 ### `view.parameter-context`
 

{mammoth_cli-2.0.21 → mammoth_cli-2.0.22}/mammoth_cli/services/input_fields.py

@@ -251,6 +251,26 @@ _EXAMPLE_INPUT_HINTS: dict[str, dict[str, Any]] = {
     "view.checkpoint.update": {
         "body": {"patches": [{"op": "command", "path": "approve", "value": None}]},
     },
+    # Same placement rule as checkpoints ("Either task_sequence or
+    # pinned_to_end must be set").
+    "view.data-check.create": {
+        "body": {
+            "checks": [
+                {
+                    "check_type": "null_percentage",
+                    "config": {"column": "Status", "condition": "lt"},
+                }
+            ],
+            "name": "Revenue report",
+            "pinned_to_end": True,
+        },
+    },
+    # ``value`` is an AddDataCheckSpec or null; enable/disable take null.
+    "view.data-check.update": {
+        "body": {"patches": [{"op": "command", "path": "disable", "value": None}]},
+    },
+    # The backend accepts NUMERIC, TEXT or DATE (4PARM008 otherwise).
+    "parameter.create": {"param_type": "TEXT", "value": "Q3"},
     # The backend requires a placement ("Data check position must be given");
     # ``pinned_to_end`` is the placement that needs no sequence number.
     "view.checkpoint.create": {

{mammoth_cli-2.0.21 → mammoth_cli-2.0.22}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "mammoth-cli"
-version = "2.0.21"
+version = "2.0.22"
 description = "Command-line interface for the Mammoth Analytics platform"
 authors = [{name = "Mammoth Analytics", email = "support@mammoth.io"}]
 readme = "README.md"

{mammoth_cli-2.0.21 → mammoth_cli-2.0.22}/spec/manifests/commands/batch.yaml

@@ -85,7 +85,7 @@ commands:
   - CT-BATCH-CREATE-ERROR
   draft_test: null
   undo_test: null
-  known_restrictions: delete_source_ds=true changes the mutation class to destructive and requires confirmation.
+  known_restrictions: SOURCE_ID is a standalone dataset in the same project (4BATC010 INVALID_SOURCE_DATASET for a file id or an append child); to append a file use file upload with append_to_ds_id. delete_source_ds=true changes the mutation class to destructive and requires confirmation.
   reviewed_by: primary
 - command_id: batch.create-spec
   command_path: batch create-spec

{mammoth_cli-2.0.21 → mammoth_cli-2.0.22}/spec/manifests/commands/parameter.yaml

@@ -29,8 +29,8 @@ commands:
   required_fixture_guard: null
   secret_fields: []
   human_example: mammoth parameter create --help
-  agent_example: 'mammoth parameter create ''Revenue report'' --input ''{"param_type": "sample", "value":
-    "sample"}'''
+  agent_example: 'mammoth parameter create ''Revenue report'' --input ''{"param_type": "TEXT", "value":
+    "Q3"}'''
   unit_tests:
   - UT-PARAMETER-CREATE
   contract_tests:
@@ -39,7 +39,7 @@ commands:
   - CT-PARAMETER-CREATE-ERROR
   draft_test: null
   undo_test: null
-  known_restrictions: null
+  known_restrictions: param_type is NUMERIC, TEXT or DATE (uppercase; 4PARM008 otherwise).
   reviewed_by: primary
 - command_id: parameter.delete
   command_path: parameter delete

{mammoth_cli-2.0.21 → mammoth_cli-2.0.22}/spec/manifests/commands/view.yaml

@@ -779,7 +779,7 @@ commands:
   secret_fields: []
   human_example: mammoth view data-check create VIEW_ID --help
   agent_example: 'mammoth view data-check create 123 123 --input ''{"body": {"checks": [{"check_type": "null_percentage",
-    "config": {"column": "Status", "condition": "lt"}}], "name": "Revenue report"}}'''
+    "config": {"column": "Status", "condition": "lt"}}], "name": "Revenue report", "pinned_to_end": true}}'''
   unit_tests:
   - UT-VIEW-DATA-CHECK-CREATE
   contract_tests:
@@ -788,7 +788,7 @@ commands:
   - CT-VIEW-DATA-CHECK-CREATE-ERROR
   draft_test: null
   undo_test: null
-  known_restrictions: null
+  known_restrictions: 'body needs a placement: pinned_to_end true or a task_sequence (4GENR007 "Either task_sequence or pinned_to_end must be set" otherwise).'
   reviewed_by: primary
 - command_id: view.data-check.delete
   command_path: view data-check delete
@@ -983,8 +983,8 @@ commands:
   required_fixture_guard: null
   secret_fields: []
   human_example: mammoth view data-check update VIEW_ID DATA_CHECK_ID --help
-  agent_example: 'mammoth view data-check update 123 123 123 --input ''{"body": {"patches": [{"op": "replace",
-    "path": "enable"}]}}'''
+  agent_example: 'mammoth view data-check update 123 123 123 --input ''{"body": {"patches": [{"op": "command",
+    "path": "disable", "value": null}]}}'''
   unit_tests:
   - UT-VIEW-DATA-CHECK-UPDATE
   contract_tests:
@@ -993,7 +993,7 @@ commands:
   - CT-VIEW-DATA-CHECK-UPDATE-ERROR
   draft_test: null
   undo_test: null
-  known_restrictions: null
+  known_restrictions: 'patches are {op: command, path: enable|disable, value: null} or {op: replace, path: spec, value: AddDataCheckSpec}. On release the PATCH returns HTTP 500 (outcome_unknown) after applying; read the check back with view data-check get.'
   reviewed_by: primary
 - command_id: view.data.get
   command_path: view data get