@copado/agentia-cli 0.92.0-alpha.0 → 0.93.0-alpha.0

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@copado/agentia-cli",
   "description": "Command-line interface for Agentia",
-  "version": "0.92.0-alpha.0",
+  "version": "0.93.0-alpha.0",
   "author": "Copado Solutions",
   "bin": {
     "agentia": "./bin/run.js"

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

@@ -31,7 +31,7 @@ Prefer Agentia MCP tools when they are available and match the task. Use CLI exa
 
 - Use Salesforce record IDs or generated names read from Copado. Do not invent story names, promotion IDs, job IDs, credential IDs, or pipeline IDs.
 - Keep human output off stdout in JSON workflows. Prefer `--json`, then parse the result object.
-- For local project work, keep the tracked working tree clean before commands that require it: `work set`, `work push`, `work submit`, and `work done`.
+- For local project work, keep the tracked working tree clean before commands that require it: `work set`, `work push`, and `work submit`.
 - Treat `cicd job` as Copado CICD JobExecution. It is different from CRT `testing job`.
 - Treat `cicd work test --local` as local quality gates. It is different from CRT `testing test run`.
 - Treat `auth` credentials as keychain/API credentials and `cicd credential` records as Copado environment credentials.

package/templates/skills/agentia-cicd/references/promotions.md

@@ -10,7 +10,7 @@ Use this reference for `agentia cicd promotion ...`, `agentia cicd promotion con
 | --- | --- | --- |
 | `agentia cicd promotion run <promotion-id>` | Promotion ID | You already know the Promotion record and want explicit merge or merge-and-deploy control. |
 | `agentia cicd work promote [story-id] --cloud` | User Story | You want Agentia to resolve the story's Promotion before running it. |
-| `agentia cicd work done` | Active User Story branch | The story is approved and should move to the next stage through the normal work lifecycle. |
+| `agentia cicd work submit --done` | Active User Story branch | The story is approved and should move to the next stage (Copado UI Submit promote). |
 
 Prefer `work promote` when the user talks about a story. Prefer `promotion run` when the user provides a Promotion ID.
 

package/templates/skills/agentia-cicd/references/work.md

@@ -2,7 +2,7 @@
 
 # CICD Work Reference
 
-Use this reference for `agentia cicd work ...` and matching MCP tools such as `agentia_work_get`, `agentia_work_commit`, `agentia_work_push`, `agentia_work_submit`, and `agentia_work_done`.
+Use this reference for `agentia cicd work ...` and matching MCP tools such as `agentia_work_get`, `agentia_work_commit`, `agentia_work_push`, and `agentia_work_submit`.
 
 ## Workflow
 
@@ -14,9 +14,9 @@ Use this reference for `agentia cicd work ...` and matching MCP tools such as `a
    - Copado cloud metadata: `agentia cicd work commit <story-id> --cloud --metadata-name <name> --metadata-type <type> --metadata-category SFDX --json`
 5. Register local commits: `agentia cicd work push --json`
 6. Validate and submit: `agentia cicd work submit --json`
-7. Promote only on explicit approval: `agentia cicd work done --json`
+7. Promote only on explicit approval: `agentia cicd work submit --done --json`
 
-`work set`, `work push`, `work submit`, and `work done` expect a clean tracked working tree and the active story context recorded by `work set`.
+`work set`, `work push`, and `work submit` expect a clean tracked working tree and the active story context recorded by `work set`.
 
 ## Core Commands
 
@@ -30,10 +30,9 @@ Use this reference for `agentia cicd work ...` and matching MCP tools such as `a
 | `work commit` | Local or cloud commit | `--local` is default; `--cloud` calls Copado commit APIs and can poll a job. |
 | `work push` | Push local commits and register with Copado | Requires active story context and clean tree. Sends stored retrieve-only permissions. |
 | `work test --local` | Run local quality gate scripts | Runs `.agentia_quality_gates.sh` or `.agentia_quality_gates.cmd` from repo root. |
-| `work submit` | Submit for review/validation | Runs local gates unless `--skip-local-tests`; can push ahead commits. |
-| `work done` | Promote after approval | Pushes if needed, then promotes without validate-only behavior. |
+| `work submit` | Submit for review/validation or promote | Runs local gates unless `--skip-local-tests`; can push ahead commits. `--done` matches Copado UI Submit when promoting. |
 | `work promote` | Story-centric promotion run | Requires `--cloud`; use `--deploy` for merge and deploy. |
-| `work status [ID]` | Check story and related executions | Useful after submit, done, promote, or commit jobs. |
+| `work status [ID]` | Check story and related executions | Useful after submit, promote, or commit jobs. |
 | `work open [ID]` | Open story in browser | CLI-only browser helper. |
 
 ## Local Commit Path
@@ -79,6 +78,6 @@ Prefer explicit flags for standard step types. Use `--config-json`, `--file`, or
 ## Gotchas
 
 - `work test --local` is not CRT. For Robot Framework execution, use the `agentia-testing` skill.
-- `work submit` and `work done` may push ahead commits, but `work set` is still required first.
-- `work done` promotes/deploys. Do not run it unless the user explicitly asked to promote or finish the story.
+- `work submit` may push ahead commits, but `work set` is still required first.
+- `work submit --done` promotes/deploys. Do not run it unless the user explicitly asked to promote or finish the story.
 - `work delete` is destructive; read the story and confirm intent first.