mammoth-cli 2.0.20__tar.gz → 2.0.22__tar.gz

{mammoth_cli-2.0.20 → mammoth_cli-2.0.22}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: mammoth-cli
-Version: 2.0.20
+Version: 2.0.22
 Summary: Command-line interface for the Mammoth Analytics platform
 Project-URL: homepage, https://mammoth.io
 Project-URL: repository, https://github.com/EdgeMetric/mammothsdk
@@ -81,21 +81,21 @@ command. An agent does this by asking the operator to run the login below in
 their own terminal; the CLI never reads credentials from environment variables:
 
 ```bash
-mammoth skill list --output json --no-input
-mammoth skill path --output json --no-input
+mammoth skill list
+mammoth skill path
 # Read the installed SKILL.md before operating.
-mammoth auth status --output json --no-input
+mammoth auth status
 # Compare the reported endpoint with the intended target before doctor.
 # Use app for production; use release only when explicitly intended.
 # Human terminal only, if profile or stored credentials are absent:
 mammoth auth login
 # Then verify configuration, credentials, endpoint, and connectivity:
-mammoth doctor --output json --no-input
+mammoth doctor
 # Then discover a task-specific route:
-mammoth schema find "TASK OR RESOURCE" --output json --no-input
-mammoth schema get COMMAND_ID --output json --no-input
+mammoth schema find "TASK OR RESOURCE"
+mammoth schema get COMMAND_ID
 # Optional API-binding inventory (not the complete CLI surface):
-mammoth capability list --output json --no-input
+mammoth capability list
 ```
 
 For an agent or CI, do not request or paste secrets into chat, prompts, shell
@@ -104,7 +104,7 @@ private owner-only (0600) file outside the repository and pass its path to:
 
 ```bash
 mammoth auth login --input /private/path/credentials.json --storage file \
-  --output json --no-input
+ 
 ```
 
 On Windows, use the approved OS keyring instead; do not use a file fallback
@@ -131,12 +131,13 @@ on automatically off a terminal, so an agent needs no special flags:
 mammoth project list | jq '.data'
 ```
 
-To be explicit, pass `--output json --no-input`. Log in without a prompt with
+To pin it for a whole session, `export MAMMOTH_OUTPUT=json MAMMOTH_NO_INPUT=1`
+(a flag still wins). Log in without a prompt with
 the private, permission-checked file described above:
 
 ```bash
 mammoth auth login --input /private/path/credentials.json --storage file \
-  --output json --no-input
+ 
 ```
 
 Feed multi-field requests as one document instead of many flags:
@@ -150,9 +151,9 @@ For pipeline transformations, prefer the typed commands and inspect their
 schemas before composing input. For example:
 
 ```bash
-mammoth schema get view.transform.filter --output json --no-input
-mammoth schema get view.transform.math --output json --no-input
-mammoth schema get view.transform.substring --output json --no-input
+mammoth schema get view.transform.filter
+mammoth schema get view.transform.math
+mammoth schema get view.transform.substring
 ```
 
 The generic `view task add`, `view task preview`, and `view task update`
@@ -163,7 +164,7 @@ their target explicitly, for example:
 
 ```bash
 mammoth dashboard import-workbook ./sample.twbx --project 456 \
