mammoth-cli 2.0.10__tar.gz → 2.0.12__tar.gz

{mammoth_cli-2.0.10 → mammoth_cli-2.0.12}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: mammoth-cli
-Version: 2.0.10
+Version: 2.0.12
 Summary: Command-line interface for the Mammoth Analytics platform
 Project-URL: homepage, https://mammoth.io
 Project-URL: repository, https://github.com/EdgeMetric/mammothsdk
@@ -17,7 +17,7 @@ Classifier: Topic :: Software Development :: Libraries :: Python Modules
 Requires-Python: <3.15,>=3.12
 Requires-Dist: jsonschema>=4.20
 Requires-Dist: keyring<26,>=25.7
-Requires-Dist: mammoth-io<0.8,>=0.7.3
+Requires-Dist: mammoth-io<0.8,>=0.7.4
 Requires-Dist: platformdirs<5,>=4.10
 Requires-Dist: pydantic<3,>=2.13
 Requires-Dist: pyyaml<7,>=6

{mammoth_cli-2.0.10 → mammoth_cli-2.0.12}/mammoth_cli/__init__.py

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

{mammoth_cli-2.0.10 → mammoth_cli-2.0.12}/mammoth_cli/bundled_skill/mammoth-cli/SKILL.md

@@ -43,6 +43,10 @@ the result.
   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`.
+- 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
+  [resources](references/recipes/resources.md).
 - Use exact view-schema **display names** in expressions and column inputs,
   never backend aliases.
 - Inspect the result after a mutation. A timeout, exit 7, or interruption does

{mammoth_cli-2.0.10 → mammoth_cli-2.0.12}/mammoth_cli/bundled_skill/mammoth-cli/references/auth.md

@@ -72,6 +72,11 @@ present and its endpoint matches, verify the live connection:
 mammoth doctor --profile PROFILE --output json --no-input
 ```
 
+`doctor` also lists the projects the credential can see (`projects` check)
+and verifies that `--project` or the selected project is one of them
+(`project_context` check). Pick the project id from that list; the API does
+not expose write permission, so the first write is what proves it.
+
 Do not continue to schema discovery or business operations after an
 authentication or doctor failure. The `app` server prefix is the production
 default; release or other environment credentials do not imply authorization

{mammoth_cli-2.0.10 → mammoth_cli-2.0.12}/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 547. 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 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.
 
 Load only the applicable domain file:
 
@@ -22,11 +22,11 @@ Load only the applicable domain file:
 - [context](commands/context.md) — 3 published commands
 - [dashboard](commands/dashboard.md) — 104 published commands
 - [data-app](commands/data-app.md) — 12 published commands
-- [dataset](commands/dataset.md) — 16 published commands
+- [dataset](commands/dataset.md) — 17 published commands
 - [doctor](commands/doctor.md) — 1 published commands
 - [external-key](commands/external-key.md) — 4 published commands
 - [file](commands/file.md) — 9 published commands
-- [folder](commands/folder.md) — 9 published commands
+- [folder](commands/folder.md) — 10 published commands
 - [job](commands/job.md) — 4 published commands
 - [notification](commands/notification.md) — 5 published commands
 - [parameter](commands/parameter.md) — 14 published commands

{mammoth_cli-2.0.10 → mammoth_cli-2.0.12}/mammoth_cli/bundled_skill/mammoth-cli/references/commands/dataset.md

@@ -82,6 +82,14 @@ Example: `mammoth dataset file-settings update 123 --input '{"delimiter": "sampl
 
 Expected success: `DatasetFileSettingsUpdateResult` in the standard JSON envelope; mutation `benign_mutation`, confirmation `none`, wait policy `not_async`. On nonzero exit, inspect the JSON error envelope and its `recovery_commands`; do not guess request fields. See [representative envelopes](../machine-output.md) for concrete success/error shapes.
 
+### `dataset.find`
+
+Run: `mammoth dataset find`. Exact input fields: `mammoth schema get dataset.find --output json --no-input`.
+
+Example: `mammoth dataset find sales --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
+
+Expected success: `DatasetFindResult` in the standard JSON envelope; mutation `read`, confirmation `none`, wait policy `not_async`. On nonzero exit, inspect the JSON error envelope and its `recovery_commands`; do not guess request fields. See [representative envelopes](../machine-output.md) for concrete success/error shapes.
+
 ### `dataset.get`
 
 Run: `mammoth dataset get`. Exact input fields: `mammoth schema get dataset.get --output json --no-input`.

{mammoth_cli-2.0.10 → mammoth_cli-2.0.12}/mammoth_cli/bundled_skill/mammoth-cli/references/commands/folder.md

@@ -24,6 +24,14 @@ Example: `mammoth folder delete 123 --output json --no-input`. Illustrative only
 
 Expected success: `FolderDeleteResult` in the standard JSON envelope; mutation `destructive`, confirmation `prompt_or_yes`, wait policy `not_async`. On nonzero exit, inspect the JSON error envelope and its `recovery_commands`; do not guess request fields. See [representative envelopes](../machine-output.md) for concrete success/error shapes.
 
