mammoth-cli 2.0.16__tar.gz → 2.0.18__tar.gz

{mammoth_cli-2.0.16 → mammoth_cli-2.0.18}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: mammoth-cli
-Version: 2.0.16
+Version: 2.0.18
 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.8
+Requires-Dist: mammoth-io<0.8,>=0.7.10
 Requires-Dist: platformdirs<5,>=4.10
 Requires-Dist: pydantic<3,>=2.13
 Requires-Dist: pyyaml<7,>=6
@@ -226,7 +226,7 @@ installer and reports modified copies instead of silently replacing them.
 | Organize | `project`, `folder`, `dashboard`, `report`, `template` |
 | Automate | `automation`, `workflow`, `schedule`, `batch`, `webhook` |
 | Administer | `workspace`, `user`, `billing`, `client-app`, `external-key` |
-| Operate the CLI | `auth`, `context`, `config`, `doctor`, `capability`, `schema`, `skill`, `upgrade` |
+| Operate the CLI | `auth`, `context`, `config`, `doctor`, `log`, `capability`, `schema`, `skill`, `upgrade` |
 
 The full generated list is in [docs/reference/commands.md](https://github.com/EdgeMetric/mammothsdk/blob/main/mammoth-cli/docs/reference/commands.md).
 
@@ -243,7 +243,7 @@ The full generated list is in [docs/reference/commands.md](https://github.com/Ed
 | [Safe mutation](https://github.com/EdgeMetric/mammothsdk/blob/main/mammoth-cli/docs/safety.md) | Mutation classes and confirmation policies. |
 | [Output and errors](https://github.com/EdgeMetric/mammothsdk/blob/main/mammoth-cli/docs/reference/output-and-errors.md) | Envelopes, exit codes, error codes. |
 | [Global flags](https://github.com/EdgeMetric/mammothsdk/blob/main/mammoth-cli/docs/reference/global-flags.md) | The flags every command shares. |
-| [Troubleshooting](https://github.com/EdgeMetric/mammothsdk/blob/main/mammoth-cli/docs/troubleshooting.md) | Exit codes, error envelopes, recovery. |
+| [Troubleshooting](https://github.com/EdgeMetric/mammothsdk/blob/main/mammoth-cli/docs/troubleshooting.md) | Exit codes, error envelopes, the run log, recovery. |
 | [Upgrade](https://github.com/EdgeMetric/mammothsdk/blob/main/mammoth-cli/docs/upgrade.md) / [Uninstall](https://github.com/EdgeMetric/mammothsdk/blob/main/mammoth-cli/docs/uninstall.md) | Keep the CLI current, or remove it. |
 | [Command reference](https://github.com/EdgeMetric/mammothsdk/blob/main/mammoth-cli/docs/reference/commands.md) | Every command, grouped by family. |
 

{mammoth_cli-2.0.16 → mammoth_cli-2.0.18}/README.md

@@ -198,7 +198,7 @@ installer and reports modified copies instead of silently replacing them.
 | Organize | `project`, `folder`, `dashboard`, `report`, `template` |
 | Automate | `automation`, `workflow`, `schedule`, `batch`, `webhook` |
 | Administer | `workspace`, `user`, `billing`, `client-app`, `external-key` |
-| Operate the CLI | `auth`, `context`, `config`, `doctor`, `capability`, `schema`, `skill`, `upgrade` |
+| Operate the CLI | `auth`, `context`, `config`, `doctor`, `log`, `capability`, `schema`, `skill`, `upgrade` |
 
 The full generated list is in [docs/reference/commands.md](https://github.com/EdgeMetric/mammothsdk/blob/main/mammoth-cli/docs/reference/commands.md).
 
@@ -215,7 +215,7 @@ The full generated list is in [docs/reference/commands.md](https://github.com/Ed
 | [Safe mutation](https://github.com/EdgeMetric/mammothsdk/blob/main/mammoth-cli/docs/safety.md) | Mutation classes and confirmation policies. |
 | [Output and errors](https://github.com/EdgeMetric/mammothsdk/blob/main/mammoth-cli/docs/reference/output-and-errors.md) | Envelopes, exit codes, error codes. |
 | [Global flags](https://github.com/EdgeMetric/mammothsdk/blob/main/mammoth-cli/docs/reference/global-flags.md) | The flags every command shares. |
-| [Troubleshooting](https://github.com/EdgeMetric/mammothsdk/blob/main/mammoth-cli/docs/troubleshooting.md) | Exit codes, error envelopes, recovery. |
+| [Troubleshooting](https://github.com/EdgeMetric/mammothsdk/blob/main/mammoth-cli/docs/troubleshooting.md) | Exit codes, error envelopes, the run log, recovery. |
 | [Upgrade](https://github.com/EdgeMetric/mammothsdk/blob/main/mammoth-cli/docs/upgrade.md) / [Uninstall](https://github.com/EdgeMetric/mammothsdk/blob/main/mammoth-cli/docs/uninstall.md) | Keep the CLI current, or remove it. |
 | [Command reference](https://github.com/EdgeMetric/mammothsdk/blob/main/mammoth-cli/docs/reference/commands.md) | Every command, grouped by family. |
 

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

{mammoth_cli-2.0.16 → mammoth_cli-2.0.18}/mammoth_cli/app.py

@@ -68,6 +68,7 @@ _GROUP_DESCRIPTIONS = {
     "completion": "Install or print shell completion.",
     "config": "Read and update local CLI configuration.",
     "connector": "Manage data connectors and connector profiles.",
+    "log": "Locate and read the local run log.",
     "context": "Inspect and select the active project context.",
     "dashboard": "Build, query, and publish dashboards.",
     "data-app": "Create and manage data applications.",
@@ -135,6 +136,7 @@ _ROOT_HELP_PANELS = {
     "config": "CLI and agent tools",
     "completion": "CLI and agent tools",
     "skill": "CLI and agent tools",
+    "log": "CLI and agent tools",
     "upgrade": "CLI and agent tools",
     "version": "CLI and agent tools",
 }
@@ -782,6 +784,7 @@ def _execute(invocation: Invocation) -> None:
         invocation.output,
         producer,
         agent_mode=invocation.no_input,
+        invocation=invocation,
         profile=invocation.profile,
     )
 

{mammoth_cli-2.0.16 → mammoth_cli-2.0.18}/mammoth_cli/bundled_skill/mammoth-cli/SKILL.md

@@ -1,5 +1,6 @@
 ---
 name: mammoth-cli
+version: 2.0.18
 description: "Use Mammoth Analytics from a terminal: install or authenticate the CLI, discover its live command contract, and safely manage projects, data, views, pipelines, dashboards, exports, and handoffs."
 ---
 
@@ -38,11 +39,27 @@ the result.
 
 ## Working rules
 
+- Every command takes its resource ids as positionals, its request fields as
+  one `--input` JSON document, plus the shared global options (`--project`,
+  `--profile`, `--output`, `--no-input`, `--yes`, `--confirm`, timeouts).
+  There are no per-field flags: `project create NAME`, not `project create
+  --name NAME`. `schema get COMMAND_ID` lists the positionals and input fields.
 - Resolve workspace/project/dataset/view parents from reads; pass observed IDs
   and `--project`. A dataset does not select a default view. Every `view`
   command that changes, exports, or deletes data requires the exact parent
-  `DATASET_ID` (trailing positional or `dataset_id` input field); only reads
-  may omit it and discover the parent. Get it from `mammoth view get VIEW_ID`.
+  `DATASET_ID`. Where it goes depends on the family: `view delete`, `view
+  data get`, `view preview`, `view get`, `view derivative *`, `view
+  conditional-format *`, `view data-check *`, `view checkpoint *`, `view
+  export list` and the typed destination exports (`view export
+  postgres|s3|dataset|...`) take it as the trailing positional after
+  `VIEW_ID`; `view transform *`, `view draft *`, `view task *`, `view
+  pipeline *` (except `items-all`), `view export csv` and the generic `view
+  export create|get|update|delete|publish-db*` take it as the `dataset_id`
+  input field. `schema get COMMAND_ID` shows which (`positionals` vs
+  `accepted_fields`);
+  reads may omit it and discover the parent. You already have it from the
+  upload result or `view list DATASET_ID`; otherwise `mammoth dataset get
+  DATASET_ID` or `mammoth view get VIEW_ID DATASET_ID`.
 - Uploads and dataset creation return a **dataset** id. Transforms, joins,
   exports, and previews need a **view** id: run `view list DATASET_ID
   --project PROJECT_ID` to get it. See
@@ -51,7 +68,22 @@ the result.
   never backend aliases.
 - Inspect the result after a mutation. A timeout, exit 7, or interruption does
   not prove it failed. Reconcile an `outcome_unknown` before replaying it.
+- A success envelope is not proof the mutation did what you meant. After a
+  row-scoped change (set-values, filter, replace, join, fill) read rows back
+  with `view data get VIEW_ID DATASET_ID` and check both rows the condition
+  should have touched and rows it should not have. A uniform result (every
+  amount 0, every region "Unknown", most join rows unmatched) is a signal
+  that the previous step went wrong, not a fact about the source data: stop
+  and re-inspect that step before building anything on it. Sample the target
+  column *before* a value-changing step so the after-read has something to
+  compare against.
+- Before reporting any number or declaring a step done, run the
+  [report checklist](references/report-checklist.md).
+- When files in this skill disagree, [capabilities](references/capabilities.md)
+  wins over a recipe, and a recipe wins over the generated command catalog.
 - Keep secrets out of argv, task notes, checkpoints, logs, and responses.
+  A command whose schema lists `secret_fields` takes `--input FILE` (mode
+  0600), never an inline document.
 - Preserve requested deliverables. Cleanup is exact-ID authorized and never means delete-all-owned-resources.
 
 ## Route only what the task needs
@@ -60,11 +92,18 @@ the result.
 - **Login, profiles, and authorized scope:** [auth](references/auth.md)
 - **Nested input, output envelopes, confirmations, jobs, or recovery:**
   [input](references/input.md), [machine output](references/machine-output.md),
-  [safety](references/safety.md), [jobs and drafts](references/jobs-drafts.md),
-  or [recovery](references/recovery.md)
+  [safety](references/safety.md), or [jobs and drafts](references/jobs-drafts.md)
 - **Import, resources, transforms, pipelines, dashboards, exports, or cleanup:**
-  [recipes](references/recipes/index.md) and [operations](references/operations.md)
+  [recipes](references/recipes/index.md)
+- **Which id is which, appending rows, response shapes, and other one-off
+  rules:** [operations](references/operations.md)
+- **Something failed or you are unsure whether to continue:**
+  [recovery](references/recovery.md) — failure modes by message and the
+  stop-condition list
 - **A known command family or exact command:** [command catalog](references/command-index.md)
+  — a lookup for the one command you need, not upfront reading; each entry
+  carries its release status line, and a `not supported` or `observed
+  blocker` entry names the route to use instead
 - **Whether a route is proven, known-blocked, or untried on release:**
   [capabilities](references/capabilities.md) — read it before promising a
   deliverable or reporting a failure as a backend fault

mammoth_cli-2.0.18/mammoth_cli/bundled_skill/mammoth-cli/references/capabilities-misc.md

@@ -0,0 +1,148 @@
+# What is proven on release: administration families
+
+Generated from `docs/release-capability-matrix.json`; do not edit by hand. Companion to [capabilities](capabilities.md), which holds the status meanings, the coverage table and the core families (dashboard, dataset, file, folder, job, project, view). Load this file only for a task in one of the families below.
+
+## `activity`
+
+Ran once: `activity.list`
+
+| Command | State | Note |
+|---|---|---|
+| `activity.export` | observed blocker | server_error: see sweep report |
+
+## `agent`
+
+Ran once: `agent.session.list`
+
+## `ai`
+
+Ran once: `ai.condition.generate`, `ai.expression.generate`
+
+| Command | State | Note |
+|---|---|---|
+| `ai.retention.condition` | observed blocker | permission: POST /workspaces/4/projects/24/sql_generation/retention_policy -> HTTP 403 4PERM001 PERMISSION_UNDEFINED, error_object {code:76,message:'Permissions have not been set c |
+| `ai.sql.generate` | observed blocker | backend_error: Fix held (dataset_id required and sent as query param -- request reached backend and got a domain-specific conflict, not an empty api_error) |
+| `ai.suggestion.list` | observed blocker | backend_error: Fix held: release UnifiedPromptSpec (suggestion_type + params, optional dataset_id/dataview_id) shape accepted and dispatched to a real job (id 381), which failed fo |
+
+## `annotation`
+
+Ran once: `annotation.list`
+
+## `automation`
+
+Ran once: `automation.create`, `automation.delete`, `automation.list`
+
+| Command | State | Note |
+|---|---|---|
+| `automation.get` | observed blocker | backend_error: SUSPECTED DEFECT: automation.get on the id just returned by automation.create (id=1) returns HTTP 500 empty body every time (3 retries, several seconds apart), not e |
+| `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 |
+
+## `batch`
+
+Ran once: `batch.bulk-delete`, `batch.delete`, `batch.get`, `batch.list`, `batch.update`
+
+| Command | State | Note |
+|---|---|---|
+| `batch.create` | observed blocker | backend_error: SUSPECTED DEFECT (4th occurrence of this pattern in the sweep): retried with source_id=87 as an actual dataset id, got HTTP 500 empty body / outcome_unknown |
+
+## `billing`
+
+Ran once: `billing.stripe.history`, `billing.stripe.payment-method.list`, `billing.stripe.status`, `billing.subscription.get`
+
+| Command | State | Note |
+|---|---|---|
+| `billing.chargebee-plan` | 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 |
+| `billing.invoice.get` | 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 |
+| `billing.invoice.list` | 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 |
+| `billing.stripe.preview-invoice` | observed blocker | backend_error: The CLI gates this GET behind --yes --confirm WORKSPACE_ID; with confirmation: HTTP 400 4SUBS037 'Failed to perform subscription operation' |
+| `billing.stripe.upcoming-invoice` | 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 |
+| `billing.stripe.usage` | observed blocker | backend_error: The CLI gates this GET behind --yes --confirm WORKSPACE_ID; with confirmation: HTTP 400 5GENR010 UNKNOWN_ERROR 'Unknown error occurred |
+
+## `browse`
+
+Ran once: `browse.workspace`
+
+| Command | State | Note |
+|---|---|---|
+| `browse.folder` | observed blocker | cli_error: rejects folder id 0 although folder.root reports id 0 as the root |
+| `browse.project` | observed blocker | backend_error: SUSPECTED DEFECT: GET /workspaces/4/projects/41/browse also 500s empty body, same pattern as browse.root, on our own fresh empty-of-folders project |
+| `browse.root` | observed blocker | backend_error: SUSPECTED DEFECT: GET /browse returns HTTP 500 empty body, reproduced twice |
+
+## `client-app`
+
+| Command | State | Note |
+|---|---|---|
+| `client-app.list` | observed blocker | forbidden: backend_code=4GENR012 INVALID_TOKEN_FOR_CLIENT_APPS: 'Cannot access this API with API-tokens' on GET /workspaces/4/clientapps |
+
+## `connector`
+
+Ran once: `connector.active`, `connector.ai.session.list`, `connector.list`
+
+| Command | State | Note |
+|---|---|---|
+| `connector.connection.list` | observed blocker | server_error: see sweep report |
+| `connector.get` | observed blocker | backend_error: SUSPECTED DEFECT: connector.get rejects the exact name_key values returned by connector.list ('azure_blob', 'bigquery' both tried) with 4CNTR002 INVALID_CONNECTOR_KE |
+| `connector.query.generate` | observed blocker | blocked_missing_fixture: No real connector connection exists in workspace 4 (connector.list shows all is_added:false; connector.active returns []), matching the documented capabili |
+| `connector.query.status` | observed blocker | blocked_missing_fixture: No real connector connection exists in workspace 4 (connector list shows all is_added:false; connector active returns []) and creating one requires externa |
+
+## `data-app`
+
+Ran once: `data-app.list`
+
+## `external-key`
+
+Ran once: `external-key.list`
+
+## `notification`
+
+Ran once: `notification.list`
+
+## `parameter`
+
+Ran once: `parameter.create`, `parameter.delete`, `parameter.dependencies`, `parameter.get`, `parameter.group.list`, `parameter.list`, `parameter.update`
+
+## `report`
+
+Ran once: `report.list`
+
+## `schedule`
+
+| Command | State | Note |
+|---|---|---|
+| `schedule.create` | observed blocker | backend_error: SUSPECTED CLI/BACKEND DEFECT: second create attempt (with work_items bound to dataset 85) returned HTTP 500 with empty response body, surfaced by CLI as code=outcome |
+| `schedule.get` | observed blocker | blocked_missing_fixture: Not run: id source schedule.list failed with backend_error (5GENR011 NOT_IMPLEMENTED, HTTP 400), so no schedule_id was observed to use |
+| `schedule.list` | observed blocker | backend_error: Re-confirms 5GENR011 NOT_IMPLEMENTED from family 3 |
+
+## `snippet`
+
+Ran once: `snippet.create`, `snippet.delete`, `snippet.dependencies`, `snippet.get`, `snippet.list`, `snippet.update`
+
+## `support`
+
+Ran once: `support.connector-profile.list`, `support.connector.list`, `support.feature-profile.list`, `support.feature.list`, `support.plan.chargebee-list`, `support.plan.list`, `support.plan.self-serve-list`, `support.user.list-all`, `support.workspace.list`
+
+## `template`
+
+Ran once: `template.create`, `template.delete`, `template.get`, `template.list`, `template.update`
+
+## `trash`
+
+Ran once: `trash.add`, `trash.list`, `trash.restore`
+
+## `user`
+
+Ran once: `user.get`, `user.preference.get`, `user.preference.update`
+
+## `webhook`
+
+Ran once: `webhook.create`, `webhook.delete`, `webhook.get`, `webhook.list`, `webhook.update`
+
+## `workflow`
+
+Ran once: `workflow.create`, `workflow.delete`, `workflow.get`, `workflow.graph`, `workflow.list`, `workflow.update`, `workflow.workspace-datasets`, `workflow.workspace-exports`, `workflow.workspace-sources`
+
+## `workspace`
+
+Ran once: `workspace.app-usage`, `workspace.get`, `workspace.list`, `workspace.segment.list`, `workspace.segment.update`, `workspace.storage-breakdown`, `workspace.user.list`
+
+Evidence collected on CLI releases 1.1.5 through 2.0.18; each row's release is recorded in `docs/release-capability-matrix.json` (`evidence_version`). A row that ran on an older release has not been re-run since unless its note says so. Details: `docs/capability-evidence/` in the repository.

mammoth_cli-2.0.18/mammoth_cli/bundled_skill/mammoth-cli/references/capabilities.md

@@ -0,0 +1,123 @@
+# What is proven on release
+
+Generated from `docs/release-capability-matrix.json`; do not edit by hand.
+The CLI publishes 551 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 (every `view transform *` command submits through `view.task.add`). 258 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 --output json --no-input`, run it, and treat the structured error envelope as the answer.
+
+Status meanings:
+
+- **ran once**: one bounded live run on release returned a success envelope (single path; variants and error paths are usually untested). It is not a guarantee that the route works for other inputs.
+- **not supported**: the backend refuses the route on release; the note says why and what to use instead.
+- **observed blocker**: the last run hit an error; the note quotes it. Re-check before relying on the route, and do not retry the same input.
+- **CLI defect fixed, untried since**: the failure was on the CLI side and this release repairs it; nobody has re-run the route yet.
+- Commands not listed under a family are untried.
+
+The typed `view transform *` commands all submit through `view.task.add`; its matrix row names the transformations that ran end to end and were read back (filter, fill-missing, join, pivot, set-values with a condition, text, bulk-replace, convert-type, discard-duplicates). A transformation not named there has the same untried status as any other command.
+
+## Coverage by family
+
+| Family | Commands | Ran once | Not supported | Untried |
+|---|---|---|---|---|
+| `dashboard` | 104 | 81 | 2 | 21 |
+| `view` | 62 | 56 | 0 | 6 |
+| `support` | 45 | 9 | 0 | 36 |
+| `billing` | 23 | 4 | 0 | 19 |
+| `connector` | 22 | 3 | 0 | 19 |
+| `workspace` | 19 | 7 | 0 | 12 |
+| `project` | 17 | 15 | 0 | 2 |
+| `workflow` | 16 | 9 | 0 | 7 |
+| `dataset` | 15 | 12 | 0 | 3 |
+| `parameter` | 14 | 7 | 0 | 7 |
+| `data-app` | 12 | 1 | 0 | 11 |
+| `folder` | 8 | 8 | 0 | 0 |
+| `snippet` | 8 | 6 | 0 | 2 |
+| `automation` | 7 | 3 | 0 | 4 |
+| `user` | 7 | 3 | 0 | 4 |
+| `webhook` | 7 | 5 | 0 | 2 |
+| `addon` | 6 | 0 | 0 | 6 |
+| `batch` | 6 | 5 | 0 | 1 |
+| `file` | 6 | 5 | 0 | 1 |
+| `agent` | 5 | 1 | 0 | 4 |
+| `ai` | 5 | 2 | 0 | 3 |
+| `annotation` | 5 | 1 | 0 | 4 |
+| `client-app` | 5 | 0 | 0 | 5 |
+| `notification` | 5 | 1 | 0 | 4 |
+| `schedule` | 5 | 0 | 0 | 5 |
+| `template` | 5 | 5 | 0 | 0 |
+| `browse` | 4 | 1 | 0 | 3 |
+| `external-key` | 4 | 1 | 0 | 3 |
+| `trash` | 3 | 3 | 0 | 0 |
+| `activity` | 2 | 1 | 0 | 1 |
+| `job` | 2 | 2 | 0 | 0 |
+| `report` | 1 | 1 | 0 | 0 |
+
+Administration families (`workspace`, `user`, `billing`, `support`, `connector`, ...) are in [capabilities-misc](capabilities-misc.md).
+
+## `dashboard`
+
+Ran once: `dashboard.action`, `dashboard.analytics`, `dashboard.archive`, `dashboard.cancel-generation`, `dashboard.canvas.get`, `dashboard.canvas.restore`, `dashboard.canvas.save`, `dashboard.chat.edit`, `dashboard.chat.history`, `dashboard.context.create`, `dashboard.context.delete`, `dashboard.context.extract`, `dashboard.context.list`, `dashboard.context.update`, `dashboard.create-blank`, `dashboard.delete`, `dashboard.descriptor-data`, `dashboard.duplicate`, `dashboard.exemplar.extract`, `dashboard.figure-intent`, `dashboard.get`, `dashboard.get-by-url`, `dashboard.job-by-url`, `dashboard.list`, `dashboard.og-card`, `dashboard.page.plan`, `dashboard.pages.add`, `dashboard.published.canvas`, `dashboard.published.share-page`, `dashboard.qa.ask`, `dashboard.qa.comment.create`, `dashboard.qa.comment.delete`, `dashboard.qa.feedback`, `dashboard.qa.session.create`, `dashboard.qa.session.delete`, `dashboard.qa.session.fork`, `dashboard.qa.session.get`, `dashboard.qa.session.list`, `dashboard.qa.session.rename`, `dashboard.qa.session.set-visibility`, `dashboard.qa.settings.get`, `dashboard.qa.settings.set`, `dashboard.query`, `dashboard.restore`, `dashboard.rls.assignment.list`, `dashboard.rls.assignment.set`, `dashboard.rls.column.list`, `dashboard.rls.value.list`, `dashboard.share`, `dashboard.signature.create`, `dashboard.signature.delete`, `dashboard.signature.list`, `dashboard.signature.update`, `dashboard.style.custom.create`, `dashboard.style.custom.delete`, `dashboard.style.custom.list`, `dashboard.style.custom.update`, `dashboard.style.default.get`, `dashboard.style.default.set`, `dashboard.style.derive`, `dashboard.style.extract-brand`, `dashboard.style.preset.list`, `dashboard.style.token.list`, `dashboard.suggestion.list`, `dashboard.swap-data`, `dashboard.tags.delete`, `dashboard.tags.list`, `dashboard.tags.merge`, `dashboard.tags.rename`, `dashboard.tags.set`, `dashboard.template.apply`, `dashboard.template.fit`, `dashboard.template.get`, `dashboard.template.list`, `dashboard.template.preview`, `dashboard.template.resolve-mapping`, `dashboard.templates.pending`, `dashboard.trash`, `dashboard.update`, `dashboard.v3.generate`, `dashboard.video-state`
+
+| Command | State | Note |
+|---|---|---|
+| `dashboard.create` | not supported | Not supported on release: 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.pdf.export` | not supported | Not supported from the CLI on release: backend HTTP 400 4GENR001 requires params.data to be the browser-hydrated DashboardData map and states it cannot rebuild it from stored descriptors (dashboard sweep and Haiku e2e, 2026-09-18). The route works only with a client render pass. |
+| `dashboard.data.draft` | observed blocker | blocked_missing_fixture: Dashboard 56 (create-blank/v3 engine) has no widgets in its canvas and getDraftData rejects with backend_code 4DASH004 DASHBOARD_WRONG_ENGINE: "This dashbo |
+| `dashboard.data.published` | observed blocker | blocked_missing_fixture: Same as dashboard.data.draft: backend_code 4DASH004 DASHBOARD_WRONG_ENGINE on /dashboards/56/getPublishData |
+| `dashboard.published-data-by-url` | observed blocker | blocked_missing_fixture: backend_code 4DASH004 DASHBOARD_WRONG_ENGINE on /dashboards/url/IuZl5tk5KcEHJWTy4tnhrA/getPublishData, same class of blocker as widget-data: this v3 dashbo |
+| `dashboard.published.data` | observed blocker | blocked_missing_fixture: Could not publish dashboard 59 to reach a live published state: `dashboard action 59 {action:publish-presentation}` failed twice with HTTP 500 outcome_unkn |
+| `dashboard.published.pdf-artifact` | observed blocker | blocked_missing_fixture: Same as dashboard.pdf-artifact: no real pdf job available; used job 313 (descriptor-data job) as the only real job id in hand and got backend_code 4DASH001 |
+| `dashboard.published.pdf.export` | observed blocker | backend_error: Got backend_code 4PERM002 PERMISSION_ERROR, "User lacks permission to perform given action" on POST /dashboards/url/IuZl5tk5KcEHJWTy4tnhrA/pdf (403), envelope: {"err |
+| `dashboard.published.video.export` | observed blocker | backend_error: backend_code 4PERM002 PERMISSION_ERROR, "User lacks permission to perform given action" on POST /dashboards/url/IuZl5tk5KcEHJWTy4tnhrA/video (403) |
+| `dashboard.source.list` | observed blocker | blocker; still broken, not one of the 11 CLI-fixed commands |
+| `dashboard.template.create` | observed blocker | backend: POST /dashboards/v3/templates -> HTTP 500, empty response_body, request_id:null, code:outcome_unknown |
+| `dashboard.template.delete` | observed blocker | blocked_missing_fixture: dashboard.template.create never produced an owned template (HTTP 500 both attempts, reconciled as not-committed via template list) |
+| `dashboard.templates.use` | observed blocker | skipped_out_of_scope: BRIEF instructs running templates.use "on that template" (i.e |
+| `dashboard.video.export` | observed blocker | backend_error: After publishing dashboard 56 (dashboard.share public + dashboard.action publish-presentation), the previously-documented "publish the dashboard before exporting a v |
+| `dashboard.widget-data` | observed blocker | blocked_missing_fixture: backend_code 4DASH004 DASHBOARD_WRONG_ENGINE, "This dashboard uses a different rendering engine -- use the matching endpoints", on POST /dashboards/56/widg |
+| `dashboard.widget-data-by-url` | observed blocker | blocked_missing_fixture: Same backend_code 4DASH004 DASHBOARD_WRONG_ENGINE, on POST /dashboards/url/IuZl5tk5KcEHJWTy4tnhrA/widgets/data |
+
+## `dataset`
+
+Ran once: `dataset.batch-data`, `dataset.bulk-delete`, `dataset.create`, `dataset.data`, `dataset.delete`, `dataset.file-settings.get`, `dataset.file-settings.undo`, `dataset.file-settings.update`, `dataset.get`, `dataset.list`, `dataset.restore`, `dataset.trash`
+
+| Command | State | Note |
+|---|---|---|
+| `dataset.bulk-update` | observed blocker | skipped_out_of_scope: SUSPECTED DEFECT: schema.get advertises this command's precondition as 'BLOCKED[B07 DATASET_PATCH_UNTYPED]; reserved, not registered' and its only documented |
+| `dataset.create-from-pdf` | observed blocker | backend: POST /workspaces/4/projects/24/datasets-from-pdf |
+
+## `file`
+
+Ran once: `file.bulk-delete`, `file.delete`, `file.get`, `file.list`, `file.upload`
+
+| Command | State | Note |
+|---|---|---|
+| `file.update` | observed blocker | backend_error: CLI accepted the typed patch and submitted job 314 (handle_file on /workspaces/4/projects/21/files/50), then correctly reported timeout after 60s with recovery_comma |
+
+## `folder`
+
+Ran once: `folder.bulk-delete`, `folder.create`, `folder.delete`, `folder.get`, `folder.list`, `folder.move`, `folder.trash`, `folder.update`
+
+## `job`
+
+Ran once: `job.get`, `job.get-many`
+
+## `project`
+
+Ran once: `project.bulk-delete`, `project.bulk-update`, `project.checkpoint.list`, `project.create`, `project.data-check.list`, `project.delete`, `project.list`, `project.pending-changes`, `project.publish-credentials`, `project.resource-dependencies`, `project.resource-dependencies.update`, `project.resource-status`, `project.sample-flow`, `project.update`, `project.user.add`
+
+| Command | State | Note |
+|---|---|---|
+| `project.user.update` | observed blocker | backend_error: HTTP 400 4PROJ010 ROLE_ALREADY_ASSIGNED: "Role already assigned to the user" -- targeted our own user (id 5, already project_admin as project owner) |
+
+## `view`
+
+Ran once: `view.active-user.list`, `view.active-user.mark`, `view.ai.generate-data`, `view.ai.profile`, `view.bulk-delete`, `view.checkpoint.create`, `view.checkpoint.delete`, `view.checkpoint.get`, `view.checkpoint.list`, `view.checkpoint.update`, `view.conditional-format.create`, `view.conditional-format.delete-all`, `view.conditional-format.list`, `view.conditional-format.update`, `view.create`, `view.data-check.create`, `view.data-check.delete`, `view.data-check.get`, `view.data-check.list`, `view.data.get`, `view.data.query`, `view.delete`, `view.derivative.create`, `view.derivative.delete`, `view.derivative.list`, `view.derivative.update`, `view.draft.command`, `view.export.delete`, `view.export.get`, `view.export.list`, `view.export.publish-db`, `view.export.update`, `view.exportable-config.apply`, `view.exportable-config.get`, `view.get`, `view.list`, `view.parameter-context`, `view.pipeline.edit`, `view.pipeline.get`, `view.pipeline.items`, `view.pipeline.rerun`, `view.preview`, `view.restore`, `view.task.add`, `view.task.delete`, `view.task.get`, `view.task.list`, `view.task.preview`, `view.task.update`, `view.trash`, `view.version.apply`, `view.version.delete`, `view.version.get`, `view.version.list`, `view.version.update`
+
+| Command | State | Note |
+|---|---|---|
+| `view.ai.generation-info` | observed blocker | backend: GET /workspaces/4/projects/24/datasets/54/dataviews/76/data/generate -> HTTP 400 5GENR011 NOT_IMPLEMENTED 'Not implemented', request_id:null |
+| `view.data-check.update` | observed blocker | backend_error: SUSPECTED DEFECT: PATCH returned HTTP 500 empty body / CLI code=outcome_unknown, but a follow-up get confirmed the mutation actually applied (enabled:false, updated_ |
+| `view.derivative.data` | observed blocker | backend_error: SUSPECTED DEFECT: using the CLI's own documented agent_example body verbatim, derivative data fetch returns HTTP 500 empty body / outcome_unknown, reproduced twice ( |
+| `view.export.create` | observed blocker | backend: CLI accepts the request (exit 0, job 358 accepted on POST /dataviews/76/actions), but job get 358 -> status:error, response:{"error":{"message":"'destination'"}} (a raw Py |
+| `view.export.publish-db-update` | CLI defect fixed, untried since | 2.0.16 (example value is the documented {"odbc_type": "postgres"} object (a bare string is rejected)) |
+
+Evidence collected on CLI releases 1.1.5 through 2.0.18; each row's release is recorded in `docs/release-capability-matrix.json` (`evidence_version`). A row that ran on an older release has not been re-run since unless its note says so. Details: `docs/capability-evidence/` in the repository.

{mammoth_cli-2.0.16 → mammoth_cli-2.0.18}/mammoth_cli/bundled_skill/mammoth-cli/references/command-index.md

@@ -1,6 +1,6 @@
 # Published CLI command catalog
 
-This generated catalog covers every command in the published CLI manifest, currently 549. 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 --output json --no-input`; `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 551; 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 --output json --no-input`; `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:
 
@@ -28,6 +28,7 @@ Load only the applicable domain file:
 - [file](commands/file.md) — 9 published commands
 - [folder](commands/folder.md) — 10 published commands
 - [job](commands/job.md) — 4 published commands
+- [log](commands/log.md) — 2 published commands
 - [notification](commands/notification.md) — 5 published commands
 - [parameter](commands/parameter.md) — 14 published commands
 - [project](commands/project.md) — 18 published commands

{mammoth_cli-2.0.16 → mammoth_cli-2.0.18}/mammoth_cli/bundled_skill/mammoth-cli/references/commands/activity.md

@@ -1,5 +1,7 @@
 # `activity` 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).
+
 ### `activity.export`
 
 Run: `mammoth activity export`. Exact input fields: `mammoth schema get activity.export --output json --no-input`.

mammoth_cli-2.0.18/mammoth_cli/bundled_skill/mammoth-cli/references/commands/addon.md

@@ -0,0 +1,73 @@
+# `addon` 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).
+
+### `addon.connector.add`
+
+Run: `mammoth addon connector add`. Exact input fields: `mammoth schema get addon.connector.add --output json --no-input`.
+
+Example: `mammoth addon connector add --input '{"connector_id": 42}' --output json --no-input`. Illustrative only: append `--yes --confirm <EXACT_TARGET>` after observing the target.
+
+Result: `AddonConnectorAddResult`; mutation `high_impact`, confirmation `confirm_target`, wait policy `not_async`.
+
+Status on release: untried; no live run recorded.
+
+### `addon.connector.remove`
+
+Run: `mammoth addon connector remove`. Exact input fields: `mammoth schema get addon.connector.remove --output json --no-input`.
+
+Example: `mammoth addon connector remove --input '{"connector_id": 42}' --output json --no-input`. Illustrative only: append `--yes --confirm <EXACT_TARGET>` after observing the target.
+
+Result: `AddonConnectorRemoveResult`; mutation `high_impact`, confirmation `confirm_target`, wait policy `not_async`.
+
+Status on release: untried; no live run recorded.
+
+### `addon.list`
+
+Run: `mammoth addon list`. Exact input fields: `mammoth schema get addon.list --output json --no-input`.
+
+Example: `mammoth addon list --output json --no-input`. Placeholders are illustrative; resolve IDs and input from observed reads.
+
+Result: `AddonListResult`; mutation `read`, confirmation `none`, wait policy `not_async`.
+
+Status on release: untried; no live run recorded.
+
+### `addon.storage.add`
+
+Run: `mammoth addon storage add`. Exact input fields: `mammoth schema get addon.storage.add --output json --no-input`.
+
+Example: `mammoth addon storage add --input '{"additional_storage_gb": 1}' --output json --no-input`. Illustrative only: append `--yes --confirm <EXACT_TARGET>` after observing the target.
+
+Result: `AddonStorageAddResult`; mutation `high_impact`, confirmation `confirm_target`, wait policy `not_async`.
+
+Status on release: untried; no live run recorded.
+
+### `addon.storage.remove`
+
+Run: `mammoth addon storage remove`. Exact input fields: `mammoth schema get addon.storage.remove --output json --no-input`.
+
+Example: `mammoth addon storage remove --input '{"removal_storage_gb": 1}' --output json --no-input`. Illustrative only: append `--yes --confirm <EXACT_TARGET>` after observing the target.
+
+Result: `AddonStorageRemoveResult`; mutation `high_impact`, confirmation `confirm_target`, wait policy `not_async`.
+
+Status on release: untried; no live run recorded.
+
+### `addon.user.add`
+
+Run: `mammoth addon user add`. Exact input fields: `mammoth schema get addon.user.add --output json --no-input`.
+
+Example: `mammoth addon user add --output json --no-input`. Illustrative only: append `--yes --confirm <EXACT_TARGET>` after observing the target.
+
+Result: `AddonUserAddResult`; mutation `high_impact`, confirmation `confirm_target`, wait policy `not_async`.
+
+Status on release: untried; no live run recorded.
+
+### `addon.user.remove`
+
+Run: `mammoth addon user remove`. Exact input fields: `mammoth schema get addon.user.remove --output json --no-input`.
+
+Example: `mammoth addon user remove --input '{"user_count": 1}' --output json --no-input`. Illustrative only: append `--yes --confirm <EXACT_TARGET>` after observing the target.
+
+Result: `AddonUserRemoveResult`; mutation `high_impact`, confirmation `confirm_target`, wait policy `not_async`.
+
+Status on release: untried; no live run recorded.

mammoth_cli-2.0.18/mammoth_cli/bundled_skill/mammoth-cli/references/commands/agent.md

@@ -0,0 +1,53 @@
+# `agent` 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).
+
+### `agent.chat`
+
+Run: `mammoth agent chat`. Exact input fields: `mammoth schema get agent.chat --output json --no-input`.
+
+Example: `mammoth agent chat --input '{"message": "Summarize revenue by region", "scope": {"sample_key": "Status"}}' --output json --no-input`. Placeholders are illustrative; resolve IDs and input from observed reads.
+
+Result: `AgentChatResult`; mutation `benign_mutation`, confirmation `none`, wait policy `not_async`.
+
+Status on release: untried; no live run recorded.
+
+### `agent.session.delete`
+
+Run: `mammoth agent session delete`. Exact input fields: `mammoth schema get agent.session.delete --output json --no-input`.
+
+Example: `mammoth agent session delete resource-123 --output json --no-input`. Illustrative only: append `--yes` after observing an owned target.
+
+Result: `AgentSessionDeleteResult`; mutation `destructive`, confirmation `prompt_or_yes`, wait policy `not_async`.
+
+Status on release: untried; no live run recorded.
+
+### `agent.session.list`
+
+Run: `mammoth agent session list`. Exact input fields: `mammoth schema get agent.session.list --output json --no-input`.
+
+Example: `mammoth agent session list --output json --no-input`. Placeholders are illustrative; resolve IDs and input from observed reads.
+
+Result: `AgentSessionListResult`; mutation `read`, confirmation `none`, wait policy `not_async`.
+
+Status on release: ran once on CLI 2.0.11 — Read-only sweep 2026-09-18: exit 0 on release with CLI 2.0.11; result keys: sessions. Single read only; no fixture variants, error envelopes, or write paths assessed.
+
+### `agent.session.messages`
+
+Run: `mammoth agent session messages`. Exact input fields: `mammoth schema get agent.session.messages --output json --no-input`.
+
+Example: `mammoth agent session messages resource-123 --output json --no-input`. Placeholders are illustrative; resolve IDs and input from observed reads.
+
+Result: `AgentSessionMessagesResult`; mutation `read`, confirmation `none`, wait policy `not_async`.
+
+Status on release: untried; no live run recorded.
+
+### `agent.session.set-visibility`
+
+Run: `mammoth agent session set-visibility`. Exact input fields: `mammoth schema get agent.session.set-visibility --output json --no-input`.
+
+Example: `mammoth agent session set-visibility resource-123 --input '{"visibility": "sample"}' --output json --no-input`. Placeholders are illustrative; resolve IDs and input from observed reads.
+
+Result: `AgentSessionSetVisibilityResult`; mutation `benign_mutation`, confirmation `none`, wait policy `not_async`.
+
+Status on release: untried; no live run recorded.