mammoth-cli 2.0.38__tar.gz → 2.0.40__tar.gz

{mammoth_cli-2.0.38 → mammoth_cli-2.0.40}/PKG-INFO

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

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

{mammoth_cli-2.0.38 → mammoth_cli-2.0.40}/mammoth_cli/bundled_skill/mammoth-cli/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: mammoth-cli
-version: 2.0.38
+version: 2.0.40
 description: "Use Mammoth Analytics from a terminal: install or authenticate the CLI, discover its live command contract, and safely manage projects, data, views, pipelines (join, merge, pivot, filter, clean), dashboards, exports, and handoffs."
 ---
 
@@ -93,21 +93,33 @@ report a real gap with the command you tried.
 Users often upload related files without saying how they relate ("make a
 dashboard from t_a and t_b"). Work it out from the data before you build:
 
-1. Read every view first: `view get VIEW_ID` (columns, types, row count) and
-   `view data get VIEW_ID --input '{"limit": 20}'`.
+1. Upload every file, then read every view in Mammoth (not the local
+   files): `view get VIEW_ID` (columns, types, row count) and `view data get
+   VIEW_ID`. The data read lists `column_warnings`: numbers or dates stored
+   as text, and blanks, each with the fix.
 2. Find the keys. A column in one view whose values appear in a column of
    the other (`customer_id` and `id`, `order_ref` and `order_no`) is a
    foreign key; the view with many rows per key is the main one.
 3. Make the keys match before the join: same type (`convert-type`), same
    case and padding (`text`), no blanks (`set-values`, `filter`).
-4. Fix what the deliverable needs: numbers stored as text (`convert-type`
-   to `NUMERIC`), dates stored as text (`convert-type` to `DATE`), blanks.
-5. `view transform join` the lookup view into the main view (`LEFT`), then
-   read back and check the match rate
-   ([worked example](references/recipes/end-to-end.md), step 5).
+4. Act on every `column_warnings` entry for a column the deliverable uses:
+   run its `fix` (`convert-type` to `NUMERIC` or `DATE`; the values that are
+   not numbers become empty). A text `price` cannot be summed on a dashboard.
+   Then decide on each `blank_values` entry: fill, filter, or keep. Write one
+   line for each in your report (the column, the count, what you did and
+   why). A blank that you saw but did not mention is a miss.
+5. `view transform join` the lookup view into the main view (`LEFT`). The
+   result's `join_check` gives `match_rate`, `unmatched_rows` and
+   `unmatched_keys`; put them in your report, and stop to compare the keys
+   if more than a few rows found no match.
 6. Build the dashboard from the joined view
-   ([dashboards](references/recipes/dashboards.md)).
+   ([dashboards](references/recipes/dashboards.md)). If the data has money,
+   show it: add `revenue` (`math`, `qty * price`, `new_column`) and chart
+   its sum. Do not sum a unit price.
 
+For the defaults that most pipelines use (new column or overwrite, `LEFT`
+joins, date steps), see
+[transforms](references/recipes/transforms.md#what-most-pipelines-look-like).
 Say what you inferred (which columns you joined on, what you converted) in
 your report. If no column links the files, ask before you combine them.
 
@@ -149,6 +161,10 @@ your report. If no column links the files, ask before you combine them.
   target column *before* the change so the after-read has a comparison.
 - A uniform result (every amount 0, every region "Unknown", most join rows
   unmatched) means the previous step went wrong; stop and re-inspect it.
+- `column_warnings` on a data read and `join_check` on a join are findings,
+  not decoration: fix each one the deliverable depends on, or say in the
+  report why you kept it. `view data get` pages with `{"offset": 51,
+  "limit": 50}`.
 - A timeout, exit 7 or interruption does not prove failure; reconcile an
   `outcome_unknown` (`job get`, `view task list`) before replaying.
 - Run the [report checklist](references/report-checklist.md) before stating

{mammoth_cli-2.0.38 → mammoth_cli-2.0.40}/mammoth_cli/bundled_skill/mammoth-cli/references/about-mammoth.md

@@ -110,7 +110,7 @@ Checkpoint Alert are the `view data-check` and `view checkpoint` families.
 | Turn wide columns into label/value rows | Unpivot | `unnest` |
 | Read fields out of a JSON column | Extract JSON | `json-extract` |
 | Classify, tag or summarise rows with AI | Generative AI | `ai` |
-| One SQL query over the view | AI SQL Query | `add-sql` (replaces the view's columns), `generate-sql` (from plain words) |
+| One SQL query over the view | AI SQL Query | `add-sql` (replaces the view's columns), `generate-sql` (writes the query from plain words; apply it with `add-sql`) |
 | Copy rows into another dataset, refreshed with the pipeline | Send to Dataset | `view export dataset` (not a `view transform`) |
 
 `join` or `lookup`: `join` adds the chosen columns from every matching row

{mammoth_cli-2.0.38 → mammoth_cli-2.0.40}/mammoth_cli/bundled_skill/mammoth-cli/references/capabilities-misc.md

@@ -140,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.28; 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.40; 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.38 → mammoth_cli-2.0.40}/mammoth_cli/bundled_skill/mammoth-cli/references/capabilities.md

@@ -11,7 +11,7 @@ Status meanings:
 - **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 matrix row names the transformations that ran end to end and were read back (filter, fill-missing, join, pivot, set-values with a condition, text, bulk-replace, convert-type, discard-duplicates). A transformation not named there has the same untried status as any other command.
+The typed `view transform *` commands all submit through `view.task.add` (`rename-columns` and `sort` through `view.update`); its matrix row names the transformations that ran end to end and were read back against a known answer: `add-column`, `add-sql`, `ai`, `bulk-replace`, `combine-columns`, `convert-type`, `copy-columns`, `crosstab`, `date-diff`, `delete-columns`, `discard-duplicates`, `extract-date`, `fill-missing`, `filter`, `generate-sql`, `increment-date`, `join`, `json-extract`, `limit-rows`, `lookup`, `math`, `pivot`, `rename-columns`, `replace`, `set-values`, `small-large`, `sort`, `split`, `substring`, `text`, `unnest`, `window`. A transformation not named there has the same untried status as any other command.
 
 ## Coverage by family
 
@@ -118,4 +118,4 @@ Ran once: `view.active-user.list`, `view.active-user.mark`, `view.ai.generate-da
 | `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.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.28; 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.40; 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.38 → mammoth_cli-2.0.40}/mammoth_cli/bundled_skill/mammoth-cli/references/commands/view.md

@@ -762,7 +762,7 @@ Example: `mammoth view task add 123 --input '{"task_spec": {"DATAVIEW_ID": 123,
 
 Result: `ViewTaskAddResult`; mutation `reversible_pipeline`, confirmation `none`, wait policy `always_wait`.
 
-Status on release: ran once on CLI 2.0.18 — golden-data check golden-20260919 (CLI 2.0.18): typed transforms bulk-replace, convert-type, discard-duplicates, filter, join, pivot, set-values, text each run once on an owned fixture on release and read back with view data get against a known answer (values…
+Status on release: ran once on CLI 2.0.40 — golden-data check golden-20260919 (CLI 2.0.18): typed transforms bulk-replace, convert-type, discard-duplicates, filter, join, pivot, set-values, text each run once on an owned fixture on release and read back with view data get against a known answer (values…
 
 ### `view.task.delete`
 
@@ -822,7 +822,7 @@ Example: `mammoth view transform add-column 123 --input '{"name": "Revenue repor
 
 Result: `ViewTransformAddColumnResult`; 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.
+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.add-sql`
 
@@ -832,7 +832,7 @@ Example: `mammoth view transform add-sql 123 --input '{"query": "SELECT region,
 
 Result: `ViewTransformAddSqlResult`; mutation `reversible_pipeline`, confirmation `none`, wait policy `always_wait`.
 
-Status on release: ran once on CLI 2.0.18 through `view.task.add` and was read back with `view data get`; other inputs for this transform are untried.
+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.ai`
 
@@ -842,7 +842,7 @@ Example: `mammoth view transform ai 123 --input '{"prompt": "Summarize revenue b
 
 Result: `ViewTransformAiResult`; 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.
+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.bulk-replace`
 
@@ -852,7 +852,7 @@ Example: `mammoth view transform bulk-replace 123 --input '{"columns": ["Status"
 
 Result: `ViewTransformBulkReplaceResult`; mutation `reversible_pipeline`, confirmation `none`, wait policy `always_wait`.
 
-Status on release: ran once on CLI 2.0.18 through `view.task.add` and was read back with `view data get`; other inputs for this transform are untried.
+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.combine-columns`
 
@@ -862,7 +862,7 @@ Example: `mammoth view transform combine-columns 123 --input '{"sources": ["Stat
 
 Result: `ViewTransformCombineColumnsResult`; 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.
+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.convert-type`
 
@@ -872,7 +872,7 @@ Example: `mammoth view transform convert-type 123 --input '{"conversions": [{"co
 
 Result: `ViewTransformConvertTypeResult`; mutation `reversible_pipeline`, confirmation `none`, wait policy `always_wait`.
 
-Status on release: ran once on CLI 2.0.18 through `view.task.add` and was read back with `view data get`; other inputs for this transform are untried.
+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.copy-columns`
 
@@ -882,7 +882,7 @@ Example: `mammoth view transform copy-columns 123 --input '{"copies": [{"source"
 
 Result: `ViewTransformCopyColumnsResult`; 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.
+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.crosstab`
 
@@ -892,7 +892,7 @@ Example: `mammoth view transform crosstab 123 --input '{"rows": ["sample"], "piv
 
 Result: `ViewTransformCrosstabResult`; 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.
+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.date-diff`
 
@@ -902,7 +902,7 @@ Example: `mammoth view transform date-diff 123 --input '{"component": "YEAR", "s
 
 Result: `ViewTransformDateDiffResult`; 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.
+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.delete-columns`
 
@@ -912,7 +912,7 @@ Example: `mammoth view transform delete-columns 123 --input '{"columns": ["Statu
 
 Result: `ViewTransformDeleteColumnsResult`; 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.
+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.discard-duplicates`
 
@@ -922,7 +922,7 @@ Example: `mammoth view transform discard-duplicates 123 --input '{"dataset_id":
 
 Result: `ViewTransformDiscardDuplicatesResult`; mutation `reversible_pipeline`, confirmation `none`, wait policy `always_wait`.
 
-Status on release: ran once on CLI 2.0.18 through `view.task.add` and was read back with `view data get`; other inputs for this transform are untried.
+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.extract-date`
 
@@ -932,7 +932,7 @@ Example: `mammoth view transform extract-date 123 --input '{"column": "Status",
 
 Result: `ViewTransformExtractDateResult`; mutation `reversible_pipeline`, confirmation `none`, wait policy `always_wait`.
 
-Status on release: ran once on CLI 2.0.18 through `view.task.add` and was read back with `view data get`; other inputs for this transform are untried.
+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.fill-missing`
 
@@ -942,7 +942,7 @@ Example: `mammoth view transform fill-missing 123 --input '{"column": "Status",
 
 Result: `ViewTransformFillMissingResult`; mutation `reversible_pipeline`, confirmation `none`, wait policy `always_wait`.
 
-Status on release: ran once on CLI 2.0.18 through `view.task.add` and was read back with `view data get`; other inputs for this transform are untried.
+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.filter`
 
@@ -952,7 +952,7 @@ Example: `mammoth view transform filter 123 --input '{"condition": {"column": "S
 
 Result: `ViewTransformFilterResult`; mutation `reversible_pipeline`, confirmation `none`, wait policy `always_wait`.
 
-Status on release: ran once on CLI 2.0.18 through `view.task.add` and was read back with `view data get`; other inputs for this transform are untried.
+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.generate-sql`
 
@@ -962,7 +962,7 @@ Example: `mammoth view transform generate-sql 123 --input '{"intent": "Summarize
 
 Result: `ViewTransformGenerateSqlResult`; 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.
+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.increment-date`
 
@@ -972,7 +972,7 @@ Example: `mammoth view transform increment-date 123 --input '{"column": "Status"
 
 Result: `ViewTransformIncrementDateResult`; 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.
+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.join`
 
@@ -982,7 +982,7 @@ Example: `mammoth view transform join 123 --input '{"foreign_view": 1, "join_typ
 
 Result: `ViewTransformJoinResult`; mutation `reversible_pipeline`, confirmation `none`, wait policy `always_wait`.
 
-Status on release: ran once on CLI 2.0.18 through `view.task.add` and was read back with `view data get`; other inputs for this transform are untried.
+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.json-extract`
 
@@ -992,7 +992,7 @@ Example: `mammoth view transform json-extract 123 --input '{"column": "Status",
 
 Result: `ViewTransformJsonExtractResult`; 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.
+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.limit-rows`
 
@@ -1002,7 +1002,7 @@ Example: `mammoth view transform limit-rows 123 --input '{"n": 1, "dataset_id":
 
 Result: `ViewTransformLimitRowsResult`; 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.
+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.lookup`
 
@@ -1012,7 +1012,7 @@ Example: `mammoth view transform lookup 123 --input '{"source": "Status", "looku
 
 Result: `ViewTransformLookupResult`; 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.
+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.math`
 
@@ -1022,7 +1022,7 @@ Example: `mammoth view transform math 123 --input '{"expression": "price * quant
 
 Result: `ViewTransformMathResult`; 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.
+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.pivot`
 
@@ -1032,7 +1032,7 @@ Example: `mammoth view transform pivot 123 --input '{"group_by": ["sample"], "ag
 
 Result: `ViewTransformPivotResult`; mutation `reversible_pipeline`, confirmation `none`, wait policy `always_wait`.
 
-Status on release: ran once on CLI 2.0.18 through `view.task.add` and was read back with `view data get`; other inputs for this transform are untried.
+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.rename-columns`
 
@@ -1042,7 +1042,7 @@ Example: `mammoth view transform rename-columns 123 --input '{"renames": {"cust_
 
 Result: `ViewTransformRenameColumnsResult`; mutation `benign_mutation`, confirmation `none`, wait policy `not_async`.
 
-Status on release: untried; it submits through `view.task.add`, but this transform was not among those run.
+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.replace`
 
@@ -1052,7 +1052,7 @@ Example: `mammoth view transform replace 123 --input '{"columns": ["Status"], "f
 
 Result: `ViewTransformReplaceResult`; 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.
+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.set-values`
 
@@ -1062,7 +1062,7 @@ Example: `mammoth view transform set-values 123 --input '{"values": [{"value": "
 
 Result: `ViewTransformSetValuesResult`; mutation `reversible_pipeline`, confirmation `none`, wait policy `always_wait`.
 
-Status on release: ran once on CLI 2.0.18 through `view.task.add` and was read back with `view data get`; other inputs for this transform are untried.
+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.small-large`
 
@@ -1072,7 +1072,7 @@ Example: `mammoth view transform small-large 123 --input '{"function": "SMALL",
 
 Result: `ViewTransformSmallLargeResult`; 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.
+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.sort`
 
@@ -1082,7 +1082,7 @@ Example: `mammoth view transform sort 123 --input '{"order_by": [["Revenue", "DE
 
 Result: `ViewTransformSortResult`; mutation `benign_mutation`, confirmation `none`, wait policy `not_async`.
 
-Status on release: untried; it submits through `view.task.add`, but this transform was not among those run.
+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.split`
 
@@ -1092,7 +1092,7 @@ Example: `mammoth view transform split 123 --input '{"column": "Status", "delimi
 
 Result: `ViewTransformSplitResult`; 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.
+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.substring`
 
@@ -1102,7 +1102,7 @@ Example: `mammoth view transform substring 123 --input '{"column": "Status", "da
 
 Result: `ViewTransformSubstringResult`; 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.
+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.text`
 
@@ -1112,7 +1112,7 @@ Example: `mammoth view transform text 123 --input '{"columns": ["Status"], "data
 
 Result: `ViewTransformTextResult`; mutation `reversible_pipeline`, confirmation `none`, wait policy `always_wait`.
 
-Status on release: ran once on CLI 2.0.18 through `view.task.add` and was read back with `view data get`; other inputs for this transform are untried.
+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.unnest`
 
@@ -1122,7 +1122,7 @@ Example: `mammoth view transform unnest 123 --input '{"columns": ["Status"], "da
 
 Result: `ViewTransformUnnestResult`; 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.
+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.window`
 
@@ -1132,7 +1132,7 @@ Example: `mammoth view transform window 123 --input '{"function": "ROW_NUMBER",
 
 Result: `ViewTransformWindowResult`; mutation `reversible_pipeline`, confirmation `none`, wait policy `always_wait`.
 
-Status on release: ran once on CLI 2.0.18 through `view.task.add` and was read back with `view data get`; other inputs for this transform are untried.
+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.trash`
 

{mammoth_cli-2.0.38 → mammoth_cli-2.0.40}/mammoth_cli/bundled_skill/mammoth-cli/references/input.md

@@ -43,7 +43,7 @@ anything else fails with `invalid_condition` before any request is sent.
 | `view transform filter` | `filter_type` | `SHOW` (keep matches, default), `REMOVE` |
 | `view transform text` | `case` | `UPPER`, `LOWER`, `TITLE`; `trim`: true/false |
 | `view transform convert-type` | `conversions[].to` | `TEXT`, `NUMERIC`, `DATE` |
-| `view transform fill-missing` | `direction` | `LAST_VALUE` (forward fill), `FIRST_VALUE` |
+| `view transform fill-missing` | `direction` | `FIRST_VALUE` (forward fill: previous row), `LAST_VALUE` (back-fill: next row) |
 | `view transform join` | `join_type` | `INNER`, `LEFT`, `RIGHT`, `OUTER` |
 | `view transform set-values` | `column_type` (new column) | `TEXT`, `NUMERIC`, `DATE` |
 

{mammoth_cli-2.0.38 → mammoth_cli-2.0.40}/mammoth_cli/bundled_skill/mammoth-cli/references/recipes/dashboards.md

@@ -65,7 +65,33 @@ correct aggregation for a "distinct people" card under a date filter);
 ID --input '{"body": {"params": {"pages": [{"title": ..., "focus": {...},
 "charts": [...]}]}}}'` adds a page, but that route runs through the LLM
 guard and may drop a unit it cannot evidence (it says so in `data.message`);
-`canvas save` keeps what you wrote.
+`canvas save` keeps what you wrote. When the route refuses a chart (for
+example a `pie` that the data does not support), `data.chart_check.refused`
+names it. A new page that got no charts is removed, and
+`data.chart_check.removed_pages` lists it. Add a chart of a different kind
+(`hbar`, `line`, `table`) for that page.
+
+## Put the money on the board
+
+If the data has money (a price, an amount, revenue or cost), the dashboard
+must show it. A board that shows only counts or quantities has left out the
+number the user most likely wants.
+
+- A money column must be `NUMERIC` first. `view data get` flags a money
+  column that is stored as text in `column_warnings`.
+- A unit price is not revenue. Do not sum a price. If the data has a
+  quantity and a unit price, add a revenue column before you build the
+  board, then chart the sum of that column:
+
+```bash
+mammoth view transform math VIEW_ID --project PROJECT_ID \
+  --input '{"dataset_id":DATASET_ID,"expression":"qty * price","new_column":"revenue"}'
+```
+
+- Put revenue in a KPI (`focus.kpis`, `agg` `sum`, `unit.prefix` for the
+  currency) and in one or more charts (revenue by product, by segment, by
+  month). Rows with an empty price give an empty revenue. Say how many there
+  are in your report.
 
 **Read the bindings back, then the numbers.** `dashboard canvas get` returns
 `data.meta.figures` — `"p1:kpi:2": {"descriptors": {"value": "<id>"}}` per

{mammoth_cli-2.0.38 → mammoth_cli-2.0.40}/mammoth_cli/bundled_skill/mammoth-cli/references/recipes/end-to-end.md

@@ -22,6 +22,8 @@ mammoth view list CUSTOMERS_DS --project PROJECT_ID # -> CUSTOMERS_VIEW
 # 2. look before you change: column names, types, row_count, a sample
 mammoth view get ORDERS_VIEW ORDERS_DS --project PROJECT_ID
 mammoth view data get ORDERS_VIEW ORDERS_DS --project PROJECT_ID
+#   data.column_warnings: text columns of numbers/dates (with the convert-type fix) and blanks;
+#   plan step 3 from them
 
 # 3. clean orders (each call waits for its job; read back after each value change)
 mammoth view transform discard-duplicates ORDERS_VIEW --project PROJECT_ID \
@@ -43,9 +45,10 @@ mammoth view get ORDERS_VIEW ORDERS_DS --project PROJECT_ID   # row_count before
 # 5. join, then check the match rate before building on it
 mammoth view transform join ORDERS_VIEW --project PROJECT_ID \
   --input '{"dataset_id": ORDERS_DS, "foreign_view": CUSTOMERS_VIEW, "foreign_dataset_id": CUSTOMERS_DS, "join_type": "LEFT", "on": [{"left": "customer_id", "right": "customer_id"}], "select": ["region"]}'
-mammoth view data get ORDERS_VIEW ORDERS_DS --project PROJECT_ID
-#   if region is empty/"Unknown" on most rows, the key does not match: compare the two key columns' values
+#   data.join_check: rows_before/rows_after, match_rate, unmatched_rows, unmatched_keys; report them
+#   if many rows are unmatched, the key does not match: compare the two key columns' values
 #   (type, padding, case) with view data get on both views; do not summarise unmatched data
+#   rows_after > rows_before: a key repeats in the other view (use lookup for one value per key)
 
 # 6. deliverable first: export the cleaned, joined rows before any step that replaces them
 mammoth view export csv ORDERS_VIEW --project PROJECT_ID \

{mammoth_cli-2.0.38 → mammoth_cli-2.0.40}/mammoth_cli/bundled_skill/mammoth-cli/references/recipes/transforms.md

@@ -21,9 +21,10 @@ Prefer typed operations such as convert-type, fill-missing, replace, join,
 lookup, filter and math only when the live schema
 lists them. Pick the operation by what it does, not by its name:
 
-- `fill-missing` copies the previous/next row's value into blanks
-  (`direction` = `LAST_VALUE` forward-fill or `FIRST_VALUE`). It cannot write a
-  literal. To fill blanks with a constant (for example `0`), use `set-values`
+- `fill-missing` copies an adjacent row's value into blanks, in the
+  `order_by` order. `direction` `FIRST_VALUE` takes the previous row's value
+  (forward fill, the usual choice); `LAST_VALUE` takes the next row's value
+  (back-fill). It cannot write a literal. To fill blanks with a constant (for example `0`), use `set-values`
   on the existing column with an `IS_EMPTY` condition:
 
 ```bash
@@ -73,6 +74,44 @@ mammoth schema get view.transform.join
 mammoth view transform join VIEW_ID --project PROJECT_ID --input INPUT_JSON
 ```
 
+## What most pipelines look like
+
+These patterns come from how Mammoth pipelines are usually built. Use them
+as defaults, and let the user's request override them:
+
+- Keep it short. Most pipelines have one to three steps and touch a few
+  columns. Add only the steps the deliverable needs.
+- New column or overwrite? `set-values`, `math` and `lookup` take
+  `new_column` (add a column) or `existing_column` (replace the values in
+  place), never both. Overwriting is as common as adding. If the user said
+  "fix", "clean" or "change" a column, use `existing_column`. If they said
+  "add", "calculate" or "flag", use `new_column`. If it is not clear, ask.
+- Joins are nearly always `LEFT` on one key column. Use `INNER`, `RIGHT`,
+  `OUTER` or a key of two or more columns only when the user asks for it or
+  the data needs it, and say why in your report.
+- Check the key before a join or lookup. Most keys go in without a prep
+  step, so a type, case or padding difference shows up as unmatched rows. Read
+  both key columns first (`view data get`) and act on `join_check`.
+- Date steps (`increment-date`, `extract-date`, and `text` on date columns)
+  fail more often than other steps. Before a date step, confirm that the
+  column type is `DATE` (`view get`); if it is `TEXT`, run `convert-type`
+  first. Check the result on a few rows.
+- Convert several columns to the same type in one `convert-type` call (one
+  `conversions` entry for each column), not one call for each column.
+  Upload already types numbers and ISO dates, so read the types (`view get`)
+  first and convert only the columns that are wrong. The CLI skips a column
+  that already has the type (`skipped` in the result).
+- Remove duplicates near the end, after the cleanup and joins, so the check
+  uses the final columns.
+- `filter` also takes a plain-language `prompt` instead of a `condition`.
+  Use a `condition` when the rule is exact (a column, an operator, a value).
+  Use `prompt` only when the user described the rule in words and no exact
+  condition expresses it, then check the kept rows.
+- "Top N" means the largest values first. Use the smallest values first only
+  when the user says "bottom", "lowest" or "smallest".
+- The last step of a pipeline is not a signal that it is finished. Say that
+  the work is done only after you verify the deliverable.
+
 ## Aggregate or summarise
 
 For a grouped summary (totals per region, counts per status) use the typed

{mammoth_cli-2.0.38 → mammoth_cli-2.0.40}/mammoth_cli/bundled_skill/mammoth-cli/references/task-start.md

@@ -9,11 +9,13 @@ or secrets in an argument, prompt, transcript, or checkpoint.
    from PyPI into a fresh environment and verify it:
 
    ```bash
-   python3 -m venv .mammoth && .mammoth/bin/python -m pip install --upgrade mammoth-cli
+   python3 -m venv .mammoth && .mammoth/bin/python -m pip install --no-cache-dir --upgrade mammoth-cli
    .mammoth/bin/mammoth --version      # or: uv tool install mammoth-cli
    ```
 
-   Pin `mammoth-cli==X.Y.Z` when the task names an approved release. Use the
+   Pin `mammoth-cli==X.Y.Z` when the task names an approved release, and
+   check that `mammoth --version` prints it (a pip cache can serve an older
+   release for a few minutes after a new one is published). Use the
    host installer script (`installers/mammoth-install.sh` in the repository)
    only when the operator names it; do not pipe a remote script to a shell on
    your own initiative. The SDK (`mammoth-io`) comes with the CLI. If a later

{mammoth_cli-2.0.38 → mammoth_cli-2.0.40}/mammoth_cli/commands/dashboard.py

@@ -36,6 +36,7 @@ from mammoth_cli.runtime.invocation import Invocation
 from mammoth_cli.runtime.session import open_service, require_project
 from mammoth_cli.services.argspec import arg_spec
 from mammoth_cli.services.command_contract import bind_command_inputs
+from mammoth_cli.services.dashboard_pages import check_added_pages
 from mammoth_cli.services.positionals import resolve_positionals
 
 HandlerResult = tuple[Any, dict[str, Any]]
@@ -671,6 +672,9 @@ def generated_dashboard(invocation: Invocation) -> HandlerResult:
     with open_service(invocation) as (service, auth):
         data = service.call(_symbol(invocation), **kwargs)
         data = _resolve_job(service, invocation, data)
+        if invocation.command_id == "dashboard.pages.add" and "body" in kwargs:
+            requested = kwargs["body"].get("params", {}).get("pages", [])
+            data = check_added_pages(service, positionals["dashboard_id"], requested, data)
     return data, _meta(invocation, auth.workspace_id)
 
 

{mammoth_cli-2.0.38 → mammoth_cli-2.0.40}/mammoth_cli/commands/schema.py

@@ -109,7 +109,7 @@ _COMMAND_DISCOVERY_PURPOSES = {
         "filter rows keep drop exclude remove delete rows where condition subset"
     ),
     "view.transform.generate-sql": (
-        "generate sql from natural language intent question and run it as a task"
+        "generate write sql query from natural language intent question"
     ),
     "view.transform.increment-date": "add subtract days months years to a date column shift",
     "view.transform.join": (