mammoth-cli 2.0.4__tar.gz → 2.0.6__tar.gz

{mammoth_cli-2.0.4 → mammoth_cli-2.0.6}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: mammoth-cli
-Version: 2.0.4
+Version: 2.0.6
 Summary: Command-line interface for the Mammoth Analytics platform
 Project-URL: homepage, https://mammoth.io
 Project-URL: repository, https://github.com/EdgeMetric/mammothsdk
@@ -64,7 +64,6 @@ then confirm it works:
 
 ```bash
 mammoth --version
-mammoth doctor          # checks config, credentials, endpoint, connectivity
 ```
 
 The installer bootstraps its own `uv` tool environment when needed and installs
@@ -73,25 +72,56 @@ X.Y.Z`; the installer has no normal prompts. See
 [Installation](https://github.com/EdgeMetric/mammothsdk/blob/main/mammoth-cli/docs/installation.md) for that option and the SDK-only pip
 installation path.
 
-## Quick start
+## First run: authenticate, check, then discover
+
+Authentication is the first operational step. Check the selected profile;
+this is a local presence check, not a live access test. If the profile or
+stored credentials are absent, log in before running `doctor` or any data
+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 auth login               # prompts for API key, API secret, workspace id
-mammoth doctor                   # confirm credentials resolve and the API answers
-mammoth project list             # a table in a terminal, JSON when piped
-mammoth dataset list --project 180
+mammoth skill list --output json --no-input
+mammoth skill path --output json --no-input
+# Read the installed SKILL.md before operating.
+mammoth auth status --output json --no-input
+# 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
+# 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
+# Optional API-binding inventory (not the complete CLI surface):
+mammoth capability list --output json --no-input
 ```
 
