@copado/agentia-cli 1.0.0-beta.6 → 1.0.0-beta.8

package/package.json

@@ -235,7 +235,7 @@
     }
   },
   "type": "module",
-  "version": "1.0.0-beta.6",
+  "version": "1.0.0-beta.8",
   "x-agentia-protected-build": true,
   "x-agentia-protected-files": [
     "dist/lib/runtime.js"

package/templates/skills/agentia-adv/SKILL.md

@@ -5,7 +5,7 @@ Use this skill when working with Copado Pipelines Advanced through the Agentia C
 
 ## Commands
 
-- Configure authentication once with `agentia auth set --adv <PAT>`. The CLI stores the PAT in the keychain and auto-discovers the Pipelines Advanced endpoint unless `--adv-base-url` is supplied.
+- Configure global authentication with `agentia auth set --adv <PAT>`, or add `--local` for current-project/current-user scope. Both store the PAT in the keychain and auto-discover the Pipelines Advanced endpoint unless `--adv-base-url` is supplied.
 - Use `agentia adv organization list|get|validate` to inspect accessible organizations and verify connectivity.
 - Use `agentia adv deployment list|get|create|options|validate|deploy|quick-deploy|cancel` to define deployments, update options, and run or stop deployments.
 - Use `agentia adv component types|list|refresh|selected|add|remove` to discover metadata types and manage selected deployment components.
@@ -16,5 +16,7 @@ Use this skill when working with Copado Pipelines Advanced through the Agentia C
 - Never pass PATs to `agentia adv ...` commands. Use `agentia auth set --adv` or project-scoped auth.
 - Prefer `--json` for automation and agents.
 - For component JSON files, use `--json-file`; `--json` remains the standard Agentia output flag.
+- In JSON or non-interactive CLI runs, deploy, quick deploy, cancel, and auth removal require `--yes`. The matching MCP deployment mutations require `confirm: true`; validation does not.
+- Treat a nonzero exit from a waited run as failure. JSON errors retain the command transaction ID and failed waited runs include `error.result.job`.
 
 See `references/pipelines-advanced.md` for command flows and examples.

package/templates/skills/agentia-adv/references/pipelines-advanced.md

@@ -8,7 +8,7 @@ agentia auth set --adv <PAT>
 agentia adv auth status --json
 ```
 
-Use `--adv-base-url` only for QA, UAT, or local development endpoints.
+Authentication is global by default. Add `--local` to `auth set` for current-project/current-user scope; the PAT still stays in the keychain. Remove global auth with `auth unset --adv [--global]` or local auth with `auth unset --adv --local`; JSON/non-interactive removal requires `--yes`. Use `--adv-base-url` only for approved non-standard endpoints.
 
 ## Deployment Journey
 
@@ -28,7 +28,23 @@ agentia adv job get <deployment-id> --json
 ## Notes
 
 - `deployment list` exposes the API `flowId` as `id`; do not use the raw list row link id.
-- `deployment options` reads current options, merges `--set` or `--file`, and sends the complete options object because the API replaces the entire object.
-- `component add` and `component remove` accept `--component Type/Name`. File inputs are `--file` for text and `--json-file` for JSON component objects.
+- `deployment list` returns at most 500 rows and has no filter.
+- `deployment options` reads current options, merges `--set` or `--file`, and sends the complete options object because the API replaces the entire object. `--set` converts exact booleans/null and finite JavaScript Number forms, including hex and exponent notation. Supported test levels include `NO_TEST_RUN`, `RUN_SPECIFIED_TESTS`, `RUN_LOCAL_TESTS`, and `RUN_ALL_TESTS_IN_ORG`.
+- `component types` can report the same type name in several views.
+- `component add` and `component remove` accept `--component Type/Name`. Add supports a text `--file`; remove does not. `--json-file` must be a bare array and accepts `{type, fullName}`, rows extracted from `result.components`, or `{nodeType: {name}, fullName}`. Remove returns the submitted array in `requested`, not a count.
 - `validate`, `deploy`, `quick-deploy`, and `cancel` are asynchronous; use `--wait` or `agentia adv job wait`.
 - `deploy`, `quick-deploy`, and `cancel` prompt interactively. JSON and non-interactive runs require `--yes`; matching MCP tools require `confirm: true`.
+- `quick-deploy --backup` invokes the server's `backupThenDeploy` action instead of a quick deploy.
+- Polling defaults to 3 seconds with a 3600-second timeout. Failed or cancelled waited runs exit nonzero; JSON errors include the normalized job.
+- `job list` excludes validation runs. Page numbering starts at 0, page size defaults to 50, and the server caps it at 100.
+- API JSON errors expose sanitized code/status/method/URL/name/message plus `transactionId`; validation errors expose name/message plus `transactionId`.
+
+## MCP Argument Names
+
+- Organizations and deployments use `id`; selected/components/jobs use `deploymentId`; component list/refresh use `flow`.
+- Deployment validate: `id`, optional `wait`, `interval`, `timeout` (no confirmation).
+- Deploy: the validation inputs plus `confirm: true`.
+- Quick deploy: deploy inputs plus optional `backup`.
+- Cancel: `id`, `confirm: true`, optional `wait`, `interval`, `timeout`.
+- Component add/remove: `deploymentId`, `components` (`Type/Name` strings or `{type, fullName, excluded?}` objects).
+- Job list: `deploymentId`, optional `page`, `pageSize`.