+### `folder.find`
+
+Run: `mammoth folder find`. Exact input fields: `mammoth schema get folder.find --output json --no-input`.
+
+Example: `mammoth folder find reports --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
+
+Expected success: `FolderFindResult` in the standard JSON envelope; mutation `read`, confirmation `none`, wait policy `not_async`. On nonzero exit, inspect the JSON error envelope and its `recovery_commands`; do not guess request fields. See [representative envelopes](../machine-output.md) for concrete success/error shapes.
+
 ### `folder.get`
 
 Run: `mammoth folder get`. Exact input fields: `mammoth schema get folder.get --output json --no-input`.

{mammoth_cli-2.0.10 → mammoth_cli-2.0.12}/mammoth_cli/bundled_skill/mammoth-cli/references/commands/view.md

@@ -240,7 +240,7 @@ Expected success: `ViewDerivativeUpdateResult` in the standard JSON envelope; mu
 
 Run: `mammoth view draft auto-run`. Exact input fields: `mammoth schema get view.draft.auto-run --output json --no-input`.
 
-Example: `mammoth view draft auto-run 123 --input '{"enabled": true}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
+Example: `mammoth view draft auto-run 123 --input '{"enabled": true, "dataset_id": 456}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
 
 Expected success: `ViewDraftAutoRunResult` in the standard JSON envelope; mutation `reversible_pipeline`, confirmation `none`, wait policy `always_wait`. On nonzero exit, inspect the JSON error envelope and its `recovery_commands`; do not guess request fields. See [representative envelopes](../machine-output.md) for concrete success/error shapes.
 
@@ -248,7 +248,7 @@ Expected success: `ViewDraftAutoRunResult` in the standard JSON envelope; mutati
 
 Run: `mammoth view draft command`. Exact input fields: `mammoth schema get view.draft.command --output json --no-input`.
 
-Example: `mammoth view draft command 123 --input '{"command": "sample"}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
+Example: `mammoth view draft command 123 --input '{"command": "sample", "dataset_id": 456}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
 
 Expected success: `ViewDraftCommandResult` in the standard JSON envelope; mutation `benign_mutation`, confirmation `none`, wait policy `not_async`. On nonzero exit, inspect the JSON error envelope and its `recovery_commands`; do not guess request fields. See [representative envelopes](../machine-output.md) for concrete success/error shapes.
 
@@ -256,7 +256,7 @@ Expected success: `ViewDraftCommandResult` in the standard JSON envelope; mutati
 
 Run: `mammoth view draft discard`. Exact input fields: `mammoth schema get view.draft.discard --output json --no-input`.
 
-Example: `mammoth view draft discard 123 --output json --no-input`. Illustrative only: append `--yes` after observing an owned target.
+Example: `mammoth view draft discard 123 --input '{"dataset_id": 456}' --output json --no-input`. Illustrative only: append `--yes` after observing an owned target.
 
 Expected success: `ViewDraftDiscardResult` in the standard JSON envelope; mutation `destructive`, confirmation `prompt_or_yes`, wait policy `always_wait`. On nonzero exit, inspect the JSON error envelope and its `recovery_commands`; do not guess request fields. See [representative envelopes](../machine-output.md) for concrete success/error shapes.
 
@@ -264,7 +264,7 @@ Expected success: `ViewDraftDiscardResult` in the standard JSON envelope; mutati
 
 Run: `mammoth view draft enter`. Exact input fields: `mammoth schema get view.draft.enter --output json --no-input`.
 
-Example: `mammoth view draft enter 123 --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
+Example: `mammoth view draft enter 123 --input '{"dataset_id": 456}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
 
 Expected success: `ViewDraftEnterResult` in the standard JSON envelope; mutation `reversible_pipeline`, confirmation `none`, wait policy `always_wait`. On nonzero exit, inspect the JSON error envelope and its `recovery_commands`; do not guess request fields. See [representative envelopes](../machine-output.md) for concrete success/error shapes.
 
@@ -280,7 +280,7 @@ Expected success: `ViewDraftStatusResult` in the standard JSON envelope; mutatio
 
 Run: `mammoth view draft submit`. Exact input fields: `mammoth schema get view.draft.submit --output json --no-input`.
 
-Example: `mammoth view draft submit 123 --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
+Example: `mammoth view draft submit 123 --input '{"dataset_id": 456}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
 
 Expected success: `ViewDraftSubmitResult` in the standard JSON envelope; mutation `reversible_pipeline`, confirmation `none`, wait policy `always_wait`. On nonzero exit, inspect the JSON error envelope and its `recovery_commands`; do not guess request fields. See [representative envelopes](../machine-output.md) for concrete success/error shapes.
 
@@ -662,7 +662,7 @@ Expected success: `ViewTaskUpdateResult` in the standard JSON envelope; mutation
 
 Run: `mammoth view transform add-column`. Exact input fields: `mammoth schema get view.transform.add-column --output json --no-input`.
 
-Example: `mammoth view transform add-column 123 --input '{"name": "Revenue report"}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
+Example: `mammoth view transform add-column 123 --input '{"name": "Revenue report", "dataset_id": 456}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
 
 Expected success: `ViewTransformAddColumnResult` in the standard JSON envelope; mutation `reversible_pipeline`, confirmation `none`, wait policy `always_wait`. On nonzero exit, inspect the JSON error envelope and its `recovery_commands`; do not guess request fields. See [representative envelopes](../machine-output.md) for concrete success/error shapes.
 
@@ -670,7 +670,7 @@ Expected success: `ViewTransformAddColumnResult` in the standard JSON envelope;
 
 Run: `mammoth view transform add-sql`. Exact input fields: `mammoth schema get view.transform.add-sql --output json --no-input`.
 
-Example: `mammoth view transform add-sql 123 --input '{"query": "SELECT region, SUM(revenue) FROM data GROUP BY region"}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
+Example: `mammoth view transform add-sql 123 --input '{"query": "SELECT region, SUM(revenue) FROM data GROUP BY region", "dataset_id": 456}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
 
 Expected success: `ViewTransformAddSqlResult` in the standard JSON envelope; mutation `reversible_pipeline`, confirmation `none`, wait policy `always_wait`. On nonzero exit, inspect the JSON error envelope and its `recovery_commands`; do not guess request fields. See [representative envelopes](../machine-output.md) for concrete success/error shapes.
 
@@ -678,7 +678,7 @@ Expected success: `ViewTransformAddSqlResult` in the standard JSON envelope; mut
 
 Run: `mammoth view transform ai`. Exact input fields: `mammoth schema get view.transform.ai --output json --no-input`.
 
-Example: `mammoth view transform ai 123 --input '{"prompt": "Summarize revenue by region", "context_columns": ["Status"]}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
+Example: `mammoth view transform ai 123 --input '{"prompt": "Summarize revenue by region", "context_columns": ["Status"], "dataset_id": 456}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
 
 Expected success: `ViewTransformAiResult` in the standard JSON envelope; mutation `reversible_pipeline`, confirmation `none`, wait policy `always_wait`. On nonzero exit, inspect the JSON error envelope and its `recovery_commands`; do not guess request fields. See [representative envelopes](../machine-output.md) for concrete success/error shapes.
 
@@ -686,7 +686,7 @@ Expected success: `ViewTransformAiResult` in the standard JSON envelope; mutatio
 
 Run: `mammoth view transform bulk-replace`. Exact input fields: `mammoth schema get view.transform.bulk-replace --output json --no-input`.
 
-Example: `mammoth view transform bulk-replace 123 --input '{"columns": ["Status"], "mapping": [{"search": ["sample"], "replace": "sample"}]}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
+Example: `mammoth view transform bulk-replace 123 --input '{"columns": ["Status"], "mapping": [{"search": ["sample"], "replace": "sample"}], "dataset_id": 456}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
 
 Expected success: `ViewTransformBulkReplaceResult` in the standard JSON envelope; mutation `reversible_pipeline`, confirmation `none`, wait policy `always_wait`. On nonzero exit, inspect the JSON error envelope and its `recovery_commands`; do not guess request fields. See [representative envelopes](../machine-output.md) for concrete success/error shapes.
 
@@ -694,7 +694,7 @@ Expected success: `ViewTransformBulkReplaceResult` in the standard JSON envelope
 
 Run: `mammoth view transform combine-columns`. Exact input fields: `mammoth schema get view.transform.combine-columns --output json --no-input`.
 
-Example: `mammoth view transform combine-columns 123 --input '{"sources": ["Status"]}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
+Example: `mammoth view transform combine-columns 123 --input '{"sources": ["Status"], "dataset_id": 456}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
 
 Expected success: `ViewTransformCombineColumnsResult` in the standard JSON envelope; mutation `reversible_pipeline`, confirmation `none`, wait policy `always_wait`. On nonzero exit, inspect the JSON error envelope and its `recovery_commands`; do not guess request fields. See [representative envelopes](../machine-output.md) for concrete success/error shapes.
 
@@ -702,7 +702,7 @@ Expected success: `ViewTransformCombineColumnsResult` in the standard JSON envel
 
 Run: `mammoth view transform convert-type`. Exact input fields: `mammoth schema get view.transform.convert-type --output json --no-input`.
 
-Example: `mammoth view transform convert-type 123 --input '{"conversions": [{"column": "Status", "to": "TEXT"}]}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
+Example: `mammoth view transform convert-type 123 --input '{"conversions": [{"column": "Status", "to": "TEXT"}], "dataset_id": 456}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
 
 Expected success: `ViewTransformConvertTypeResult` in the standard JSON envelope; mutation `reversible_pipeline`, confirmation `none`, wait policy `always_wait`. On nonzero exit, inspect the JSON error envelope and its `recovery_commands`; do not guess request fields. See [representative envelopes](../machine-output.md) for concrete success/error shapes.
 
@@ -710,7 +710,7 @@ Expected success: `ViewTransformConvertTypeResult` in the standard JSON envelope
 
 Run: `mammoth view transform copy-columns`. Exact input fields: `mammoth schema get view.transform.copy-columns --output json --no-input`.
 
-Example: `mammoth view transform copy-columns 123 --input '{"copies": [{"source": "Status"}]}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
+Example: `mammoth view transform copy-columns 123 --input '{"copies": [{"source": "Status"}], "dataset_id": 456}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
 
 Expected success: `ViewTransformCopyColumnsResult` in the standard JSON envelope; mutation `reversible_pipeline`, confirmation `none`, wait policy `always_wait`. On nonzero exit, inspect the JSON error envelope and its `recovery_commands`; do not guess request fields. See [representative envelopes](../machine-output.md) for concrete success/error shapes.
 
@@ -718,7 +718,7 @@ Expected success: `ViewTransformCopyColumnsResult` in the standard JSON envelope
 
 Run: `mammoth view transform crosstab`. Exact input fields: `mammoth schema get view.transform.crosstab --output json --no-input`.
 
-Example: `mammoth view transform crosstab 123 --input '{"rows": ["sample"], "pivot_column": "Status", "select": {"function": "SUM"}, "dataset_name": "Revenue report"}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
+Example: `mammoth view transform crosstab 123 --input '{"rows": ["sample"], "pivot_column": "Status", "select": {"function": "SUM"}, "dataset_name": "Revenue report", "dataset_id": 456}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
 
 Expected success: `ViewTransformCrosstabResult` in the standard JSON envelope; mutation `reversible_pipeline`, confirmation `none`, wait policy `always_wait`. On nonzero exit, inspect the JSON error envelope and its `recovery_commands`; do not guess request fields. See [representative envelopes](../machine-output.md) for concrete success/error shapes.
 
@@ -726,7 +726,7 @@ Expected success: `ViewTransformCrosstabResult` in the standard JSON envelope; m
 
 Run: `mammoth view transform date-diff`. Exact input fields: `mammoth schema get view.transform.date-diff --output json --no-input`.
 
-Example: `mammoth view transform date-diff 123 --input '{"component": "YEAR", "start": "sample", "end": "sample"}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
+Example: `mammoth view transform date-diff 123 --input '{"component": "YEAR", "start": "sample", "end": "sample", "dataset_id": 456}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
 
 Expected success: `ViewTransformDateDiffResult` in the standard JSON envelope; mutation `reversible_pipeline`, confirmation `none`, wait policy `always_wait`. On nonzero exit, inspect the JSON error envelope and its `recovery_commands`; do not guess request fields. See [representative envelopes](../machine-output.md) for concrete success/error shapes.
 
@@ -734,7 +734,7 @@ Expected success: `ViewTransformDateDiffResult` in the standard JSON envelope; m
 
 Run: `mammoth view transform delete-columns`. Exact input fields: `mammoth schema get view.transform.delete-columns --output json --no-input`.
 
-Example: `mammoth view transform delete-columns 123 --input '{"columns": ["Status"]}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
+Example: `mammoth view transform delete-columns 123 --input '{"columns": ["Status"], "dataset_id": 456}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
 
 Expected success: `ViewTransformDeleteColumnsResult` in the standard JSON envelope; mutation `reversible_pipeline`, confirmation `none`, wait policy `always_wait`. On nonzero exit, inspect the JSON error envelope and its `recovery_commands`; do not guess request fields. See [representative envelopes](../machine-output.md) for concrete success/error shapes.
 
@@ -742,7 +742,7 @@ Expected success: `ViewTransformDeleteColumnsResult` in the standard JSON envelo
 
 Run: `mammoth view transform discard-duplicates`. Exact input fields: `mammoth schema get view.transform.discard-duplicates --output json --no-input`.
 
-Example: `mammoth view transform discard-duplicates 123 --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
+Example: `mammoth view transform discard-duplicates 123 --input '{"dataset_id": 456}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
 
 Expected success: `ViewTransformDiscardDuplicatesResult` in the standard JSON envelope; mutation `reversible_pipeline`, confirmation `none`, wait policy `always_wait`. On nonzero exit, inspect the JSON error envelope and its `recovery_commands`; do not guess request fields. See [representative envelopes](../machine-output.md) for concrete success/error shapes.
 
@@ -750,7 +750,7 @@ Expected success: `ViewTransformDiscardDuplicatesResult` in the standard JSON en
 
 Run: `mammoth view transform extract-date`. Exact input fields: `mammoth schema get view.transform.extract-date --output json --no-input`.
 
-Example: `mammoth view transform extract-date 123 --input '{"column": "Status", "component": "year"}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
+Example: `mammoth view transform extract-date 123 --input '{"column": "Status", "component": "year", "dataset_id": 456}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
 
 Expected success: `ViewTransformExtractDateResult` in the standard JSON envelope; mutation `reversible_pipeline`, confirmation `none`, wait policy `always_wait`. On nonzero exit, inspect the JSON error envelope and its `recovery_commands`; do not guess request fields. See [representative envelopes](../machine-output.md) for concrete success/error shapes.
 
@@ -758,7 +758,7 @@ Expected success: `ViewTransformExtractDateResult` in the standard JSON envelope
 
 Run: `mammoth view transform fill-missing`. Exact input fields: `mammoth schema get view.transform.fill-missing --output json --no-input`.
 
-Example: `mammoth view transform fill-missing 123 --input '{"column": "Status", "direction": "FIRST_VALUE"}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
+Example: `mammoth view transform fill-missing 123 --input '{"column": "Status", "direction": "FIRST_VALUE", "dataset_id": 456}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
 
 Expected success: `ViewTransformFillMissingResult` in the standard JSON envelope; mutation `reversible_pipeline`, confirmation `none`, wait policy `always_wait`. On nonzero exit, inspect the JSON error envelope and its `recovery_commands`; do not guess request fields. See [representative envelopes](../machine-output.md) for concrete success/error shapes.
 
@@ -766,7 +766,7 @@ Expected success: `ViewTransformFillMissingResult` in the standard JSON envelope
 
 Run: `mammoth view transform filter`. Exact input fields: `mammoth schema get view.transform.filter --output json --no-input`.
 
-Example: `mammoth view transform filter 123 --input '{"condition": {"column": "Status", "operator": "EQ", "value": "Active"}}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
+Example: `mammoth view transform filter 123 --input '{"condition": {"column": "Status", "operator": "EQ", "value": "Active"}, "dataset_id": 456}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
 
 Expected success: `ViewTransformFilterResult` in the standard JSON envelope; mutation `reversible_pipeline`, confirmation `none`, wait policy `always_wait`. On nonzero exit, inspect the JSON error envelope and its `recovery_commands`; do not guess request fields. See [representative envelopes](../machine-output.md) for concrete success/error shapes.
 
@@ -774,7 +774,7 @@ Expected success: `ViewTransformFilterResult` in the standard JSON envelope; mut
 
 Run: `mammoth view transform generate-sql`. Exact input fields: `mammoth schema get view.transform.generate-sql --output json --no-input`.
 
-Example: `mammoth view transform generate-sql 123 --input '{"intent": "Summarize revenue by region"}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
+Example: `mammoth view transform generate-sql 123 --input '{"intent": "Summarize revenue by region", "dataset_id": 456}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
 
 Expected success: `ViewTransformGenerateSqlResult` in the standard JSON envelope; mutation `reversible_pipeline`, confirmation `none`, wait policy `always_wait`. On nonzero exit, inspect the JSON error envelope and its `recovery_commands`; do not guess request fields. See [representative envelopes](../machine-output.md) for concrete success/error shapes.
 
@@ -782,7 +782,7 @@ Expected success: `ViewTransformGenerateSqlResult` in the standard JSON envelope
 
 Run: `mammoth view transform increment-date`. Exact input fields: `mammoth schema get view.transform.increment-date --output json --no-input`.
 
-Example: `mammoth view transform increment-date 123 --input '{"column": "Status", "delta": {}}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
+Example: `mammoth view transform increment-date 123 --input '{"column": "Status", "delta": {}, "dataset_id": 456}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
 
 Expected success: `ViewTransformIncrementDateResult` in the standard JSON envelope; mutation `reversible_pipeline`, confirmation `none`, wait policy `always_wait`. On nonzero exit, inspect the JSON error envelope and its `recovery_commands`; do not guess request fields. See [representative envelopes](../machine-output.md) for concrete success/error shapes.
 
@@ -790,7 +790,7 @@ Expected success: `ViewTransformIncrementDateResult` in the standard JSON envelo
 
 Run: `mammoth view transform join`. Exact input fields: `mammoth schema get view.transform.join --output json --no-input`.
 
-Example: `mammoth view transform join 123 --input '{"foreign_view": 1, "join_type": "INNER", "on": [{"left": "sample", "right": "sample"}], "select": ["sample"]}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
+Example: `mammoth view transform join 123 --input '{"foreign_view": 1, "join_type": "INNER", "on": [{"left": "sample", "right": "sample"}], "select": ["sample"], "dataset_id": 456, "foreign_dataset_id": 457}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
 
 Expected success: `ViewTransformJoinResult` in the standard JSON envelope; mutation `reversible_pipeline`, confirmation `none`, wait policy `always_wait`. On nonzero exit, inspect the JSON error envelope and its `recovery_commands`; do not guess request fields. See [representative envelopes](../machine-output.md) for concrete success/error shapes.
 
@@ -798,7 +798,7 @@ Expected success: `ViewTransformJoinResult` in the standard JSON envelope; mutat
 
 Run: `mammoth view transform json-extract`. Exact input fields: `mammoth schema get view.transform.json-extract --output json --no-input`.
 
-Example: `mammoth view transform json-extract 123 --input '{"column": "Status"}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
+Example: `mammoth view transform json-extract 123 --input '{"column": "Status", "dataset_id": 456}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
 
 Expected success: `ViewTransformJsonExtractResult` in the standard JSON envelope; mutation `reversible_pipeline`, confirmation `none`, wait policy `always_wait`. On nonzero exit, inspect the JSON error envelope and its `recovery_commands`; do not guess request fields. See [representative envelopes](../machine-output.md) for concrete success/error shapes.
 
@@ -806,7 +806,7 @@ Expected success: `ViewTransformJsonExtractResult` in the standard JSON envelope
 
 Run: `mammoth view transform limit-rows`. Exact input fields: `mammoth schema get view.transform.limit-rows --output json --no-input`.
 
-Example: `mammoth view transform limit-rows 123 --input '{"n": 1}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
+Example: `mammoth view transform limit-rows 123 --input '{"n": 1, "dataset_id": 456}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
 
 Expected success: `ViewTransformLimitRowsResult` in the standard JSON envelope; mutation `reversible_pipeline`, confirmation `none`, wait policy `always_wait`. On nonzero exit, inspect the JSON error envelope and its `recovery_commands`; do not guess request fields. See [representative envelopes](../machine-output.md) for concrete success/error shapes.
 
@@ -814,7 +814,7 @@ Expected success: `ViewTransformLimitRowsResult` in the standard JSON envelope;
 
 Run: `mammoth view transform lookup`. Exact input fields: `mammoth schema get view.transform.lookup --output json --no-input`.
 
-Example: `mammoth view transform lookup 123 --input '{"source": "Status", "lookup_view_id": 1, "key": "Status", "value": "sample"}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
+Example: `mammoth view transform lookup 123 --input '{"source": "Status", "lookup_view_id": 1, "key": "Status", "value": "sample", "dataset_id": 456, "lookup_dataset_id": 457}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
 
 Expected success: `ViewTransformLookupResult` in the standard JSON envelope; mutation `reversible_pipeline`, confirmation `none`, wait policy `always_wait`. On nonzero exit, inspect the JSON error envelope and its `recovery_commands`; do not guess request fields. See [representative envelopes](../machine-output.md) for concrete success/error shapes.
 
@@ -822,7 +822,7 @@ Expected success: `ViewTransformLookupResult` in the standard JSON envelope; mut
 
 Run: `mammoth view transform math`. Exact input fields: `mammoth schema get view.transform.math --output json --no-input`.
 
-Example: `mammoth view transform math 123 --input '{"expression": "price * quantity"}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
+Example: `mammoth view transform math 123 --input '{"expression": "price * quantity", "dataset_id": 456}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
 
 Expected success: `ViewTransformMathResult` in the standard JSON envelope; mutation `reversible_pipeline`, confirmation `none`, wait policy `always_wait`. On nonzero exit, inspect the JSON error envelope and its `recovery_commands`; do not guess request fields. See [representative envelopes](../machine-output.md) for concrete success/error shapes.
 
@@ -830,7 +830,7 @@ Expected success: `ViewTransformMathResult` in the standard JSON envelope; mutat
 
 Run: `mammoth view transform pivot`. Exact input fields: `mammoth schema get view.transform.pivot --output json --no-input`.
 
-Example: `mammoth view transform pivot 123 --input '{"group_by": ["sample"], "aggregations": [{"column": "Status", "function": "SUM"}]}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
+Example: `mammoth view transform pivot 123 --input '{"group_by": ["sample"], "aggregations": [{"column": "Status", "function": "SUM"}], "dataset_id": 456}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
 
 Expected success: `ViewTransformPivotResult` in the standard JSON envelope; mutation `reversible_pipeline`, confirmation `none`, wait policy `always_wait`. On nonzero exit, inspect the JSON error envelope and its `recovery_commands`; do not guess request fields. See [representative envelopes](../machine-output.md) for concrete success/error shapes.
 
@@ -838,7 +838,7 @@ Expected success: `ViewTransformPivotResult` in the standard JSON envelope; muta
 
 Run: `mammoth view transform replace`. Exact input fields: `mammoth schema get view.transform.replace --output json --no-input`.
 
-Example: `mammoth view transform replace 123 --input '{"columns": ["Status"], "find": "sample", "replace": "sample"}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
+Example: `mammoth view transform replace 123 --input '{"columns": ["Status"], "find": "sample", "replace": "sample", "dataset_id": 456}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
 
 Expected success: `ViewTransformReplaceResult` in the standard JSON envelope; mutation `reversible_pipeline`, confirmation `none`, wait policy `always_wait`. On nonzero exit, inspect the JSON error envelope and its `recovery_commands`; do not guess request fields. See [representative envelopes](../machine-output.md) for concrete success/error shapes.
 
@@ -846,7 +846,7 @@ Expected success: `ViewTransformReplaceResult` in the standard JSON envelope; mu
 
 Run: `mammoth view transform set-values`. Exact input fields: `mammoth schema get view.transform.set-values --output json --no-input`.
 
-Example: `mammoth view transform set-values 123 --input '{"values": [{"value": "sample"}]}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
+Example: `mammoth view transform set-values 123 --input '{"values": [{"value": "sample"}], "dataset_id": 456}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
 
 Expected success: `ViewTransformSetValuesResult` in the standard JSON envelope; mutation `reversible_pipeline`, confirmation `none`, wait policy `always_wait`. On nonzero exit, inspect the JSON error envelope and its `recovery_commands`; do not guess request fields. See [representative envelopes](../machine-output.md) for concrete success/error shapes.
 
@@ -854,7 +854,7 @@ Expected success: `ViewTransformSetValuesResult` in the standard JSON envelope;
 
 Run: `mammoth view transform small-large`. Exact input fields: `mammoth schema get view.transform.small-large --output json --no-input`.
 
-Example: `mammoth view transform small-large 123 --input '{"function": "SMALL", "columns": ["Status"]}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
+Example: `mammoth view transform small-large 123 --input '{"function": "SMALL", "columns": ["Status"], "dataset_id": 456}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
 
 Expected success: `ViewTransformSmallLargeResult` in the standard JSON envelope; mutation `reversible_pipeline`, confirmation `none`, wait policy `always_wait`. On nonzero exit, inspect the JSON error envelope and its `recovery_commands`; do not guess request fields. See [representative envelopes](../machine-output.md) for concrete success/error shapes.
 
@@ -862,7 +862,7 @@ Expected success: `ViewTransformSmallLargeResult` in the standard JSON envelope;
 
 Run: `mammoth view transform split`. Exact input fields: `mammoth schema get view.transform.split --output json --no-input`.
 
-Example: `mammoth view transform split 123 --input '{"column": "Status", "delimiter": "sample", "new_columns": [{"name": "Revenue report"}]}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
+Example: `mammoth view transform split 123 --input '{"column": "Status", "delimiter": "sample", "new_columns": [{"name": "Revenue report"}], "dataset_id": 456}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
 
 Expected success: `ViewTransformSplitResult` in the standard JSON envelope; mutation `reversible_pipeline`, confirmation `none`, wait policy `always_wait`. On nonzero exit, inspect the JSON error envelope and its `recovery_commands`; do not guess request fields. See [representative envelopes](../machine-output.md) for concrete success/error shapes.
 
@@ -870,7 +870,7 @@ Expected success: `ViewTransformSplitResult` in the standard JSON envelope; muta
 
 Run: `mammoth view transform substring`. Exact input fields: `mammoth schema get view.transform.substring --output json --no-input`.
 
-Example: `mammoth view transform substring 123 --input '{"column": "Status"}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
+Example: `mammoth view transform substring 123 --input '{"column": "Status", "dataset_id": 456}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
 
 Expected success: `ViewTransformSubstringResult` in the standard JSON envelope; mutation `reversible_pipeline`, confirmation `none`, wait policy `always_wait`. On nonzero exit, inspect the JSON error envelope and its `recovery_commands`; do not guess request fields. See [representative envelopes](../machine-output.md) for concrete success/error shapes.
 
@@ -878,7 +878,7 @@ Expected success: `ViewTransformSubstringResult` in the standard JSON envelope;
 
 Run: `mammoth view transform text`. Exact input fields: `mammoth schema get view.transform.text --output json --no-input`.
 
-Example: `mammoth view transform text 123 --input '{"columns": ["Status"]}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
+Example: `mammoth view transform text 123 --input '{"columns": ["Status"], "dataset_id": 456}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
 
 Expected success: `ViewTransformTextResult` in the standard JSON envelope; mutation `reversible_pipeline`, confirmation `none`, wait policy `always_wait`. On nonzero exit, inspect the JSON error envelope and its `recovery_commands`; do not guess request fields. See [representative envelopes](../machine-output.md) for concrete success/error shapes.
 
@@ -886,7 +886,7 @@ Expected success: `ViewTransformTextResult` in the standard JSON envelope; mutat
 
 Run: `mammoth view transform unnest`. Exact input fields: `mammoth schema get view.transform.unnest --output json --no-input`.
 
-Example: `mammoth view transform unnest 123 --input '{"columns": ["Status"]}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
+Example: `mammoth view transform unnest 123 --input '{"columns": ["Status"], "dataset_id": 456}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
 
 Expected success: `ViewTransformUnnestResult` in the standard JSON envelope; mutation `reversible_pipeline`, confirmation `none`, wait policy `always_wait`. On nonzero exit, inspect the JSON error envelope and its `recovery_commands`; do not guess request fields. See [representative envelopes](../machine-output.md) for concrete success/error shapes.
 
@@ -894,7 +894,7 @@ Expected success: `ViewTransformUnnestResult` in the standard JSON envelope; mut
 
 Run: `mammoth view transform window`. Exact input fields: `mammoth schema get view.transform.window --output json --no-input`.
 
-Example: `mammoth view transform window 123 --input '{"function": "ROW_NUMBER"}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
+Example: `mammoth view transform window 123 --input '{"function": "ROW_NUMBER", "dataset_id": 456}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
 
 Expected success: `ViewTransformWindowResult` in the standard JSON envelope; mutation `reversible_pipeline`, confirmation `none`, wait policy `always_wait`. On nonzero exit, inspect the JSON error envelope and its `recovery_commands`; do not guess request fields. See [representative envelopes](../machine-output.md) for concrete success/error shapes.
 

{mammoth_cli-2.0.10 → mammoth_cli-2.0.12}/mammoth_cli/bundled_skill/mammoth-cli/references/operations.md

@@ -9,6 +9,13 @@ wait policy, known restrictions, and recovery/verification metadata. Read the
 schema immediately before composing a request because support and fields can
 vary by release, profile, or backend.
 
+`schema find`/`schema get`/`schema list` read the installed manifest. They
+need no project and no stored credentials. `dataset list`, `folder list`, and
+`view list` call the live API and are scoped to one project through
+`--project`. `dataset find NAME` and `folder find NAME` search every project
+the credential can see (or one, with `--project`); they still need
+credentials because they call the live API.
+
 ```bash
 mammoth capability find "transform" --output json --no-input
 mammoth capability find "pipeline" --output json --no-input
