@copado/agentia-cli 1.2.0 → 1.4.0

package/CHANGELOG.md

@@ -4,10 +4,65 @@ All published sections are mapped to immutable npm publication metadata. New use
 
 ## [Unreleased]
 
+## [1.4.0] - 2026-11-06
+
+### Added
+
+- `cicd promotion status` (MCP `agentia_promotion_status`) reports actionable promotion state: user stories, current job step, queue summary, and whether a Manual Task or queue item needs attention. Prefer it when asking if a promotion is blocked or what is running. `promotion get` human output now lists user stories and queue summary and points agents at `promotion status`.
+- MCP `agentia_cloud_promote` matches `cicd cloud promote` when no Promotion contains the User Story: it creates a forward Draft promotion, adds the story, then runs. CLI and MCP JSON include optional `createdPromotion` when a promotion was created.
+- `cicd work environment-sync` waits for the cloud deployment JobExecution after a successful sync by default (`--[no-]wait`, `--wait-timeout`, default 900s), matching `cicd cloud promote`. After the sync result and first `Elapsed` line it notes that stopping the CLI leaves the deployment running in the background, then prints `Elapsed` again when the wait finishes.
+- `cicd work test --gate <id>` (repeatable) runs only selected local quality gates, `--all` runs the whole script, and `--list-gates` shows the gates a script declares with `# agentia-gate: <id> - <description>`. The selection reaches the script as `AGENTIA_GATES`; `--gate apex` runs the Apex tests directly. The sample `.sh` and `.cmd` scripts now declare and conditionally run the standard `lint`, `apex` and `lwc` gates; the sample lint gate now scans only files changed on the branch (merge-base with the pipeline base branch, plus uncommitted and untracked files) and falls back to a full scan outside git, or when `LINT_SCOPE=all`. MCP `agentia_work_test` accepts `gates`, `all` and `listGates`.
+
+### Changed
+
+- `cicd work environment-sync` is marked experimental (`This command is experimental and may change without notice.` in human stderr and `--json` `warnings`).
+- `cicd cloud commit` help documents multi-component commits via `--file` / `--stdin` `changes[]` and clarifies that simple metadata flags commit exactly one component.
+- `cicd work environment-sync` accepts `--deployment=none|local|cloud|auto` (default `auto`) and `--sf-alias`. Resolved `none|local|cloud` is sent to `promote-action/complete` (never `auto`). `auto` picks `local` when every back-promotion change is Add and `--sf-alias` is set, otherwise `cloud`. `local` runs `sf project deploy start --ignore-conflicts` before complete (Add-only; rejects Delete/RetrieveOnly/Full). Cloud deployment wait runs only when the resolved deployment is `cloud`.
+- `cicd work environment-sync` stops on a feature branch when unpublished commits are present (HEAD ahead of `origin/<feature>` or the remote ref is missing) and suggests `cicd work publish` before syncing.
+- `cicd work environment-sync` creates `promotion/<promotionName>` from the dest org branch, merges next-env pathspecs into that branch, merges the promotion branch into dest, and pushes both refs (instead of merging next-env directly into feature/dest). When the run started on a feature branch, it then refreshes that branch's changed files from dest and tells you to re-check and publish again.
+
+### Fixed
+
+- `cicd job result-file get` and MCP `agentia_job_result_file_get` download Result-linked files using the list response `fileId` (ContentVersion, 068 prefix). A ContentDocument id (069) is resolved through the list endpoint before download. The list table includes a FILE ID column.
+- Environment-variable replacement during `cicd work publish` applies to newly added files and handles Windows paths correctly.
+- `cicd work environment-sync --deployment=local` deploys from the dest org branch (after merge/push) before refreshing the feature branch, so `sf project deploy start --manifest` can resolve source-backed components. Deploy failures now include the full `package.xml` (and destructive manifest when present) plus sanitized Salesforce CLI stdout/stderr in the human and `--json` error message.
+- Cursor-paginated CICD lists (`--cursor` / MCP `cursor`) no longer fail hard when the API returns category `SF-014` for an expired or invalid cursor. Agentia retries once without the cursor, returns the first page, and surfaces a `warnings` entry in human output, `--json`, and MCP results.
+
+### Removed
+
+- Remove `agentia testing browser reports` (and its deprecated `testing live reports` alias and `agentia_testing_browser_reports` MCP tool).
+
+## [1.3.0] - 2026-11-03
+
+### Added
+
+- Experimental `agentia help-agent`, `agentia support`, and `agentia help --agent` start the same multi-turn Copado support conversation without an eager CICD credential preflight. Responses render as SSE deltas arrive. Every request obtains a fresh non-persisted HMAC, refreshes bounded runtime/recent-command context and dominant CLI/IDE/MCP usage, and sends a redacted digest of up to six successful prior messages. The system prompt asks one brief question when tooling or local-versus-cloud operations cannot be determined.
+- `agentia history list` and `agentia history clear` inspect or remove owner-private temporary history. Command history retains at most 100 sanitized CLI/IDE summaries or metadata-only MCP summaries. Successful Help Agent turn pairs are separately redacted, capped at 4 KiB per message, and retained for a rolling 24 hours/100 pairs without restoring them into later chats; `history clear --yes` deletes both stores.
+- Named CICD connections: `agentia auth set --cicd <key> --connection <name> [--kind sandbox|production]` stores an alternate Copado API key and endpoint without changing the active/default connection. Use `--cicd-connection <name>` only on `agentia cicd ...` commands (or `AGENTIA_CICD_CONNECTION`, or MCP `cicdConnection` on CICD tools) for that invocation only—not on `ai`, `adv`, `testing`, or `auth`. Production-tagged connections require confirmation (CLI), `--yes`, or `AGENTIA_CICD_ALLOW_PRODUCTION=true` (required for MCP). Combining a named connection with `AGENTIA_CICD_API_KEY` / `AGENTIA_CICD_BASE_URL` errors instead of silently choosing one. `auth get` lists named connections with masked keys; `auth unset --connection` removes one.
+- `cicd promotion queue list` and `cicd promotion queue remove` (MCP `agentia_promotion_queue_list`, `agentia_promotion_queue_remove`) show and clear the job queue of a promotion; removal requires the Manage Queue permission and `--yes` for headless runs.
+- `agentia testing browser view` provisions a session-scoped CRT user parameter (`agentia_cli_lt_<sessionId>`) for the web noVNC viewer and includes `projectId` and `orgId` in the `/browser/session/<sessionId>` viewer URL; `testing browser stop` deletes the parameter on teardown.
+- `agentia testing browser execute --stdin` reads Robot Framework lines or suite content from standard input; `testing browser history` adds `--lines-only`, `--keyword`, `--include-failed`, and `--job` while preserving 4-space Robot Framework argument separators and redacting `TypeSecret` values; `testing browser inspect --dom --json` returns raw DOM in JSON without requiring `--output`; and `testing browser recorder` adds `--force` and `--json`.
+- `agentia-testing` skill pack adds `references/browser-testing.md`, `references/flow-automation.md`, `references/qweb.md`, and `references/qforce.md`.
+
+### Changed
+
+- `cicd cloud promote` creates a forward Draft promotion for the User Story and adds it when no promotion contains the story, then runs it, instead of failing and requiring you to create the promotion by hand.
+- Rename `agentia testing live` commands to `agentia testing browser` (`start|stop|status|execute|inspect|screenshot|reports|set-options|history|view|recorder`) with hidden deprecated `testing live ...` CLI aliases, and replace `agentia_testing_live_*` MCP tools with `agentia_testing_browser_*`.
+
+### Removed
+
+- Remove unused `testing live continue` and `testing live interrupt` commands and their `agentia_testing_live_continue` / `agentia_testing_live_interrupt` MCP tools.
+
+### Fixed
+
+- MCP server and `testing job runs` commands failed to load in 1.2.0 packaged builds.
+
 ## [1.2.0] - 2026-10-28
 
 ### Added
 
