@copado/agentia-cli 1.0.0-beta.1 → 1.0.0-beta.4

package/CHANGELOG.md

@@ -4,6 +4,73 @@ All published sections are mapped to immutable npm publication metadata. New use
 
 ## [Unreleased]
 
+## [1.0.0-beta.4] - 2026-10-07
+
+### Added
+
+- Add `agentia runtime`, a bounded custom NDJSON process the Agentia IDE uses to reuse one warm CLI for many invokes instead of starting Node and oclif per call. Runtime command bodies are serialized, stdout/stderr and structured failures are preserved, stdin-consuming commands are rejected, and nested commands publish normal `command.completed` refresh events. This is process amortization, not a login daemon.
+- Add a plugin host and the `@copado/agentia-plugin-sdk` package so plugins call Copado through a curated set of domain methods instead of importing CLI internals. The host exposes `work.getWorkItem`, `organization.healthCheck`, `auth.status` (configured/ready/source only), and table formatting; results are allowlisted and redacted, including errors. Plugin requests are labelled `plugin:<command id>`. The SDK ships `AgentiaCommand`, lets a plugin declare the host methods it needs (`getAgentiaHost({requires})`) so an older CLI fails with a clear message, and plugins never receive credentials.
+
+### Removed
+
+- Remove the in-repo `sample_plugin/` directory. Use the reference plugin and generator in the `cli-plugin-generator` repository (`@copado/create-agentia-plugin`) instead.
+
+## [1.0.0-beta.3] - 2026-10-06
+
+### Changed
+
+- Improve repository setup with guided HTTPS, SSH, and OAuth authentication flows. Repository credentials are now configured separately from repository details, stay out of command arguments, and are protected from accidental replacement by default.
+- `cicd work environment-sync --json` includes a `logs` array of captured progress (and subprocess stdout/stderr), matching `cicd work publish` and `cicd work submit`.
+- `cicd work environment-sync` human output lists committed metadata as `userstory  action  type  name  category` lines and no longer prints pathspec tables.
+- `cicd work environment-sync` ends human output with `Elapsed: <seconds>s`, matching `cicd work publish` and `cicd work submit`.
+- `cicd work environment-sync --continue` commits the in-progress merge when conflicts are resolved and staged but not yet committed (`MERGE_HEAD` present). If you already ran `git commit`, it skips that step and finishes the remaining sync.
+- `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, advising `agentia cicd work environment-sync` to retrieve and merge the newest changes.
+- When merging a feature branch into the dest/dev org branch (`environment-sync` and work publish), remaining conflicts after `-X theirs` are auto-resolved by taking the feature branch (`checkout --theirs`, or `git rm` when that branch deleted the path) and completing the merge commit.
+
+### Fixed
+
+- `cicd project default set --credential` validates the credential from the environment record. The credential resource does not accept GET and returned HTTP 405.
+- Surface git stdout and stderr when `cicd work environment-sync` (and related git merge paths) fail, instead of only Node's generic `Command failed: git …` / exit code.
+
+### Fixed
+
+- Default omitted `limit` to `50000` on `cicd data template save-detail` and MCP `agentia_data_template_save_detail` so gateway PUT validation succeeds when a v2 detail omits the field; explicit limits, including `0`, are unchanged (`US-0632625`).
+
+### Fixed
+
+- Resolve local MCP project authentication, defaults, `.env`, and Git context consistently across Cursor, Claude Code, and supported roots-aware local clients; stale Cursor registrations are now upgraded to pass the active workspace root.
+
+## [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