-  --yes --confirm 456 --output json --no-input
+  --yes --confirm 456
 ```
 
 The sample path and project ID are placeholders for a local workbook and a
@@ -198,6 +199,29 @@ putting credentials into the handoff.
 
 ## Give your coding agent the CLI playbook
 
+The shortest handover is a prompt. Fill `PROJECT NAME` and `TASK` and paste
+it into any agent with a bash tool; it installs the CLI, walks you through the
+one-time login, and works from the shipped skill. The long form is
+[docs/agent-prompt.md](https://github.com/EdgeMetric/mammothsdk/blob/main/mammoth-cli/docs/agent-prompt.md).
+
+```text
+Use Mammoth Analytics only through the `mammoth` CLI in bash; run
+`export MAMMOTH_OUTPUT=json MAMMOTH_NO_INPUT=1` once. Onboard me first:
+1. If `mammoth --version` fails, install, then re-check (new shell if needed):
+   curl -fsSL https://raw.githubusercontent.com/EdgeMetric/mammothsdk/main/mammoth-cli/installers/mammoth-install.sh | bash
+2. Run `mammoth auth status`. If it shows no credentials, print exactly this
+   and wait until I say done: "In the Mammoth web app open account settings,
+   create an API key (key + secret) and note your workspace id, then run in
+   your own terminal: mammoth auth login" — never ask for, read, or pass a key
+   or secret yourself, and never run auth login.
+3. Require `mammoth doctor` to pass, then `cat` the SKILL.md at
+   `mammoth skill path` (data.canonical) and follow it.
+Work inside `mammoth project ensure 'PROJECT NAME'` unless I name a project;
+take ids only from reads; `schema get COMMAND_ID` before a new command; read
+results back before reporting.
+TASK: <what to achieve, and how you will know it is done>
+```
+
 The bundled skill describes authentication, discovery, structured input, job
 handling, and confirmations. Install it for the supported coding-agent tools:
 

{mammoth_cli-2.0.20 → mammoth_cli-2.0.22}/README.md

@@ -53,21 +53,21 @@ command. An agent does this by asking the operator to run the login below in
 their own terminal; the CLI never reads credentials from environment variables:
 
 ```bash
-mammoth skill list --output json --no-input
-mammoth skill path --output json --no-input
+mammoth skill list
+mammoth skill path
 # Read the installed SKILL.md before operating.
-mammoth auth status --output json --no-input
+mammoth auth status
 # Compare the reported endpoint with the intended target before doctor.
 # Use app for production; use release only when explicitly intended.
 # Human terminal only, if profile or stored credentials are absent:
 mammoth auth login
 # Then verify configuration, credentials, endpoint, and connectivity:
-mammoth doctor --output json --no-input
+mammoth doctor
 # Then discover a task-specific route:
-mammoth schema find "TASK OR RESOURCE" --output json --no-input
-mammoth schema get COMMAND_ID --output json --no-input
+mammoth schema find "TASK OR RESOURCE"
+mammoth schema get COMMAND_ID
 # Optional API-binding inventory (not the complete CLI surface):
-mammoth capability list --output json --no-input
+mammoth capability list
 ```
 
 For an agent or CI, do not request or paste secrets into chat, prompts, shell
@@ -76,7 +76,7 @@ private owner-only (0600) file outside the repository and pass its path to:
 
 ```bash
 mammoth auth login --input /private/path/credentials.json --storage file \
-  --output json --no-input
+ 
 ```
 
 On Windows, use the approved OS keyring instead; do not use a file fallback
@@ -103,12 +103,13 @@ on automatically off a terminal, so an agent needs no special flags:
 mammoth project list | jq '.data'
 ```
 
-To be explicit, pass `--output json --no-input`. Log in without a prompt with
+To pin it for a whole session, `export MAMMOTH_OUTPUT=json MAMMOTH_NO_INPUT=1`
+(a flag still wins). Log in without a prompt with
 the private, permission-checked file described above:
 
 ```bash
 mammoth auth login --input /private/path/credentials.json --storage file \
-  --output json --no-input
+ 
 ```
 
 Feed multi-field requests as one document instead of many flags:
@@ -122,9 +123,9 @@ For pipeline transformations, prefer the typed commands and inspect their
 schemas before composing input. For example:
 
 ```bash
-mammoth schema get view.transform.filter --output json --no-input
-mammoth schema get view.transform.math --output json --no-input
-mammoth schema get view.transform.substring --output json --no-input
+mammoth schema get view.transform.filter
+mammoth schema get view.transform.math
+mammoth schema get view.transform.substring
 ```
 
 The generic `view task add`, `view task preview`, and `view task update`
@@ -135,7 +136,7 @@ their target explicitly, for example:
 
 ```bash
 mammoth dashboard import-workbook ./sample.twbx --project 456 \
-  --yes --confirm 456 --output json --no-input
+  --yes --confirm 456
 ```
 
 The sample path and project ID are placeholders for a local workbook and a