+- `cicd metadata dependency list --path` (and MCP `agentia_metadata_dependency_list` `path`) resolves one or more local Salesforce source file paths into metadata selections via the existing SDR path helpers, then runs the same dependency gateway request with `localPaths` enrichment. Mutually exclusive with `--file`, `--stdin`, and `--from-changes`.
+- `cicd metadata dependency list` (and MCP `agentia_metadata_dependency_list`) resolves omitted `--pipeline-id`, `--source-credential-id`, `--source-org-id`, and `--platform-experience` from the active work item, then from project defaults for pipeline/credential/org. Platform falls back to `sfdx` when still unset. `--target-org-id` is never inferred.
 - Automatic proxy support: Agentia honors `HTTPS_PROXY`, `HTTP_PROXY`, `NO_PROXY`, and npm-style proxy environment variables on CICD, AI, CRT, Pipelines Advanced, version check, plugin trust, and CRT live WebSocket traffic, with proxy-aware transport errors and masked proxy credentials in debug output.
 - `cicd work get`, `cicd work create`, and `cicd work update` (and MCP `agentia_work_get`, `agentia_work_create`, `agentia_work_update`) support subscriber User Story `customFields`: get surfaces the gateway read DTOs in human and `--json` output; create/update accept writes via repeatable `--custom-field ApiName=value`, and MCP accepts the same data as a `customFields` array.
 - `cicd metadata explore` (experimental; MCP `agentia_metadata_explore`) explores Salesforce metadata through Org Intelligence. `agentia setup` can install the `agentia-metadata` skill for agent workflows.