@@ -31,6 +38,11 @@ mammoth schema find "fill missing" --output json --no-input
 mammoth schema find "replace" --output json --no-input
 ```
 
+There is no pipeline `union`/`append` transform. `join` and `lookup` are the
+typed routes for combining views. Appending rows is a dataset-level
+operation: upload into the existing dataset with `file upload --input
+'{"append_to_ds_id": DATASET_ID}'`, not a view transform.
+
 Use the exact returned command ID, then read its schema and the current view
 schema before composing input. For row-oriented sources such as OWID files,
 preserve the observed display names (often `Entity`, `Code`, `Year`, and one
@@ -51,11 +63,12 @@ exact schema; do not use a guessed alias, raw HTTP, local processing, or opaque
 Prefer a typed `view transform <operation>` command. Its schema is the
 discoverable request contract and its result should be verified with a view
 read, preview, pipeline read/items, or the returned job according to
-`wait_policy`:
+`wait_policy`. Every transform and draft mutation carries the exact parent
+`dataset_id` in `--input`; it never falls back to project-wide discovery:
 
 ```bash
 mammoth view transform math VIEW_ID --project PROJECT_ID \
-  --input '{"expression":"Unit Price * Quantity","new_column":"Revenue"}' \
+  --input '{"dataset_id":DATASET_ID,"expression":"Unit Price * Quantity","new_column":"Revenue"}' \
   --output json --no-input
 mammoth view pipeline get VIEW_ID --project PROJECT_ID --output json --no-input
 ```
@@ -83,6 +96,14 @@ status, submit, and verify pipeline state; discard only with the required
 confirmation. A draft submit result is not proof that every intended task was
 applied.
 
+## Response shapes
+
+Response shapes are not uniform; never reuse one `jq` path across commands.
+`dataset get` returns `data.dataset.{...}`. `dataset list` returns
+`data.datasets[]`. `project list` returns `data.projects[]`. Every other
+command returns its object directly under `data`. Inspect the first response
+before extracting a field.
+
 ## Exports
 
 First inspect `view.export.list/get` for existing configuration and the exact

{mammoth_cli-2.0.10 → mammoth_cli-2.0.12}/mammoth_cli/bundled_skill/mammoth-cli/references/recipes/index.md

@@ -11,6 +11,7 @@ hashes; stop on ambiguous schemas, authorization errors, or unknown effects.
 
 - [auth and scope](auth-scope.md)
 - [files, datasets, views and settings](resources.md)
+- [datasets stuck in `need_action` after upload](need-action.md)
 - [typed transformations and drafts](transforms.md)
 - [typed ETL discovery](typed-etl-discovery.md)
 - [exports and artifacts](exports.md)

mammoth_cli-2.0.12/mammoth_cli/bundled_skill/mammoth-cli/references/recipes/need-action.md

@@ -0,0 +1,36 @@
+# Datasets stuck in `need_action` after upload
+
+A freshly uploaded file can land in `status: "need_action"` with
+`status_info.need_action` = "We need your input before we process this file".
+No views exist yet and transforms cannot start. This is not a UI-only step:
+the CLI resolves it. Do not hand it to the operator unless the settings read
+below is itself ambiguous.
+
+The usual cause is a CSV whose date column is ambiguous (`01/02/2023` can be
+US or UK). `dataset file-settings get` then reports `has_ambiguous_dates: true`
+and `date_format: null`.
+
+```bash
+mammoth dataset get DATASET_ID --project PROJECT_ID --output json --no-input
+mammoth dataset file-settings get DATASET_ID --project PROJECT_ID --output json --no-input
+mammoth schema get dataset.file-settings.update --output json --no-input
+```
+
+Read the detected `delimiter`, `has_header`, `initial_skip_count`, and
+`quotechar` from the `file-settings get` response and send them back
+unchanged, adding the one decision the platform is waiting for. For
+ambiguous dates that is `date_format` (`"US"` or `"UK"`); decide it from the
+task or the data itself (a day value above 12 settles it), and ask the
+operator only when neither does.
+
+```bash
+mammoth dataset file-settings update DATASET_ID --project PROJECT_ID \
+  --input '{"delimiter": ",", "has_header": true, "initial_skip_count": 0, "quotechar": "\"", "date_format": "US"}' \
+  --output json --no-input
+```
+
+The response is a job (`operation: "understand_csv"`). Poll `dataset get`
+until `status` leaves `need_action`; it normally reaches `ready` within a few
+seconds, after which `view list` returns the generated view and typed
+transforms can proceed. If the status becomes `error`, read `status_info`
+and stop; do not retry with guessed settings.

{mammoth_cli-2.0.10 → mammoth_cli-2.0.12}/mammoth_cli/bundled_skill/mammoth-cli/references/recipes/resources.md

@@ -1,5 +1,11 @@
 # Files, URL imports, datasets, views and settings
 
+Uploads and dataset creation return a dataset id, not a view id. Every
+pipeline transform, `join`'s `foreign_view`, export, and preview needs a view
+id instead. Run `view list DATASET_ID --project PROJECT_ID` to get it. Do not
+dig through `dataset get` and its `dependencies` field for a view id; `view
+list` is the supported route.
+
 Discover exact contracts, then upload and read back explicit parents:
 
 ```bash