-Full walkthrough: [docs/quickstart.md](https://github.com/EdgeMetric/mammothsdk/blob/main/mammoth-cli/docs/quickstart.md).
-
-The login command has no workspace shortcut flag. For CI or an agent, use a
-protected request document instead:
+For an agent or CI, do not request or paste secrets into chat, prompts, shell
+history, or command arguments. On POSIX, put the required JSON credentials in a
+private owner-only (0600) file outside the repository and pass its path to:
 
 ```bash
-chmod 600 creds.json
-mammoth auth login --input creds.json --output json --no-input
+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
+unless its ACL hardening is approved, and stop if it is not available.
+
+The default server prefix is `app`; pass `--server-prefix release` only when
+the release endpoint is explicitly intended. Compare the endpoint reported by
+`auth status` with the intended target before running `doctor`; if it does not
+match, stop and switch to a separate correctly configured profile. See
+[Authentication](https://github.com/EdgeMetric/mammothsdk/blob/main/mammoth-cli/docs/authentication.md)
+for the required JSON fields and profile behavior. After `doctor` succeeds,
+resolve the exact workspace, project, dataset, and view from read results
+before operating; verify every mutation. Use `schema find`/`schema get` for
+typed and local CLI routes; `capability list` is only an API-binding inventory
+and may omit them. Full walkthrough:
+[docs/quickstart.md](https://github.com/EdgeMetric/mammothsdk/blob/main/mammoth-cli/docs/quickstart.md).
+
 ## Built for agents and CI
 
 Piping or redirecting output yields the machine envelope, and `--no-input` turns
@@ -101,11 +131,12 @@ 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 a
-permission-checked file:
+To be explicit, pass `--output json --no-input`. Log in without a prompt with
+the private, permission-checked file described above:
 
 ```bash
-mammoth auth login --input creds.json --output json --no-input
+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:

{mammoth_cli-2.0.4 → mammoth_cli-2.0.6}/README.md

@@ -36,7 +36,6 @@ then confirm it works:
 
 ```bash
 mammoth --version
-mammoth doctor          # checks config, credentials, endpoint, connectivity
 ```
 
 The installer bootstraps its own `uv` tool environment when needed and installs
@@ -45,25 +44,56 @@ X.Y.Z`; the installer has no normal prompts. See
 [Installation](https://github.com/EdgeMetric/mammothsdk/blob/main/mammoth-cli/docs/installation.md) for that option and the SDK-only pip
 installation path.
 
-## Quick start
+## First run: authenticate, check, then discover
+
+Authentication is the first operational step. Check the selected profile;
+this is a local presence check, not a live access test. If the profile or
+stored credentials are absent, log in before running `doctor` or any data
+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 auth login               # prompts for API key, API secret, workspace id
-mammoth doctor                   # confirm credentials resolve and the API answers
-mammoth project list             # a table in a terminal, JSON when piped
-mammoth dataset list --project 180
+mammoth skill list --output json --no-input
+mammoth skill path --output json --no-input
+# Read the installed SKILL.md before operating.
+mammoth auth status --output json --no-input
+# 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
+# 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
+# Optional API-binding inventory (not the complete CLI surface):
+mammoth capability list --output json --no-input
 ```
 
-Full walkthrough: [docs/quickstart.md](https://github.com/EdgeMetric/mammothsdk/blob/main/mammoth-cli/docs/quickstart.md).
-
-The login command has no workspace shortcut flag. For CI or an agent, use a
-protected request document instead:
+For an agent or CI, do not request or paste secrets into chat, prompts, shell
+history, or command arguments. On POSIX, put the required JSON credentials in a
+private owner-only (0600) file outside the repository and pass its path to:
 
 ```bash
-chmod 600 creds.json
-mammoth auth login --input creds.json --output json --no-input
+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
+unless its ACL hardening is approved, and stop if it is not available.
+
+The default server prefix is `app`; pass `--server-prefix release` only when
+the release endpoint is explicitly intended. Compare the endpoint reported by
+`auth status` with the intended target before running `doctor`; if it does not
+match, stop and switch to a separate correctly configured profile. See
+[Authentication](https://github.com/EdgeMetric/mammothsdk/blob/main/mammoth-cli/docs/authentication.md)
+for the required JSON fields and profile behavior. After `doctor` succeeds,
+resolve the exact workspace, project, dataset, and view from read results
+before operating; verify every mutation. Use `schema find`/`schema get` for
+typed and local CLI routes; `capability list` is only an API-binding inventory
+and may omit them. Full walkthrough:
+[docs/quickstart.md](https://github.com/EdgeMetric/mammothsdk/blob/main/mammoth-cli/docs/quickstart.md).
+
 ## Built for agents and CI
 
 Piping or redirecting output yields the machine envelope, and `--no-input` turns
@@ -73,11 +103,12 @@ 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 a
-permission-checked file:
+To be explicit, pass `--output json --no-input`. Log in without a prompt with
+the private, permission-checked file described above:
 
 ```bash
-mammoth auth login --input creds.json --output json --no-input
+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:

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

{mammoth_cli-2.0.4 → mammoth_cli-2.0.6}/mammoth_cli/bundled_skill/mammoth-cli/SKILL.md

@@ -5,8 +5,26 @@ description: "Use Mammoth Analytics from a terminal: install or authenticate the
 
 # Mammoth CLI
 
-Use this skill for Mammoth shell work, not for Python SDK integration. Start
-with the installed command contract rather than guessed routes or payloads:
+Use this skill for Mammoth shell work, not for Python SDK integration. Complete
+the authentication preflight below before using the installed command contract;
+never guess routes or payloads:
+
+Before any remote read or write, establish authentication. For ordinary
+operator runs, determine the intended environment from the task: production
+defaults to the `app` endpoint; use `release` only when explicitly named.
+Check the selected profile with `mammoth auth status --output json --no-input`
+and compare its reported `endpoint` to that target before running doctor. If
+the profile is missing, credentials are absent, or the endpoint does not match,
+stop and follow [authentication](references/auth.md); never silently reuse or
+rewrite a profile from another environment. Then run `mammoth doctor
+--profile PROFILE --output json --no-input` and require success before
+discovering resources or operating on them. A failed status, login, or doctor
+check is a precondition failure—not a reason to try the business command
+anyway. If no matching profile has credentials, the operator must run
+`mammoth auth login` themselves in their own terminal: tell them the exact
+command, wait, then re-check `auth status`. Never ask for the key or secret
+in chat, never read them from environment variables or files you were not
+given, and never run `auth login` on the operator's behalf.
 
 ```bash
 mammoth schema find "TASK OR RESOURCE" --output json --no-input

mammoth_cli-2.0.6/mammoth_cli/bundled_skill/mammoth-cli/references/auth.md

@@ -0,0 +1,107 @@
+# Authentication and profiles
+
+Required: API key, API secret, workspace id. Optional: a one-label server
+prefix (default `app`, resolving to `https://app.mammoth.io/api/v2`).
+
+## Precedence
+1. Explicit login handed to the current command (secure prompt or `--input`).
+2. The selected or `--profile` profile's saved credentials.
+
+There is no third source. The CLI and SDK do not read credentials from
+environment variables, and an agent must not search the environment, shell
+history, or unrelated files for them.
+
+## How an agent obtains credentials
+
+An agent never receives the key or secret. When `auth status` reports a
+missing profile or `has_credentials=false`, stop and hand the login to the
+human operator:
+
+1. Tell the operator the exact command to run in **their own** terminal, with
+   the profile name and the intended server prefix:
+
+   ```bash
+   mammoth auth login --profile PROFILE --server-prefix app
+   ```
+
+   The command prompts for the key and secret with hidden input, then the
+   workspace id, so no secret enters chat, argv, or history.
+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`.
+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.
+
+The only supported configuration is the API key, API secret, workspace id, and
+an optional one-label server prefix (default `app`). There is no base-url
+override.
+
+## Cold-start sequence
+
+For an ordinary operator, identify the intended environment before any remote
+command. Production means the `app` endpoint by default; use `release` only
+when the task explicitly requests the release environment. Inspect
+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
+```
+
+If status reports a missing profile or `has_credentials=false`, run the secure
+login flow, then check status again:
+
+```bash
+mammoth auth login --profile PROFILE --server-prefix app
+mammoth auth status --profile PROFILE --output json --no-input
+```
+
+`auth status` is a local profile/credential-presence check; it does not prove
+that credentials are valid remotely. Compare its reported `endpoint` with the
+intended environment before proceeding. A profile for another endpoint is a
+scope mismatch: stop and select or authenticate the explicitly intended
+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
+```
+
+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
+for `app`, and a release profile is not appropriate unless the task explicitly
+targets release.
+
+## Commands
+```bash
+mammoth auth login --profile PROFILE --server-prefix app  # hidden prompts
+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
+```
+
+`PROFILE` means the actual nonsecret profile name selected by the operator or
+reported by `auth status` (for example, `default` or `work`). Substitute that
+name; never type the literal placeholder or invent a profile to evade an
+authorization failure. When using the selected profile, `--profile PROFILE`
+may be omitted.
+
+For an ordinary human-operated terminal, prefer the first command: it asks
+for the key and secret without putting either in shell history, argv, chat, or
+logs. For headless POSIX work, create the JSON file outside the repository, set
+its permissions to `0600`, and pass only its path. With a protected POSIX file,
+specify `--storage file` explicitly; `--storage auto` can require an available
+OS keyring and is not a reliable headless fallback. On Windows, do not use the
+file backend as a secret store; use the OS keyring or stop and obtain a
+supported secure store. Remove any input file after the
+profile is stored.
+
+`creds.json` is a `0600` JSON file: `{"api_key": "...", "api_secret": "...",
+"workspace_id": 4, "server_prefix": "app"}` (`server_prefix` optional). You can
+also pipe it with `--input - --input-format json`.
+
+Secrets live in the OS keyring (or an explicitly selected `0600` file
+fallback). They are never printed, logged, or included in any envelope. Never
+pass a secret as a plain argument; use the hidden prompt or `--input`.

{mammoth_cli-2.0.4 → mammoth_cli-2.0.6}/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).
+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.
 
 Load only the applicable domain file:
 

{mammoth_cli-2.0.4 → mammoth_cli-2.0.6}/mammoth_cli/bundled_skill/mammoth-cli/references/commands/file.md

@@ -44,7 +44,9 @@ Expected success: `FileListResult` in the standard JSON envelope; mutation `read
 
 Run: `mammoth file set-password`. Exact input fields: `mammoth schema get file.set-password --output json --no-input`.
 
-Example: `mammoth file set-password 123 --input '{"password": "replace-with-secret"}' --output json --no-input`. Illustrative only: append `--yes --confirm <EXACT_TARGET>` after observing the target.
+Example: `mammoth file set-password 123 --input /private/path/request.json --output json --no-input`. Illustrative only: append `--yes --confirm <EXACT_TARGET>` after observing the target.
+
+Sensitive structured input must come from a private file or pipe; never put secrets in literal argv.
 
 Expected success: `FileSetPasswordResult` in the standard JSON envelope; mutation `high_impact`, confirmation `confirm_target`, 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.4 → mammoth_cli-2.0.6}/mammoth_cli/bundled_skill/mammoth-cli/references/commands/user.md

@@ -20,7 +20,9 @@ Expected success: `UserAvatarUploadResult` in the standard JSON envelope; mutati
 
 Run: `mammoth user change-password`. Exact input fields: `mammoth schema get user.change-password --output json --no-input`.
 
-Example: `mammoth user change-password --input '{"current_password": "replace-with-secret", "new_password": "replace-with-secret"}' --output json --no-input`. Illustrative only: append `--yes --confirm <EXACT_TARGET>` after observing the target.
+Example: `mammoth user change-password --input /private/path/request.json --output json --no-input`. Illustrative only: append `--yes --confirm <EXACT_TARGET>` after observing the target.
+
+Sensitive structured input must come from a private file or pipe; never put secrets in literal argv.
 
 Expected success: `UserChangePasswordResult` in the standard JSON envelope; mutation `high_impact`, confirmation `confirm_target`, 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.
 

{mammoth_cli-2.0.4 → mammoth_cli-2.0.6}/mammoth_cli/bundled_skill/mammoth-cli/references/commands/view.md

@@ -288,7 +288,9 @@ Expected success: `ViewDraftSubmitResult` in the standard JSON envelope; mutatio
 
 Run: `mammoth view export azure-blob`. Exact input fields: `mammoth schema get view.export.azure-blob --output json --no-input`.
 
-Example: `mammoth view export azure-blob 123 123 --input '{"storage_account_name": "storage-account", "tenant_id": "tenant-id", "client_id": "client-id", "client_secret": "replace-with-secret", "container_name": "exports"}' --output json --no-input`. Illustrative only: append `--yes` after observing an owned target.
+Example: `mammoth view export azure-blob 123 123 --input /private/path/request.json --output json --no-input`. Illustrative only: append `--yes` after observing an owned target.
+
+Sensitive structured input must come from a private file or pipe; never put secrets in literal argv.
 
 Expected success: `ViewExportAzureBlobResult` in the standard JSON envelope; mutation `external_effect`, confirmation `yes_always`, wait policy `returns_job`. 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.
 
@@ -336,7 +338,9 @@ Expected success: `ViewExportDeleteResult` in the standard JSON envelope; mutati
 
 Run: `mammoth view export elasticsearch`. Exact input fields: `mammoth schema get view.export.elasticsearch --output json --no-input`.
 
-Example: `mammoth view export elasticsearch 123 123 --input '{"host": "elastic.example", "username": "agent", "password": "replace-with-secret", "index": "exports"}' --output json --no-input`. Illustrative only: append `--yes` after observing an owned target.
+Example: `mammoth view export elasticsearch 123 123 --input /private/path/request.json --output json --no-input`. Illustrative only: append `--yes` after observing an owned target.
+
+Sensitive structured input must come from a private file or pipe; never put secrets in literal argv.
 
 Expected success: `ViewExportElasticsearchResult` in the standard JSON envelope; mutation `external_effect`, confirmation `yes_always`, wait policy `returns_job`. 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.
 
@@ -352,7 +356,9 @@ Expected success: `ViewExportEmailResult` in the standard JSON envelope; mutatio
 
 Run: `mammoth view export ftp`. Exact input fields: `mammoth schema get view.export.ftp --output json --no-input`.
 
-Example: `mammoth view export ftp 123 123 --input '{"domain": "ftp.example", "directory": "/exports", "file": "report.csv", "username": "agent", "password": "replace-with-secret"}' --output json --no-input`. Illustrative only: append `--yes` after observing an owned target.
+Example: `mammoth view export ftp 123 123 --input /private/path/request.json --output json --no-input`. Illustrative only: append `--yes` after observing an owned target.
+
+Sensitive structured input must come from a private file or pipe; never put secrets in literal argv.
 
 Expected success: `ViewExportFtpResult` in the standard JSON envelope; mutation `external_effect`, confirmation `yes_always`, wait policy `returns_job`. 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.
 
@@ -384,7 +390,9 @@ Expected success: `ViewExportManagedS3Result` in the standard JSON envelope; mut
 
 Run: `mammoth view export mssql`. Exact input fields: `mammoth schema get view.export.mssql --output json --no-input`.
 
-Example: `mammoth view export mssql 123 123 --input '{"host": "db.example", "port": 1433, "database": "analytics", "table": "exports", "username": "agent", "password": "replace-with-secret"}' --output json --no-input`. Illustrative only: append `--yes` after observing an owned target.
+Example: `mammoth view export mssql 123 123 --input /private/path/request.json --output json --no-input`. Illustrative only: append `--yes` after observing an owned target.
+
+Sensitive structured input must come from a private file or pipe; never put secrets in literal argv.
 
 Expected success: `ViewExportMssqlResult` in the standard JSON envelope; mutation `external_effect`, confirmation `yes_always`, wait policy `returns_job`. 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.
 
@@ -392,7 +400,9 @@ Expected success: `ViewExportMssqlResult` in the standard JSON envelope; mutatio
 
 Run: `mammoth view export mysql`. Exact input fields: `mammoth schema get view.export.mysql --output json --no-input`.
 
-Example: `mammoth view export mysql 123 123 --input '{"host": "db.example", "port": 3306, "database": "analytics", "table": "exports", "username": "agent", "password": "replace-with-secret"}' --output json --no-input`. Illustrative only: append `--yes` after observing an owned target.
+Example: `mammoth view export mysql 123 123 --input /private/path/request.json --output json --no-input`. Illustrative only: append `--yes` after observing an owned target.
+
+Sensitive structured input must come from a private file or pipe; never put secrets in literal argv.
 
 Expected success: `ViewExportMysqlResult` in the standard JSON envelope; mutation `external_effect`, confirmation `yes_always`, wait policy `returns_job`. 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.
 
@@ -400,7 +410,9 @@ Expected success: `ViewExportMysqlResult` in the standard JSON envelope; mutatio
 
 Run: `mammoth view export onedrive`. Exact input fields: `mammoth schema get view.export.onedrive --output json --no-input`.
 
-Example: `mammoth view export onedrive 123 123 --input '{"tenant_id": "tenant-id", "client_id": "client-id", "client_secret": "replace-with-secret", "user_id": "user-id"}' --output json --no-input`. Illustrative only: append `--yes` after observing an owned target.
+Example: `mammoth view export onedrive 123 123 --input /private/path/request.json --output json --no-input`. Illustrative only: append `--yes` after observing an owned target.
+
+Sensitive structured input must come from a private file or pipe; never put secrets in literal argv.
 
 Expected success: `ViewExportOnedriveResult` in the standard JSON envelope; mutation `external_effect`, confirmation `yes_always`, wait policy `returns_job`. 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.
 
@@ -408,7 +420,9 @@ Expected success: `ViewExportOnedriveResult` in the standard JSON envelope; muta
 
 Run: `mammoth view export postgres`. Exact input fields: `mammoth schema get view.export.postgres --output json --no-input`.
 
-Example: `mammoth view export postgres 123 123 --input '{"host": "db.example", "port": 5432, "database": "analytics", "table": "exports", "username": "agent", "password": "replace-with-secret"}' --output json --no-input`. Illustrative only: append `--yes` after observing an owned target.
+Example: `mammoth view export postgres 123 123 --input /private/path/request.json --output json --no-input`. Illustrative only: append `--yes` after observing an owned target.
+
+Sensitive structured input must come from a private file or pipe; never put secrets in literal argv.
 
 Expected success: `ViewExportPostgresResult` in the standard JSON envelope; mutation `external_effect`, confirmation `yes_always`, wait policy `returns_job`. 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.
 
@@ -416,7 +430,9 @@ Expected success: `ViewExportPostgresResult` in the standard JSON envelope; muta
 
 Run: `mammoth view export powerbi`. Exact input fields: `mammoth schema get view.export.powerbi --output json --no-input`.
 
-Example: `mammoth view export powerbi 123 123 --input '{"username": "agent", "password": "replace-with-secret", "client_id": "client-id", "dataset": "dataset", "table": "exports"}' --output json --no-input`. Illustrative only: append `--yes` after observing an owned target.
+Example: `mammoth view export powerbi 123 123 --input /private/path/request.json --output json --no-input`. Illustrative only: append `--yes` after observing an owned target.
+
+Sensitive structured input must come from a private file or pipe; never put secrets in literal argv.
 
 Expected success: `ViewExportPowerbiResult` in the standard JSON envelope; mutation `external_effect`, confirmation `yes_always`, wait policy `returns_job`. 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.
 
@@ -440,7 +456,9 @@ Expected success: `ViewExportPublishDbUpdateResult` in the standard JSON envelop
 
 Run: `mammoth view export redshift`. Exact input fields: `mammoth schema get view.export.redshift --output json --no-input`.
 
-Example: `mammoth view export redshift 123 123 --input '{"host": "db.example", "port": 5439, "database": "analytics", "table": "exports", "username": "agent", "password": "replace-with-secret"}' --output json --no-input`. Illustrative only: append `--yes` after observing an owned target.
+Example: `mammoth view export redshift 123 123 --input /private/path/request.json --output json --no-input`. Illustrative only: append `--yes` after observing an owned target.
+
+Sensitive structured input must come from a private file or pipe; never put secrets in literal argv.
 
 Expected success: `ViewExportRedshiftResult` in the standard JSON envelope; mutation `external_effect`, confirmation `yes_always`, wait policy `returns_job`. 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.
 
@@ -464,7 +482,9 @@ Expected success: `ViewExportSftpResult` in the standard JSON envelope; mutation
 
 Run: `mammoth view export sharepoint`. Exact input fields: `mammoth schema get view.export.sharepoint --output json --no-input`.
 
-Example: `mammoth view export sharepoint 123 123 --input '{"tenant_id": "tenant-id", "client_id": "client-id", "client_secret": "replace-with-secret", "site_url": "https://sharepoint.example/site"}' --output json --no-input`. Illustrative only: append `--yes` after observing an owned target.
+Example: `mammoth view export sharepoint 123 123 --input /private/path/request.json --output json --no-input`. Illustrative only: append `--yes` after observing an owned target.
+
+Sensitive structured input must come from a private file or pipe; never put secrets in literal argv.
 
 Expected success: `ViewExportSharepointResult` in the standard JSON envelope; mutation `external_effect`, confirmation `yes_always`, wait policy `returns_job`. 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.
 
@@ -472,7 +492,9 @@ Expected success: `ViewExportSharepointResult` in the standard JSON envelope; mu
 
 Run: `mammoth view export tableau`. Exact input fields: `mammoth schema get view.export.tableau --output json --no-input`.
 
-Example: `mammoth view export tableau 123 123 --input '{"server_url": "https://tableau.example", "token_name": "token", "token_secret": "replace-with-secret"}' --output json --no-input`. Illustrative only: append `--yes` after observing an owned target.
+Example: `mammoth view export tableau 123 123 --input /private/path/request.json --output json --no-input`. Illustrative only: append `--yes` after observing an owned target.
+
+Sensitive structured input must come from a private file or pipe; never put secrets in literal argv.
 
 Expected success: `ViewExportTableauResult` in the standard JSON envelope; mutation `external_effect`, confirmation `yes_always`, wait policy `returns_job`. 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.4 → mammoth_cli-2.0.6}/mammoth_cli/bundled_skill/mammoth-cli/references/commands/workspace.md

