mammoth-cli 2.0.39__tar.gz → 2.0.41__tar.gz

{mammoth_cli-2.0.39 → mammoth_cli-2.0.41}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: mammoth-cli
-Version: 2.0.39
+Version: 2.0.41
 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.39 → mammoth_cli-2.0.41}/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.39"
+__version__ = "2.0.41"
 
 # The versioned machine output envelope contract.
 SCHEMA_VERSION = 1

{mammoth_cli-2.0.39 → mammoth_cli-2.0.41}/mammoth_cli/bundled_skill/mammoth-cli/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: mammoth-cli
-version: 2.0.39
+version: 2.0.41
 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,10 +93,11 @@ 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. 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.
+1. Upload every file. Each upload result carries a `view` preview of what
+   Mammoth made of the file (`view_id`, column types, sample rows,
+   `column_warnings`, and `before_dashboard`). Read every view in Mammoth, not
+   the local files: `view data get VIEW_ID` for each one. The warnings list
+   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.
@@ -104,14 +105,22 @@ dashboard from t_a and t_b"). Work it out from the data before you build:
    case and padding (`text`), no blanks (`set-values`, `filter`).
 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), then decide on blanks (fill, filter, or keep and
-   say so). A text `price` cannot be summed on a dashboard.
+   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)).
+6. If the data has money, add it before you make the dashboard: `revenue`
+   (`math`, `qty * price`, `new_column`), the `fix` in `before_dashboard`.
+   A dashboard sees only the columns the view had when it was made.
+7. Build the dashboard from the joined view
+   ([dashboards](references/recipes/dashboards.md)) and chart the sum of
+   revenue. Do not sum a unit price. `create-blank`, `canvas save` and
+   `pages add` return `deliverable_check`: fix each warning, or say in the
+   report why not.
 
 For the defaults that most pipelines use (new column or overwrite, `LEFT`
 joins, date steps), see

{mammoth_cli-2.0.39 → mammoth_cli-2.0.41}/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.39 → mammoth_cli-2.0.41}/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.39 → mammoth_cli-2.0.41}/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.39 → mammoth_cli-2.0.41}/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.39 → mammoth_cli-2.0.41}/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.39 → mammoth_cli-2.0.41}/mammoth_cli/bundled_skill/mammoth-cli/references/recipes/dashboards.md

@@ -65,7 +65,42 @@ 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"}'
+```
+
+- Add every column the board needs before `create-blank`. A dashboard sees
+  only the columns the view had when the dashboard was made: `pages add`
+  refuses a later column ("isn't a measure in this data"). If you added it
+  after, make a new dashboard and delete the old one if you made it for this
+  task. The upload result's `before_dashboard` names the column to add.
+- 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.
+- `create-blank`, `canvas save` and `pages add` return `deliverable_check`:
+  `money_not_shown` (with the `math` command in `fix`), `unit_price_summed`,
+  and one `blank_values` entry for each column on the board that has blanks.
+  Fix each warning, or say in your report why you kept it.
 
 **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.39 → mammoth_cli-2.0.41}/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
@@ -97,6 +98,9 @@ as defaults, and let the user's request override them:
   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`.

{mammoth_cli-2.0.39 → mammoth_cli-2.0.41}/mammoth_cli/commands/dashboard.py

@@ -16,6 +16,8 @@ from typing import Any
 from mammoth.models.dashboards import AddPagesSpec
 from pydantic import ValidationError
 
