mammoth-cli 2.0.48__tar.gz → 2.0.49__tar.gz

{mammoth_cli-2.0.48 → mammoth_cli-2.0.49}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: mammoth-cli
-Version: 2.0.48
+Version: 2.0.49
 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.8,>=0.7.20
+Requires-Dist: mammoth-io<0.8,>=0.7.21
 Requires-Dist: platformdirs<5,>=4.10
 Requires-Dist: pydantic<3,>=2.13
 Requires-Dist: pyyaml<7,>=6

{mammoth_cli-2.0.48 → mammoth_cli-2.0.49}/mammoth_cli/__init__.py

@@ -6,7 +6,7 @@ not implement a second HTTP client and does not call private SDK members.
 
 from __future__ import annotations
 
-__version__ = "2.0.48"
+__version__ = "2.0.49"
 
 # The versioned machine output envelope contract.
 SCHEMA_VERSION = 1

{mammoth_cli-2.0.48 → mammoth_cli-2.0.49}/mammoth_cli/bundled_skill/mammoth-cli/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: mammoth-cli
-version: 2.0.48
+version: 2.0.49
 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."
 ---
 
@@ -73,7 +73,8 @@ mammoth view transform --help              # every data transformation
 | Add rows to an existing dataset, or combine two sources | `file upload FILE --input '{"append_to_ds_id": DATASET_ID}'`; then `discard-duplicates` and diff `row_count` before/after ([about Mammoth](references/about-mammoth.md#view-settings-and-what-has-no-command)) |
 | Keep or remove rows | `view transform filter` |
 | Remove duplicate rows | `view transform discard-duplicates` |
-| Totals, counts, averages per group | `view transform pivot` |
+| Totals, counts, averages per group — just to read the number | `view data aggregate` (read-only: `--input '{"group_by": [...], "aggregations": [{"column": ..., "function": "SUM"}]}'` or `{"metric": {...}}`); never add a `pivot` task just to answer a question |
+| Totals, counts, averages per group — as a lasting change to the pipeline | `view transform pivot` |
 | A calculated column | `view transform math` |
 | Blanks to a constant, or to the previous row's value | `view transform set-values` (`IS_EMPTY`), `view transform fill-missing` |
 | Clean text | `view transform text`, `replace`, `bulk-replace` |

{mammoth_cli-2.0.48 → mammoth_cli-2.0.49}/mammoth_cli/bundled_skill/mammoth-cli/references/about-mammoth.md

@@ -140,12 +140,15 @@ No command:
 - **Union or append two views.** There is no union task. Upload a file into
   an existing dataset with `append_to_ds_id`, or send a view's rows into an
   existing dataset with `view export dataset` (`target_ds_id` and
-  `save_as_mode` `APPEND_TO_DS`; that mode is untried on release). A row
-  present in both sources lands twice: note the appended view's `row_count`
-  (`view get`), run `view transform discard-duplicates` on it (`ignore_columns`
-  for any column you added per source, e.g. a region tag, since it would
-  make shared rows differ), read `row_count` again, and report the
-  difference as duplicates removed.
+  `save_as_mode` `APPEND_TO_DS`). An append is a standing link: it is stored
+  as a pipeline step of the source view, so every later re-run of that view
+  appends again into the target dataset, not just the first run. To stack
+  rows into a brand-new dataset instead of an existing one, omit
+  `target_ds_id`. A row present in both sources lands twice: note the
+  appended view's `row_count` (`view get`), run `view transform
+  discard-duplicates` on it (`ignore_columns` for any column you added per
+  source, e.g. a region tag, since it would make shared rows differ), read
+  `row_count` again, and report the difference as duplicates removed.
 - **Hide or reorder columns.** Display changes in the web app; they do not
   change the data.
 

{mammoth_cli-2.0.48 → mammoth_cli-2.0.49}/mammoth_cli/bundled_skill/mammoth-cli/references/capabilities-misc.md

@@ -34,7 +34,7 @@ Ran once: `automation.create`, `automation.delete`, `automation.list`
 | Command | State | Note |
 |---|---|---|
 | `automation.get` | observed blocker | backend_error: SUSPECTED DEFECT: automation.get on the id that automation.create returned (id=1) returns HTTP 500 empty body every time (3 retries, several seconds apart), not even |
-| `automation.update` | observed blocker | cli_error: CLI rejected 'name' field; error message says accepted field is 'patch' (nested patch object), not documented in agent_example |
+| `automation.update` | CLI defect fixed, untried since | mammoth-io 0.7.19 / mammoth-cli 2.0.46: AutomationsAPI.update sent path=status value='resume' to the backend verbatim |
 
 ## `batch`
 

{mammoth_cli-2.0.48 → mammoth_cli-2.0.49}/mammoth_cli/bundled_skill/mammoth-cli/references/command-index.md

@@ -20,7 +20,8 @@ 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](commands/dashboard.md) — 104 published commands
+- [dashboard-qa](commands/dashboard-qa.md) — 13 published commands
+- [dashboard](commands/dashboard.md) — 90 published commands
 - [data-app](commands/data-app.md) — 12 published commands
 - [dataset](commands/dataset.md) — 17 published commands
 - [doctor](commands/doctor.md) — 1 published commands
@@ -43,7 +44,8 @@ Load only the applicable domain file:
 - [upgrade](commands/upgrade.md) — 1 published commands
 - [user](commands/user.md) — 8 published commands
 - [version](commands/version.md) — 1 published commands
-- [view](commands/view.md) — 118 published commands
+- [view-transform](commands/view-transform.md) — 32 published commands
+- [view](commands/view.md) — 87 published commands
 - [webhook](commands/webhook.md) — 7 published commands
 - [workflow](commands/workflow.md) — 16 published commands
 - [workspace](commands/workspace.md) — 20 published commands

{mammoth_cli-2.0.48 → mammoth_cli-2.0.49}/mammoth_cli/bundled_skill/mammoth-cli/references/commands/billing.md

@@ -6,9 +6,9 @@ Every command returns the standard JSON envelope. On nonzero exit, read the erro
 
 Run: `mammoth billing chargebee-plan`. Exact input fields: `mammoth schema get billing.chargebee-plan`.
 
-Example: `mammoth billing chargebee-plan`. Illustrative only: append `--yes --confirm <EXACT_TARGET>` after observing the target.
+Example: `mammoth billing chargebee-plan`. Placeholders are illustrative; resolve IDs and input from observed reads.
 
-Result: `BillingChargebeePlanResult`; mutation `high_impact`, confirmation `confirm_target`, wait policy `not_async`.
+Result: `BillingChargebeePlanResult`; mutation `read`, confirmation `none`, wait policy `not_async`.
 
 Status on release: observed blocker — backend_error: The CLI gates this GET behind --yes --confirm WORKSPACE_ID; with confirmation: HTTP 400 4SUBS014 'Chargebee plan not found for the given workspace' (workspace 4 is n. Re-check before relying on it.
 
@@ -36,9 +36,9 @@ Status on release: untried; no live run recorded.
 
 Run: `mammoth billing invoice get`. Exact input fields: `mammoth schema get billing.invoice.get`.
 
-Example: `mammoth billing invoice get 123`. Illustrative only: append `--yes --confirm <EXACT_TARGET>` after observing the target.
+Example: `mammoth billing invoice get 123`. Placeholders are illustrative; resolve IDs and input from observed reads.
 
-Result: `BillingInvoiceGetResult`; mutation `high_impact`, confirmation `confirm_target`, wait policy `not_async`.
+Result: `BillingInvoiceGetResult`; mutation `read`, confirmation `none`, wait policy `not_async`.
 
 Status on release: observed blocker — blocked_missing_fixture: The CLI gates this GET behind --yes --confirm WORKSPACE_ID; with confirmation: billing invoice list answered HTTP 500, so no invoice id was observed. Re-check before relying on it.
 
@@ -46,9 +46,9 @@ Status on release: observed blocker — blocked_missing_fixture: The CLI gates t
 
 Run: `mammoth billing invoice list`. Exact input fields: `mammoth schema get billing.invoice.list`.
 
-Example: `mammoth billing invoice list`. Illustrative only: append `--yes --confirm <EXACT_TARGET>` after observing the target.
+Example: `mammoth billing invoice list`. Placeholders are illustrative; resolve IDs and input from observed reads.
 
-Result: `BillingInvoiceListResult`; mutation `high_impact`, confirmation `confirm_target`, wait policy `not_async`.
+Result: `BillingInvoiceListResult`; mutation `read`, confirmation `none`, wait policy `not_async`.
 
 Status on release: observed blocker — backend_error: The CLI gates this GET behind --yes --confirm WORKSPACE_ID; with confirmation: HTTP 500 with empty body on GET /workspaces/4/subscription_v1/invoices. Re-check before relying on it.
 
@@ -96,9 +96,9 @@ Status on release: untried; no live run recorded.
 
 Run: `mammoth billing stripe get`. Exact input fields: `mammoth schema get billing.stripe.get`.
 
-Example: `mammoth billing stripe get`. Illustrative only: append `--yes --confirm <EXACT_TARGET>` after observing the target.
+Example: `mammoth billing stripe get`. Placeholders are illustrative; resolve IDs and input from observed reads.
 
-Result: `BillingStripeGetResult`; mutation `high_impact`, confirmation `confirm_target`, wait policy `not_async`.
+Result: `BillingStripeGetResult`; mutation `read`, confirmation `none`, wait policy `not_async`.
 
 Status on release: untried; no live run recorded.
 
@@ -106,9 +106,9 @@ Status on release: untried; no live run recorded.
 
 Run: `mammoth billing stripe history`. Exact input fields: `mammoth schema get billing.stripe.history`.
 
-Example: `mammoth billing stripe history`. Illustrative only: append `--yes --confirm <EXACT_TARGET>` after observing the target.
+Example: `mammoth billing stripe history`. Placeholders are illustrative; resolve IDs and input from observed reads.
 
-Result: `BillingStripeHistoryResult`; mutation `high_impact`, confirmation `confirm_target`, wait policy `not_async`.
+Result: `BillingStripeHistoryResult`; mutation `read`, confirmation `none`, wait policy `not_async`.
 
 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.billing_history Single invocation only.
 
@@ -126,9 +126,9 @@ Status on release: untried; no live run recorded.
 
 Run: `mammoth billing stripe payment-method list`. Exact input fields: `mammoth schema get billing.stripe.payment-method.list`.
 
-Example: `mammoth billing stripe payment-method list`. Illustrative only: append `--yes --confirm <EXACT_TARGET>` after observing the target.
+Example: `mammoth billing stripe payment-method list`. Placeholders are illustrative; resolve IDs and input from observed reads.
 
-Result: `BillingStripePaymentMethodListResult`; mutation `high_impact`, confirmation `confirm_target`, wait policy `not_async`.
+Result: `BillingStripePaymentMethodListResult`; mutation `read`, confirmation `none`, wait policy `not_async`.
 
 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.payment_methods Single invocation only.
 
@@ -156,9 +156,9 @@ Status on release: untried; no live run recorded.
 
 Run: `mammoth billing stripe preview-invoice`. Exact input fields: `mammoth schema get billing.stripe.preview-invoice`.
 
-Example: `mammoth billing stripe preview-invoice`. Illustrative only: append `--yes --confirm <EXACT_TARGET>` after observing the target.
+Example: `mammoth billing stripe preview-invoice`. Placeholders are illustrative; resolve IDs and input from observed reads.
 
-Result: `BillingStripePreviewInvoiceResult`; mutation `high_impact`, confirmation `confirm_target`, wait policy `not_async`.
+Result: `BillingStripePreviewInvoiceResult`; mutation `read`, confirmation `none`, wait policy `not_async`.
 
 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.
 
@@ -176,9 +176,9 @@ Status on release: untried; no live run recorded.
 
 Run: `mammoth billing stripe status`. Exact input fields: `mammoth schema get billing.stripe.status`.
 
-Example: `mammoth billing stripe status`. Illustrative only: append `--yes --confirm <EXACT_TARGET>` after observing the target.
+Example: `mammoth billing stripe status`. Placeholders are illustrative; resolve IDs and input from observed reads.
 
-Result: `BillingStripeStatusResult`; mutation `high_impact`, confirmation `confirm_target`, wait policy `not_async`.
+Result: `BillingStripeStatusResult`; mutation `read`, confirmation `none`, wait policy `not_async`.
 
 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…
 
@@ -196,9 +196,9 @@ Status on release: untried; no live run recorded.
 
 Run: `mammoth billing stripe upcoming-invoice`. Exact input fields: `mammoth schema get billing.stripe.upcoming-invoice`.
 
-Example: `mammoth billing stripe upcoming-invoice`. Illustrative only: append `--yes --confirm <EXACT_TARGET>` after observing the target.
+Example: `mammoth billing stripe upcoming-invoice`. Placeholders are illustrative; resolve IDs and input from observed reads.
 
-Result: `BillingStripeUpcomingInvoiceResult`; mutation `high_impact`, confirmation `confirm_target`, wait policy `not_async`.
+Result: `BillingStripeUpcomingInvoiceResult`; mutation `read`, confirmation `none`, wait policy `not_async`.
 
 Status on release: observed blocker — backend_error: The CLI gates this GET behind --yes --confirm WORKSPACE_ID; with confirmation: HTTP 400 4SUBS074 'Upcoming invoice not found' (no active Stripe subscription on works. Re-check before relying on it.
 
@@ -206,9 +206,9 @@ Status on release: observed blocker — backend_error: The CLI gates this GET be
 
 Run: `mammoth billing stripe usage`. Exact input fields: `mammoth schema get billing.stripe.usage`.
 
-Example: `mammoth billing stripe usage`. Illustrative only: append `--yes --confirm <EXACT_TARGET>` after observing the target.
+Example: `mammoth billing stripe usage`. Placeholders are illustrative; resolve IDs and input from observed reads.
 
-Result: `BillingStripeUsageResult`; mutation `high_impact`, confirmation `confirm_target`, wait policy `not_async`.
+Result: `BillingStripeUsageResult`; mutation `read`, confirmation `none`, wait policy `not_async`.
 
 Status on release: observed blocker — backend_error: The CLI gates this GET behind --yes --confirm WORKSPACE_ID; with confirmation: HTTP 400 5GENR010 UNKNOWN_ERROR 'Unknown error occurred. Re-check before relying on it.
 
@@ -216,9 +216,9 @@ Status on release: observed blocker — backend_error: The CLI gates this GET be
 
 Run: `mammoth billing subscription get`. Exact input fields: `mammoth schema get billing.subscription.get`.
 
-Example: `mammoth billing subscription get`. Illustrative only: append `--yes --confirm <EXACT_TARGET>` after observing the target.
+Example: `mammoth billing subscription get`. Placeholders are illustrative; resolve IDs and input from observed reads.
 
-Result: `BillingSubscriptionGetResult`; mutation `high_impact`, confirmation `confirm_target`, wait policy `not_async`.
+Result: `BillingSubscriptionGetResult`; mutation `read`, confirmation `none`, wait policy `not_async`.
 
 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 current_plan_new, next_action_info, over_limit_info, sms_details Single in…
 

mammoth_cli-2.0.49/mammoth_cli/bundled_skill/mammoth-cli/references/commands/dashboard-qa.md

@@ -0,0 +1,133 @@
+# `dashboard-qa` 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, *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.qa.ask`
+
+Run: `mammoth dashboard qa ask`. Exact input fields: `mammoth schema get dashboard.qa.ask`.
+
+Example: `mammoth dashboard qa ask 123 123 --input '{"body": {"params": {"question": "Summarize revenue by region"}}}'`. Placeholders are illustrative; resolve IDs and input from observed reads.
+
+Result: `DashboardQaAskResult`; 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: answer. AI answered with kpi block and narrative text; not quota-gated Single invocation only; no error-path or variant coverage.
+
+### `dashboard.qa.comment.create`
+
+Run: `mammoth dashboard qa comment create`. Exact input fields: `mammoth schema get dashboard.qa.comment.create`.
+
+Example: `mammoth dashboard qa comment create 123 123 --input '{"body": {"params": {"body": "sample"}}}'`. Placeholders are illustrative; resolve IDs and input from observed reads.
+
+Result: `DashboardQaCommentCreateResult`; 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: session. created comment id=1 on session 1 Single invocation only; no error-path or variant coverage.
+
+### `dashboard.qa.comment.delete`
+
+Run: `mammoth dashboard qa comment delete`. Exact input fields: `mammoth schema get dashboard.qa.comment.delete`.
+
+Example: `mammoth dashboard qa comment delete 123 123 123`. Illustrative only: append `--yes` after observing an owned target.
+
+Result: `DashboardQaCommentDeleteResult`; 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: session. deleted comment 1 from session 1 Single invocation only; no error-path or variant coverage.
+
+### `dashboard.qa.feedback`
+
+Run: `mammoth dashboard qa feedback`. Exact input fields: `mammoth schema get dashboard.qa.feedback`.
+
+Example: `mammoth dashboard qa feedback 123 123 123 --input '{"body": {"params": {"rating": "up"}}}'`. Placeholders are illustrative; resolve IDs and input from observed reads.
+
+Result: `DashboardQaFeedbackResult`; 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: session. recorded thumbs-up feedback on message id=2 Single invocation only; no error-path or variant coverage.
+
+### `dashboard.qa.session.create`
+
+Run: `mammoth dashboard qa session create`. Exact input fields: `mammoth schema get dashboard.qa.session.create`.
+
+Example: `mammoth dashboard qa session create 123 --input '{"body": {"params": {"title": "Revenue report"}}}'`. Placeholders are illustrative; resolve IDs and input from observed reads.
+
+Result: `DashboardQaSessionCreateResult`; 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: session. created qa session id=1 on D=52 Single invocation only; no error-path or variant coverage.
+
+### `dashboard.qa.session.delete`
+
+Run: `mammoth dashboard qa session delete`. Exact input fields: `mammoth schema get dashboard.qa.session.delete`.
+
+Example: `mammoth dashboard qa session delete 123 123`. Illustrative only: append `--yes` after observing an owned target.
+
+Result: `DashboardQaSessionDeleteResult`; 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 forked session 2 and original session 1, both ok:true Single invocation only; no error-path or variant coverage.
+
+### `dashboard.qa.session.fork`
+
+Run: `mammoth dashboard qa session fork`. Exact input fields: `mammoth schema get dashboard.qa.session.fork`.
+
+Example: `mammoth dashboard qa session fork 123 123`. Placeholders are illustrative; resolve IDs and input from observed reads.
+
+Result: `DashboardQaSessionForkResult`; 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: session. forked session 1 -> new session id=2 with copied messages Single invocation only; no error-path or variant coverage.
+
+### `dashboard.qa.session.get`
+
+Run: `mammoth dashboard qa session get`. Exact input fields: `mammoth schema get dashboard.qa.session.get`.
+
+Example: `mammoth dashboard qa session get 123 123`. Placeholders are illustrative; resolve IDs and input from observed reads.
+
+Result: `DashboardQaSessionGetResult`; mutation `read`, 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: session. fetched session 1 Single invocation only; no error-path or variant coverage.
+
+### `dashboard.qa.session.list`
+
+Run: `mammoth dashboard qa session list`. Exact input fields: `mammoth schema get dashboard.qa.session.list`.
+
+Example: `mammoth dashboard qa session list 123`. Placeholders are illustrative; resolve IDs and input from observed reads.
+
+Result: `DashboardQaSessionListResult`; mutation `read`, confirmation `none`, wait policy `not_async`.
+
+Status on release: ran once on CLI 2.0.12 — Published PyPI CLI 1.1.11 / SDK 0.7.1 Q&A session-list read succeeded for retained dashboard 48 with empty mine/shared lists. One dashboard only; not Full. Also: Dashboard sweep 2026-09-18: exit 0 on release with CLI 2.0.12; result keys: mine, shared. 1 own s…
+
+### `dashboard.qa.session.rename`
+
+Run: `mammoth dashboard qa session rename`. Exact input fields: `mammoth schema get dashboard.qa.session.rename`.
+
+Example: `mammoth dashboard qa session rename 123 123 --input '{"body": {"params": {"title": "Revenue report"}}}'`. Placeholders are illustrative; resolve IDs and input from observed reads.
+
+Result: `DashboardQaSessionRenameResult`; 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: session. renamed session 1 Single invocation only; no error-path or variant coverage.
+
+### `dashboard.qa.session.set-visibility`
+
+Run: `mammoth dashboard qa session set-visibility`. Exact input fields: `mammoth schema get dashboard.qa.session.set-visibility`.
+
+Example: `mammoth dashboard qa session set-visibility 123 123 --input '{"body": {"params": {"visibility": "sample"}}}'`. Placeholders are illustrative; resolve IDs and input from observed reads.
+
+Result: `DashboardQaSessionSetVisibilityResult`; 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: session. set visibility=shared Single invocation only; no error-path or variant coverage.
+
+### `dashboard.qa.settings.get`
+
+Run: `mammoth dashboard qa settings get`. Exact input fields: `mammoth schema get dashboard.qa.settings.get`.
+
+Example: `mammoth dashboard qa settings get 123`. Placeholders are illustrative; resolve IDs and input from observed reads.
+
+Result: `DashboardQaSettingsGetResult`; mutation `read`, confirmation `none`, wait policy `not_async`.
+
+Status on release: ran once on CLI 2.0.12 — Published PyPI CLI 1.1.11 / SDK 0.7.1 Q&A settings read succeeded for retained dashboard 48. One dashboard only; not Full. Also: Dashboard sweep 2026-09-18: exit 0 on release with CLI 2.0.12; result keys: allow_viewer_qa, can_manage, public_link. returned all…
+
+### `dashboard.qa.settings.set`
+
+Run: `mammoth dashboard qa settings set`. Exact input fields: `mammoth schema get dashboard.qa.settings.set`.
+
+Example: `mammoth dashboard qa settings set 123 --input '{"body": {"params": {"allow_viewer_qa": true}}}'`. Placeholders are illustrative; resolve IDs and input from observed reads.
+
+Result: `DashboardQaSettingsSetResult`; 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: allow_viewer_qa, can_manage, public_link. set allow_viewer_qa=true Single invocation only; no error-path or variant coverage.

{mammoth_cli-2.0.48 → mammoth_cli-2.0.49}/mammoth_cli/bundled_skill/mammoth-cli/references/commands/dashboard.md

@@ -162,14 +162,6 @@ Result: `DashboardContextUpdateResult`; mutation `benign_mutation`, confirmation
 
 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: context. renamed context 1 Single invocation only; no error-path or variant coverage.
 
-### `dashboard.create`
-
-Run: `mammoth dashboard create`. Exact input fields: `mammoth schema get dashboard.create`.
-
-Example: `mammoth dashboard create 'Summarize revenue by region' --input '{"source": [1]}'`. Placeholders are illustrative; resolve IDs and input from observed reads.
-
-Do not run: not supported — backend returns HTTP 409 4DASH012 DASHBOARD_LEGACY_CREATION_RETIRED (legacy dashboard creation retired). Use dashboard.create-blank or dashboard.v3.generate. Dashboard sweep 2026-09-18, CLI 2.0.12.
-
 ### `dashboard.create-blank`
 
 Run: `mammoth dashboard create-blank`. Exact input fields: `mammoth schema get dashboard.create-blank`.
@@ -438,136 +430,6 @@ Result: `DashboardPublishedVideoExportResult`; mutation `benign_mutation`, confi
 
 Status on release: observed blocker — backend_error: backend_code 4PERM002 PERMISSION_ERROR, "User lacks permission to perform given action" on POST /dashboards/url/IuZl5tk5KcEHJWTy4tnhrA/video (403). Re-check before relying on it.
 
-### `dashboard.qa.ask`
-
-Run: `mammoth dashboard qa ask`. Exact input fields: `mammoth schema get dashboard.qa.ask`.
-
-Example: `mammoth dashboard qa ask 123 123 --input '{"body": {"params": {"question": "Summarize revenue by region"}}}'`. Placeholders are illustrative; resolve IDs and input from observed reads.
-
-Result: `DashboardQaAskResult`; 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: answer. AI answered with kpi block and narrative text; not quota-gated Single invocation only; no error-path or variant coverage.
-
-### `dashboard.qa.comment.create`
-
-Run: `mammoth dashboard qa comment create`. Exact input fields: `mammoth schema get dashboard.qa.comment.create`.
-
-Example: `mammoth dashboard qa comment create 123 123 --input '{"body": {"params": {"body": "sample"}}}'`. Placeholders are illustrative; resolve IDs and input from observed reads.
-
-Result: `DashboardQaCommentCreateResult`; 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: session. created comment id=1 on session 1 Single invocation only; no error-path or variant coverage.
-
-### `dashboard.qa.comment.delete`
-
-Run: `mammoth dashboard qa comment delete`. Exact input fields: `mammoth schema get dashboard.qa.comment.delete`.
-
-Example: `mammoth dashboard qa comment delete 123 123 123`. Illustrative only: append `--yes` after observing an owned target.
-
-Result: `DashboardQaCommentDeleteResult`; 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: session. deleted comment 1 from session 1 Single invocation only; no error-path or variant coverage.
-
-### `dashboard.qa.feedback`
-
-Run: `mammoth dashboard qa feedback`. Exact input fields: `mammoth schema get dashboard.qa.feedback`.
-
-Example: `mammoth dashboard qa feedback 123 123 123 --input '{"body": {"params": {"rating": "up"}}}'`. Placeholders are illustrative; resolve IDs and input from observed reads.
-
-Result: `DashboardQaFeedbackResult`; 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: session. recorded thumbs-up feedback on message id=2 Single invocation only; no error-path or variant coverage.
-
-### `dashboard.qa.session.create`
-
-Run: `mammoth dashboard qa session create`. Exact input fields: `mammoth schema get dashboard.qa.session.create`.
-
-Example: `mammoth dashboard qa session create 123 --input '{"body": {"params": {"title": "Revenue report"}}}'`. Placeholders are illustrative; resolve IDs and input from observed reads.
-
-Result: `DashboardQaSessionCreateResult`; 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: session. created qa session id=1 on D=52 Single invocation only; no error-path or variant coverage.
-
-### `dashboard.qa.session.delete`
-
-Run: `mammoth dashboard qa session delete`. Exact input fields: `mammoth schema get dashboard.qa.session.delete`.
-
-Example: `mammoth dashboard qa session delete 123 123`. Illustrative only: append `--yes` after observing an owned target.
-
-Result: `DashboardQaSessionDeleteResult`; 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 forked session 2 and original session 1, both ok:true Single invocation only; no error-path or variant coverage.
-
-### `dashboard.qa.session.fork`
-
-Run: `mammoth dashboard qa session fork`. Exact input fields: `mammoth schema get dashboard.qa.session.fork`.
-
-Example: `mammoth dashboard qa session fork 123 123`. Placeholders are illustrative; resolve IDs and input from observed reads.
-
-Result: `DashboardQaSessionForkResult`; 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: session. forked session 1 -> new session id=2 with copied messages Single invocation only; no error-path or variant coverage.
-
-### `dashboard.qa.session.get`
-
-Run: `mammoth dashboard qa session get`. Exact input fields: `mammoth schema get dashboard.qa.session.get`.
-
-Example: `mammoth dashboard qa session get 123 123`. Placeholders are illustrative; resolve IDs and input from observed reads.
-
-Result: `DashboardQaSessionGetResult`; mutation `read`, 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: session. fetched session 1 Single invocation only; no error-path or variant coverage.
-
-### `dashboard.qa.session.list`
-
-Run: `mammoth dashboard qa session list`. Exact input fields: `mammoth schema get dashboard.qa.session.list`.
-
-Example: `mammoth dashboard qa session list 123`. Placeholders are illustrative; resolve IDs and input from observed reads.
-
-Result: `DashboardQaSessionListResult`; mutation `read`, confirmation `none`, wait policy `not_async`.
-
-Status on release: ran once on CLI 2.0.12 — Published PyPI CLI 1.1.11 / SDK 0.7.1 Q&A session-list read succeeded for retained dashboard 48 with empty mine/shared lists. One dashboard only; not Full. Also: Dashboard sweep 2026-09-18: exit 0 on release with CLI 2.0.12; result keys: mine, shared. 1 own s…
-
-### `dashboard.qa.session.rename`
-
-Run: `mammoth dashboard qa session rename`. Exact input fields: `mammoth schema get dashboard.qa.session.rename`.
-
-Example: `mammoth dashboard qa session rename 123 123 --input '{"body": {"params": {"title": "Revenue report"}}}'`. Placeholders are illustrative; resolve IDs and input from observed reads.
-
-Result: `DashboardQaSessionRenameResult`; 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: session. renamed session 1 Single invocation only; no error-path or variant coverage.
-
-### `dashboard.qa.session.set-visibility`
-
-Run: `mammoth dashboard qa session set-visibility`. Exact input fields: `mammoth schema get dashboard.qa.session.set-visibility`.
-
-Example: `mammoth dashboard qa session set-visibility 123 123 --input '{"body": {"params": {"visibility": "sample"}}}'`. Placeholders are illustrative; resolve IDs and input from observed reads.
-
-Result: `DashboardQaSessionSetVisibilityResult`; 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: session. set visibility=shared Single invocation only; no error-path or variant coverage.
-
-### `dashboard.qa.settings.get`
-
-Run: `mammoth dashboard qa settings get`. Exact input fields: `mammoth schema get dashboard.qa.settings.get`.
-
-Example: `mammoth dashboard qa settings get 123`. Placeholders are illustrative; resolve IDs and input from observed reads.
-
-Result: `DashboardQaSettingsGetResult`; mutation `read`, confirmation `none`, wait policy `not_async`.
-
-Status on release: ran once on CLI 2.0.12 — Published PyPI CLI 1.1.11 / SDK 0.7.1 Q&A settings read succeeded for retained dashboard 48. One dashboard only; not Full. Also: Dashboard sweep 2026-09-18: exit 0 on release with CLI 2.0.12; result keys: allow_viewer_qa, can_manage, public_link. returned all…
-
-### `dashboard.qa.settings.set`
-
-Run: `mammoth dashboard qa settings set`. Exact input fields: `mammoth schema get dashboard.qa.settings.set`.
-
-Example: `mammoth dashboard qa settings set 123 --input '{"body": {"params": {"allow_viewer_qa": true}}}'`. Placeholders are illustrative; resolve IDs and input from observed reads.
-
-Result: `DashboardQaSettingsSetResult`; 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: allow_viewer_qa, can_manage, public_link. set allow_viewer_qa=true Single invocation only; no error-path or variant coverage.
-
 ### `dashboard.query`
 
 Run: `mammoth dashboard query`. Exact input fields: `mammoth schema get dashboard.query`.