@@ -4,7 +4,9 @@
 
 Run: `mammoth workspace accept-invite`. Exact input fields: `mammoth schema get workspace.accept-invite --output json --no-input`.
 
-Example: `mammoth workspace accept-invite --input '{"token": "replace-with-secret"}' --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
+Example: `mammoth workspace accept-invite --input /private/path/request.json --output json --no-input`. Runnable only after resolving schema-required IDs and input from observed reads.
+
+Sensitive structured input must come from a private file or pipe; never put secrets in literal argv.
 
 Expected success: `WorkspaceAcceptInviteResult` 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.
 

{mammoth_cli-2.0.4 → mammoth_cli-2.0.6}/mammoth_cli/bundled_skill/mammoth-cli/references/handoff.md

@@ -4,11 +4,10 @@ Use a nonsecret JSON checkpoint when another agent or session must continue.
 This is a record, not a resume subcommand. The receiving agent chooses
 its own plan only after fresh reads.
 
-For evaluated/isolated agents, authentication remains controller-owned: use
-the provided broker/sidecar and never mount or read a saved profile. If that
-broker is absent, stop before authenticated actions. Ordinary operator
-handoffs may reference the authorized profile name, but must not copy its path
-or contents into the checkpoint.
+A handoff may reference the authorized profile name, but must not copy its
+path or contents into the checkpoint. The receiving agent re-checks
+`auth status` and `doctor`; if credentials are missing on its host, the
+operator logs in from their own terminal as described in [auth](auth.md).
 
 ## Required record
 
@@ -49,9 +48,5 @@ mammoth view get VIEW_ID --project PROJECT_ID --output json --no-input
 mammoth job get JOB_ID --output json --no-input
 ```
 