+from mammoth_cli.commands.view import view_profiles
+from mammoth_cli.context import profiles
 from mammoth_cli.errors.envelope import (
     CODE_INVALID_ARGUMENT,
     CODE_MISSING_ARGUMENT,
@@ -25,6 +27,7 @@ from mammoth_cli.errors.envelope import (
     CliError,
 )
 from mammoth_cli.manifest.loader import command_by_id
+from mammoth_cli.runtime import parents
 from mammoth_cli.runtime.confirm import (
     POLICY_CONFIRM_TARGET,
     POLICY_NONE,
@@ -33,9 +36,16 @@ from mammoth_cli.runtime.confirm import (
     enforce_confirmation,
 )
 from mammoth_cli.runtime.invocation import Invocation
-from mammoth_cli.runtime.session import open_service, require_project
+from mammoth_cli.runtime.session import open_service, require_project, resolved_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.dashboard_review import (
+    CANVAS_GET,
+    NEW_COLUMN_NOTE,
+    has_profiles,
+    review,
+)
 from mammoth_cli.services.positionals import resolve_positionals
 
 HandlerResult = tuple[Any, dict[str, Any]]
@@ -671,9 +681,71 @@ 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)
+        if invocation.command_id in _REVIEWED_COMMANDS:
+            data = _with_deliverable_check(invocation, service, auth, positionals, data)
     return data, _meta(invocation, auth.workspace_id)
 
 
+#: Authoring steps whose result carries ``deliverable_check``.
+_REVIEWED_COMMANDS = frozenset(
+    {"dashboard.create-blank", "dashboard.canvas.save", "dashboard.pages.add"}
+)
+
+
+def _with_deliverable_check(
+    invocation: Invocation, service: Any, auth: Any, positionals: dict[str, Any], data: Any
+) -> Any:
+    """Add ``deliverable_check`` (money shown? blanks decided?) to an authoring result.
+
+    One canvas read; advice only, so a failed read leaves the result as it was.
+    """
+    if hasattr(data, "model_dump"):
+        data = data.model_dump(mode="json")
+    if not isinstance(data, dict):
+        return data
+    dashboard_id = positionals.get("dashboard_id") or data.get("id")
+    if not isinstance(dashboard_id, int):
+        return data
+    try:
+        canvas_doc = service.call(CANVAS_GET, dashboard_id=dashboard_id)
+        if hasattr(canvas_doc, "model_dump"):
+            canvas_doc = canvas_doc.model_dump(mode="json")
+        source = (canvas_doc.get("canvas") or {}).get("dataset") or {}
+        view_id = source.get("dataview_id")
+        profile = invocation.profile or profiles.get_selected()
+        dataset_id = (
+            parents.lookup(profile, auth.workspace_id, view_id)
+            if isinstance(view_id, int)
+            else None
+        )
+        fallback = None
+        if not has_profiles(canvas_doc) and isinstance(view_id, int) and dataset_id is not None:
+            fallback = view_profiles(service, dataset_id, view_id, resolved_project(invocation))
+        warnings = review(canvas_doc, dataset_id, fallback)
+    except Exception:  # noqa: BLE001 -- advice must never fail the authoring step
+        return data
+    if warnings:
+        data = {
+            **data,
+            "deliverable_check": {
+                "warnings": warnings,
+                "note": (
+                    "Fix these before you report the dashboard as done, or say in your "
+                    "report why not."
+                    + (
+                        " " + NEW_COLUMN_NOTE
+                        if any("fix" in warning for warning in warnings)
+                        else ""
+                    )
+                ),
+            },
+        }
+    return data
+
+
 def dashboard_assess_twb(invocation: Invocation) -> HandlerResult:
     """Assess a local Tableau workbook through the SDK multipart seam."""
     file_path = _require_str_positional(invocation, "file")

{mammoth_cli-2.0.39 → mammoth_cli-2.0.41}/mammoth_cli/commands/file.py

@@ -15,6 +15,8 @@ from collections.abc import Callable
 from pathlib import Path
 from typing import Any
 
+from mammoth_cli.commands.view import upload_preview
+from mammoth_cli.context import profiles
 from mammoth_cli.errors.envelope import (
     CODE_INVALID_ARGUMENT,
     CODE_MISSING_ARGUMENT,
@@ -24,6 +26,7 @@ from mammoth_cli.errors.envelope import (
     CliError,
 )
 from mammoth_cli.manifest.loader import command_by_id
+from mammoth_cli.runtime import parents
 from mammoth_cli.runtime.confirm import (
     POLICY_CONFIRM_TARGET,
     POLICY_PROMPT_OR_YES,
@@ -226,6 +229,18 @@ def file_upload(invocation: Invocation) -> HandlerResult:
         # ambiguous date column lands in ``need_action`` with no view. Report
         # the status the platform holds for each dataset, not an assumed one.
         result = _upload_result(data, lambda dataset_id: _dataset_status(service, dataset_id))
+        project_id = resolved_project(invocation)
+        for entry in result["datasets"]:
+            if entry.get("status") != "ready":
+                continue
+            preview = upload_preview(service, int(entry["id"]), project_id)
+            if preview is not None:
+                entry["view"] = preview
+                parents.remember(
+                    invocation.profile or profiles.get_selected(),
+                    auth.workspace_id,
+                    {preview["view_id"]: int(entry["id"])},
+                )
     return result, _meta(invocation, auth.workspace_id, resolved_project(invocation))