mammoth-cli 2.0.67__tar.gz → 2.0.69__tar.gz

{mammoth_cli-2.0.67 → mammoth_cli-2.0.69}/PKG-INFO

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

{mammoth_cli-2.0.67 → mammoth_cli-2.0.69}/mammoth_cli/bundled_skill/mammoth-cli/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: mammoth-cli
-version: 2.0.67
+version: 2.0.69
 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."
 ---
 
@@ -85,7 +85,8 @@ mammoth view transform --help              # every data transformation
 | Deliver the rows | `view export csv`, `view export postgres` (and other destinations), `view export dataset` |
 | Run something on a schedule or on new data (refresh, append, alert) | `automation create`: a condition (`at_specific_time`, new file in a folder, ...) and tasks (`run_data_retrieval`, `append_data`, `send_an_alert`, `pull_cloud_files`). `schedule create` only pulls a connector's data. A dataset made from an uploaded file has no source to refresh from; say so. Full recipe, including a known `automation get` backend caveat: [recurring work](references/recipes/scheduling.md) |
 
-A search with no full match returns `suggestions` and a `hint`. Before you
+Call a find result (or `suggestions` entry) from its `accepted_fields` and
+`agent_example`. Before you
 conclude the CLI cannot do something the web app does, check
 `view transform --help` and "View settings, and what has no command" in
 [about Mammoth](references/about-mammoth.md). Do not switch to the web app
@@ -177,10 +178,10 @@ your report. If no column links the files, ask before you combine them.
   "limit": 50}`.
 - A timeout, exit 7 or interruption does not prove failure; reconcile an
   `outcome_unknown` (`job get`, `view task list`) before replaying.
-- Before you report, run `mammoth project check PROJECT_ID`. Its `to_report`
-  has one line for each open finding in every view and dashboard (blanks,
-  text numbers, money not shown, columns a dashboard cannot see). Fix each
-  one, or give it one line in the report.
+- Check an answer with no write against the question (a trend: time
+  buckets, a partial period named); no `project check`.
+- After a write, run `mammoth project check PROJECT_ID` and fix each
+  `to_report` line, or give it one line in the report.
 - Run the [report checklist](references/report-checklist.md) before stating
   a number or calling a step done. When files here disagree,
   [capabilities](references/capabilities.md) wins over a recipe, and a recipe

{mammoth_cli-2.0.67 → mammoth_cli-2.0.69}/mammoth_cli/commands/schema.py

@@ -257,7 +257,7 @@ _COMMAND_DISCOVERY_PURPOSES = {
     # The web app's column Explore cards: what is trending, how a column is
     # spread, its top values, a count over time.
     "view.data.explore": (
-        "explore trend trends trending over time per day week month quarter year "
+        "explore trend trends trending over time per day week month quarter year by date "
         "distribution spread histogram top most common frequent values breakdown share "
         "percentage profile"
     ),
@@ -1361,6 +1361,19 @@ def brief_schema(entry: dict[str, Any]) -> dict[str, Any]:
     return brief
 
 
+def _inline_call_detail(entries: list[dict[str, Any]]) -> None:
+    """Add each entry's compact accepted fields and agent example in place."""
+    for entry in entries:
+        record = command_by_id(entry["command_id"])
+        if record is None:
+            continue
+        fields = _compact_accepted_fields(record)
+        if fields is not None:
+            entry["accepted_fields"] = fields
+        if record.get("agent_example"):
+            entry["agent_example"] = record["agent_example"]
+
+
 def find_schemas(
     query: str,
     *,
@@ -1471,17 +1484,7 @@ def find_schemas(
     )
     total_matches = len(ranked_matches)
     page = [match for _, match in ranked_matches[offset : offset + bounded_limit]]
-    for rank, match in enumerate(page, start=offset):
-        if rank >= _INLINE_DETAIL_COUNT:
-            break
-        match_record = command_by_id(match["command_id"])
-        if match_record is None:
-            continue
-        fields = _compact_accepted_fields(match_record)
-        if fields is not None:
-            match["accepted_fields"] = fields
-        if match_record.get("agent_example"):
-            match["agent_example"] = match_record["agent_example"]
+    _inline_call_detail(page[: max(0, _INLINE_DETAIL_COUNT - offset)])
     has_more = offset + len(page) < total_matches
     continuation = (
         {
@@ -1508,6 +1511,9 @@ def find_schemas(
             {**entry, "matched_terms": matched}
             for _, _, entry, matched in near_misses[:_MAX_SUGGESTIONS]
         ]
+        # A goal phrased in the user's words rarely carries every term; the
+        # best near misses still say how to call them, so one find suffices.
+        _inline_call_detail(result["suggestions"][:_INLINE_DETAIL_COUNT])
         result["hint"] = _NO_MATCH_HINT
     return result
 

{mammoth_cli-2.0.67 → mammoth_cli-2.0.69}/mammoth_cli/commands/view.py

@@ -957,8 +957,18 @@ def _build_pivot_fields(
     fields: dict[str, Any] = {"aggregations": resolved_aggregations}
     group_by = document.get("group_by")
     if group_by:
-        fields["group_by"] = [column_map.get(column, column) for column in group_by]
-        as_map.update({f"group_{index}": column for index, column in enumerate(group_by)})
+        # A string groups by the column's values; {column, truncate|resolution}
+        # buckets a DATE (DAY..YEAR) or NUMERIC column first, like Explore.
+        columns = [item["column"] if isinstance(item, dict) else item for item in group_by]
+        fields["group_by"] = [
+            (
+                {**item, "column": column_map.get(item["column"], item["column"])}
+                if isinstance(item, dict)
+                else column_map.get(item, item)
+            )
+            for item in group_by
+        ]
+        as_map.update({f"group_{index}": column for index, column in enumerate(columns)})
     return fields, as_map
 
 

{mammoth_cli-2.0.67 → mammoth_cli-2.0.69}/pyproject.toml

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

{mammoth_cli-2.0.67 → mammoth_cli-2.0.69}/spec/manifests/commands/view.yaml

@@ -1136,7 +1136,11 @@ commands:
   known_restrictions: 'Read-only: computes and returns an aggregated result without adding a task to
     the view''s pipeline or otherwise changing it. Pass exactly one of ''aggregations'' (a PIVOT
     group-by; ''group_by'' is optional) or ''metric'' (a single METRIC value). ''function'' is one of
-    SUM, COUNT, AVG, MIN, MAX.'
+    SUM, COUNT, AVG, MIN, MAX, STDDEV, DISTINCT_COUNT. A group_by item is a column name, or
+    {"column": C, "truncate": DAY|WEEK|MONTH|QUARTER|YEAR} to bucket a DATE (a trend over time),
+    or {"column": C, "resolution": N} to bucket a NUMERIC; grouping by a raw date gives one row per
+    day. A metric is a number: only COUNT and DISTINCT_COUNT work on a DATE or TEXT column. For one
+    column''s trend, top values or spread, view data explore is the shorter call.'
   reviewed_by: primary
 - command_id: view.data.explore
   command_path: view data explore