@copado/agentia-cli 1.0.0-rc.0 → 1.1.0

package/package.json

@@ -235,7 +235,7 @@
     }
   },
   "type": "module",
-  "version": "1.0.0-rc.0",
+  "version": "1.1.0",
   "x-agentia-protected-build": true,
   "x-agentia-protected-files": [
     "dist/lib/runtime.js"

package/templates/rules/cursor/agentia.mdc

@@ -0,0 +1,29 @@
+---
+description: Use Agentia for Copado CICD, Testing, AI, and advanced pipeline workflows
+alwaysApply: false
+---
+
+<!-- Agentia managed rules: agentia setup skills -->
+
+# Agentia CLI
+
+Use Agentia to manage Copado work items. Prefer registered Agentia MCP tools; otherwise use the CLI with `--json`.
+
+Authentication must be configured before operational commands. Never print credentials, tokens, or unmasked environment variables.
+
+## Copado workflow
+
+`list → get → set → (implement & git commit) → test → publish → submit [--done|--deploy]`
+
+Read records before changing them and use IDs returned by Copado. Do not skip `work set` before coding; use one story per feature branch. Keep the working tree clean for lifecycle commands, and confirm promotion/deployment intent before `done`.
+
+## Agent Skills
+
+Load exactly one copy of each applicable installed Agentia skill:
+
+- `agentia-cicd`: Copado stories, commits, publish, submit, done, promotions, jobs, Functions, Job Templates, environments, pipelines, Slack notification configure, and data.
+- `agentia-testing`: Copado Robotic Testing operations.
+- `agentia-ai`: Copado AI operations.
+- `agentia-adv`: advanced pipeline workflows.
+
+Project-specific instructions take precedence over managed Agentia skills. Refresh managed skills with `agentia setup skills update`; do not hand-edit managed files.

package/templates/skills/agentia/SKILL.md

@@ -0,0 +1,29 @@
+---
+name: agentia
+description: Use when working with Agentia or Copado CICD, Robotic Testing, AI, pipelines, user stories, commits, promotions, deployments, jobs, environments, credentials, or data templates.
+---
+
+<!-- Agentia managed skill file: agentia setup skills -->
+
+# Agentia CLI
+
+Use Agentia to manage Copado work items. Prefer registered Agentia MCP tools; otherwise use the CLI with `--json`.
+
+Authentication must be configured before operational commands. Never print credentials, tokens, or unmasked environment variables.
+
+## Copado workflow
+
+`list → get → set → (implement & git commit) → test → publish → submit [--done|--deploy]`
+
+Read records before changing them and use IDs returned by Copado. Do not skip `work set` before coding; use one story per feature branch. Keep the working tree clean for lifecycle commands, and confirm promotion/deployment intent before `done`.
+
+## Agent Skills
+
+Use the applicable installed domain skill for detailed instructions:
+
+- `agentia-cicd`: Copado stories, commits, publish, submit, done, promotions, jobs, Functions, Job Templates, environments, pipelines, Slack notification configure, and data.
+- `agentia-testing`: Copado Robotic Testing operations.
+- `agentia-ai`: Copado AI operations.
+- `agentia-adv`: advanced pipeline workflows.
+
+Project-specific instructions take precedence over managed Agentia skills. Refresh managed skills with `agentia setup skills update`; do not hand-edit managed files.

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

@@ -1,6 +1,6 @@
 ---
 name: agentia-cicd
-description: Use this skill when managing Copado CICD work with the Agentia CLI or Agentia MCP tools: user stories (including current/active story context), cloud commit/promote, work publish/submit/done, promotion runs and conflicts, job executions, Copado Functions, Job Templates, environments, credentials, pipelines, stages, Slack pipeline notification subscriptions, and release data templates. Use it whenever the user asks an agent to operate Copado CICD from a terminal, IDE, or headless workflow.
+description: Use this skill when managing Copado CICD work with the Agentia CLI or Agentia MCP tools: user stories (including current/active story context), cloud commit/promote, work publish/submit/done, promotion runs and conflicts, job executions, Copado Functions, Job Templates, git-hosted CICD extensions, environments, credentials, pipelines, stages, Slack pipeline notification subscriptions, and release data templates. Use it whenever the user asks an agent to operate Copado CICD from a terminal, IDE, or headless workflow.
 ---
 
 <!-- Agentia managed skill file: agentia setup skills -->
@@ -24,6 +24,7 @@ Prefer Agentia MCP tools when they are available and match the task. Use CLI exa
 - Promotion lookup, run, resume, merge conflicts, and story-centric promotion: [references/promotions.md](references/promotions.md)
 - Copado JobExecution lookup, actions, logs, and monitoring: [references/jobs.md](references/jobs.md)
 - Copado Functions lifecycle, remote run/results, and local Docker run: [references/functions.md](references/functions.md)
+- Git-hosted Copado CICD extensions (`cicd extension`, experimental): [references/extensions.md](references/extensions.md)
 - Copado Job Templates (`cicd template`, not data templates): [references/templates.md](references/templates.md)
 - Copado environments, environment credentials, and browser authentication: [references/environments-and-credentials.md](references/environments-and-credentials.md)
 - Pipelines, environment connections, stages, and stage connections: [references/pipelines.md](references/pipelines.md)
@@ -38,6 +39,7 @@ Prefer Agentia MCP tools when they are available and match the task. Use CLI exa
 - For local project work, keep the tracked working tree clean before commands that require it: `work set`, `work publish`, and `work submit`. If `work set` returns `status: "warning"`, show the message and do not assume a feature branch was created; branch keys are cleared and the work item id/name/title are still recorded in config.user.json.
 - Treat `cicd job` as Copado CICD JobExecution. It is different from CRT `testing job`.
 - Treat `cicd function` as Copado Function definitions and runs. It is different from JobExecution (`cicd job`) and Job Templates (`cicd template`).
+- Treat `cicd extension` as experimental git-hosted packaging of Functions/Templates (plus optional `force-app`). It is different from per-asset `cicd function` / `cicd template` upserts.
 - Treat `cicd template` as Copado Job Templates via `/release/jobs/templates`. It is different from Release Data Templates (`cicd data template`).
 - Treat `cicd work test` as local quality gates (`--local` is the default). It is different from CRT `testing test run`.
 - Treat `cicd work test apex` as the Apex test runner that local quality gates (`.agentia_quality_gates.*`) usually call. An empty `--apex-test-classes` list skips Salesforce CLI. It can also be invoked directly. It is different from CRT.

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

@@ -0,0 +1,49 @@
+# Copado CICD Extensions
+
+Use this reference for experimental git-hosted extension commands under `agentia cicd extension ...`.
+
+## Scope
+
+`cicd extension` packages Copado Functions and Job Templates (plus optional `force-app`) as a git repository with a semver tag. It is not the same as individual `cicd function` / `cicd template` upserts, Salesforce unlocked packages, or MCP tools (none in v1).
+
+Layout:
+
+- `copado/extension_manifest.json` (includes additive semver `version`)
+- `copado/functions/`
+- `copado/templates/`
+- optional `force-app/`
+
+## Author workflow
+
+```sh
+agentia cicd extension create --name my-extension --version 1.0.0
+agentia cicd extension validate --require-version
+agentia cicd extension package --json
+# commit the manifest version before publish
+agentia cicd extension publish --remote origin
+agentia cicd extension publish --local --force   # offline tag only
+```
+
+`publish --version` fails if the bump is still uncommitted. Prefer committing the version, then publishing without rewriting it.
+
+## Install and uninstall
+
+```sh
+agentia cicd extension install https://gitlab.com/org/my-ext.git --version 1.0.0 --dry-run
+agentia cicd extension install https://gitlab.com/org/my-ext.git --version 1.0.0 --yes --sf-alias destOrg
+agentia cicd extension install ./my-extension --version 1.0.0 --exclude-sf-deploy --yes --json
+agentia cicd extension uninstall ./my-extension --version 1.0.0 --yes --json
+```
+
+Rules:
+
+- Install and uninstall need `--yes` (or a prompt) except `--dry-run`.
+- `force-app` needs `--sf-alias` or `--exclude-sf-deploy`.
+- Symlinks and paths outside the extension root are rejected.
+- Uninstall deletes listed Functions/Templates only (404 = already gone); it does not undeploy `force-app`.
+
+## Related
+
+- Individual Functions: [functions.md](functions.md)
+- Individual Job Templates: [templates.md](templates.md)
+- Customer enablement: `docs/enablement/features/agentia-cli-cicd-extensions.md`

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

@@ -11,7 +11,7 @@ Pipeline connections, stage connections, and stages are related but distinct. Re
 | Command | Use For | Notes |
 | --- | --- | --- |
 | `pipeline list` | Find pipelines | Filter by `--active`, `--name`, `--platform`, cursor, and page size. |
-| `pipeline get ID` | Inspect one pipeline | Returns describe-style details, including embedded connections. |
+| `pipeline get ID` | Inspect one pipeline | Returns describe-style details, including embedded connections. JSON may also include redesigned `automations` / `qualityGates` rule aggregates (one quality-gate entry per condition row). |
 | `pipeline create NAME` | Create a pipeline | Common flags: `--platform`, `--main-branch`, `--git-repository-id`. |
 | `pipeline update ID` | Sparse pipeline changes | Set `--name`, branch, repository, or conflict strategy fields. |
 | `pipeline open ID` | Open in browser | CLI-only navigation helper. |

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

@@ -1,5 +1,7 @@
 
 
+<!-- Agentia managed skill file: agentia setup skills -->
+
 # CICD Work Reference
 
 Use this reference for `agentia cicd work ...`, `agentia cicd cloud ...`, and matching MCP tools such as `agentia_work_get`, `agentia_cloud_commit`, `agentia_work_publish`, and `agentia_work_submit`.
@@ -47,7 +49,7 @@ Use this path when the change exists in the local repository:
 Use this path when Copado should retrieve metadata from a configured source environment instead of using local Git changes:
 
 1. Inspect the Story and pass its Salesforce ID explicitly when possible. An active Story from `work set` is optional, not a prerequisite for the cloud operation.
-2. Start a cloud commit with `agentia cicd cloud commit <story-id> ... --json`. Use the simple metadata flags for one change, or `--file`/`--stdin` for a multi-change request. Salesforce metadata requires `--metadata-category SFDX`.
+2. Start a cloud commit with `agentia cicd cloud commit <story-id> ... --json`. Use the simple metadata flags for one change, or `--file`/`--stdin` for a multi-change request. Always pass `--metadata-category` (use `SFDX` for Salesforce metadata). With `--file`/`--stdin`, each change requires `c` (or `category`).
 3. Let the command wait for its Job Execution by default. After a timeout, use the returned execution ID with `agentia cicd job get` and `agentia cicd job log get`; do not immediately submit a duplicate commit.
 4. When explicitly approved to promote an existing Promotion, use `agentia cicd cloud promote <story-id> --json`; add `--deploy` only for promote-and-deploy. This is independent of local `work submit`.
 
@@ -59,11 +61,11 @@ Cloud commit checks Story readiness and source credentials before submission. Av
 | Command            | Use For                                        | Notes                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
 | ------------------ | ---------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `work list`        | Find candidate stories                         | Use `--assigned-to-me`, `--status`, `--project-name`, `--name`, pagination flags.                                                                                                                                                                                                                                                                                                                                                                                                                    |
-| `work get [ID]`    | Read story details                             | ID is optional after `work set`. Human output redacts OAuth signatures; JSON preserves structured fields.                                                                                                                                                                                                                                                                                                                                                                                            |
+| `work get [ID]`    | Read story details                             | ID is optional after `work set`. Human output redacts OAuth signatures; JSON preserves structured fields. `--committed-metadata` also includes the Story committed metadata list as `committedMetadata` in the result.                                                                                                                                                                                                                                                                                |
 | `work create`      | Create a story                                 | Use `--title`, project/team/assignee/theme fields, specs, and short acceptance criteria. `--source-credential` sends `sourceEnvironment` as null so Salesforce assigns the environment.                                                                                                                                                                                                                                                                                                              |
 | `work update [ID]` | Mutate story fields or status                  | ID is optional after `work set`. Acceptance criteria must be fewer than 255 chars. `--source-credential` sends `sourceEnvironment` as null.                                                                                                                                                                                                                                                                                                                                                          |
 | `work set ID`      | Mark active and prepare branch                 | Fetches the base branch and, when present, the remote feature branch; creates/checks out `feature/<story-name>` from `origin/feature` when that ref exists, otherwise from the base; stores local context. A gateway warning prints the message, skips git, clears branch keys, and records work-item id/name/title. Warns without PATCHing when the Story credential differs from the project default; use `work update --source-credential` to change it. `--none` clears every `last*` key and checks out `lastBaseBranch`, else `main`, else `master`. |
-| `cloud commit`     | Copado cloud metadata commit                   | For local Git work, use `git commit` then `work publish`. `work commit` is a hidden compatibility alias.                                                                                                                                                                                                                                                                                                                                                                                              |
+| `cloud commit`     | Copado cloud metadata commit                   | Prefer `agentia cicd cloud commit`. Requires `--metadata-category` (or `c`/`category` per `--file` change); use `SFDX` for Salesforce metadata. For local Git work, use `git commit` then `work publish`. `cicd work commit` remains a hidden compatibility alias.                                                                                                                                                                                                                                  |
 | `work publish`     | Publish local commits and register with Copado | Requires active story context and clean tree. Accepts `--permissions` and `--full-metadata` when nested detection is not enough. `work push` is a compatibility alias.                                                                                                                                                                                                                                                                                                                               |
 | `work test`        | Run local quality gate scripts                 | `--local` is default. Runs `.agentia_quality_gates.sh` or `.agentia_quality_gates.cmd` from repo root. If missing, warns and runs the stock setup sample from a temp file. `--cloud` is not implemented yet.                                                                                                                                                                                                                                                                                         |
 | `work test apex`   | Run named Apex test classes                    | Optional `--apex-test-classes`. Omit or pass empty to log a skip and exit 0 without calling Salesforce CLI. `--rerun-failed-apex-tests` reruns classes from `.agentia/apex.tests.<user-story>.json`. Optional `--wait` minutes (default 60). Usually invoked from `.agentia_quality_gates.*`. |
@@ -105,7 +107,7 @@ agentia cicd cloud commit <story-id> --message "Commit AccountService" --metadat
 agentia cicd cloud commit <story-id> --file commit-request.json --json
 ```
 
-For Salesforce metadata, include `--metadata-category SFDX`. Without the SFDX category, Copado deploy logs can report "Salesforce changes not found."
+`--metadata-category` is required on simple flag input. Each `--file`/`--stdin` change requires `c` (or `category`). For Salesforce metadata, use `SFDX`. Without `c:SFDX`, Copado deploy logs can report "Salesforce changes not found."
 
 For a cloud promotion, the Story must already belong to a Promotion:
 

package/templates/AGENTS.md

@@ -1,24 +0,0 @@
-# Agentia CLI for AI Agents
-
-<!-- agentia:managed:start -->
-
-Use Agentia to manage Copado work items. Prefer registered Agentia MCP tools; otherwise use the CLI with `--json`.
-
-Authentication must be configured before operational commands. Never print credentials, tokens, or unmasked environment variables.
-
-## Copado workflow
-
-`list → get → set → (implement & git commit) → test → publish → submit [--done|--deploy]`
-
-Read records before changing them and use IDs returned by Copado. Do not skip `work set` before coding; use one story per feature branch. Keep the working tree clean for lifecycle commands, and confirm promotion/deployment intent before `done`.
-
-## Agent Skills
-
-Load exactly one copy of each applicable Agentia skill. Prefer the client-specific root when available (`.cursor/skills` in Cursor or `.claude/skills` in Claude); otherwise use `.agents/skills`.
-
-- `agentia-cicd/SKILL.md`: Copado stories, commits, publish, submit, done, promotions, jobs, Functions, Job Templates, environments, pipelines, Slack notification configure, and data.
-- `agentia-testing/SKILL.md`: Copado Robotic Testing operations.
-- `agentia-ai/SKILL.md`: Copado AI operations.
-
-Project rules in this file take precedence over managed skill guidance. Refresh managed skills with `agentia setup skills update`; do not hand-edit managed files.
-<!-- agentia:managed:end -->