@copado/agentia-cli 1.3.0 → 1.4.0

package/CHANGELOG.md

@@ -4,6 +4,34 @@ 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