@copado/agentia-cli 1.0.0 → 1.1.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (42) hide show
  1. package/CHANGELOG.md +17 -0
  2. package/README.md +481 -278
  3. package/dist/commands/cicd/cloud/commit.js +7 -2
  4. package/dist/commands/cicd/extension/create.js +53 -0
  5. package/dist/commands/cicd/extension/install.js +127 -0
  6. package/dist/commands/cicd/extension/package.js +35 -0
  7. package/dist/commands/cicd/extension/publish.js +61 -0
  8. package/dist/commands/cicd/extension/uninstall.js +99 -0
  9. package/dist/commands/cicd/extension/validate.js +47 -0
  10. package/dist/commands/cicd/work/get.js +18 -2
  11. package/dist/commands/setup/skills/create.js +1 -1
  12. package/dist/commands/setup/skills/update.js +1 -1
  13. package/dist/commands/setup.js +1 -1
  14. package/dist/lib/extension/assets.js +4 -0
  15. package/dist/lib/extension/create.js +3 -0
  16. package/dist/lib/extension/git.js +17 -0
  17. package/dist/lib/extension/index.js +27 -0
  18. package/dist/lib/extension/install.js +4 -0
  19. package/dist/lib/extension/manifest.js +21 -0
  20. package/dist/lib/extension/package.js +3 -0
  21. package/dist/lib/extension/paths.js +5 -0
  22. package/dist/lib/extension/publish.js +3 -0
  23. package/dist/lib/extension/sf-deploy.js +8 -0
  24. package/dist/lib/extension/source.js +7 -0
  25. package/dist/lib/extension/uninstall.js +3 -0
  26. package/dist/lib/function-types.js +3 -1
  27. package/dist/lib/mcp/work-tools.js +19 -6
  28. package/dist/lib/project-setup.js +5 -4
  29. package/dist/lib/runtime.js +1 -1
  30. package/dist/lib/setup-skills.js +4 -1
  31. package/dist/lib/setup-templates.js +1 -4
  32. package/dist/lib/template-types.js +3 -1
  33. package/dist/lib/work-committed-metadata.js +4 -0
  34. package/dist/lib/work-get.js +2 -1
  35. package/oclif.manifest.json +414 -7
  36. package/package.json +1 -1
  37. package/templates/rules/cursor/agentia.mdc +29 -0
  38. package/templates/skills/agentia/SKILL.md +29 -0
  39. package/templates/skills/agentia-cicd/SKILL.md +3 -1
  40. package/templates/skills/agentia-cicd/references/extensions.md +49 -0
  41. package/templates/skills/agentia-cicd/references/work.md +6 -4
  42. package/templates/AGENTS.md +0 -24
package/CHANGELOG.md CHANGED
@@ -4,6 +4,23 @@ All published sections are mapped to immutable npm publication metadata. New use
4
4
 
5
5
  ## [Unreleased]
6
6
 
7
+ ## [1.1.0] - 2026-10-21
8
+
9
+ ### Added
10
+
11
+ - `agentia cicd extension create|validate|package|publish|install|uninstall` packages Copado CICD extensions as git-hosted bundles (`copado/extension_manifest.json`, functions, job templates, optional `force-app`), publishes annotated semver tags (including `--local` offline tags), installs from a git URL or local path, and uninstalls by deleting listed assets. Function and job-template file upserts pass through unknown custom fields.
12
+ - `cicd work get` accepts `--committed-metadata` (MCP `committedMetadata`) to fetch Copado committed metadata for the user story in parallel and include it in human and `--json` output.
13
+
14
+ ### Changed
15
+
16
+ - `agentia setup` and `agentia setup skills create|update` install target-specific Agentia routing artifacts (Cursor rules, a Claude routing skill, or a portable routing skill) instead of synchronizing customer root `AGENTS.md`.
17
+ - `agentia setup` asks before removing a legacy Agentia managed section from an existing `AGENTS.md`, and leaves the rest of that file unchanged.
18
+ - `cicd cloud commit` (and the hidden `cicd work commit` alias) requires a metadata category: `--metadata-category` for simple flag input, and `c` / `category` on each change for JSON/`--file`/`--stdin` and MCP. Use `SFDX` for Salesforce metadata.
19
+
20
+ ### Fixed
21
+
22
+ - `cicd work set` creates local feature branches with `--no-track`, and work publish / other origin pushes use `git push -u`, so a new feature branch no longer tracks `origin/main` (or another base) and instead tracks `origin/<same-branch-name>` after the first push.
23
+
7
24
  ## [1.0.0] - 2026-10-19
8
25
 
9
26
  ### Added