-The commands above are ordinary operator examples; an evaluated/isolated agent
-must use the controller broker/sidecar instead of `--profile` and must stop if
-that broker is absent.
-
 The required fields and receiving procedure above are self-contained for a
 cold-start agent; no repository checkout or unshipped document is required.

{mammoth_cli-2.0.4 → mammoth_cli-2.0.6}/mammoth_cli/bundled_skill/mammoth-cli/references/recipes/auth-scope.md

@@ -3,7 +3,8 @@
 Use `mammoth auth status`, `mammoth doctor`, `mammoth project list`, and
 `mammoth schema get project.list` with `--output json --no-input`. Require
 successful `data` and observed workspace/project metadata. Never put secrets in
-argv; evaluated agents use the controller broker and never mount profiles.
+argv. If credentials are missing, the operator logs in from their own terminal;
+see [auth](../auth.md).
 
 ```bash
 mammoth context project use PROJECT_ID --profile PROFILE --output json --no-input
@@ -13,8 +14,8 @@ The successful envelope should identify the selected profile/workspace/project
 in `data` or `meta`; retain only nonsecret IDs. A deliberately invalid or
 expired profile should return the structured auth error (exit 4), which is a
 stop-and-recover condition, not permission to retry mutations. Never inline
-tokens or secrets in argv, logs, or evidence. Interactive login may receive
-protected credential JSON through stdin or a 0600 input file; evaluated agents
-must use the controller broker and never expose a profile to their shell.
+tokens or secrets in argv, logs, or evidence. Headless login may receive
+protected credential JSON through stdin or a 0600 input file only when the
+operator explicitly supplies that file.
 
 Exit 4 is auth/authorization; preserve the structured error and stop safely.

{mammoth_cli-2.0.4 → mammoth_cli-2.0.6}/mammoth_cli/bundled_skill/mammoth-cli/references/task-start.md

@@ -5,12 +5,6 @@ task and has no repository or prior chat context. The user supplies the intent,
 authorized scope, and (when needed) a protected profile. Never put credentials
 or secrets in an argument, prompt, transcript, or checkpoint.
 
-For an evaluated or isolated agent, follow the controller-provided credential
-broker/sidecar instead of using a saved profile. Never mount or read the saved
-profile in that shell. If the broker/sidecar is not provided, stop before any
-authenticated action. The profile workflow below remains for ordinary,
-non-evaluated operator use.
-
 1. Check whether `mammoth` is available. If it is absent, install the CLI and
    bundled skill with the supported host installer:
 
@@ -27,9 +21,32 @@ non-evaluated operator use.
    install is required for the agent host, run `mammoth skill install
    --output json --no-input` and verify ownership with `mammoth skill list
    --output json --no-input`.
-3. Use the protected profile/configuration supplied by the user or environment.
-   Run `mammoth doctor --profile PROFILE --output json --no-input`; do not print,
-   echo, or copy its secret-bearing inputs.
+3. Establish authentication before any remote read or write. Determine the
+   intended environment from the task first: production defaults to the `app` endpoint;
+   use `release` only when the task explicitly names release. Then inspect the
+   selected profile without attempting business work:
+
+   ```bash
+   mammoth auth status --output json --no-input
+   ```
+
+   Compare the status response's `endpoint` with the intended environment. If
+   the profile or credentials are missing, or the endpoint is for another
+   environment, stop and follow [authentication](auth.md): tell the operator
+   the exact `mammoth auth login --profile PROFILE --server-prefix app`
+   command to run in their own terminal, wait for them, then re-check status.
+   The CLI does not read credentials from environment variables; do not look
+   for them there. Never silently reuse or rewrite a mismatched profile,
+   invent a profile, ask for credentials in chat, or put secrets in argv.
+   After the operator has logged in (or when an existing, matching profile is
+   present), run the connectivity and configuration check and require success:
+
+   ```bash
+   mammoth doctor --profile PROFILE --output json --no-input
+   ```
+
+   Do not print, echo, or copy secret-bearing inputs. A failed status, login,
+   or doctor check stops the task before discovery and business commands.
 4. Discover instead of guessing. Run `mammoth schema list/find/get --output
    json --no-input` for local CLI routes; `mammoth capability list --output
    json --no-input` is an API-binding inventory and can omit typed/local