mammoth-cli 2.2.5__tar.gz → 2.2.7__tar.gz

{mammoth_cli-2.2.5 → mammoth_cli-2.2.7}/PKG-INFO

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

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

{mammoth_cli-2.2.5 → mammoth_cli-2.2.7}/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 597 commands. 455 of them bind one of the 528 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, 2 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 612 commands. 455 of them bind one of the 528 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, 2 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.5 → mammoth_cli-2.2.7}/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 597; 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 612; 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:
 
@@ -12,8 +12,8 @@ Load only the applicable domain file:
 - [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) — 22 published commands
-- [browse](commands/browse.md) — 4 published commands
+- [billing](commands/billing.md) — 25 published commands
+- [browse](commands/browse.md) — 8 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
@@ -22,8 +22,8 @@ Load only the applicable domain file:
 - [connector](commands/connector.md) — 22 published commands
 - [context](commands/context.md) — 3 published commands
 - [dashboard-qa](commands/dashboard-qa.md) — 13 published commands
-- [dashboard-style](commands/dashboard-style.md) — 10 published commands
-- [dashboard](commands/dashboard.md) — 93 published commands
+- [dashboard-template](commands/dashboard-template.md) — 12 published commands
+- [dashboard](commands/dashboard.md) — 98 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
@@ -51,4 +51,4 @@ Load only the applicable domain file:
 - [view](commands/view.md) — 90 published commands
 - [webhook](commands/webhook.md) — 7 published commands
 - [workflow](commands/workflow.md) — 16 published commands
-- [workspace](commands/workspace.md) — 25 published commands
+- [workspace](commands/workspace.md) — 26 published commands

{mammoth_cli-2.2.5 → mammoth_cli-2.2.7}/mammoth_cli/bundled_skill/mammoth-cli/references/commands/billing.md