@@ -170,6 +171,29 @@ putting credentials into the handoff.
 
 ## Give your coding agent the CLI playbook
 
+The shortest handover is a prompt. Fill `PROJECT NAME` and `TASK` and paste
+it into any agent with a bash tool; it installs the CLI, walks you through the
+one-time login, and works from the shipped skill. The long form is
+[docs/agent-prompt.md](https://github.com/EdgeMetric/mammothsdk/blob/main/mammoth-cli/docs/agent-prompt.md).
+
+```text
+Use Mammoth Analytics only through the `mammoth` CLI in bash; run
+`export MAMMOTH_OUTPUT=json MAMMOTH_NO_INPUT=1` once. Onboard me first:
+1. If `mammoth --version` fails, install, then re-check (new shell if needed):
+   curl -fsSL https://raw.githubusercontent.com/EdgeMetric/mammothsdk/main/mammoth-cli/installers/mammoth-install.sh | bash
+2. Run `mammoth auth status`. If it shows no credentials, print exactly this
+   and wait until I say done: "In the Mammoth web app open account settings,
+   create an API key (key + secret) and note your workspace id, then run in
+   your own terminal: mammoth auth login" — never ask for, read, or pass a key
+   or secret yourself, and never run auth login.
+3. Require `mammoth doctor` to pass, then `cat` the SKILL.md at
+   `mammoth skill path` (data.canonical) and follow it.
+Work inside `mammoth project ensure 'PROJECT NAME'` unless I name a project;
+take ids only from reads; `schema get COMMAND_ID` before a new command; read
+results back before reporting.
+TASK: <what to achieve, and how you will know it is done>
+```
+
 The bundled skill describes authentication, discovery, structured input, job
 handling, and confirmations. Install it for the supported coding-agent tools:
 

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

{mammoth_cli-2.0.20 → mammoth_cli-2.0.22}/mammoth_cli/app.py

@@ -813,9 +813,48 @@ def _command_help(command_id: str, record: dict[str, Any] | None) -> str | None:
     example = (record or {}).get("agent_example")
     if example:
         parts.append(f"Example: {example}")
+    fields = _help_input_fields(command_id)
+    if fields:
+        parts.append(f"Input fields: {fields}")
     return "\n\n".join(parts) or None
 
 
+def _help_input_fields(command_id: str) -> str | None:
+    """One line naming the ``--input`` fields, so ``--help`` can replace ``schema get``.
+
+    Required fields come first and are marked with ``*``; each carries its
+    short type, or its enum values. Bounded to keep ``--help`` readable; the
+    full contract stays behind ``schema get``.
+    """
+    from mammoth_cli.services.command_contract import resolve_command_contract
+
+    try:
+        contract = resolve_command_contract(command_id)
+    except Exception:  # noqa: BLE001 -- help must never fail on a contract quirk
+        return None
+    if contract is None or not contract.accepted_fields:
+        return None
+    rendered: list[str] = []
+    fields = sorted(contract.accepted_fields, key=lambda item: (not item.required, item.name))
+    for field in fields:
+        label = f"{field.name}*" if field.required else field.name
+        enum = field.enum_values
+        kind = "|".join(str(item) for item in enum[:6]) if enum else _short_type(field.type_name)
+        rendered.append(f"{label} ({kind})" if kind else label)
+        if len(rendered) == 12 and len(fields) > 12:
+            rendered.append(f"... {len(fields) - 12} more (schema get {command_id})")
+            break
+    return ", ".join(rendered)
+
+
+def _short_type(type_name: str) -> str:
+    """``mammoth.condition.Condition | ...`` -> ``condition``; dotted names lose their module."""
+    text = str(type_name or "")
+    if "condition." in text:
+        return "condition"
+    return " | ".join(part.strip().rsplit(".", 1)[-1] for part in text.split("|"))[:40]
+
+
 def build_app() -> typer.Typer:
     """Construct the full Typer command tree from the command manifests."""
     root = typer.Typer(

mammoth_cli-2.0.22/mammoth_cli/bundled_skill/mammoth-cli/SKILL.md

@@ -0,0 +1,110 @@
+---
+name: mammoth-cli
+version: 2.0.22
+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."
+---
+
+# Mammoth CLI
+
+Use this skill for Mammoth shell work, not for Python SDK integration. The
+CLI is the contract: it validates every request locally, returns one JSON
+envelope, and never needs a flag to do so when its output is piped.
+
+## Start
+
+```bash
+mammoth doctor                          # auth, endpoint, connectivity, version; must succeed
+mammoth project ensure 'PROJECT NAME'   # get-or-create; becomes the active project
+```
+
+`doctor` failing is a precondition failure, not a reason to try the business
+command anyway. Production is the `app` endpoint; use `release` only when the
+task names it, and check `meta.profile`/`auth status` `endpoint` match the
+intended environment before doing anything. If no profile has credentials,
+tell the operator the exact `mammoth auth login --profile PROFILE` command to
+run in their own terminal and wait; never ask for a key or secret in chat,
+never read one from a file or environment variable, never run `auth login`
+yourself. If any envelope carries `meta.update_available`, run its `command`
+before the next step.
+
+## Defaults you do not repeat
+
+- Piped stdout is compact JSON and prompts are off. Only in a session that
+  is not piped, `export MAMMOTH_OUTPUT=json MAMMOTH_NO_INPUT=1` once.
+- `project ensure` saves the active project; `--project` only overrides it.
+  `MAMMOTH_PROFILE` / `MAMMOTH_PROJECT` also work as session defaults.
+- The CLI remembers which dataset owns each view from any read (`view list
+  DATASET_ID`, `view get VIEW_ID`, an upload). After that, no `dataset_id`
+  on transforms, exports or deletes. If a command asks for the parent
+  `DATASET_ID`, read the view once and repeat it; an explicit value always
+  wins.
+- Commands that start platform work wait up to 300 s for the job; on
+  `timeout` use the `job get` recovery command printed, do not resubmit.
+
+## Calling a command
+
+- Ids are positionals; request fields are one `--input '{...}'` document;
+  there are no per-field flags (`project create NAME`, not `--name`).
+- `COMMAND --help` lists the input fields with types; `mammoth schema get
+  COMMAND_ID` is the full contract (add `--input '{"full": true}'` for the
+  JSON Schema); `schema list` is the family index, `schema list view` one
+  family, `schema find WORDS` a search.
+- Uploads return a **dataset** id; transforms, joins, exports and previews
+  take the **view** id from `view list DATASET_ID`.
+- Column inputs and expressions use the exact **display names** the view
+  returns, never backend aliases.
+- Destructive commands need `--yes --confirm ID`. Preserve requested
+  deliverables; cleanup is exact-ID authorized and
+  never means delete-all-owned-resources: delete only ids this run created,
+  one per call, and read back that they are gone.
+- A command whose schema lists `secret_fields` takes `--input FILE` (mode
+  0600); secrets never go in argv, notes, checkpoints or replies.
+
+## Verify before you report
+
+- A success envelope proves the call, not the outcome. After a row-scoped
+  change (set-values, filter, replace, join, fill) run `view data get
+  VIEW_ID` (50 rows by default, `limit` to change) and check rows the
+  condition should have touched and rows it should not have. Sample the
+  target column *before* the change so the after-read has a comparison.
+- A uniform result (every amount 0, every region "Unknown", most join rows
+  unmatched) means the previous step went wrong; stop and re-inspect it.
+- A timeout, exit 7 or interruption does not prove failure; reconcile an
+  `outcome_unknown` (`job get`, `view task list`) before replaying.
+- Run the [report checklist](references/report-checklist.md) before stating
+  a number or calling a step done. When files here disagree,
+  [capabilities](references/capabilities.md) wins over a recipe, and a recipe
+  over the generated command catalog.
+
+## Route only what the task needs
+
+- **Cold start, task plan, or unsupported route:** [task start](references/task-start.md)
+- **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), or [jobs and drafts](references/jobs-drafts.md)
+- **Import, resources, transforms, pipelines, dashboards, exports, or cleanup:**
+  [recipes](references/recipes/index.md) — the
+  [worked example](references/recipes/end-to-end.md) is the whole flow
+- **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
+- **Pause or transfer to another agent:** [handoff](references/handoff.md)
+
+## Handoff checklist
+
+Before yielding work, write a nonsecret checkpoint with the intent and
+acceptance criteria; authorized profile/workspace/project; observed resource
+parents; verified evidence hashes; known jobs and unknown outcomes; remaining
+objectives; and exact cleanup ownership. The receiving agent validates that
+record and re-reads remote state before deciding what to do next. The handoff
+is not a resume command or a grant of authority.

{mammoth_cli-2.0.20 → mammoth_cli-2.0.22}/mammoth_cli/bundled_skill/mammoth-cli/references/auth.md

@@ -31,8 +31,8 @@ human operator:
    history. Credentials are per environment: a release key never
    authenticates on `app`.
 2. Wait for the operator to confirm, then re-run
-   `mammoth auth status --profile PROFILE --output json --no-input` and
-   `mammoth doctor --profile PROFILE --output json --no-input`.
+   `mammoth auth status --profile PROFILE` and
+   `mammoth doctor --profile PROFILE`.
 3. Do not ask the operator to paste the key or secret into chat. Do not run
    `auth login` yourself, with or without `--input`, unless the operator has
    explicitly given you a protected `0600` credential file path to use.
@@ -50,7 +50,7 @@ authentication and then verify the connection. These checks are mandatory even
 when a profile may already exist:
 
 ```bash
-mammoth auth status --profile PROFILE --output json --no-input
+mammoth auth status --profile PROFILE
 ```
 
 If status reports a missing profile or `has_credentials=false`, run the secure
@@ -58,7 +58,7 @@ login flow, then check status again:
 
 ```bash
 mammoth auth login                       # production; add --profile NAME if not 'default'
-mammoth auth status --output json --no-input
+mammoth auth status
 ```
 
 `auth status` is a local profile/credential-presence check; it does not prove
@@ -69,7 +69,7 @@ profile; do not silently reuse, rewrite, or promote it. After the profile is
 present and its endpoint matches, verify the live connection:
 
 ```bash
-mammoth doctor --profile PROFILE --output json --no-input
+mammoth doctor --profile PROFILE
 ```
 
 `doctor` also lists the projects the credential can see (`projects` check)
@@ -87,9 +87,9 @@ targets release.
 ```bash
 mammoth auth login                                        # hidden prompts; production
 mammoth auth login --server-prefix release                # release environment
-mammoth auth login --profile PROFILE --input creds.json --storage file --output json --no-input
-mammoth auth status --profile PROFILE --output json --no-input
-mammoth auth logout --profile default --output json --no-input --yes
+mammoth auth login --profile PROFILE --input creds.json --storage file
+mammoth auth status --profile PROFILE
+mammoth auth logout --profile default --yes
 ```
 
 `PROFILE` means the actual nonsecret profile name selected by the operator or

{mammoth_cli-2.0.20 → mammoth_cli-2.0.22}/mammoth_cli/bundled_skill/mammoth-cli/references/capabilities-misc.md

@@ -16,13 +16,12 @@ Ran once: `agent.session.list`
 
 ## `ai`
 
-Ran once: `ai.condition.generate`, `ai.expression.generate`
+Ran once: `ai.condition.generate`, `ai.expression.generate`, `ai.suggestion.list`
 
 | 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 |
+| `ai.sql.generate` | observed blocker | backend_error: 4DTVW029 conflict: 'Cannot run AI generation for this rule: the input table from the previous rule is not available' on a fresh dataset with no prior rule |
 
 ## `annotation`
 
@@ -39,11 +38,7 @@ Ran once: `automation.create`, `automation.delete`, `automation.list`
 
 ## `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 |
+Ran once: `batch.bulk-delete`, `batch.create`, `batch.delete`, `batch.get`, `batch.list`, `batch.update`
 
 ## `billing`
 
@@ -65,8 +60,8 @@ 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 |
+| `browse.project` | observed blocker | backend_error: GET /workspaces/4/projects/47/browse HTTP 500 empty body |
+| `browse.root` | observed blocker | backend_error: GET /browse still HTTP 500 empty body on release (same as 2026-09-18/19 sweeps) |
 
 ## `client-app`
 
@@ -111,7 +106,7 @@ Ran once: `report.list`
 |---|---|---|
 | `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 |
+| `schedule.list` | observed blocker | backend_error: 5GENR011 NOT_IMPLEMENTED on GET /workspaces/4/projects/47/schedules; schedules remain unimplemented on release |
 
 ## `snippet`
 
@@ -145,4 +140,4 @@ Ran once: `workflow.create`, `workflow.delete`, `workflow.get`, `workflow.graph`
 
 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.
+Evidence collected on CLI releases 1.1.5 through 2.0.21; 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.20 → mammoth_cli-2.0.22}/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 552 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.
+The CLI publishes 552 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`). 260 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.
 
 Status meanings:
 
