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

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

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: mammoth-cli
-Version: 2.0.41
+Version: 2.0.42
 Summary: Command-line interface for the Mammoth Analytics platform
 Project-URL: homepage, https://mammoth.io
 Project-URL: repository, https://github.com/EdgeMetric/mammothsdk

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

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

@@ -1,6 +1,6 @@
 ---
 name: mammoth-cli
-version: 2.0.41
+version: 2.0.42
 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."
 ---
 
@@ -95,9 +95,10 @@ dashboard from t_a and t_b"). Work it out from the data before you build:
 
 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.
+   `column_warnings`, and `before_dashboard`). Do not open the local files
+   (`cat`, `head`): what counts is what Mammoth made of them. Run `view data
+   get VIEW_ID` for each view. 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.

{mammoth_cli-2.0.41 → mammoth_cli-2.0.42}/mammoth_cli/bundled_skill/mammoth-cli/references/report-checklist.md

@@ -8,6 +8,7 @@ Every "yes" must point at a command you ran in this task and its response.
 | State rows in and rows out for every step that can change row count (filter, discard-duplicates, join, limit, unnest, pivot) | `view data get` or `view get` (`row_count`) before and after the step, or the `view data get` around a set-values |
 | Read back every value-changing transform | `view data get VIEW_ID DATASET_ID` (full page; `view data query` with `limit`/`condition` for a slice) after the job reached `success`; the sample shows the intended change and nothing else changed |
 | No measure column is all-zero, all-null, or all one value after a transform | inspect the readback sample; an all-`0` / all-`Unknown` column means the condition or column mapping was wrong, not that the data is like that |
+| Decide on every blank the deliverable uses | one report line for each `blank_values` entry (from the upload, a data read or `deliverable_check`), in every view: the column, the count, and filled, filtered, or kept and why. Kept is a decision only when you write it down |
 | A join states its match rate and explains unmatched rows | row count before/after, `IS_EMPTY` filter count on a right-side column, and the key columns named exactly as both view schemas show them |
 | Group counts add up | Σ of per-group counts from a pivot/crosstab equals the source row count (or nulls in the group key explain the difference) |
 | Every job you submitted reached a terminal state | `job get JOB_ID` shows `success`; report anything else as failed/unknown, not done |

{mammoth_cli-2.0.41 → mammoth_cli-2.0.42}/pyproject.toml

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