@@ -18,6 +73,8 @@ All published sections are mapped to immutable npm publication metadata. New use
 
 ### Changed
 
+- `cicd metadata dependency list` human output is a single table with parent (evaluated metadata), relation (`used by` / `dependant`), name, type, and compare status field (status column omitted when absent, for example without a target org). Agentia metadata skill templates document `--path`, context defaults, and when to prefer the Copado dependency graph over Org Intelligence `find_references`.
+- Project Cursor rule `skill-management` (scoped to `src/commands`, `src/lib`, and `templates/skills`) requires updating `templates/skills` (and syncing installed skill copies) whenever CLI/MCP or agent workflow contracts change.
 - Consolidate Copado Robotic Testing job definitions, files, and runs under `agentia testing job`: `testing job create|update|run|list|get|delete|refs`, `testing job files list|upload|download`, `testing job runs list|search|get|logs|abort`, and `testing job schedule get|set|remove`. Older `testing create|update|status|logs|run`, `testing test ...`, `testing build ...`, and `testing job files|upload|download` forms remain as hidden deprecated aliases that print a migration warning.
 - `testing job run` now waits for a terminal CRT build result and streams sanitized Robot Framework logs by default in human output (printing `Run ID:` and a `Run is queued...` progress indicator while queued, treating `finished` as a transitional status during polling, and exiting nonzero when the run does not succeed unless `--no-exit-code` is set). Use `--no-wait` to return once queued (`--wait-for-result` is a deprecated alias for `--wait`), or `--no-stream-logs` to show a spinner instead; `--datatable` batch runs never wait, `--save-artifacts` and `--xunit` require waiting, and `--json` never streams.
 - `testing job runs get` fetches the full build record in human output so the summary includes xUnit test totals, while `--json` continues to return the compact record unless `--full` is passed.
@@ -33,7 +90,7 @@ All published sections are mapped to immutable npm publication metadata. New use
 - `cicd environment open` opens environments only; use `cicd credential open` for credentials.
 - `cicd environment auth status` and `cicd environment auth web login` (and MCP `agentia_environment_auth_status`) accept `--credentialid` / `credentialId` without an environment ID and resolve the environment from the credential.
 - Installed plugins can contribute agent skills through an `agentia:contribute` hook. `agentia setup skills list` shows what plugins offer and why invalid skills are skipped, interactive `setup skills create` lets you tick plugin skills (none preselected), `setup skills create|update --plugin <name>` installs them headless, and `setup skills update` refreshes plugin skills already in the project and warns about skills whose plugin was removed; `setup skills update --prune` deletes those orphaned plugin skills. Plugin skills are Markdown only and validated before install.
-- `agentia ai agent ask|chat` and MCP `agentia_ai_ask` default to the Orchestrate agent, which routes work to the right specialist; `--agent` is optional and still accepts `plan`, `build`, `test`, `release`, `operate`, or `knowledge`. The plugin SDK `host.ai.ask` follows the same default;   plugins that need the previous behavior pass `agent: 'knowledge'`.
+- `agentia ai agent ask|chat` and MCP `agentia_ai_ask` default to the Orchestrate agent, which routes work to the right specialist; `--agent` is optional and still accepts `plan`, `build`, `test`, `release`, `operate`, or `knowledge`. The plugin SDK `host.ai.ask` follows the same default; plugins that need the previous behavior pass `agent: 'knowledge'`.
 
 ### Fixed