mammoth-cli 2.2.86__tar.gz → 2.2.88__tar.gz

{mammoth_cli-2.2.86 → mammoth_cli-2.2.88}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: mammoth-cli
-Version: 2.2.86
+Version: 2.2.88
 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.44
+Requires-Dist: mammoth-io<0.9,>=0.8.45
 Requires-Dist: platformdirs<5,>=4.10
 Requires-Dist: pydantic<3,>=2.12.5
 Requires-Dist: pyyaml<7,>=6

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

{mammoth_cli-2.2.86 → mammoth_cli-2.2.88}/mammoth_cli/bundled_skill/mammoth-cli/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: mammoth-cli
-version: 2.2.86
+version: 2.2.88
 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."
 ---
 
@@ -90,7 +90,7 @@ mammoth schema find "join two datasets; remove duplicates; build a dashboard"
 | Rank, running total, previous row | `view transform window` |
 | A dashboard, or its PDF or slides | `dashboard v3 generate`, then `chat edit` ([dashboards](references/recipes/dashboards.md)) |
 | Deliver the rows | `view export csv`, `view export postgres`, `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 from an uploaded file or URL is a one-time copy with no source to refresh; say so. Recipe and caveats: [recurring work](references/recipes/scheduling.md) |
+| 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. An upload can't refresh; a URL dataset: `dataset refresh` on demand, never on a schedule; say so. Recipe: [recurring work](references/recipes/scheduling.md) |
 
 Call a find result (or `suggestions` entry) from its `accepted_fields` and
 `agent_example`. Before concluding the CLI cannot do something the web app

{mammoth_cli-2.2.86 → mammoth_cli-2.2.88}/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 781 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 782 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.86 → mammoth_cli-2.2.88}/mammoth_cli/bundled_skill/mammoth-cli/references/command-index.md

@@ -1,6 +1,6 @@
 # Published CLI command catalog
 
-This generated catalog is a lookup table for every command in the published CLI manifest, currently 781; 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 782; 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:
 
@@ -30,7 +30,7 @@ Load only the applicable domain file:
 - [dashboard-published](commands/dashboard-published.md) — 8 published commands
 - [dashboard](commands/dashboard.md) — 104 published commands
 - [data-app](commands/data-app.md) — 12 published commands
-- [dataset](commands/dataset.md) — 27 published commands
+- [dataset](commands/dataset.md) — 28 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

{mammoth_cli-2.2.86 → mammoth_cli-2.2.88}/mammoth_cli/bundled_skill/mammoth-cli/references/commands/dataset.md

@@ -212,6 +212,16 @@ Result: `DatasetListResult`; mutation `read`, confirmation `none`, wait policy `
 
 Status on release: ran once on CLI 2.0.28 — ILG simulation 2026-09-19: exit 0 on release with CLI 2.0.28. Listed the datasets the sends created in the target project. Single invocation only.
 
+### `dataset.refresh`
+
+Run: `mammoth dataset refresh`. Exact input fields: `mammoth schema get dataset.refresh`.
+
+Example: `mammoth dataset refresh 123 --yes`. Illustrative only: append `--yes` after observing an owned target.
+
+Result: `DatasetRefreshResult`; mutation `benign_mutation`, confirmation `prompt_or_yes`, wait policy `always_wait`.
+
+Status on release: untried; no live run recorded.
+
 ### `dataset.rename`
 
 Run: `mammoth dataset rename`. Exact input fields: `mammoth schema get dataset.rename`.

{mammoth_cli-2.2.86 → mammoth_cli-2.2.88}/mammoth_cli/bundled_skill/mammoth-cli/references/recipes/dashboards.md

@@ -59,6 +59,13 @@ tile they do not want), say so in the next `chat edit` prompt in the user's
 words ("show revenue in pounds", "remove the Key insights tile"); the builder
 decides how.
 