@@ -34,10 +34,10 @@ The typed `view transform *` commands all submit through `view.task.add`; its ma
 | `user` | 7 | 3 | 0 | 4 |
 | `webhook` | 7 | 5 | 0 | 2 |
 | `addon` | 6 | 0 | 0 | 6 |
-| `batch` | 6 | 5 | 0 | 1 |
+| `batch` | 6 | 6 | 0 | 0 |
 | `file` | 6 | 5 | 0 | 1 |
 | `agent` | 5 | 1 | 0 | 4 |
-| `ai` | 5 | 2 | 0 | 3 |
+| `ai` | 5 | 3 | 0 | 2 |
 | `annotation` | 5 | 1 | 0 | 4 |
 | `client-app` | 5 | 0 | 0 | 5 |
 | `notification` | 5 | 1 | 0 | 4 |
@@ -68,7 +68,7 @@ Ran once: `dashboard.action`, `dashboard.analytics`, `dashboard.archive`, `dashb
 | `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.create` | observed blocker | backend_error: POST /dashboards/v3/templates HTTP 500 empty body / outcome_unknown, as on 2026-09-18 |
 | `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 |
@@ -115,9 +115,9 @@ Ran once: `view.active-user.list`, `view.active-user.mark`, `view.ai.generate-da
 | 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.data-check.update` | observed blocker | backend_error: PATCH with the schema's documented {op: command, path: enable/disable, value: null} shape returns HTTP 500 empty body (CLI outcome_unknown, exit 7) while the mutatio |
 | `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.
+Evidence collected on CLI releases 1.1.5 through 2.0.21; 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.20 → mammoth_cli-2.0.22}/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 552; 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.
+This generated catalog is a lookup table for every command in the published CLI manifest, currently 552; 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:
 

{mammoth_cli-2.0.20 → mammoth_cli-2.0.22}/mammoth_cli/bundled_skill/mammoth-cli/references/commands/activity.md

@@ -4,9 +4,9 @@ Every command returns the standard JSON envelope. On nonzero exit, read the erro
 
 ### `activity.export`
 
-Run: `mammoth activity export`. Exact input fields: `mammoth schema get activity.export --output json --no-input`.
+Run: `mammoth activity export`. Exact input fields: `mammoth schema get activity.export`.
 
-Example: `mammoth activity export --output json --no-input`. Discovery only: this command is fail-closed and must not dispatch a request.
+Example: `mammoth activity export`. Discovery only: this command is fail-closed and must not dispatch a request.
 
 Execution is unavailable for the current contract and returns `unsupported_contract`. Do not infer request fields or retry it; use only a separately typed alternative.
 
@@ -14,9 +14,9 @@ Known restriction: BLOCKED[B19 ACTIVITY_EXPORT_UNTYPED_ASYNC]: format/filters/do
 
 ### `activity.list`
 
-Run: `mammoth activity list`. Exact input fields: `mammoth schema get activity.list --output json --no-input`.
+Run: `mammoth activity list`. Exact input fields: `mammoth schema get activity.list`.
 
-Example: `mammoth activity list --output json --no-input`. Discovery only: this command is fail-closed and must not dispatch a request.
+Example: `mammoth activity list`. Discovery only: this command is fail-closed and must not dispatch a request.
 
 Execution is unavailable for the current contract and returns `unsupported_contract`. Do not infer request fields or retry it; use only a separately typed alternative.