@copado/agentia-cli 0.98.0-alpha.0 → 0.100.0-alpha.0

package/package.json

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

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

@@ -33,7 +33,7 @@ Prefer Agentia MCP tools when they are available and match the task. Use CLI exa
 - 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`, 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 `cicd work test` as local quality gates (`--local` is the default). It is different from CRT `testing test run`.
 - Treat `auth` credentials as keychain/API credentials and `cicd credential` records as Copado environment credentials.
 
 ## Report Back

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

@@ -15,7 +15,7 @@ Use this path when the change exists in the local repository:
 1. Discover and inspect: `agentia cicd work list --assigned-to-me --json`, then `agentia cicd work get <id-or-name> --json`.
 2. Activate: `agentia cicd work set <id-or-name> --json`. This fetches the configured base branch, checks out `feature/<story-name>`, and records the story, base branch, dev org branch, and pull-request context in `.agentia/config.user.json`. Use `--base-branch <branch>` only when intentionally overriding the Pipeline default.
 3. Implement and stage new files with `git add`. Commit with Git, or use `agentia cicd work commit --local --all --json` when Agentia should also remember permission, full-metadata, or Apex-test selections. `--local` is the default, and `--all` includes tracked changes only.
-4. Run project-owned gates: `agentia cicd work test --local --json`. This runs `.agentia_quality_gates.sh` or `.agentia_quality_gates.cmd` from the repository root when present.
+4. Run project-owned gates: `agentia cicd work test --json`. This runs `.agentia_quality_gates.sh` or `.agentia_quality_gates.cmd` from the repository root when present. `--local` is the default; `--cloud` is reserved and not implemented yet.
 5. Register and synchronize: `agentia cicd work push --json`. A plain `git push` does not register a Copado Commit or merge the feature branch into the recorded dev org branch.
 6. Validate and open the merge-request flow: `agentia cicd work submit --json`. Submit runs the local gates unless `--skip-local-tests` is explicit, pushes ahead commits, and submits with validate-only behavior.
 7. Only with explicit approval to promote and deploy, run `agentia cicd work submit --done --json`. `work done` is a compatibility alias.
@@ -42,10 +42,10 @@ Cloud commit checks Story readiness and source credentials before submission. Av
 | `work get [ID]` | Read story details | ID is optional after `work set`. Human output redacts OAuth signatures; JSON preserves structured fields. |
 | `work create` | Create a story | Use `--title`, project/team/assignee/theme fields, specs, and short acceptance criteria. |
 | `work update [ID]` | Mutate story fields or status | ID is optional after `work set`. Acceptance criteria must be fewer than 255 chars. |
-| `work set ID` | Mark active and prepare branch | Fetches base branch, creates/checks out `feature/<story-name>`, stores local context. |
+| `work set ID` | Mark active and prepare branch | Fetches base branch, creates/checks out `feature/<story-name>`, stores local context. `--none` clears every `last*` key and checks out `lastBaseBranch`, else `main`, else `master`. |
 | `work commit` | Local or cloud commit | The flag sets are disjoint. `--local` is default and performs no gateway call; `--cloud` calls Copado commit APIs and polls by default. |
 | `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 test` | Run local quality gate scripts | `--local` is default. Runs `.agentia_quality_gates.sh` or `.agentia_quality_gates.cmd` from repo root. `--cloud` is not implemented yet. |
 | `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 done` | Compatibility alias | Prefer `work submit --done`; both promote and deploy rather than validate-only. |
 | `work promote` | Story-centric promotion run | Requires `--cloud`; use `--deploy` for merge and deploy. |
@@ -59,14 +59,14 @@ Use local commits for normal source changes. Stage new files explicitly because
 ```sh
 git add -A
 agentia cicd work commit --local --all --permissions CustomField:Account.SLA__c,ApexClass:AccountService --json
-agentia cicd work test --local --json
+agentia cicd work test --json
 agentia cicd work push --json
 agentia cicd work submit --json
 ```
 
 `--permissions` records metadata that Copado should treat as Retrieve Only during push. List the components whose access changed, not the permission set or profile files. Use `--full-metadata` only when a profile or permission set should travel as a complete file, because it can overwrite permissions the Story did not touch. Both selections are sticky in local user config until replaced or cleared with an empty value. Push-time selections apply only to that push.
 
-`--apex-test-classes` records story-related test class names for later reference. `work test --local` and `work submit` still take `--apex-test-classes` explicitly when you want the local gate script to receive them.
+`--apex-test-classes` records story-related test class names for later reference. `work test` and `work submit` still take `--apex-test-classes` explicitly when you want the local gate script to receive them.
 
 `work push` detects nested metadata across the full branch diff from the merge base to `HEAD`, applies Copado environment-variable and YAML replacements, registers every commit in the range, and merges into the recorded dev org branch. Review unexpected Retrieve Only, Full Metadata, or nested-deletion output before continuing.
 
@@ -108,7 +108,7 @@ 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 test` is not CRT. For Robot Framework execution, use the `agentia-testing` skill.
 - Local `work commit` rejects Story IDs and cloud-only flags; cloud `work commit --cloud` rejects local-only flags.
 - `work submit` may push ahead commits, but the local flow still needs story and branch context from `work set`.
 - `work submit --done` promotes/deploys. Do not run it unless the user explicitly asked to promote or finish the story.