+## A month axis
+
+To chart by month from a date, extract `year_month_number` ("2026-10") with
+`view transform extract-date`: it sorts in time order. `year_month`
+("2026, October") is text and a chart axis sorts it alphabetically, April
+before August; use it only when the user asks for that wording.
+
 ## "Per region", "per month", "for each X": one board and a filter control
 
 A request for a board "per <dimension>" (per region, per month, per rep, by
@@ -185,6 +192,11 @@ not publish: `was_published` stays false until you also run
 `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.
+Auto-publish (`auto_publish: true`) republishes **data refreshes only**. A chat
+edit or any other layout change stays in the draft, and `dashboard get` shows
+`is_publish_presentation_pending: true`, until you run `publish-presentation`.
+After editing a live board with auto-publish on, tell the user the layout
+change is not live yet, and publish only if they asked for it.
 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.86 → mammoth_cli-2.2.88}/mammoth_cli/bundled_skill/mammoth-cli/references/recipes/resources.md

@@ -127,6 +127,9 @@ not sufficient. `dataset.create` waits for its asynchronous work; only the
 If the schema does not accept a URL,
 report URL import unsupported; do not silently substitute local processing. A
 4/5/7 envelope is a failed or uncertain operation, not a usable dataset. A
-`weburl` dataset is a one-time copy: it keeps no source details, so it cannot be
-scheduled to refresh (see [recurring work](scheduling.md)); say so rather than
-promising a refreshable source.
+`weburl` dataset keeps its link and can be refreshed on demand (`dataset refresh
+DATASET_ID --yes`, or "Refresh from URL" in the web app; a single CSV only), but
+never on a schedule: `run_data_retrieval` cannot refresh it (see
+[recurring work](scheduling.md)). `dataset list` shows such a dataset as
+`url: <host>`. For a scheduled pull from a URL, use the REST
+API connector. Say so rather than promising a scheduled refresh.

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

@@ -31,8 +31,10 @@ 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).
+Sample a REST source with `connector ds-config create` and `"data_sample":
+true`, as below. It creates no dataset. Do not use `connector connection query`
+for a REST source: it runs only one read-only SQL `SELECT` and refuses the
+endpoint config.
 
 `query` is a **JSON string** (not an object) of the data-source config:
 `endpoint_path`, `http_method` (`GET|POST`), `request_body`, `query_params`,

{mammoth_cli-2.2.86 → mammoth_cli-2.2.88}/mammoth_cli/bundled_skill/mammoth-cli/references/recipes/scheduling.md

@@ -48,9 +48,13 @@ mammoth automation create 'Nightly refresh' --yes --input '{
 }'
 ```
 
-`run_data_retrieval` only refreshes a cloud-connected dataset; a dataset made
-from an uploaded file or a URL (`weburl`) is a one-time copy with no source
-details to refresh from — say so rather than scheduling one.
+`run_data_retrieval` only refreshes a cloud-connected dataset. A dataset made
+from an uploaded file has no source to refresh from. A URL (`weburl`) dataset
+keeps its link and can be refreshed on demand (`dataset refresh DATASET_ID
+--yes`, or "Refresh from URL" in the web app; a single CSV only), but
+not on a schedule. For a
+scheduled pull from a URL, use the REST API connector. Say so rather than
+scheduling a refresh.
 
 That is not the same as "this dataset can never be recurring." A
 file-backed dataset's pipeline re-runs on new data exactly like any other

{mammoth_cli-2.2.86 → mammoth_cli-2.2.88}/mammoth_cli/commands/dashboard.py

@@ -631,9 +631,20 @@ def dashboard_share(invocation: Invocation) -> HandlerResult:
             + _board_findings(invocation, service, auth, dashboard_id),
         )
         data = service.call(_symbol(invocation), **kwargs)
+        if data is None:
+            # The route answers 200 with no body, so the result was ``data: null`` and
+            # the caller could not see whether the share took. Read it back.
+            data = _share_readback(service, dashboard_id)
     return data, _meta(invocation, auth.workspace_id)
 
 
+def _share_readback(service: Any, dashboard_id: int) -> dict[str, Any]:
+    """The board's share state as ``dashboard get`` reports it after a share."""
+    board = _dump_model(service.call(_DASHBOARD_GET, dashboard_id=dashboard_id))
+    board = board if isinstance(board, dict) else {}
+    return {"dashboard_id": dashboard_id, "share": board.get("share")}
+
+
 def _was_published(service: Any, dashboard_id: int) -> bool:
     """Whether the board was ever published; ``dashboard get`` carries ``was_published``."""
     board = _dump_model(service.call(_DASHBOARD_GET, dashboard_id=dashboard_id))

