mammoth-cli 2.2.76__tar.gz → 2.2.78__tar.gz

{mammoth_cli-2.2.76 → mammoth_cli-2.2.78}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: mammoth-cli
-Version: 2.2.76
+Version: 2.2.78
 Summary: Command-line interface for the Mammoth Analytics platform
 Project-URL: homepage, https://mammoth.io
 Project-URL: repository, https://github.com/EdgeMetric/mammothsdk
@@ -18,7 +18,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.9,>=0.8.40
+Requires-Dist: mammoth-io<0.9,>=0.8.42
 Requires-Dist: platformdirs<5,>=4.10
 Requires-Dist: pydantic<3,>=2.12.5
 Requires-Dist: pyyaml<7,>=6
@@ -243,11 +243,14 @@ mammoth skill install --input '{"agents": ["codex"], "scope": "project"}'
 Use `mammoth skill update` after a CLI upgrade. It refreshes copies owned by the
 installer and reports modified copies instead of silently replacing them.
 
-The CLI checks PyPI for a newer release at most once an hour, after a command
-has finished: every JSON envelope carries `meta.update_available` and human
-output adds one stderr line. In a terminal it also upgrades itself before the
-next command; set `MAMMOTH_AUTO_UPGRADE=0` to stop that, or
-`MAMMOTH_NO_UPDATE_CHECK=1` to turn the check off (see
+The CLI keeps itself up to date. At most once a day, after a command has
+finished and written its output, a detached process asks PyPI and installs a
+newer release through the same package manager as `mammoth upgrade`. It never
+delays or fails a command, prints nothing, and writes any failure to the run
+log. `meta.update_available` (and the stderr line in human output) appears only
+when a newer release exists and will not be installed by itself. Set
+`MAMMOTH_NO_AUTO_UPDATE=1` to keep the check but never install (CI, containers,
+pinned environments), or `MAMMOTH_NO_UPDATE_CHECK=1` to turn the check off (see
 [Upgrade](https://github.com/EdgeMetric/mammothsdk/blob/main/mammoth-cli/docs/upgrade.md)).
 
 ## What you can do

{mammoth_cli-2.2.76 → mammoth_cli-2.2.78}/README.md

@@ -214,11 +214,14 @@ mammoth skill install --input '{"agents": ["codex"], "scope": "project"}'
 Use `mammoth skill update` after a CLI upgrade. It refreshes copies owned by the
 installer and reports modified copies instead of silently replacing them.
 
-The CLI checks PyPI for a newer release at most once an hour, after a command
-has finished: every JSON envelope carries `meta.update_available` and human
-output adds one stderr line. In a terminal it also upgrades itself before the
-next command; set `MAMMOTH_AUTO_UPGRADE=0` to stop that, or
-`MAMMOTH_NO_UPDATE_CHECK=1` to turn the check off (see
+The CLI keeps itself up to date. At most once a day, after a command has
+finished and written its output, a detached process asks PyPI and installs a
+newer release through the same package manager as `mammoth upgrade`. It never
+delays or fails a command, prints nothing, and writes any failure to the run
+log. `meta.update_available` (and the stderr line in human output) appears only
+when a newer release exists and will not be installed by itself. Set
+`MAMMOTH_NO_AUTO_UPDATE=1` to keep the check but never install (CI, containers,
+pinned environments), or `MAMMOTH_NO_UPDATE_CHECK=1` to turn the check off (see
 [Upgrade](https://github.com/EdgeMetric/mammothsdk/blob/main/mammoth-cli/docs/upgrade.md)).
 
 ## What you can do

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

{mammoth_cli-2.2.76 → mammoth_cli-2.2.78}/mammoth_cli/app.py

@@ -114,7 +114,7 @@ _AGENT_SUBGROUP_DESCRIPTIONS = {
     "goldens": "Manage and run the golden cases an agent definition is proven against.",
     "memory": "Manage the facts an agent definition has learned, per project.",
     "message": "Correct the request kind of a reply in an agent chat.",
-    "plan": "Edit the waiting workflow proposal of an agent chat plan.",
+    "plan": "Approve, skip or discard the plan of an agent chat, or edit its workflow proposal.",
     "projects": "Set or clear the projects an agent definition works in.",
     "run": "Inspect and control an agent's runs.",
     "scratch": "Read, write and clear an agent definition's scratchpad notes per project.",
@@ -203,6 +203,7 @@ _SUBGROUP_DESCRIPTIONS = {
     "dashboard video": "Export a dashboard as a video.",
     "data-app user": "List and remove the users of a data app.",
     "dataset broken-rows": "List and resolve rows that failed to load.",
+    "dataset definition": "List, save and remove what terms mean for a dataset.",
     "dataset file-settings": "Read, update and undo a dataset's file settings.",
     "dataset interpretation": "Preview and confirm how a file is interpreted.",
     "parameter group": "Create, list, update, reorder and delete parameter groups.",

{mammoth_cli-2.2.76 → mammoth_cli-2.2.78}/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 714 commands. 516 of them bind one of the 545 API operations in the matrix; the remainder are local commands (`schema`, `auth`, `doctor`, `log`, ...) or typed variants that share an operation (`view transform *` commands submit through `view.task.add`, except `rename-columns` and `sort`, which set view display properties through `view.update`). 262 bound commands ran once successfully on release, 1 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. Use an untried command normally: confirm a write with the user first, check its result with a read afterwards, and never refuse a command only because it is untried.
+The CLI publishes 753 commands. 516 of them bind one of the 545 API operations in the matrix; the remainder are local commands (`schema`, `auth`, `doctor`, `log`, ...) or typed variants that share an operation (`view transform *` commands submit through `view.task.add`, except `rename-columns` and `sort`, which set view display properties through `view.update`). 262 bound commands ran once successfully on release, 1 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. Use an untried command normally: confirm a write with the user first, check its result with a read afterwards, and never refuse a command only because it is untried.
 
 Status meanings:
 

{mammoth_cli-2.2.76 → mammoth_cli-2.2.78}/mammoth_cli/bundled_skill/mammoth-cli/references/command-index.md

@@ -1,12 +1,12 @@
 # Published CLI command catalog
 
-This generated catalog is a lookup table for every command in the published CLI manifest, currently 740; each entry carries its release status line. It is a command-contract index, not an assertion that every backend/OpenAPI operation has a CLI binding. For an exact local CLI contract, run `mammoth schema get COMMAND_ID`; `mammoth capability list` is an API-binding inventory and can omit typed/local CLI routes. For focused workflows, read the [recipes index](recipes/index.md). Sensitive structured input must come from a private file or pipe; never put secrets in literal argv.
+This generated catalog is a lookup table for every command in the published CLI manifest, currently 753; each entry carries its release status line. It is a command-contract index, not an assertion that every backend/OpenAPI operation has a CLI binding. For an exact local CLI contract, run `mammoth schema get COMMAND_ID`; `mammoth capability list` is an API-binding inventory and can omit typed/local CLI routes. For focused workflows, read the [recipes index](recipes/index.md). Sensitive structured input must come from a private file or pipe; never put secrets in literal argv.
 
 Load only the applicable domain file:
 
 - [activity](commands/activity.md) — 2 published commands
 - [addon](commands/addon.md) — 7 published commands
-- [agent](commands/agent.md) — 51 published commands
+- [agent](commands/agent.md) — 54 published commands
 - [ai](commands/ai.md) — 5 published commands
 - [annotation](commands/annotation.md) — 5 published commands
 - [auth](commands/auth.md) — 5 published commands
@@ -20,14 +20,14 @@ Load only the applicable domain file:
 - [collection](commands/collection.md) — 16 published commands
 - [completion](commands/completion.md) — 2 published commands
 - [config](commands/config.md) — 4 published commands
-- [connector](commands/connector.md) — 22 published commands
-- [context](commands/context.md) — 3 published commands
+- [connector](commands/connector.md) — 23 published commands
+- [context](commands/context.md) — 4 published commands
 - [dashboard-qa](commands/dashboard-qa.md) — 14 published commands
 - [dashboard-template](commands/dashboard-template.md) — 12 published commands
 - [dashboard-style](commands/dashboard-style.md) — 10 published commands
 - [dashboard](commands/dashboard.md) — 108 published commands
 - [data-app](commands/data-app.md) — 12 published commands
-- [dataset](commands/dataset.md) — 22 published commands
+- [dataset](commands/dataset.md) — 27 published commands
 - [doctor](commands/doctor.md) — 1 published commands
 - [external-key](commands/external-key.md) — 4 published commands
 - [file](commands/file.md) — 11 published commands
@@ -51,8 +51,8 @@ Load only the applicable domain file:
 - [upgrade](commands/upgrade.md) — 1 published commands
 - [user](commands/user.md) — 8 published commands
 - [version](commands/version.md) — 1 published commands
-- [view-transform](commands/view-transform.md) — 34 published commands
-- [view](commands/view.md) — 101 published commands
+- [view-transform](commands/view-transform.md) — 35 published commands
+- [view](commands/view.md) — 103 published commands
 - [webhook](commands/webhook.md) — 7 published commands
 - [workflow](commands/workflow.md) — 20 published commands
 - [workspace](commands/workspace.md) — 31 published commands

{mammoth_cli-2.2.76 → mammoth_cli-2.2.78}/mammoth_cli/bundled_skill/mammoth-cli/references/commands/agent.md

@@ -76,7 +76,7 @@ Status on release: untried; no live run recorded.
 
 Run: `mammoth agent chat`. Exact input fields: `mammoth schema get agent.chat`.
 
-Example: `mammoth agent chat --input '{"message": "Summarize revenue by region", "scope": {"sample_key": "Status"}}'`. Placeholders are illustrative; resolve IDs and input from observed reads.
+Example: `mammoth agent chat --input '{"message": "Summarize revenue by region", "scope": {"type": "workspace", "workspace_id": 123}, "client_context": {"project_id": 456}}'`. Placeholders are illustrative; resolve IDs and input from observed reads.
 
 Result: `AgentChatResult`; mutation `benign_mutation`, confirmation `none`, wait policy `not_async`.
 
@@ -232,6 +232,26 @@ Result: `AgentMessageSetRequestKindResult`; mutation `benign_mutation`, confirma
 
 Status on release: untried; no live run recorded.
 
+### `agent.plan.approve`
+
+Run: `mammoth agent plan approve`. Exact input fields: `mammoth schema get agent.plan.approve`.
+
+Example: `mammoth agent plan approve resource-123`. Illustrative only: append `--yes` after observing an owned target.
+
+Result: `AgentPlanApproveResult`; mutation `benign_mutation`, confirmation `prompt_or_yes`, wait policy `not_async`.
+
+Status on release: untried; no live run recorded.
+
+### `agent.plan.discard`
+
+Run: `mammoth agent plan discard`. Exact input fields: `mammoth schema get agent.plan.discard`.
+
+Example: `mammoth agent plan discard resource-123`. Placeholders are illustrative; resolve IDs and input from observed reads.
+
+Result: `AgentPlanDiscardResult`; mutation `benign_mutation`, confirmation `none`, wait policy `not_async`.
+
+Status on release: untried; no live run recorded.
+
 ### `agent.plan.edit-proposal`
 
 Run: `mammoth agent plan edit-proposal`. Exact input fields: `mammoth schema get agent.plan.edit-proposal`.
@@ -242,6 +262,16 @@ Result: `AgentPlanEditProposalResult`; mutation `benign_mutation`, confirmation
 
 Status on release: untried; no live run recorded.
 
+### `agent.plan.skip`
+
+Run: `mammoth agent plan skip`. Exact input fields: `mammoth schema get agent.plan.skip`.
+
+Example: `mammoth agent plan skip resource-123 123`. Placeholders are illustrative; resolve IDs and input from observed reads.
+
+Result: `AgentPlanSkipResult`; mutation `benign_mutation`, confirmation `none`, wait policy `not_async`.
+
+Status on release: untried; no live run recorded.
+
 ### `agent.projects.clear`
 
 Run: `mammoth agent projects clear`. Exact input fields: `mammoth schema get agent.projects.clear`.

{mammoth_cli-2.2.76 → mammoth_cli-2.2.78}/mammoth_cli/bundled_skill/mammoth-cli/references/commands/batch.md

@@ -66,7 +66,7 @@ Status on release: ran once on CLI 2.0.21 — ergonomics sweep 2026-09-19: exit
 
 Run: `mammoth batch update`. Exact input fields: `mammoth schema get batch.update`.
 
-Example: `mammoth batch update 123 --input '{"patch": [{"sample_key": "Status"}]}'`. Placeholders are illustrative; resolve IDs and input from observed reads.
+Example: `mammoth batch update 123 --input '{"patch": {"sample_key": "Status"}}'`. Placeholders are illustrative; resolve IDs and input from observed reads.
 
 Result: `BatchUpdateResult`; mutation `benign_mutation`, confirmation `none`, wait policy `returns_job`.
 

{mammoth_cli-2.2.76 → mammoth_cli-2.2.78}/mammoth_cli/bundled_skill/mammoth-cli/references/commands/connector.md

@@ -114,6 +114,16 @@ Result: `ConnectorConnectionListResult`; mutation `read`, confirmation `none`, w
 
 Status on release: observed blocker — server_error: see sweep report. Re-check before relying on it.
 
+### `connector.connection.query`
+
+Run: `mammoth connector connection query`. Exact input fields: `mammoth schema get connector.connection.query`.
+
+Example: `mammoth connector connection query sample sample --input '{"query": "SELECT region, SUM(revenue) FROM data GROUP BY region"}'`. Placeholders are illustrative; resolve IDs and input from observed reads.
+
+Result: `ConnectorConnectionQueryResult`; mutation `read`, confirmation `none`, wait policy `not_async`.
+
+Status on release: untried; no live run recorded.
+
 ### `connector.connection.update`
 
 Run: `mammoth connector connection update`. Exact input fields: `mammoth schema get connector.connection.update`.

{mammoth_cli-2.2.76 → mammoth_cli-2.2.78}/mammoth_cli/bundled_skill/mammoth-cli/references/commands/context.md

@@ -31,3 +31,13 @@ Example: `mammoth context project use 123`. Placeholders are illustrative; resol
 Result: `ContextProjectUseResult`; mutation `benign_mutation`, confirmation `none`, wait policy `not_async`.
 
 Status on release: untried; no live run recorded.
+
+### `context.show`
+
+Run: `mammoth context show`. Exact input fields: `mammoth schema get context.show`.
+
+Example: `mammoth context show`. Placeholders are illustrative; resolve IDs and input from observed reads.
+
+Result: `ContextShowResult`; mutation `read`, confirmation `none`, wait policy `not_async`.
+
+Status on release: untried; no live run recorded.

{mammoth_cli-2.2.76 → mammoth_cli-2.2.78}/mammoth_cli/bundled_skill/mammoth-cli/references/commands/dataset.md

@@ -52,6 +52,16 @@ Execution is unavailable for the current contract and returns `unsupported_contr
 
 Known restriction: BLOCKED[B07 DATASET_PATCH_UNTYPED]; reserved, not registered.
 
+### `dataset.column-stats`
+
+Run: `mammoth dataset column-stats`. Exact input fields: `mammoth schema get dataset.column-stats`.
+
+Example: `mammoth dataset column-stats`. Placeholders are illustrative; resolve IDs and input from observed reads.
+
+Result: `DatasetColumnStatsResult`; mutation `read`, confirmation `none`, wait policy `not_async`.
+
+Status on release: untried; no live run recorded.
+
 ### `dataset.create`
 
 Run: `mammoth dataset create`. Exact input fields: `mammoth schema get dataset.create`.
@@ -82,6 +92,36 @@ Result: `DatasetDataResult`; mutation `read`, confirmation `none`, wait policy `
 
 Status on release: ran once on CLI 1.1.10 — Bounded retained-resource read with published CLI 1.1.10 and explicit timeout=30,poll_interval=1 returned 100 rows and five headers for dataset 28. No Full claim: retained ETL-owned resource and no option/error/lifecycle matrix beyond this read.
 
+### `dataset.definition.add`
+
+Run: `mammoth dataset definition add`. Exact input fields: `mammoth schema get dataset.definition.add`.
+
+Example: `mammoth dataset definition add 123 --input '{"term": "late", "definition": "delivered more than 5 days after shipped_date"}'`. Illustrative only: append `--yes --confirm <EXACT_TARGET>` after observing the target.
+
+Result: `DatasetDefinitionAddResult`; mutation `benign_mutation`, confirmation `confirm_target`, wait policy `not_async`.
+
+Status on release: untried; no live run recorded.
+
+### `dataset.definition.list`
+
+Run: `mammoth dataset definition list`. Exact input fields: `mammoth schema get dataset.definition.list`.
+
+Example: `mammoth dataset definition list 123`. Placeholders are illustrative; resolve IDs and input from observed reads.
+
+Result: `DatasetDefinitionListResult`; mutation `read`, confirmation `none`, wait policy `not_async`.
+
+Status on release: untried; no live run recorded.
+
+### `dataset.definition.remove`
+
+Run: `mammoth dataset definition remove`. Exact input fields: `mammoth schema get dataset.definition.remove`.
+
+Example: `mammoth dataset definition remove 123 a1b2c3d4`. Illustrative only: append `--yes` after observing an owned target.
+
+Result: `DatasetDefinitionRemoveResult`; mutation `benign_mutation`, confirmation `prompt_or_yes`, wait policy `not_async`.
+
+Status on release: untried; no live run recorded.
+
 ### `dataset.delete`
 
 Run: `mammoth dataset delete`. Exact input fields: `mammoth schema get dataset.delete`.
@@ -192,6 +232,16 @@ Result: `DatasetRestoreResult`; mutation `benign_mutation`, confirmation `none`,
 
 Status on release: ran once on CLI 2.0.14 — write sweep 2026-09-18: exit 0 on release with CLI 2.0.14. job 312 restore_datasource -> status success. dataset list --project 21 confirms dataset 49 (name 'stores.csv 2') is back and visible alongside 48. Single invocation only.
 
+### `dataset.schema-diff`
+
+Run: `mammoth dataset schema-diff`. Exact input fields: `mammoth schema get dataset.schema-diff`.
+
+Example: `mammoth dataset schema-diff 10 11`. Placeholders are illustrative; resolve IDs and input from observed reads.
+
+Result: `DatasetSchemaDiffResult`; mutation `read`, confirmation `none`, wait policy `not_async`.
+
+Status on release: untried; no live run recorded.
+
 ### `dataset.search`
 
 Run: `mammoth dataset search`. Exact input fields: `mammoth schema get dataset.search`.

{mammoth_cli-2.2.76 → mammoth_cli-2.2.78}/mammoth_cli/bundled_skill/mammoth-cli/references/commands/view-transform.md

@@ -32,6 +32,16 @@ Result: `ViewTransformAiResult`; mutation `reversible_pipeline`, confirmation `n
 
 Status on release: ran once on CLI 2.0.40 through `view.task.add` and was read back with `view data get`; other inputs for this transform are untried.
 
+### `view.transform.batch`
+
+Run: `mammoth view transform batch`. Exact input fields: `mammoth schema get view.transform.batch`.
+
+Example: `mammoth view transform batch 123 --input '{"steps": [{"op": "filter", "input": {"condition": {"column": "Cost", "operator": "GTE", "value": 20}}}, {"op": "sort", "input": {"order_by": [["Cost", "DESC"]]}}, {"op": "limit-rows", "input": {"n": 2}}], "dataset_id": 456}'`. Placeholders are illustrative; resolve IDs and input from observed reads.
+
+Result: `ViewTransformBatchResult`; mutation `reversible_pipeline`, confirmation `none`, wait policy `always_wait`.
+
+Status on release: untried; it submits through `view.task.add`, but this transform was not among those run.
+
 ### `view.transform.bulk-replace`
 
 Run: `mammoth view transform bulk-replace`. Exact input fields: `mammoth schema get view.transform.bulk-replace`.

{mammoth_cli-2.2.76 → mammoth_cli-2.2.78}/mammoth_cli/bundled_skill/mammoth-cli/references/commands/view.md

@@ -252,6 +252,16 @@ Result: `ViewDataCompareResult`; mutation `read`, confirmation `none`, wait poli
 
 Status on release: untried; no live run recorded.
 
+### `view.data.drivers`
+
+Run: `mammoth view data drivers`. Exact input fields: `mammoth schema get view.data.drivers`.
+
+Example: `mammoth view data drivers 123 --input '{"measure": {"column": "revenue", "function": "SUM"}, "date_column": "sale_date", "compare": ["2026-07", "2026-08"], "by": ["store", "category"]}'`. Placeholders are illustrative; resolve IDs and input from observed reads.
+
+Result: `ViewDataDriversResult`; mutation `read`, confirmation `none`, wait policy `not_async`.
+
+Status on release: untried; no live run recorded.
+
 ### `view.data.explore`
 
 Run: `mammoth view data explore`. Exact input fields: `mammoth schema get view.data.explore`.
@@ -262,6 +272,16 @@ Result: `ViewDataExploreResult`; mutation `read`, confirmation `none`, wait poli
 
 Status on release: untried; no live run recorded.
 
+### `view.data.forecast`
+
+Run: `mammoth view data forecast`. Exact input fields: `mammoth schema get view.data.forecast`.
+
+Example: `mammoth view data forecast 123 --input '{"measure": {"column": "revenue", "function": "SUM"}, "date_column": "sale_date", "unit": "month", "periods": 2}'`. Placeholders are illustrative; resolve IDs and input from observed reads.
+
+Result: `ViewDataForecastResult`; mutation `read`, confirmation `none`, wait policy `not_async`.
+
+Status on release: untried; no live run recorded.
+
 ### `view.data.get`
 
 Run: `mammoth view data get`. Exact input fields: `mammoth schema get view.data.get`.

{mammoth_cli-2.2.76 → mammoth_cli-2.2.78}/mammoth_cli/bundled_skill/mammoth-cli/references/commands/workflow.md

@@ -66,7 +66,7 @@ Status on release: untried; no live run recorded.
 
 Run: `mammoth workflow canvas`. Exact input fields: `mammoth schema get workflow.canvas`.
 
-Example: `mammoth workflow canvas 12 --input '{"canvas_state": {"proposed_changes": [{"op": "add_view", "dataset_id": 415, "name": "Urgent tickets", "ref": "urgent"}, {"op": "send_to_new_dataset", "dataset_id": 415, "view_ref": "urgent", "name": "Urgent tickets by team"}]}}'`. Placeholders are illustrative; resolve IDs and input from observed reads.
+Example: `mammoth workflow canvas 12 --input '{"canvas_state": {"proposed_changes": [{"op": "add_view", "dataset_id": 415, "name": "Urgent tickets", "ref": "urgent"}, {"op": "add_step", "view_ref": "urgent", "transform": "filter", "params": {"condition": {"column": "Priority", "operator": "EQ", "value": "Urgent"}}, "label": "Keep urgent tickets"}, {"op": "send_to_new_dataset", "dataset_id": 415, "view_ref": "urgent", "name": "Urgent tickets by team"}]}}'`. Placeholders are illustrative; resolve IDs and input from observed reads.
 
 Result: `WorkflowCanvasResult`; mutation `benign_mutation`, confirmation `none`, wait policy `not_async`.
 

{mammoth_cli-2.2.76 → mammoth_cli-2.2.78}/mammoth_cli/bundled_skill/mammoth-cli/references/operations.md

@@ -44,6 +44,18 @@ returns the project's datasets whose name, column names or sampled column
 values contain TERM, each with the matched column and value. `dataset find`
 and `browse` search match names only. A `browse` search hit carries `dataset_id` or `view_id`: use those,
 never the tree `id`.
+To check missing values or blanks across a project's datasets, run
+`dataset column-stats` once instead of profiling each view: it returns every
+dataset's columns with their blank count and share, type and distinct count,
+from stats stored at the last load or pipeline run.
+When the user states what a term means for a dataset ("late means delivered
+more than 5 days after shipped_date"), save it with
+`dataset definition add DATASET_ID --input '{"term": "...", "definition": "..."}'`,
+written in the dataset's real column names. A definition is shared by
+everyone's chats on that dataset, so the save needs
+`--yes --confirm DATASET_ID`, and a definition for an existing term replaces
+it. Do not save one for a one-off question. `dataset definition list` and
+`dataset definition remove DATASET_ID DEFINITION_ID` read and drop them.
 
 ```bash
 mammoth capability find "transform"
@@ -82,6 +94,14 @@ task submission does not prove that the task removed duplicates.
 For deduplication, discover and use `view.transform.discard-duplicates`; see
 recipes/transforms.md for the full procedure.
 
+When several transforms go on the same view in a row (for example filter, sort, then
+limit-rows), send them in one `view transform batch VIEW_ID --input '{"steps": [{"op":
+"filter", "input": {...}}, ...]}'` instead of one command each: the pipeline runs once and
+one verified outcome comes back (`row_check`, and `tasks` with each new task's status).
+Each `input` is what that `view transform` command takes. A step cannot use a column an
+earlier step of the batch creates: run those steps first. If a task fails, the batch's tasks
+are removed and the error names `steps[i]`.
+
 Prefer a typed `view transform <operation>` command. Its schema is the
 discoverable request contract. A job status or pipeline/task definition only
 proves that the task ran. For a value-changing step, the proof is the
@@ -130,16 +150,19 @@ NAME --input '{"seed_datasource_id": ROOT_DATASET_ID}'`, which returns its
 record id. `workflow cleanup` deletes the project's orphaned skeleton
 ("ghost") workflows (destructive; needs `--yes`).
 
-To only *suggest* a workflow's shape for the user to review, use `workflow
+To only *suggest* changes to a workflow for the user to review, use `workflow
 canvas WORKFLOW_ID --input '{"canvas_state": {"proposed_changes": [...]}}'`.
-Nothing is built until the user presses Save on the Workflows canvas; tell
-them the changes are waiting there. Changes are `add_view`, `rename_view`,
-`trash_view`, `rename_dataset`, `trash_dataset`, `send_to_new_dataset`,
-`send_to_dataset`, `join` and `export` (fields per op: `schema get
-workflow.canvas`). A later change in the same call can point at an earlier
-one: give the earlier change a `ref`, then use `view_ref`, `dataset_ref` or
-`target_dataset_ref` instead of an id. It cannot add filters, calculations or
-other tasks; if the request needs those, build it with `view` commands.
+Nothing is built until the user presses Save on the Workflows canvas, which
+builds every change in flow order; tell them the changes are waiting there.
+Changes are `add_view`, `rename_view`, `trash_view`, `rename_dataset`,
+`trash_dataset`, `send_to_new_dataset`, `send_to_dataset`, `join`, `export`,
+and, for the steps inside a view, `add_step`, `update_step` and `remove_step`
+(fields per op: `schema get workflow.canvas`). A later change in the same call
+can point at an earlier one: give the earlier change a `ref`, then use
+`view_ref`, `dataset_ref` or `target_dataset_ref` instead of an id. Propose the
+filters, calculations and other tasks a view needs as `add_step` changes in the
+same call (`transform` is a `view transform` kind, `params` its `--input`),
+never as `view` commands run afterwards.
 
 Draft mode is server-side batching for view pipeline edits. Enter, inspect
 status, submit, and verify pipeline state; discard only with the required
@@ -158,6 +181,18 @@ applied.
   put a card on a dashboard, say it to `dashboard chat edit`. Figures
   from `explore` and `view data aggregate` are rounded for display (2
   decimals; 4 below 1); `view data compare` keeps full precision.
+- "Why did revenue drop from July to August", "what drove the change": one
+  `view data drivers VIEW_ID` call, not a series of aggregates. It returns
+  each period's total and row count, the change, whether it came from volume
+  or value per row, and per `by` column the groups that moved most with their
+  signed `share_of_change`; `partial_period` names a period the data does not
+  cover to its end.
+- "Forecast", "what will revenue be in October": `view data forecast
+  VIEW_ID` (a linear trend over the complete months, quarters or weeks, with a
+  95% range; seasonal only with two full cycles). A last period the data does
+  not cover to its end is left out and reported as `excluded_partial`, and it
+  is the first period forecast: for October with data ending mid-September,
+  pass `periods` 2. Never scale a partial period up by its days.
 - "Who changed X": `activity list` (a change list of time, user, action and a
   `path` naming the dataset and view). Filter with `resource_id` in the log's
   typed form, `dataview_<id>` or `datasource_<id>` (a bare number matches

{mammoth_cli-2.2.76 → mammoth_cli-2.2.78}/mammoth_cli/bundled_skill/mammoth-cli/references/recipes/dashboards.md

@@ -103,8 +103,9 @@ mammoth view transform math VIEW_ID --project PROJECT_ID \
   revenue. Say how many there are in your report.
 - A generate or edit result may carry `deliverable_check`: `money_not_shown`
   (with the `math` command in `fix`), `unit_price_summed`,
-  `columns_not_on_dashboard` (view columns added after the dashboard was made)
-  and one `blank_values` entry for each column on the board that has blanks.
+  `columns_not_on_dashboard` (view columns added after the dashboard was made),
+  `count_titled_as_rate` (a card or tile counts rows, but its title reads as a
+  rate) and one `blank_values` entry for each column on the board that has blanks.
   Fix each warning (add the column, then ask again in words), or say in your
   report why you kept it.
 
@@ -168,6 +169,9 @@ the user to use Download PDF in the app; never retry with `{"data": {}}`.
 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`.
+`dashboard action` with `publish-data` on a board that was never published
+publishes the presentation instead and says so. `share` and `action` print the
+deliverable check in their confirmation text.
 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

{mammoth_cli-2.2.76 → mammoth_cli-2.2.78}/mammoth_cli/bundled_skill/mammoth-cli/references/recipes/database-import.md

@@ -25,8 +25,19 @@ mammoth connector connection get mssql CONNECTION_KEY     # read it back; config
 ```
 
 There is no table-browse command. Ask the user for the table (and schema), or
-draft the SQL with `connector query generate`. Then import it as a dataset
-(a write: confirm first). `query` is required; `validate` is on by default:
+draft the SQL with `connector query generate`. Try the SELECT first: it shows
+sample rows and saves nothing (no dataset, no data source), so it needs no
+`--yes`. The CLI accepts only one SELECT (or WITH ... SELECT); the connection's
+database user decides what the database allows, and the sample is limited to
+the first rows, so add your own LIMIT for a large table:
+
+```bash
+mammoth connector connection query mssql CONNECTION_KEY \
+  --input '{"query": "SELECT TOP 5 * FROM dbo.Orders"}'
+```
+
+Then import it as a dataset (a write: confirm first). `query` is required;
+`validate` is on by default:
 
 ```bash
 mammoth connector ds-config create mssql CONNECTION_KEY \

{mammoth_cli-2.2.76 → mammoth_cli-2.2.78}/mammoth_cli/bundled_skill/mammoth-cli/references/recipes/exports.md

@@ -108,6 +108,14 @@ mammoth view export postgres VIEW_ID DATASET_ID --project PROJECT_ID \
 mammoth view export list VIEW_ID DATASET_ID --project PROJECT_ID
 ```
 
+The command returns after the export has run. The result carries
+`export: {id, status, error, ran_at, result}`: `status` `ok` means the run
+finished, so there is nothing to poll or read back to confirm it. A run that
+failed is an `export_failed` error naming the destination's error. With
+`"run_immediately": false` nothing runs now and `export.status` is `scheduled`.
+`mammoth job wait JOB_ID` on the add job (`add_action`) returns the same
+`export` block.
+
 If the operator has not supplied such a file, stop and ask for it; do not
 compose the body yourself from values seen in chat.
 

{mammoth_cli-2.2.76 → mammoth_cli-2.2.78}/mammoth_cli/bundled_skill/mammoth-cli/references/recipes/rest-api-import.md

@@ -31,6 +31,9 @@ does not include this connector (or its paid addon is not active).
 
 ## 2. Try the data-source config (creates no dataset)
 
+`mammoth connector connection query generic_rest_api CONNECTION_KEY --input
+sample.json` runs the same sample read-only (no `--yes`, nothing saved).
+
 `query` is a **JSON string** (not an object) of the data-source config:
 `endpoint_path`, `http_method` (`GET|POST`), `request_body`, `query_params`,
 `data_root_path` (JSONPath to the records; `[*]` is supported), `pagination`,

{mammoth_cli-2.2.76 → mammoth_cli-2.2.78}/mammoth_cli/bundled_skill/mammoth-cli/references/recipes/transforms.md

@@ -81,6 +81,11 @@ mammoth view transform math VIEW_ID --project PROJECT_ID \
   --input '{"dataset_id":DATASET_ID,"expression":"GDP / Population","new_column":"GDP per capita"}'
 ```
 
+A TEXT column that writes numbers with a decimal comma (`1.234,5`) converts with
+`"decimal_separator":","` on its `conversions` entry (`thousands_separator`
+defaults to the other mark). `view data profile` lists such a column under
+`summary.mixed_number_format` when its values mix notations.
+
 In a math `expression`, write a multi-word display name bare (`Quantity * Unit
 Price`) or quoted (`Quantity * \"Unit Price\"` inside the JSON string).
 

{mammoth_cli-2.2.76 → mammoth_cli-2.2.78}/mammoth_cli/commands/__init__.py

@@ -21,6 +21,7 @@ _TARGETS: dict[str, str] = {
     "config.set": "mammoth_cli.commands.config:config_set",
     "config.list": "mammoth_cli.commands.config:config_list",
     "config.path": "mammoth_cli.commands.config:config_path",
+    "context.show": "mammoth_cli.commands.context:context_show",
     "context.project.status": "mammoth_cli.commands.context:context_project_status",
     "context.project.use": "mammoth_cli.commands.context:context_project_use",
     "context.project.clear": "mammoth_cli.commands.context:context_project_clear",