@copado/agentia-cli 1.0.0-beta.0 → 1.0.0-beta.2

package/CHANGELOG.md

@@ -4,6 +4,46 @@ All published sections are mapped to immutable npm publication metadata. New use
 
 ## [Unreleased]
 
+## [1.0.0-beta.2] - 2026-10-02
+
+### Added
+
+- Add `--user-stories-ahead-behind` to `cicd work get`. When the user story has a pipeline and source environment with one next environment, it compares ahead/behind counts via `/agentia/headless/work/user-stories-ahead-behind` and includes them in human and `--json` output.
+- Require `enableLocalPromote: true` in `.agentia/config.json` (or `.agentia/config.user.json`) before `cicd work promote` runs. The command is experimental because it skips Quality Gates; when the option is missing or not `true`, it fails with an error that tells you to set that option.
+- Add `cicd work promote` to create a forward promotion, or a back promotion with `--backpromote --destination-branch`, for one or more user stories. A back promotion infers the destination environment from that pipeline connection branch. The command merges each `feature/<name>` branch in order into `promotion/<promotionName>` created from the destination environment branch, then sets the promotion status to Completed or Merge Conflict. After a merge conflict, resolve the files and re-run `cicd work promote --promotion=<name-or-id> --continue` to commit the merge and finish the remaining stories. The continue hint repeats `--validate` or `--deploy` and `--sf-alias` when the original command used them. `--validate` and `--deploy` require `--sf-alias` and deploy the promotion metadata with `sf project deploy start --test-level NoTestRun`. `--validate` uses `--dry-run`, skips the destination-branch merge, and sets the status to Validated. `--deploy` merges the promotion branch into the destination branch and sets the status to Completed only after that deployment succeeds. User story records are left unchanged.
+- Add `cicd work environment-sync`. It creates a Copado `back_promotion` for every user story behind the destination environment. Continue after conflicts with `cicd work environment-sync --promotion=<name> --continue`.
+- Add `--abort` to `cicd work promote` and `cicd work environment-sync`. With `--promotion`, it runs `git merge --abort` and patches the promotion status to Draft (`Cancelled` is reserved by Salesforce). Conflict error suggestions include the matching `--abort` command.
+- Add organization-scoped governance health checks with optional local git-sizer analysis.
+
+### Changed
+
+- Declare standard MCP tool annotations (`readOnlyHint`, `destructiveHint`, `idempotentHint`, `openWorldHint`) on every Agentia MCP tool so MCP clients can auto-approve safe reads and prompt before destructive tools. The hints are advisory and do not add a server-side confirmation. Tool names, inputs, and outputs are unchanged.
+- Rename `cicd work commit` to `cicd cloud commit` so Copado cloud commits are distinct from local work-item commands. `--cloud` is no longer required. `cicd work commit` remains a hidden compatibility alias and still accepts `--cloud`. MCP tools follow the same split (`agentia_cloud_commit`), with `agentia_work_commit` kept as an alias.
+- Move Copado cloud promotion runs to `cicd cloud promote` / MCP `agentia_cloud_promote`. `cicd work promote` is the experimental local promotion command (previously drafted as `quick-promote`), not a cloud alias. The former MCP `agentia_work_promote` cloud alias is removed; use `agentia_cloud_promote`.
+- `cicd work environment-sync` always syncs every user story behind the destination environment. It no longer accepts user story IDs or `--next-env-branch`. The next environment branch is resolved from `--destination-environment` or `--dev-org-branch`.
+- `cicd work submit` (including `--done` / `--deploy` and MCP `agentia_work_submit`) counts user stories ahead and behind the next pipeline environment and warns when stories behind might cause promotion conflicts.
+
+### Fixed
+
+- Allow `cicd function upsert --file <payload.json> --json` without treating `--json` as a payload flag conflict (`US-0632393` — CLI v1.1.0-alpha.0).
+- Show the Salesforce component, file, and problem when `cicd work promote --validate` or `--deploy` fails, instead of only the deploy status.
+- Tolerate SSE keepalive comment lines (for example `: heartbeat`) and `data:` prefixes in the Copado AI NDJSON stream instead of failing with `malformed NDJSON`, and keep the received answer with a warning when the stream closes without a `stream_complete` record.
+- On a `cicd work set` / `agentia_work_set` gateway warning, clear `lastBaseBranch`, `lastDevOrgBranch`, and `lastPullRequestBaseUrl`, and record `lastWorkItemId`, `lastWorkItem`, and `lastWorkItemTitle` from the returned work item instead of leaving user config unchanged.
+- Cast the `tty-table` v7 default export so TypeScript accepts the callable factory used by table formatting after the security bump.
+
+### Security
+
+- Bump `brace-expansion` and bundled `npm` overrides, and apply `npm audit fix --force` (including `tty-table` to v7) so `security:gate` clears the current high advisories.
+
+## [1.0.0-beta.1] - 2026-09-29
+
+### Changed
+
+- Standardize human-readable `auth get` authentication details with the scoped multiline presentation used by `agentia setup`.
+- Show global and project-scoped authentication separately when both are configured, with colored authentication section titles.
+- Auto-discover the Copado AI domain from an AI PAK and organization ID in `auth set` and interactive setup when no domain is supplied.
+- Require a CRT organization ID when storing a CRT PAK, validating or discovering its domain before persistence.
+
 ## [1.0.0-beta.0] - 2026-09-23
 
 ### Added