{mammoth_cli-2.2.86 → mammoth_cli-2.2.88}/mammoth_cli/commands/dataset.py

@@ -755,6 +755,8 @@ def dataset_list(invocation: Invocation) -> HandlerResult:
     only the cheap fields, so it holds no row counts or column names: ``view list
     DATASET_ID`` shows a dataset's columns, and ``dataset find --input '{"columns":
     [...]}'`` finds the dataset that has given columns.
+    The result carries ``total``, the project's whole dataset count, so "how many
+    datasets" never needs paging: read ``total`` with the first page's newest names.
     ``full: true`` returns the raw ``{id, name}`` list instead. ``name`` keeps only datasets
     whose name contains it (case-insensitive) across every page, as short rows without
     column lists; ``limit``/``offset`` then page over the matches.
@@ -772,13 +774,26 @@ def dataset_list(invocation: Invocation) -> HandlerResult:
         kwargs["fields"] = DATASET_ROW_FIELDS
     with open_service(invocation) as (service, auth):
         data = service.call(_symbol(invocation), **kwargs)
-    if compact:
-        data = _compact_dataset_list(
-            data, kwargs.get("offset", 0), kwargs.get("sort"), kwargs.get("limit", 100)
-        )
+        if compact:
+            data = _compact_dataset_list(
+                data, kwargs.get("offset", 0), kwargs.get("sort"), kwargs.get("limit", 100)
+            )
+            if isinstance(data, dict) and "shown" in data:
+                data["total"] = _dataset_total(service, project_id, data, kwargs.get("offset", 0))
     return data, _meta(invocation, auth.workspace_id, project_id)
 
 
+def _dataset_total(service: Any, project_id: int, page: dict[str, Any], offset: int) -> int:
+    """The project's whole dataset count. The list route sends none, so a page that
+    is the last one counts itself; otherwise the ids are read once, here, in one call."""
+    if not page.get("more"):
+        return int(offset) + page["shown"]
+    everything = service.call(
+        "mammoth.api.datasets.DatasetsAPI.list_all", project_id=project_id, fields="id"
+    )
+    return len(everything.get("datasets", []))
+
+
 def _dataset_name_search(
     invocation: Invocation, project_id: int, name: str, document: dict[str, Any]
 ) -> HandlerResult:
@@ -1481,6 +1496,27 @@ def dataset_rename(invocation: Invocation) -> HandlerResult:
     return data, _meta(invocation, auth.workspace_id, project_id)
 
 
+def dataset_refresh(invocation: Invocation) -> HandlerResult:
+    """Fetch a URL dataset's link again into the same dataset. Prompt or ``--yes`` required.
+
+    The server refuses a dataset not made from a URL and a URL that serves JSON; its
+    reason reaches the caller. Waits for the job (honoring ``--job-timeout``).
+    """
+    project_id = require_project(invocation)
+    dataset_id = _require_int_positional(invocation, "dataset id")
+    enforce_confirmation(
+        invocation,
+        policy=POLICY_PROMPT_OR_YES,
+        action=f"fetch the link of dataset {dataset_id} again and update its data",
+    )
+    with open_service(invocation) as (service, auth):
+        handle = service.call(_symbol(invocation), dataset_id=dataset_id, project_id=project_id)
+        service.wait_if_job(handle)
+    return {"dataset_id": dataset_id, "refreshed": True}, _meta(
+        invocation, auth.workspace_id, project_id
+    )
+
+
 def dataset_trash(invocation: Invocation) -> HandlerResult:
     """Move one dataset to the project trash (reversible)."""
     project_id = require_project(invocation)

{mammoth_cli-2.2.86 → mammoth_cli-2.2.88}/mammoth_cli/commands/help_summaries.json