{mammoth_cli-2.0.10 → mammoth_cli-2.0.12}/mammoth_cli/bundled_skill/mammoth-cli/references/recipes/transforms.md

@@ -9,6 +9,14 @@ mammoth schema get view.transform.join --output json --no-input
 mammoth view transform OPERATION VIEW_ID --project PROJECT_ID --input INPUT_JSON --output json --no-input
 ```
 
+Every `view transform *` and `view draft *` mutation needs the exact parent
+dataset: put `"dataset_id": DATASET_ID` in `--input` (these commands take no
+DATASET_ID positional). Without it the command fails closed with
+`missing_argument`; it never falls back to project-wide discovery, which on
+large projects browses every folder and can 500 or miss the view. Get the
+parent from `view list DATASET_ID` (you already know it after upload) or
+`view get VIEW_ID` (a read, which may discover it).
+
 Prefer typed operations such as convert-type, fill-missing, replace, join,
 lookup, filter and math only when the live schema
 lists them. For each operation, a successful result should contain a returned
@@ -21,23 +29,23 @@ command manifest; substitute only observed view IDs and display names:
 ```bash
 mammoth schema get view.transform.convert-type --output json --no-input
 mammoth view transform convert-type VIEW_ID --project PROJECT_ID \
-  --input '{"conversions":[{"column":"Amount","to":"NUMERIC"}]}' \
+  --input '{"dataset_id":DATASET_ID,"conversions":[{"column":"Amount","to":"NUMERIC"}]}' \
   --output json --no-input
 mammoth schema get view.transform.math --output json --no-input
 mammoth view transform math VIEW_ID --project PROJECT_ID \