@@ -152,6 +152,26 @@ Result: `BillingStripePreviewInvoiceResult`; mutation `read`, confirmation `none
 
 Status on release: observed blocker — backend_error: The CLI gates this GET behind --yes --confirm WORKSPACE_ID; with confirmation: HTTP 400 4SUBS037 'Failed to perform subscription operation'. Re-check before relying on it.
 
+### `billing.stripe.recheck-limits`
+
+Run: `mammoth billing stripe recheck-limits`. Exact input fields: `mammoth schema get billing.stripe.recheck-limits`.
+
+Example: `mammoth billing stripe recheck-limits`. Placeholders are illustrative; resolve IDs and input from observed reads.
+
+Result: `BillingStripeRecheckLimitsResult`; mutation `benign_mutation`, confirmation `none`, wait policy `not_async`.
+
+Status on release: untried; no live run recorded.
+
+### `billing.stripe.resume`
+
+Run: `mammoth billing stripe resume`. Exact input fields: `mammoth schema get billing.stripe.resume`.
+
+Example: `mammoth billing stripe resume`. Illustrative only: append `--yes --confirm <EXACT_TARGET>` after observing the target.
+
+Result: `BillingStripeResumeResult`; mutation `high_impact`, confirmation `confirm_target`, wait policy `not_async`.
+
+Status on release: untried; no live run recorded.
+
 ### `billing.stripe.retry-payment`
 
 Run: `mammoth billing stripe retry-payment`. Exact input fields: `mammoth schema get billing.stripe.retry-payment`.
@@ -172,6 +192,16 @@ Result: `BillingStripeStatusResult`; mutation `read`, confirmation `none`, wait
 
 Status on release: ran once on CLI 2.0.15 — admin read sweep 2026-09-18: exit 0 on release with CLI 2.0.15. The CLI gates this GET behind --yes --confirm WORKSPACE_ID (confirm_target policy); with confirmation: exit 0; data with billing_cycle, has_active_subscription, is_trial_expired, ... (20 keys) Si…
 
+### `billing.stripe.storage.set`
+
+Run: `mammoth billing stripe storage set`. Exact input fields: `mammoth schema get billing.stripe.storage.set`.
+
+Example: `mammoth billing stripe storage set --input '{"storage_gb": 1}'`. Illustrative only: append `--yes --confirm <EXACT_TARGET>` after observing the target.
+
+Result: `BillingStripeStorageSetResult`; mutation `high_impact`, confirmation `confirm_target`, wait policy `not_async`.
+
+Status on release: untried; no live run recorded.
+
 ### `billing.stripe.sync`
 
 Run: `mammoth billing stripe sync`. Exact input fields: `mammoth schema get billing.stripe.sync`.

{mammoth_cli-2.2.5 → mammoth_cli-2.2.7}/mammoth_cli/bundled_skill/mammoth-cli/references/commands/browse.md

@@ -2,6 +2,16 @@
 
 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).
 
+### `browse.ancestors`
+
+Run: `mammoth browse ancestors`. Exact input fields: `mammoth schema get browse.ancestors`.
+
+Example: `mammoth browse ancestors 123`. Placeholders are illustrative; resolve IDs and input from observed reads.
+
+Result: `BrowseAncestorsResult`; mutation `read`, confirmation `none`, wait policy `not_async`.
+
+Status on release: untried; no live run recorded.
+
 ### `browse.folder`
 
 Run: `mammoth browse folder`. Exact input fields: `mammoth schema get browse.folder`.
@@ -22,6 +32,26 @@ Result: `BrowseProjectResult`; mutation `read`, confirmation `none`, wait policy
 
 Status on release: observed blocker — backend_error: GET /workspaces/4/projects/47/browse HTTP 500 empty body. Re-check before relying on it.
 
+### `browse.resource`
+
+Run: `mammoth browse resource`. Exact input fields: `mammoth schema get browse.resource`.
+
+Example: `mammoth browse resource dataset 123`. Placeholders are illustrative; resolve IDs and input from observed reads.
+
+Result: `BrowseResourceResult`; mutation `read`, confirmation `none`, wait policy `not_async`.
+
+Status on release: untried; no live run recorded.
+
+### `browse.resources`
+
+Run: `mammoth browse resources`. Exact input fields: `mammoth schema get browse.resources`.
+
+Example: `mammoth browse resources`. Placeholders are illustrative; resolve IDs and input from observed reads.
+
+Result: `BrowseResourcesResult`; 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`.
@@ -32,6 +62,16 @@ Result: `BrowseRootResult`; mutation `read`, confirmation `none`, wait policy `n
 
 Status on release: observed blocker — backend_error: GET /browse still HTTP 500 empty body on release (same as 2026-09-18/19 sweeps). Re-check before relying on it.
 
+### `browse.search`
+
+Run: `mammoth browse search`. Exact input fields: `mammoth schema get browse.search`.
+
+Example: `mammoth browse search`. Placeholders are illustrative; resolve IDs and input from observed reads.
+
+Result: `BrowseSearchResult`; mutation `read`, confirmation `none`, wait policy `not_async`.
+
+Status on release: untried; no live run recorded.
+
 ### `browse.workspace`
 
 Run: `mammoth browse workspace`. Exact input fields: `mammoth schema get browse.workspace`.

mammoth_cli-2.2.7/mammoth_cli/bundled_skill/mammoth-cli/references/commands/dashboard-template.md

@@ -0,0 +1,123 @@
+# `dashboard-template` 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.template.apply`
+
+Run: `mammoth dashboard template apply`. Exact input fields: `mammoth schema get dashboard.template.apply`.
+
+Example: `mammoth dashboard template apply --input '{"body": {"params": {"source_dashboard_id": 1, "target_dataview_id": 1}}}'`. Placeholders are illustrative; resolve IDs and input from observed reads.
+
+Result: `DashboardTemplateApplyResult`; mutation `benign_mutation`, confirmation `none`, wait policy `always_wait`.
+
+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. Succeeded and created a NEW dashboard (id 57, derived_from 56, url U6WuS1Z2haJj8h96JkcFxw) mapped onto view 45 with fidelity {"blocked":false,"dropped":0,"unmatched_required":[]}. This i…
+
+### `dashboard.template.create`
+
+Run: `mammoth dashboard template create`. Exact input fields: `mammoth schema get dashboard.template.create`.
+
+Example: `mammoth dashboard template create --input '{"body": {"params": {"dashboard_id": 1, "title": "Revenue report"}}}'`. Placeholders are illustrative; resolve IDs and input from observed reads.
+
+Result: `DashboardTemplateCreateResult`; mutation `benign_mutation`, confirmation `none`, wait policy `not_async`.
+
+Status on release: observed blocker — backend_error: POST /dashboards/v3/templates HTTP 500 empty body / outcome_unknown, as on 2026-09-18. Re-check before relying on it.
+
+### `dashboard.template.delete`
+
+Run: `mammoth dashboard template delete`. Exact input fields: `mammoth schema get dashboard.template.delete`.
+
+Example: `mammoth dashboard template delete resource-123`. Illustrative only: append `--yes` after observing an owned target.
+
+Result: `DashboardTemplateDeleteResult`; mutation `destructive`, confirmation `prompt_or_yes`, wait policy `not_async`.
+
+Status on release: observed blocker — blocked_missing_fixture: dashboard.template.create never produced an owned template (HTTP 500 both attempts, reconciled as not-committed via template list). Re-check before relying on it.
+
+### `dashboard.template.fit`
+
+Run: `mammoth dashboard template fit`. Exact input fields: `mammoth schema get dashboard.template.fit`.
+
+Example: `mammoth dashboard template fit 123`. Placeholders are illustrative; resolve IDs and input from observed reads.
+
+Result: `DashboardTemplateFitResult`; mutation `read`, confirmation `none`, wait policy `not_async`.
+
+Status on release: ran once on CLI 2.0.12 — Read-only sweep 2026-09-18: exit 0 on release with CLI 2.0.11; result keys: dataview_id, fits. Single read only; no fixture variants, error envelopes, or write paths assessed. Also: Dashboard sweep 2026-09-18: exit 0 on release with CLI 2.0.12; result keys: d…
+
+### `dashboard.template.get`
+
+Run: `mammoth dashboard template get`. Exact input fields: `mammoth schema get dashboard.template.get`.
+
+Example: `mammoth dashboard template get resource-123`. Placeholders are illustrative; resolve IDs and input from observed reads.
+
+Result: `DashboardTemplateGetResult`; 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 full matched structured body ({"explore":{...},"self_fit":{"grade":"great",...},"source_dashboard_id":1,"template":{...}}) instead of raising Vali…
+
+### `dashboard.template.list`
+
+Run: `mammoth dashboard template list`. Exact input fields: `mammoth schema get dashboard.template.list`.
+
+Example: `mammoth dashboard template list`. Placeholders are illustrative; resolve IDs and input from observed reads.
+
+Result: `DashboardTemplateListResult`; mutation `read`, confirmation `none`, wait policy `not_async`.
+
+Status on release: ran once on CLI 2.0.21 — ergonomics sweep 2026-09-19: exit 0 on release with CLI 2.0.21. Returned the template catalogue (formats, functions, ...). Single invocation only.
+
+### `dashboard.template.preview`
+
+Run: `mammoth dashboard template preview`. Exact input fields: `mammoth schema get dashboard.template.preview`.
+
+Example: `mammoth dashboard template preview --input '{"body": {"params": {"source_dashboard_id": 1, "target_dataview_id": 1}}}'`. Placeholders are illustrative; resolve IDs and input from observed reads.
+
+Result: `DashboardTemplatePreviewResult`; 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: canvas, fidelity, mapping, meta, plan, specs, target_fields. previewed D=52's canvas retargeted to dataview 47 (life expectancy dataset) Single invocation only; no error-path or varia…
+
+### `dashboard.template.rename`
+
+Run: `mammoth dashboard template rename`. Exact input fields: `mammoth schema get dashboard.template.rename`.
+
+Example: `mammoth dashboard template rename resource-123 --input '{"body": {"params": {"title": "Revenue report"}}}'`. Placeholders are illustrative; resolve IDs and input from observed reads.
+
+Result: `DashboardTemplateRenameResult`; mutation `benign_mutation`, confirmation `none`, wait policy `not_async`.
+
+Status on release: untried; no live run recorded.
+
+### `dashboard.template.resolve-mapping`
+
+Run: `mammoth dashboard template resolve-mapping`. Exact input fields: `mammoth schema get dashboard.template.resolve-mapping`.
+
+Example: `mammoth dashboard template resolve-mapping --input '{"body": {"params": {"source_dashboard_id": 1, "target_dataview_id": 1}}}'`. Placeholders are illustrative; resolve IDs and input from observed reads.
+
+Result: `DashboardTemplateResolveMappingResult`; 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: fidelity, mapping, target_fields. resolved mapping from D=52's current dataview (46, GDP after swap-data) to target dataview 47 (life expectancy) Single invocation only; no error-path…
+
+### `dashboard.template.thumbnail.clear`
+
+Run: `mammoth dashboard template thumbnail clear`. Exact input fields: `mammoth schema get dashboard.template.thumbnail.clear`.
+
+Example: `mammoth dashboard template thumbnail clear resource-123`. Illustrative only: append `--yes` after observing an owned target.
+
+Result: `DashboardTemplateThumbnailClearResult`; mutation `destructive`, confirmation `prompt_or_yes`, wait policy `not_async`.
+
+Status on release: untried; no live run recorded.
+
+### `dashboard.template.thumbnail.get`
+
+Run: `mammoth dashboard template thumbnail get`. Exact input fields: `mammoth schema get dashboard.template.thumbnail.get`.
+
+Example: `mammoth dashboard template thumbnail get resource-123`. Placeholders are illustrative; resolve IDs and input from observed reads.
+
+Result: `DashboardTemplateThumbnailGetResult`; mutation `read`, confirmation `none`, wait policy `not_async`.
+
+Status on release: untried; no live run recorded.
+
+### `dashboard.template.thumbnail.set`
+
+Run: `mammoth dashboard template thumbnail set`. Exact input fields: `mammoth schema get dashboard.template.thumbnail.set`.
+
+Example: `mammoth dashboard template thumbnail set resource-123 card.png`. Placeholders are illustrative; resolve IDs and input from observed reads.
+
+Result: `DashboardTemplateThumbnailSetResult`; mutation `benign_mutation`, confirmation `none`, wait policy `not_async`.
+
+Status on release: untried; no live run recorded.