@@ -377,6 +377,7 @@
   "dataset.interpretation.confirm": "Preview or confirm how a file that can be read several ways is interpreted.",
   "dataset.interpretation.preview": "Preview or confirm how a file that can be read several ways is interpreted.",
   "dataset.list": "List datasets in the active project, newest first, each with what tells them apart.",
+  "dataset.refresh": "Fetch a URL dataset's link again into the same dataset. Prompt or '--yes' required.",
   "dataset.rename": "Rename a dataset. Dataset id is positional; new name comes from '--input'.",
   "dataset.restore": "Restore a trashed dataset.",
   "dataset.schema-diff": "Compare two datasets' columns and propose the 'batch create' mapping.",

{mammoth_cli-2.2.86 → mammoth_cli-2.2.88}/mammoth_cli/commands/registry.py

@@ -382,6 +382,7 @@ _TARGETS: dict[str, str] = {
     "dataset.interpretation.confirm": "mammoth_cli.commands.dataset:dataset_interpretation",
     "dataset.create": "mammoth_cli.commands.dataset:dataset_create",
     "dataset.create-from-pdf": "mammoth_cli.commands.dataset:dataset_create_from_pdf",
+    "dataset.refresh": "mammoth_cli.commands.dataset:dataset_refresh",
     "dataset.rename": "mammoth_cli.commands.dataset:dataset_rename",
     "dataset.trash": "mammoth_cli.commands.dataset:dataset_trash",
     "dataset.restore": "mammoth_cli.commands.dataset:dataset_restore",

{mammoth_cli-2.2.86 → mammoth_cli-2.2.88}/mammoth_cli/commands/schema.py

@@ -106,6 +106,7 @@ _FIXED_EXAMPLES: dict[str, tuple[tuple[str, ...], dict[str, Any]]] = {
         {"term": "late", "definition": "delivered more than 5 days after shipped_date"},
     ),
     "dataset.definition.remove": (("123", "a1b2c3d4"), {}),
+    "dataset.refresh": (("123",), {}),
     "view.data.drivers": (
         ("123",),
         {

{mammoth_cli-2.2.86 → mammoth_cli-2.2.88}/mammoth_cli/runtime/state.py

@@ -115,6 +115,25 @@ def _unfinished_state(data: dict[str, Any]) -> dict[str, Any] | None:
     }
 
 
+#: Backend codes a get answers for an id a delete just removed, besides a 404. The
+#: dashboard get route checks permission before existence, and a missing dashboard
+#: has no one who may view it: ``dashboard get`` on a deleted id answers ``4PERM002``.
+#: Read straight after OUR successful delete of that id, it means gone; anywhere else
+#: it keeps meaning "no permission".
+_GONE_AFTER_DELETE: dict[str, frozenset[str]] = {
+    "dashboard.delete": frozenset({"4PERM002", "4DASH001"}),
+}
+
+
+def _proves_gone(invocation: Invocation, exc: Exception) -> bool:
+    if not isinstance(exc, CliError):
+        return False
+    if exc.code == CODE_RESOURCE_NOT_FOUND:
+        return True
+    backend_code = (exc.details or {}).get("backend_code")
+    return backend_code in _GONE_AFTER_DELETE.get(invocation.command_id, frozenset())
+
+
 def _build_state(
     invocation: Invocation, data: dict[str, Any], readback: dict[str, Any]
 ) -> dict[str, Any]:
@@ -150,8 +169,7 @@ def _build_state(
         read_by = _read_by_label(read_command_id, resolved_ids)
         if (
             invocation.command_id.endswith(".delete")
-            and isinstance(exc, CliError)
-            and exc.code == CODE_RESOURCE_NOT_FOUND
+            and _proves_gone(invocation, exc)
             and kind == "object"
             and resolved_ids
         ):

{mammoth_cli-2.2.86 → mammoth_cli-2.2.88}/mammoth_cli/services/command_contract.py

@@ -533,6 +533,7 @@ S2_COMMANDS = frozenset(
         "dataset.file-settings.update",
         "dataset.get",
         "dataset.list",
+        "dataset.refresh",
         "dataset.rename",
         "dataset.restore",
         "dataset.trash",

{mammoth_cli-2.2.86 → mammoth_cli-2.2.88}/mammoth_cli/services/listing.py

@@ -15,6 +15,7 @@ from __future__ import annotations
 import json
 from collections.abc import Callable
 from typing import Any
+from urllib.parse import urlsplit
 
 from mammoth_cli.services.stored_stats import stored_facts
 
@@ -75,11 +76,28 @@ def compact_columns(columns: list[tuple[str, Any]], limit: int | None = _MAX_COL
     return ", ".join(shown) + (f" (+{extra} more)" if extra > 0 else "")
 
 
+def _url_host(info: Any) -> str | None:
+    """The host of the link a fetch-from-URL dataset was made from, or None.
+
+    The backend stores such a dataset as source type ``file`` and keeps the link in
+    ``additional_info.ORIGINAL_FILE_PROPS.URL``. Only the host is returned: the path
+    and query can carry secrets.
+    """
+    original = info.get("ORIGINAL_FILE_PROPS") if isinstance(info, dict) else None
+    url = original.get("URL") if isinstance(original, dict) else None
+    return urlsplit(url).hostname if isinstance(url, str) and url else None
+
+
 def source_of(dataset: dict[str, Any]) -> str:
-    """How the dataset's data arrived: the stored source type and, for a file, its name."""
+    """How the dataset's data arrived: the stored source type and, for a file, its name.
+
+    A dataset fetched from a link reads ``url: <host>``.
+    """
     info = dataset.get("additional_info")
     if isinstance(info, dict) and info.get("DATAVIEW_ID") is not None:
         return f"export of view {info['DATAVIEW_ID']}"
+    if host := _url_host(info):
+        return f"url: {host}"
     sources = dataset.get("sources")
     first = sources[0] if isinstance(sources, list) and sources else None
     if not isinstance(first, dict):

{mammoth_cli-2.2.86 → mammoth_cli-2.2.88}/pyproject.toml

@@ -1,13 +1,13 @@
 [project]
 name = "mammoth-cli"
-version = "2.2.86"
+version = "2.2.88"
 description = "Command-line interface for the Mammoth Analytics platform"
 authors = [{name = "Mammoth Analytics", email = "support@mammoth.io"}]
 readme = "README.md"
 license = "LicenseRef-Proprietary"
 requires-python = ">=3.12,<3.15"
 dependencies = [
-    "mammoth-io (>=0.8.44,<0.9)",
+    "mammoth-io (>=0.8.45,<0.9)",
     "typer (>=0.27,<0.28)",
     "rich (>=15,<16)",
     "platformdirs (>=4.10,<5)",

{mammoth_cli-2.2.86 → mammoth_cli-2.2.88}/spec/manifests/commands/dashboard.yaml

@@ -942,8 +942,9 @@ commands:
   pagination_policy: none
   acceptance_evidence: contract_only_no_disposable_fixture
   readback:
-    command: dashboard.list
-    ids: {}
+    command: dashboard.get
+    ids:
+      dashboard_id: positional.0
     kind: object
   live_test: null
   live_exemption_reason: Dashboard mutation has contract coverage but no automated disposable-dashboard

{mammoth_cli-2.2.86 → mammoth_cli-2.2.88}/spec/manifests/commands/dataset.yaml

@@ -247,7 +247,7 @@ commands:
   - CT-DATASET-CREATE-ERROR
   draft_test: null
   undo_test: null
-  known_restrictions: 'ds_creation_type=weburl (dataset_spec.url), clone, or cloud (a file, REST API or database query from a connection); the command waits for the job and returns the new dataset_id. A weburl dataset is a one-time copy that keeps no source details to refresh from, so automation''s run_data_retrieval task cannot refresh it (only a cloud-connected dataset can be refreshed); say so rather than scheduling a refresh for it. The result''s name is the dataset''s real name; when the requested name was taken the server adds a suffix, and requested_name and note say so. Use name, not the name you asked for. To copy a dataset as a new independent one: {"ds_creation_type": "clone", "dataset_spec": {"ds_name": NEW_NAME, "source_ds_id": ID, "clone_dataview_ids": [DEFAULT_VIEW_ID], "exclude_data": false}}, DEFAULT_VIEW_ID being the id in dataset''s `default_view` from view list (other views only when asked); an empty clone_dataview_ids is refused here because it makes a blank view. A clone waits and returns the new dataset_id; never use view export dataset for a plain copy, which leaves a live export on the source. A weburl import names the dataset after the downloaded file: follow it with dataset rename to the name the user picked. To import a file from an SFTP server (or another file connector) as a new dataset: connector connection create sftp, then {"ds_creation_type": "cloud", "dataset_spec": {"connector_key": "sftp", "connection_key": KEY, "query_properties": {"ds_name": NAME, "file_path": PATH_ON_SERVER, "data_pull_file": "Pull same file"}}}. data_pull_file is a string and may be left out, which means "Pull same file" (what the web app does); its only other value is "Pull next file based on name pattern", which also needs folder_path and name_pattern. A pull that finds no file at the path fails the create with the server''s reason; the recipe is recipes/file-import.md. To import from a REST API or Elasticsearch: the connection must exist first (connector connection create generic_rest_api, in the same project); try the query with connector ds-config create (data_sample, creates no dataset) or connector connection query; then {"ds_creation_type": "cloud", "dataset_spec": {"connector_key": "generic_rest_api", "connection_key": KEY, "query_properties": {"ds_name": NAME, "table_name": TABLE, "query": "<JSON string of the endpoint config>"}, "schedule_properties": {"schedule_type": "moment", "first_pull_at": "now", "on_refresh_action": "replace"}, "recurrence_info": {"interval": 1, "start_at": "<future ISO time>"}}}. schedule_properties and recurrence_info are required (without them the job fails with Invalid parameters); on_refresh_action combine appends every refresh, so rows duplicate. The recipe is recipes/rest-api-import.md. To make a dataset from a database query (SQL Server, MySQL, Postgres, ...): connector connection create for the database, try the SELECT with connector connection query (read-only, saves nothing), then connector ds-config create CONNECTOR_KEY CONNECTION_KEY with {"query": SELECT, "table": NAME}; the recipe is recipes/database-import.md. Other ds_creation_type values and dataset_spec shapes: variants beyond the documented path are not qualified.'
+  known_restrictions: 'ds_creation_type=weburl (dataset_spec.url), clone, or cloud (a file, REST API or database query from a connection); the command waits for the job and returns the new dataset_id. A weburl dataset keeps its link and can be refreshed on demand (dataset refresh DATASET_ID --yes, or Refresh from URL in the web app; a single CSV only), but never on a schedule: automation''s run_data_retrieval task cannot refresh it (only a cloud-connected dataset can be refreshed); for a scheduled pull from a URL use the REST API connector. Say so rather than scheduling a refresh for it. The result''s name is the dataset''s real name; when the requested name was taken the server adds a suffix, and requested_name and note say so. Use name, not the name you asked for. To copy a dataset as a new independent one: {"ds_creation_type": "clone", "dataset_spec": {"ds_name": NEW_NAME, "source_ds_id": ID, "clone_dataview_ids": [DEFAULT_VIEW_ID], "exclude_data": false}}, DEFAULT_VIEW_ID being the id in dataset''s `default_view` from view list (other views only when asked); an empty clone_dataview_ids is refused here because it makes a blank view. A clone waits and returns the new dataset_id; never use view export dataset for a plain copy, which leaves a live export on the source. A weburl import names the dataset after the downloaded file: follow it with dataset rename to the name the user picked. To import a file from an SFTP server (or another file connector) as a new dataset: connector connection create sftp, then {"ds_creation_type": "cloud", "dataset_spec": {"connector_key": "sftp", "connection_key": KEY, "query_properties": {"ds_name": NAME, "file_path": PATH_ON_SERVER, "data_pull_file": "Pull same file"}}}. data_pull_file is a string and may be left out, which means "Pull same file" (what the web app does); its only other value is "Pull next file based on name pattern", which also needs folder_path and name_pattern. A pull that finds no file at the path fails the create with the server''s reason; the recipe is recipes/file-import.md. To import from a REST API or Elasticsearch: the connection must exist first (connector connection create generic_rest_api, in the same project); try the query with connector ds-config create (data_sample, creates no dataset; connector connection query takes SQL only and refuses a REST config); then {"ds_creation_type": "cloud", "dataset_spec": {"connector_key": "generic_rest_api", "connection_key": KEY, "query_properties": {"ds_name": NAME, "table_name": TABLE, "query": "<JSON string of the endpoint config>"}, "schedule_properties": {"schedule_type": "moment", "first_pull_at": "now", "on_refresh_action": "replace"}, "recurrence_info": {"interval": 1, "start_at": "<future ISO time>"}}}. schedule_properties and recurrence_info are required (without them the job fails with Invalid parameters); on_refresh_action combine appends every refresh, so rows duplicate. The recipe is recipes/rest-api-import.md. To make a dataset from a database query (SQL Server, MySQL, Postgres, ...): connector connection create for the database, try the SELECT with connector connection query (read-only, saves nothing), then connector ds-config create CONNECTOR_KEY CONNECTION_KEY with {"query": SELECT, "table": NAME}; the recipe is recipes/database-import.md. Other ds_creation_type values and dataset_spec shapes: variants beyond the documented path are not qualified.'
   reviewed_by: primary
 - command_id: dataset.create-from-pdf
   command_path: dataset create-from-pdf
@@ -766,6 +766,52 @@ commands:
     cols; no column lists) with matched, and more with next_offset when cut; limit and offset then
     page over the matches. limit must be at most 100. Without a project use dataset find NAME_SUBSTRING.'
   reviewed_by: primary
+- command_id: dataset.refresh
+  command_path: dataset refresh
+  disposition: command
+  alias_of: null
+  operation_ids:
+  - UpdateDataset
+  positionals:
+  - name: dataset_id
+    type: int
+    required: true
+    metavar: DATASET_ID
+    falls_back_to_field: null
+    help: ID of the dataset.
+  options: []
+  sdk_symbol: mammoth.api.datasets.DatasetsAPI.refresh_from_url
+  sdk_conversion: Call mammoth.api.datasets.DatasetsAPI.refresh_from_url with validated request fields.
+  request_model: DatasetRefreshRequest
+  result_model: DatasetRefreshResult
+  mutation_class: benign_mutation
+  edits_target: true
+  confirmation: prompt_or_yes
+  wait_policy: always_wait
+  pagination_policy: none
+  acceptance_evidence: contract_only_no_disposable_fixture
+  readback:
+    command: dataset.get
+    ids:
+      dataset_id: positional.0
+    kind: object
+  live_test: null
+  live_exemption_reason: No automated disposable-project fixture wired into tests/live yet for this command.
+  contract_fixture: null
+  required_fixture_guard: null
+  secret_fields: []
+  human_example: mammoth dataset refresh DATASET_ID --help
+  agent_example: mammoth dataset refresh 123 --yes
+  unit_tests:
+  - UT-DATASET-REFRESH
+  contract_tests:
+  - CT-DATASET-REFRESH-HUMAN
+  - CT-DATASET-REFRESH-JSON
+  - CT-DATASET-REFRESH-ERROR
+  draft_test: null
+  undo_test: null
+  known_restrictions: Fetches the link of a dataset made from a URL (dataset create with ds_creation_type weburl; dataset list shows it as source url with the link host) again into the same dataset, and waits for the job. Whether the new data replaces or adds to the old follows the dataset's own data addition setting. A dataset not made from a URL is refused, and so is a URL that serves JSON; the server's reason is shown. A single CSV only. It never refreshes on a schedule, and automation run_data_retrieval cannot refresh it; for a scheduled pull from a URL use the REST API connector.
+  reviewed_by: primary
 - command_id: dataset.rename
   command_path: dataset rename
   disposition: command

{mammoth_cli-2.2.86 → mammoth_cli-2.2.88}/spec/manifests/commands/view.yaml

@@ -5176,7 +5176,9 @@ commands:
   draft_test: LT-VIEW-TRANSFORM-EXTRACT-DATE-DRAFT
   undo_test: LT-VIEW-TRANSFORM-EXTRACT-DATE-UNDO
   known_restrictions: 'Observe first: `view get VIEW_ID` to confirm the column type is DATE (run convert-type
-    first if TEXT) and `view data get` to check a few values.'
+    first if TEXT) and `view data get` to check a few values. For a month bucket use `year_month_number`
+    ("2026-10"), which sorts in time order; `year_month` ("2026, October") sorts alphabetically on a chart
+    axis.'
   reviewed_by: primary
 - command_id: view.transform.fill-missing
   command_path: view transform fill-missing

{mammoth_cli-2.2.86 → mammoth_cli-2.2.88}/spec/manifests/edits-target.source.yaml

@@ -131,6 +131,7 @@ edits_target_commands:
 - dataset.file-settings.undo
 - dataset.file-settings.update
 - dataset.interpretation.confirm
+- dataset.refresh
 - dataset.rename
 - dataset.restore
 - dataset.trash

{mammoth_cli-2.2.86 → mammoth_cli-2.2.88}/spec/manifests/sdk-catalog.source.yaml

@@ -3010,6 +3010,13 @@ sdk_methods:
   wait_policy: null
   pagination_policy: null
   openapi_operation_ids: []
+- sdk_symbol: mammoth.api.datasets.DatasetsAPI.refresh_from_url
+  canonical_command: dataset.refresh
+  alias_of: null
+  mutation_class: benign_mutation
+  wait_policy: always_wait
+  pagination_policy: none
+  openapi_operation_ids: []
 - sdk_symbol: mammoth.api.datasets.DatasetsAPI.rename
   canonical_command: dataset.rename
   alias_of: null

{mammoth_cli-2.2.86 → mammoth_cli-2.2.88}/spec/manifests/sdk-methods.yaml

@@ -1,5 +1,5 @@
 manifest_schema_version: 1
-method_count: 800
+method_count: 801
 generator_version: '1'
 methods:
 - sdk_symbol: mammoth._mixins._advanced_ops.AdvancedOpsMixin.add_sql
@@ -3256,9 +3256,9 @@ methods:
   reviewed_by: primary
 - sdk_symbol: mammoth.api.dashboards.DashboardsAPI.embed_config_set
   implementation_origin: mammoth.api.dashboards.DashboardsAPI.embed_config_set
-  signature: 'embed_config_set(self, dashboard_id: ''int'', mode: "Literal[''key'', ''signed'']" = ''key'',
-    allow_any_origin: ''bool'' = True, allowed_origins: ''_list[str] | None'' = None, appearance: ''dict[str,
-    Any] | None'' = None, snippet: ''dict[str, Any] | None'' = None) -> ''EmbedConfigResponse'''
+  signature: 'embed_config_set(self, dashboard_id: ''int'', mode: "Literal[''key'', ''signed''] | None"
+    = None, allow_any_origin: ''bool | None'' = None, allowed_origins: ''_list[str] | None'' = None, appearance:
+    ''dict[str, Any] | None'' = None, snippet: ''dict[str, Any] | None'' = None) -> ''EmbedConfigResponse'''
   openapi_operation_ids:
   - PutEmbedConfig
   canonical_command: dashboard.embed.config.set
@@ -5501,6 +5501,19 @@ methods:
   pagination_policy: null
   secret_fields: []
   reviewed_by: primary
+- sdk_symbol: mammoth.api.datasets.DatasetsAPI.refresh_from_url
+  implementation_origin: mammoth.api.datasets.DatasetsAPI.refresh_from_url
+  signature: 'refresh_from_url(self, dataset_id: ''int'', workspace_id: ''int | None'' = None, project_id:
+    ''int | None'' = None) -> ''dict[str, Any]'''
+  openapi_operation_ids: []
+  canonical_command: dataset.refresh
+  alias_of: null
+  no_command_reason: null
+  mutation_class: benign_mutation
+  wait_policy: always_wait
+  pagination_policy: none
+  secret_fields: []
+  reviewed_by: primary
 - sdk_symbol: mammoth.api.datasets.DatasetsAPI.remove_definition
   implementation_origin: mammoth.api.datasets.DatasetsAPI.remove_definition
   signature: 'remove_definition(self, dataset_id: ''int'', definition_id: ''str'', workspace_id: ''int