-  --input '{"expression":"GDP / Population","new_column":"GDP per capita"}' \
+  --input '{"dataset_id":DATASET_ID,"expression":"GDP / Population","new_column":"GDP per capita"}' \
   --output json --no-input
 ```
 
 The released catalog exposes typed dedupe through `schema find duplicate` as
-`view.transform.discard-duplicates`. Inspect its optional `ignore_columns` and
-`dataset_id` fields before submitting. For a join, verify both schemas and
+`view.transform.discard-duplicates`. Inspect its optional `ignore_columns`
+field before submitting. For a join, verify both schemas and
 expected multiplicity:
 
 ```bash
 mammoth schema get view.transform.discard-duplicates --output json --no-input
 mammoth view transform discard-duplicates VIEW_ID --project PROJECT_ID \
-  --input '{"ignore_columns":["ID"]}' --output json --no-input
+  --input '{"dataset_id":DATASET_ID,"ignore_columns":["ID"]}' --output json --no-input
 mammoth schema get view.transform.join --output json --no-input
 mammoth view transform join VIEW_ID --project PROJECT_ID --input INPUT_JSON --output json --no-input
 ```

{mammoth_cli-2.0.10 → mammoth_cli-2.0.12}/mammoth_cli/bundled_skill/mammoth-cli/references/recipes/typed-etl-discovery.md

@@ -1,5 +1,13 @@
 # Typed ETL discovery
 
+There is no pipeline union or append transform. `join` and `lookup` are the
+typed routes for combining views; neither appends rows across two views.
+Appending rows is a dataset-level operation: upload into the existing dataset
+with `mammoth file upload FILE --project PROJECT_ID --input
+'{"append_to_ds_id": DATASET_ID}' --output json --no-input`. Confirm the exact
+field name first with `mammoth schema get file.upload --output json
+--no-input`; do not guess a `union`/`append` command id.
+
 Start with typed transforms rather than raw `view task` payloads:
 
 ```bash