mammoth-cli 2.2.10__tar.gz → 2.2.12__tar.gz

{mammoth_cli-2.2.10 → mammoth_cli-2.2.12}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: mammoth-cli
-Version: 2.2.10
+Version: 2.2.12
 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.9,>=0.8.11
+Requires-Dist: mammoth-io<0.9,>=0.8.12
 Requires-Dist: platformdirs<5,>=4.10
 Requires-Dist: pydantic<3,>=2.12.5
 Requires-Dist: pyyaml<7,>=6

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

{mammoth_cli-2.2.10 → mammoth_cli-2.2.12}/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 633 commands. 504 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 645 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:
 
@@ -17,9 +17,9 @@ The typed `view transform *` commands all submit through `view.task.add` (`renam
 
 | Family | Commands | Ran once | Not supported | Untried |
 |---|---|---|---|---|
-| `dashboard` | 122 | 81 | 1 | 40 |
+| `dashboard` | 131 | 81 | 1 | 49 |
 | `support` | 66 | 9 | 0 | 57 |
-| `view` | 62 | 58 | 0 | 4 |
+| `view` | 63 | 58 | 0 | 5 |
 | `billing` | 24 | 4 | 0 | 20 |
 | `connector` | 22 | 3 | 0 | 19 |
 | `workspace` | 20 | 7 | 0 | 13 |
@@ -28,16 +28,16 @@ The typed `view transform *` commands all submit through `view.task.add` (`renam
 | `workflow` | 16 | 9 | 0 | 7 |
 | `parameter` | 14 | 7 | 0 | 7 |
 | `data-app` | 12 | 1 | 0 | 11 |
+| `browse` | 9 | 1 | 0 | 8 |
 | `automation` | 8 | 3 | 0 | 5 |
-| `browse` | 8 | 1 | 0 | 7 |
 | `folder` | 8 | 8 | 0 | 0 |
 | `snippet` | 8 | 6 | 0 | 2 |
 | `user` | 7 | 3 | 0 | 4 |
 | `webhook` | 7 | 5 | 0 | 2 |
 | `addon` | 6 | 0 | 0 | 6 |
+| `agent` | 6 | 1 | 0 | 5 |
 | `batch` | 6 | 6 | 0 | 0 |
 | `file` | 6 | 5 | 0 | 1 |
-| `agent` | 5 | 1 | 0 | 4 |
 | `ai` | 5 | 3 | 0 | 2 |
 | `annotation` | 5 | 1 | 0 | 4 |
 | `client-app` | 5 | 0 | 0 | 5 |

{mammoth_cli-2.2.10 → mammoth_cli-2.2.12}/mammoth_cli/bundled_skill/mammoth-cli/references/command-index.md

@@ -1,19 +1,19 @@
 # Published CLI command catalog
 
-This generated catalog is a lookup table for every command in the published CLI manifest, currently 633; 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 645; 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:
 
 - [activity](commands/activity.md) — 2 published commands
 - [addon](commands/addon.md) — 7 published commands
-- [agent](commands/agent.md) — 14 published commands
+- [agent](commands/agent.md) — 15 published commands
 - [ai](commands/ai.md) — 5 published commands
 - [annotation](commands/annotation.md) — 5 published commands
 - [auth](commands/auth.md) — 3 published commands
 - [automation](commands/automation.md) — 8 published commands
 - [batch](commands/batch.md) — 7 published commands
 - [billing](commands/billing.md) — 25 published commands
-- [browse](commands/browse.md) — 8 published commands
+- [browse](commands/browse.md) — 9 published commands
 - [calc](commands/calc.md) — 1 published commands
 - [capability](commands/capability.md) — 3 published commands
 - [client-app](commands/client-app.md) — 5 published commands
@@ -21,9 +21,10 @@ Load only the applicable domain file:
 - [config](commands/config.md) — 4 published commands
 - [connector](commands/connector.md) — 22 published commands
 - [context](commands/context.md) — 3 published commands
-- [dashboard-qa](commands/dashboard-qa.md) — 13 published commands
+- [dashboard-qa](commands/dashboard-qa.md) — 14 published commands
 - [dashboard-template](commands/dashboard-template.md) — 12 published commands
-- [dashboard](commands/dashboard.md) — 98 published commands
+- [dashboard-style](commands/dashboard-style.md) — 10 published commands
+- [dashboard](commands/dashboard.md) — 96 published commands
 - [data-app](commands/data-app.md) — 12 published commands
 - [dataset](commands/dataset.md) — 21 published commands
 - [doctor](commands/doctor.md) — 1 published commands
@@ -48,7 +49,7 @@ Load only the applicable domain file:
 - [user](commands/user.md) — 8 published commands
 - [version](commands/version.md) — 1 published commands
 - [view-transform](commands/view-transform.md) — 32 published commands
-- [view](commands/view.md) — 90 published commands
+- [view](commands/view.md) — 91 published commands
 - [webhook](commands/webhook.md) — 7 published commands
 - [workflow](commands/workflow.md) — 16 published commands
 - [workspace](commands/workspace.md) — 26 published commands

{mammoth_cli-2.2.10 → mammoth_cli-2.2.12}/mammoth_cli/bundled_skill/mammoth-cli/references/commands/agent.md

@@ -141,3 +141,13 @@ Example: `mammoth agent session set-visibility resource-123 --input '{"visibilit
 Result: `AgentSessionSetVisibilityResult`; mutation `benign_mutation`, confirmation `none`, wait policy `not_async`.
 
 Status on release: untried; no live run recorded.
+
+### `agent.turn.cancel`
+
+Run: `mammoth agent turn cancel`. Exact input fields: `mammoth schema get agent.turn.cancel`.
+
+Example: `mammoth agent turn cancel resource-123`. Placeholders are illustrative; resolve IDs and input from observed reads.
+
+Result: `AgentTurnCancelResult`; mutation `benign_mutation`, confirmation `none`, wait policy `not_async`.
+
+Status on release: untried; no live run recorded.

{mammoth_cli-2.2.10 → mammoth_cli-2.2.12}/mammoth_cli/bundled_skill/mammoth-cli/references/commands/browse.md

@@ -52,6 +52,16 @@ Result: `BrowseResourcesResult`; mutation `read`, confirmation `none`, wait poli
 
 Status on release: untried; no live run recorded.
 
+### `browse.resources.bulk`
+
+Run: `mammoth browse resources bulk`. Exact input fields: `mammoth schema get browse.resources.bulk`.
+
+Example: `mammoth browse resources bulk --input '{"items": [["dataview", 42]]}'`. Placeholders are illustrative; resolve IDs and input from observed reads.
+
+Result: `BrowseResourcesBulkResult`; mutation `read`, confirmation `none`, wait policy `not_async`.
+
+Status on release: untried; no live run recorded.
+
 ### `browse.root`
 
 Run: `mammoth browse root`. Exact input fields: `mammoth schema get browse.root`.

{mammoth_cli-2.2.10 → mammoth_cli-2.2.12}/mammoth_cli/bundled_skill/mammoth-cli/references/commands/dashboard-qa.md

@@ -42,6 +42,16 @@ Result: `DashboardQaFeedbackResult`; mutation `benign_mutation`, confirmation `n
 
 Status on release: ran once on CLI 2.0.12 — Dashboard sweep 2026-09-18: exit 0 on release with CLI 2.0.12; result keys: session. recorded thumbs-up feedback on message id=2 Single invocation only; no error-path or variant coverage.
 
+### `dashboard.qa.insights`
+
+Run: `mammoth dashboard qa insights`. Exact input fields: `mammoth schema get dashboard.qa.insights`.
+
+Example: `mammoth dashboard qa insights 123`. Placeholders are illustrative; resolve IDs and input from observed reads.
+
+Result: `DashboardQaInsightsResult`; mutation `read`, confirmation `none`, wait policy `not_async`.
+
+Status on release: untried; no live run recorded.
+
 ### `dashboard.qa.session.create`
 
 Run: `mammoth dashboard qa session create`. Exact input fields: `mammoth schema get dashboard.qa.session.create`.

mammoth_cli-2.2.12/mammoth_cli/bundled_skill/mammoth-cli/references/commands/dashboard-style.md

@@ -0,0 +1,103 @@
+# `dashboard-style` commands
+
+Every command returns the standard JSON envelope. On nonzero exit, read the error envelope and its `recovery_commands`; do not guess request fields. "Status on release" is joined from `docs/release-capability-matrix.json`: *ran once* means one bounded live run succeeded on the named CLI release, *untried* means nobody has run it (use it normally: confirm writes with the user, check the result afterwards), *not supported* means the backend refuses it. When this file disagrees with [capabilities](../capabilities.md) or a recipe, they win. Envelope shapes: [machine output](../machine-output.md).
+
+### `dashboard.style.custom.create`
+
+Run: `mammoth dashboard style custom create`. Exact input fields: `mammoth schema get dashboard.style.custom.create`.
+
+Example: `mammoth dashboard style custom create --input '{"body": {"params": {"signals": {}}}}'`. Placeholders are illustrative; resolve IDs and input from observed reads.
+
+Result: `DashboardStyleCustomCreateResult`; mutation `benign_mutation`, confirmation `none`, wait policy `not_async`.
+
+Status on release: ran once on CLI 2.0.12 — Dashboard sweep 2026-09-18: exit 0 on release with CLI 2.0.12; result keys: style. created custom style id=1 with full unredacted colors/font/viz (no tokens field passed) Single invocation only; no error-path or variant coverage.
+
+### `dashboard.style.custom.delete`
+
+Run: `mammoth dashboard style custom delete`. Exact input fields: `mammoth schema get dashboard.style.custom.delete`.
+
+Example: `mammoth dashboard style custom delete resource-123`. Illustrative only: append `--yes` after observing an owned target.
+
+Result: `DashboardStyleCustomDeleteResult`; mutation `destructive`, confirmation `prompt_or_yes`, wait policy `not_async`.
+
+Status on release: ran once on CLI 2.0.12 — Dashboard sweep 2026-09-18: exit 0 on release with CLI 2.0.12; result keys: ok. deleted custom style 1 Single invocation only; no error-path or variant coverage.
+
+### `dashboard.style.custom.list`
+
+Run: `mammoth dashboard style custom list`. Exact input fields: `mammoth schema get dashboard.style.custom.list`.
+
+Example: `mammoth dashboard style custom list`. Placeholders are illustrative; resolve IDs and input from observed reads.
+
+Result: `DashboardStyleCustomListResult`; mutation `read`, confirmation `none`, wait policy `not_async`.
+
+Status on release: ran once on CLI 2.0.12 — Bounded release read succeeded with pinned CLI 1.1.9 in workspace 4; empty custom-style list observed. No Full claim: no non-empty fixture. Also: Dashboard sweep 2026-09-18: exit 0 on release with CLI 2.0.12; result keys: styles. empty custom styles list Sing…
+
+### `dashboard.style.custom.update`
+
+Run: `mammoth dashboard style custom update`. Exact input fields: `mammoth schema get dashboard.style.custom.update`.
+
+Example: `mammoth dashboard style custom update resource-123 --input '{"body": {"params": {"signals": {}}}}'`. Placeholders are illustrative; resolve IDs and input from observed reads.
+
+Result: `DashboardStyleCustomUpdateResult`; mutation `benign_mutation`, confirmation `none`, wait policy `not_async`.
+
+Status on release: ran once on CLI 2.0.12 — Dashboard sweep 2026-09-18: exit 0 on release with CLI 2.0.12; result keys: style. renamed custom style 1 Single invocation only; no error-path or variant coverage.
+
+### `dashboard.style.default.get`
+
+Run: `mammoth dashboard style default get`. Exact input fields: `mammoth schema get dashboard.style.default.get`.
+
+Example: `mammoth dashboard style default get`. Placeholders are illustrative; resolve IDs and input from observed reads.
+
+Result: `DashboardStyleDefaultGetResult`; mutation `read`, confirmation `none`, wait policy `not_async`.
+
+Status on release: ran once on CLI 2.0.14 — dashboard re-verification 2026-09-18: exit 0 on release with CLI 2.0.14. CLI defect fixed, confirmed: returned a real matched body {"styleId":"stone"} instead of raising ValidationError on an unmatched 2xx. Single invocation only.
+
+### `dashboard.style.default.set`
+
+Run: `mammoth dashboard style default set`. Exact input fields: `mammoth schema get dashboard.style.default.set`.
+
+Example: `mammoth dashboard style default set --input '{"body": {"params": {"styleId": "sample"}}}'`. Placeholders are illustrative; resolve IDs and input from observed reads.
+
+Result: `DashboardStyleDefaultSetResult`; mutation `benign_mutation`, confirmation `none`, wait policy `not_async`.
+
+Status on release: ran once on CLI 2.0.14 — dashboard re-verification 2026-09-18: exit 0 on release with CLI 2.0.14. Set styleId to the exact value read from style default get ("stone"), i.e. a verified no-op restore. Result {"styleId":"stone"}; re-ran style default get afterward and confirmed it still…
+
+### `dashboard.style.derive`
+
+Run: `mammoth dashboard style derive`. Exact input fields: `mammoth schema get dashboard.style.derive`.
+
+Example: `mammoth dashboard style derive --input '{"body": {"params": {"signals": {}}}}'`. Placeholders are illustrative; resolve IDs and input from observed reads.
+
+Result: `DashboardStyleDeriveResult`; mutation `benign_mutation`, confirmation `none`, wait policy `not_async`.
+
+Status on release: ran once on CLI 2.0.14 — dashboard re-verification 2026-09-18: exit 0 on release with CLI 2.0.14. CLI defect fixed, confirmed: returned a full real styleTokens object (colors, font, viz palette, radius, shadow, etc.) with no '***REDACTED***' placeholders anywhere in the body. Single…
+
+### `dashboard.style.extract-brand`
+
+Run: `mammoth dashboard style extract-brand`. Exact input fields: `mammoth schema get dashboard.style.extract-brand`.
+
+Example: `mammoth dashboard style extract-brand --input '{"body": {"params": {"url": "https://example.com/data.csv"}}}'`. Placeholders are illustrative; resolve IDs and input from observed reads.
+
+Result: `DashboardStyleExtractBrandResult`; mutation `benign_mutation`, confirmation `none`, wait policy `always_wait`.
+
+Status on release: ran once on CLI 2.0.12 — Dashboard sweep 2026-09-18: exit 0 on release with CLI 2.0.12; result keys: screenshot, signals. captured screenshot + extracted brand signals (accents/font/ground/primary), no redaction here Single invocation only; no error-path or variant coverage.
+
+### `dashboard.style.preset.list`
+
+Run: `mammoth dashboard style preset list`. Exact input fields: `mammoth schema get dashboard.style.preset.list`.
+
+Example: `mammoth dashboard style preset list`. Placeholders are illustrative; resolve IDs and input from observed reads.
+
+Result: `DashboardStylePresetListResult`; mutation `read`, confirmation `none`, wait policy `not_async`.
+
+Status on release: ran once on CLI 2.0.12 — Bounded release read succeeded with pinned CLI 1.1.9 in workspace 4; 10 stock presets returned. No Full claim: custom preset fixture not observed. Also: Dashboard sweep 2026-09-18: exit 0 on release with CLI 2.0.12; result keys: presets. returns built-in styl…
+
+### `dashboard.style.token.list`
+
+Run: `mammoth dashboard style token list`. Exact input fields: `mammoth schema get dashboard.style.token.list`.
+
+Example: `mammoth dashboard style token list resource-123`. Placeholders are illustrative; resolve IDs and input from observed reads.
+
+Result: `DashboardStyleTokenListResult`; mutation `read`, confirmation `none`, wait policy `not_async`.
+
+Status on release: ran once on CLI 1.1.11 — Published PyPI CLI 1.1.11 / SDK 0.7.1 read of observed preset stone returned a redacted token payload. Bounded to one preset and redacted semantics; not Full. Dashboard sweep 2026-09-18 on release observed cli_error: HTTP 200 but result is tokens='***REDACTED…

{mammoth_cli-2.2.10 → mammoth_cli-2.2.12}/mammoth_cli/bundled_skill/mammoth-cli/references/commands/dashboard.md

@@ -52,6 +52,46 @@ Result: `TwbAssessResponse`; mutation `read`, confirmation `none`, wait policy `
 
 Status on release: untried; no live run recorded.
 
+### `dashboard.audience.digest.get`
+
+Run: `mammoth dashboard audience digest get`. Exact input fields: `mammoth schema get dashboard.audience.digest.get`.
+
+Example: `mammoth dashboard audience digest get 123`. Placeholders are illustrative; resolve IDs and input from observed reads.
+
+Result: `DashboardAudienceDigestGetResult`; mutation `read`, confirmation `none`, wait policy `not_async`.
+
+Status on release: untried; no live run recorded.
+
+### `dashboard.audience.digest.set`
+
+Run: `mammoth dashboard audience digest set`. Exact input fields: `mammoth schema get dashboard.audience.digest.set`.
+
+Example: `mammoth dashboard audience digest set 123 --input '{"enabled": true}'`. Placeholders are illustrative; resolve IDs and input from observed reads.
+
+Result: `DashboardAudienceDigestSetResult`; mutation `benign_mutation`, confirmation `none`, wait policy `not_async`.
+
+Status on release: untried; no live run recorded.
+
+### `dashboard.audience.get`
+
+Run: `mammoth dashboard audience get`. Exact input fields: `mammoth schema get dashboard.audience.get`.
+
+Example: `mammoth dashboard audience get 123`. Placeholders are illustrative; resolve IDs and input from observed reads.
+
+Result: `DashboardAudienceGetResult`; mutation `read`, confirmation `none`, wait policy `not_async`.
+
+Status on release: untried; no live run recorded.
+
+### `dashboard.audience.summary`
+
+Run: `mammoth dashboard audience summary`. Exact input fields: `mammoth schema get dashboard.audience.summary`.
+
+Example: `mammoth dashboard audience summary --input '{"dashboard_ids": [1]}'`. Placeholders are illustrative; resolve IDs and input from observed reads.
+
+Result: `DashboardAudienceSummaryResult`; mutation `read`, confirmation `none`, wait policy `not_async`.
+
+Status on release: untried; no live run recorded.
+
 ### `dashboard.bi-export`
 
 Run: `mammoth dashboard bi-export`. Exact input fields: `mammoth schema get dashboard.bi-export`.
@@ -132,6 +172,26 @@ Result: `DashboardChatHistoryResult`; mutation `read`, confirmation `none`, wait
 
 Status on release: ran once on CLI 2.0.12 — Published PyPI CLI 1.1.11 chat-history read for retained dashboard48 returned empty history with sequence1; bounded and not Full. Also: Dashboard sweep 2026-09-18: exit 0 on release with CLI 2.0.12; result keys: history_index, messages, sequence. no chat mess…
 
+### `dashboard.columns`
+
+Run: `mammoth dashboard columns`. Exact input fields: `mammoth schema get dashboard.columns`.
+
+Example: `mammoth dashboard columns 123`. Placeholders are illustrative; resolve IDs and input from observed reads.
+
+Result: `DashboardColumnsResult`; mutation `read`, confirmation `none`, wait policy `not_async`.
+
+Status on release: untried; no live run recorded.
+
+### `dashboard.context.apply`
+
+Run: `mammoth dashboard context apply`. Exact input fields: `mammoth schema get dashboard.context.apply`.
+
+Example: `mammoth dashboard context apply 123 resource-123 --yes --confirm 123`. Illustrative only: append `--yes --confirm <EXACT_TARGET>` after observing the target.
+
+Result: `DashboardContextApplyResult`; mutation `benign_mutation`, confirmation `confirm_target`, wait policy `always_wait`.
+
+Status on release: untried; no live run recorded.
+
 ### `dashboard.context.create`
 
 Run: `mammoth dashboard context create`. Exact input fields: `mammoth schema get dashboard.context.create`.
@@ -172,6 +232,16 @@ Result: `DashboardContextListResult`; mutation `read`, confirmation `none`, wait
 
 Status on release: ran once on CLI 2.0.12 — Bounded release read succeeded with pinned CLI 1.1.9 in workspace 4; empty context list observed. No Full claim: no non-empty fixture. Also: Dashboard sweep 2026-09-18: exit 0 on release with CLI 2.0.12; result keys: contexts. empty contexts list Single invoc…
 
+### `dashboard.context.review`
+
+Run: `mammoth dashboard context review`. Exact input fields: `mammoth schema get dashboard.context.review`.
+
+Example: `mammoth dashboard context review 123`. Placeholders are illustrative; resolve IDs and input from observed reads.
+
+Result: `DashboardContextReviewResult`; mutation `read`, confirmation `none`, wait policy `always_wait`.
+
+Status on release: untried; no live run recorded.
+
 ### `dashboard.context.update`
 
 Run: `mammoth dashboard context update`. Exact input fields: `mammoth schema get dashboard.context.update`.
@@ -720,106 +790,6 @@ Result: `DashboardSourceListResult`; mutation `read`, confirmation `none`, wait
 
 Status on release: observed blocker — blocker; still broken, not one of the 11 CLI-fixed commands. Re-check before relying on it.
 
-### `dashboard.style.custom.create`
-
-Run: `mammoth dashboard style custom create`. Exact input fields: `mammoth schema get dashboard.style.custom.create`.
-
-Example: `mammoth dashboard style custom create --input '{"body": {"params": {"signals": {}}}}'`. Placeholders are illustrative; resolve IDs and input from observed reads.
-
-Result: `DashboardStyleCustomCreateResult`; mutation `benign_mutation`, confirmation `none`, wait policy `not_async`.
-
-Status on release: ran once on CLI 2.0.12 — Dashboard sweep 2026-09-18: exit 0 on release with CLI 2.0.12; result keys: style. created custom style id=1 with full unredacted colors/font/viz (no tokens field passed) Single invocation only; no error-path or variant coverage.
-
-### `dashboard.style.custom.delete`
-
-Run: `mammoth dashboard style custom delete`. Exact input fields: `mammoth schema get dashboard.style.custom.delete`.
-
-Example: `mammoth dashboard style custom delete resource-123`. Illustrative only: append `--yes` after observing an owned target.
-
-Result: `DashboardStyleCustomDeleteResult`; mutation `destructive`, confirmation `prompt_or_yes`, wait policy `not_async`.
-
-Status on release: ran once on CLI 2.0.12 — Dashboard sweep 2026-09-18: exit 0 on release with CLI 2.0.12; result keys: ok. deleted custom style 1 Single invocation only; no error-path or variant coverage.
-
-### `dashboard.style.custom.list`
-
-Run: `mammoth dashboard style custom list`. Exact input fields: `mammoth schema get dashboard.style.custom.list`.
-
-Example: `mammoth dashboard style custom list`. Placeholders are illustrative; resolve IDs and input from observed reads.
-
-Result: `DashboardStyleCustomListResult`; mutation `read`, confirmation `none`, wait policy `not_async`.
-
-Status on release: ran once on CLI 2.0.12 — Bounded release read succeeded with pinned CLI 1.1.9 in workspace 4; empty custom-style list observed. No Full claim: no non-empty fixture. Also: Dashboard sweep 2026-09-18: exit 0 on release with CLI 2.0.12; result keys: styles. empty custom styles list Sing…
-
-### `dashboard.style.custom.update`
-
-Run: `mammoth dashboard style custom update`. Exact input fields: `mammoth schema get dashboard.style.custom.update`.
-
-Example: `mammoth dashboard style custom update resource-123 --input '{"body": {"params": {"signals": {}}}}'`. Placeholders are illustrative; resolve IDs and input from observed reads.
-
-Result: `DashboardStyleCustomUpdateResult`; mutation `benign_mutation`, confirmation `none`, wait policy `not_async`.
-
-Status on release: ran once on CLI 2.0.12 — Dashboard sweep 2026-09-18: exit 0 on release with CLI 2.0.12; result keys: style. renamed custom style 1 Single invocation only; no error-path or variant coverage.
-
-### `dashboard.style.default.get`
-
-Run: `mammoth dashboard style default get`. Exact input fields: `mammoth schema get dashboard.style.default.get`.
-
-Example: `mammoth dashboard style default get`. Placeholders are illustrative; resolve IDs and input from observed reads.
-
-Result: `DashboardStyleDefaultGetResult`; mutation `read`, confirmation `none`, wait policy `not_async`.
-
-Status on release: ran once on CLI 2.0.14 — dashboard re-verification 2026-09-18: exit 0 on release with CLI 2.0.14. CLI defect fixed, confirmed: returned a real matched body {"styleId":"stone"} instead of raising ValidationError on an unmatched 2xx. Single invocation only.
-
-### `dashboard.style.default.set`
-
-Run: `mammoth dashboard style default set`. Exact input fields: `mammoth schema get dashboard.style.default.set`.
-
-Example: `mammoth dashboard style default set --input '{"body": {"params": {"styleId": "sample"}}}'`. Placeholders are illustrative; resolve IDs and input from observed reads.
-
-Result: `DashboardStyleDefaultSetResult`; mutation `benign_mutation`, confirmation `none`, wait policy `not_async`.
-
-Status on release: ran once on CLI 2.0.14 — dashboard re-verification 2026-09-18: exit 0 on release with CLI 2.0.14. Set styleId to the exact value read from style default get ("stone"), i.e. a verified no-op restore. Result {"styleId":"stone"}; re-ran style default get afterward and confirmed it still…
-
-### `dashboard.style.derive`
-
-Run: `mammoth dashboard style derive`. Exact input fields: `mammoth schema get dashboard.style.derive`.
-
-Example: `mammoth dashboard style derive --input '{"body": {"params": {"signals": {}}}}'`. Placeholders are illustrative; resolve IDs and input from observed reads.
-
-Result: `DashboardStyleDeriveResult`; mutation `benign_mutation`, confirmation `none`, wait policy `not_async`.
-
-Status on release: ran once on CLI 2.0.14 — dashboard re-verification 2026-09-18: exit 0 on release with CLI 2.0.14. CLI defect fixed, confirmed: returned a full real styleTokens object (colors, font, viz palette, radius, shadow, etc.) with no '***REDACTED***' placeholders anywhere in the body. Single…
-
-### `dashboard.style.extract-brand`
-
-Run: `mammoth dashboard style extract-brand`. Exact input fields: `mammoth schema get dashboard.style.extract-brand`.
-
-Example: `mammoth dashboard style extract-brand --input '{"body": {"params": {"url": "https://example.com/data.csv"}}}'`. Placeholders are illustrative; resolve IDs and input from observed reads.
-
-Result: `DashboardStyleExtractBrandResult`; mutation `benign_mutation`, confirmation `none`, wait policy `always_wait`.
-
-Status on release: ran once on CLI 2.0.12 — Dashboard sweep 2026-09-18: exit 0 on release with CLI 2.0.12; result keys: screenshot, signals. captured screenshot + extracted brand signals (accents/font/ground/primary), no redaction here Single invocation only; no error-path or variant coverage.
-
-### `dashboard.style.preset.list`
-
-Run: `mammoth dashboard style preset list`. Exact input fields: `mammoth schema get dashboard.style.preset.list`.
-
-Example: `mammoth dashboard style preset list`. Placeholders are illustrative; resolve IDs and input from observed reads.
-
-Result: `DashboardStylePresetListResult`; mutation `read`, confirmation `none`, wait policy `not_async`.
-
-Status on release: ran once on CLI 2.0.12 — Bounded release read succeeded with pinned CLI 1.1.9 in workspace 4; 10 stock presets returned. No Full claim: custom preset fixture not observed. Also: Dashboard sweep 2026-09-18: exit 0 on release with CLI 2.0.12; result keys: presets. returns built-in styl…
-
-### `dashboard.style.token.list`
-
-Run: `mammoth dashboard style token list`. Exact input fields: `mammoth schema get dashboard.style.token.list`.
-
-Example: `mammoth dashboard style token list resource-123`. Placeholders are illustrative; resolve IDs and input from observed reads.
-
-Result: `DashboardStyleTokenListResult`; mutation `read`, confirmation `none`, wait policy `not_async`.
-
-Status on release: ran once on CLI 1.1.11 — Published PyPI CLI 1.1.11 / SDK 0.7.1 read of observed preset stone returned a redacted token payload. Bounded to one preset and redacted semantics; not Full. Dashboard sweep 2026-09-18 on release observed cli_error: HTTP 200 but result is tokens='***REDACTED…
-
 ### `dashboard.suggestion.list`
 
 Run: `mammoth dashboard suggestion list`. Exact input fields: `mammoth schema get dashboard.suggestion.list`.
@@ -840,6 +810,16 @@ Result: `ObjectJobSchema`; mutation `benign_mutation`, confirmation `confirm_tar
 
 Status on release: ran once on CLI 2.0.12 — Dashboard sweep 2026-09-18: exit 0 on release with CLI 2.0.12; result keys: bake_ok, fidelity, id, sequence. swapped D=52 from dataview 45 (population) to dataview 46 (GDP), both Terra OWID reference views with similar schema; fidelity: 1 mapped, 1 dropped, n…
 
+### `dashboard.swap-fit`
+
+Run: `mammoth dashboard swap-fit`. Exact input fields: `mammoth schema get dashboard.swap-fit`.
+
+Example: `mammoth dashboard swap-fit 123 --input '{"target_dataview_ids": [1]}'`. Placeholders are illustrative; resolve IDs and input from observed reads.
+
+Result: `DashboardSwapFitResult`; mutation `read`, confirmation `none`, wait policy `not_async`.
+
+Status on release: untried; no live run recorded.
+
 ### `dashboard.tags.delete`
 
 Run: `mammoth dashboard tags delete`. Exact input fields: `mammoth schema get dashboard.tags.delete`.

{mammoth_cli-2.2.10 → mammoth_cli-2.2.12}/mammoth_cli/bundled_skill/mammoth-cli/references/commands/view.md

@@ -160,7 +160,7 @@ Example: `mammoth view create 123`. Placeholders are illustrative; resolve IDs a
 
 Result: `ViewCreateResult`; mutation `benign_mutation`, confirmation `none`, wait policy `always_wait`.
 
-Status on release: ran once on CLI 2.0.18 — golden-data check 2026-09-19 (CLI 2.0.18): plain create on an owned dataset returned the new view's record (id, dataset_id; earlier releases printed '<unserializable View>'), and discard-duplicates then ran on it. clone_from is not usable on release: the clon…
+Status on release: ran once on CLI 2.0.18 — golden-data check 2026-09-19 (CLI 2.0.18): plain create on an owned dataset returned the new view's record (id, dataset_id; earlier releases printed '<unserializable View>'), and discard-duplicates then ran on it. clone_from works on a backend with mvc e56f23…
 
 ### `view.data-check.create`
 
@@ -694,6 +694,16 @@ Result: `ViewGetResult`; mutation `read`, confirmation `none`, wait policy `not_
 
 Status on release: ran once on CLI 2.0.21 — ergonomics sweep 2026-09-19: exit 0 on release with CLI 2.0.21. Read back without a dataset id (parent from cache). row_count 6 after the append. Single invocation only.
 
+### `view.impact`
+
+Run: `mammoth view impact`. Exact input fields: `mammoth schema get view.impact`.
+
+Example: `mammoth view impact 123 123 --input '{"scope": "view"}'`. Placeholders are illustrative; resolve IDs and input from observed reads.
+
+Result: `ViewImpactResult`; mutation `read`, confirmation `none`, wait policy `not_async`.
+
+Status on release: untried; no live run recorded.
+
 ### `view.list`
 
 Run: `mammoth view list`. Exact input fields: `mammoth schema get view.list`.

{mammoth_cli-2.2.10 → mammoth_cli-2.2.12}/mammoth_cli/bundled_skill/mammoth-cli/references/recipes/end-to-end.md

@@ -56,8 +56,8 @@ mammoth view export csv ORDERS_VIEW --project PROJECT_ID \
 #   check the file's header and row count against the last readback
 
 # 7. per-region summary as the LAST step on the same view (pivot replaces the view's columns in place;
-#    do not use view create with clone_from for this: on release the clone job succeeds but the copy
-#    answers every read with 4DTVW019 and its copied tasks never execute)
+#    to keep the uncollapsed view as well, copy it first with view create DATASET_ID --input '{"clone_from": VIEW_ID}'
+#    (same dataset only; the copy keeps the source's steps) and pivot the copy instead)
 mammoth view transform pivot ORDERS_VIEW --project PROJECT_ID \
   --input '{"dataset_id": ORDERS_DS, "group_by": ["region"], "aggregations": [{"column": "amount", "function": "SUM", "as_name": "total_amount"}, {"column": "order_id", "function": "COUNT", "as_name": "order_count"}]}'
 mammoth view data get ORDERS_VIEW ORDERS_DS --project PROJECT_ID

{mammoth_cli-2.2.10 → mammoth_cli-2.2.12}/mammoth_cli/bundled_skill/mammoth-cli/references/recipes/transforms.md

@@ -151,11 +151,15 @@ display name) with display-name columns; unquoted or placeholder table names
 select queries allowed". The result replaces the view's columns: never run it
 (or `pivot`) on a view whose rows are still needed; export those rows first
 (`view export csv`) and run the summary as the last step, and prefer `pivot`
-(proven on release) over a SQL task. Do not build the summary on a
-`view create ... "clone_from": VIEW_ID` copy: on release the clone job succeeds
-but the copy answers every read with `4DTVW019` and its copied tasks never
-execute. A plain `view create DATASET_ID` (no `clone_from`) gives a fresh view
-of the raw upload, without the pipeline:
+(proven on release) over a SQL task. To keep the view's rows and still
+summarise, copy it first with `view create DATASET_ID --input
+'{"clone_from": VIEW_ID}'` (same dataset only) and run the summary on the
+copy: the copy keeps the source's steps and runs them (koyal, 2026-10-02: the
+cloned steps executed and the copy took a further filter). Only a backend
+older than 2026-09-26 left the copy's tasks unrun, answering reads with
+`4DTVW019`; see recovery.md. A plain `view create DATASET_ID` (no
+`clone_from`) is not a copy: it gives a fresh view of the raw upload, without
+the pipeline:
 
 A task must fit the column's type: `replace-values`, `bulk-replace` and the
 text operations take TEXT columns, `math` takes NUMERIC. Check `type` in the

{mammoth_cli-2.2.10 → mammoth_cli-2.2.12}/mammoth_cli/bundled_skill/mammoth-cli/references/recovery.md

@@ -30,7 +30,7 @@ these commands are not blanket permission to replay a mutation.
 | `resource_not_found` (exit 5) after `view get VIEW_ID` / `view data get VIEW_ID` without a parent | discovery could not find the view in the selected project | pass `--project PROJECT_ID` and the `DATASET_ID` positional from `view list` |
 | `{"data": "<unserializable View>"}` from `view get VIEW_ID` | CLI ≤ 2.0.17 only; fixed in 2.0.18 | upgrade, or rerun as `view get VIEW_ID DATASET_ID` |
 | `pipeline_reference_error` (exit 1) from a transform or `view task add`, `details.reference_errors[].reason` `type mismatch` / `not available` | the backend stored the task but cannot bind it to that column (find/replace and text operations take TEXT columns, math takes NUMERIC); the view is in `ref_error` and every read of it fails with `4DTVW019` until the task goes | run the printed `view task delete VIEW_ID TASK_ID --yes`, then convert-type the column or pick a transform for its type; CLI ≤ 2.0.24 reported this as success with `has_error: true` |
-| `4DTVW019 INVALID_RESPONSE_GENERATED` on every read of a view made with `view create ... "clone_from"` | backend: the clone is never processed (tasks stay `added`) | delete the copy; export the source view's rows, then run the summary in place as the last step; see recipes/end-to-end.md |
+| `4DTVW019 INVALID_RESPONSE_GENERATED` on every read of a view made with `view create ... "clone_from"` | only a backend older than mvc `e56f2338b6` (2026-09-26) leaves the clone's copied tasks `added`, never run; on a current backend a same-dataset clone runs its copied tasks and reads normally (koyal view 4429: both tasks `executed`), so any other cause is the `ref_error` row above | `view task list VIEW_ID DATASET_ID`: tasks stuck at `added` mean an old backend, so delete the copy and rebuild the steps on a plain view; a task in `ref_error` means delete that task. A copy of a view should still be made with `clone_from` (same dataset only), which keeps the source's steps; see recipes/end-to-end.md |
 | `needs_view` in `file upload` result, or `status: ready` with `status_info.ready` "more than one plausible way to be read" and `view list` empty | all-text CSV: the platform ingests the rows but creates no view | run the `next_command` (`view create DATASET_ID`) once, then `view list DATASET_ID`; see recipes/need-action.md |
 | `need_action` in `file upload` result | the platform needs a parsing decision (e.g. ambiguous dates) | run the `next_command` it returns (`dataset file-settings get ID`), then `dataset file-settings update ID`; see recipes/need-action.md |
 | `confirmation_required` (exit 2) | destructive/high-impact command without `--yes` (and `--confirm TARGET` when policy is confirm_target) | re-run with the flag after you have read the target back by id |

{mammoth_cli-2.2.10 → mammoth_cli-2.2.12}/mammoth_cli/commands/addon.py

@@ -20,9 +20,9 @@ from typing import Any
 from mammoth_cli.errors.envelope import (
     CODE_MISSING_FIELD,
     CODE_SDK_SYMBOL_UNRESOLVED,
-    CODE_UNSUPPORTED_CONTRACT,
     EXIT_USAGE,
     CliError,
+    not_available_error,
 )
 from mammoth_cli.manifest.loader import command_by_id
 from mammoth_cli.runtime.confirm import POLICY_CONFIRM_TARGET, enforce_confirmation
@@ -115,21 +115,17 @@ def addon_connector_remove(invocation: Invocation) -> HandlerResult:
 
 
 def addon_list(invocation: Invocation) -> HandlerResult:
-    """List active addons for the workspace.
+    """Retired: the server has no route that lists a workspace's addons.
 
-    RCA T1-W-17: ``GET /workspaces/{id}/addons`` has no backing route on the
-    backend at all (a 404 from Litestar's own routing trie, not a typed
-    error) -- fail loud with that fact up front rather than surface the raw
-    404 as if the call had merely found nothing.
+    ``GET /workspaces/{id}/addons`` is gone (the server serves only the add and
+    remove routes under ``/addons/*``), and nothing replaces it: the Stripe
+    subscription's ``addons`` field is never filled in. The command stays so a
+    caller gets a clear answer instead of a bare 404.
     """
-    raise CliError(
-        code=CODE_UNSUPPORTED_CONTRACT,
-        message=(
-            "addon list has no backend route (GET /workspaces/{workspace_id}/addons does not "
-            "exist) and always 404s; it is currently non-functional."
-        ),
-        exit_status=EXIT_USAGE,
-        hint="Use `billing chargebee-plan` or `billing subscription get` for plan/storage info.",
+    raise not_available_error(
+        "addon list",
+        web_path="Settings > Plan (Billing & Invoices), where the add-ons are listed",
+        instead="`billing stripe status` shows the storage allowance and plan.",
     )
 
 

{mammoth_cli-2.2.10 → mammoth_cli-2.2.12}/mammoth_cli/commands/agent.py

@@ -271,3 +271,8 @@ def agent_run_units_set(invocation: Invocation) -> HandlerResult:
     document = _bound_document(invocation)
     kwargs = {field: _require_field(document, field) for field in ("step", "kind", "units")}
     return _session_call(invocation, run_id=run_id, **kwargs)
+
+
+def agent_turn_cancel(invocation: Invocation) -> HandlerResult:
+    """Stop one turn of an agent chat session (the session's owner only)."""
+    return _session_call(invocation, turn_id=_require_string_positional(invocation, "turn id"))