@copado/agentia-cli 0.95.0-alpha.0 → 0.96.0-alpha.0

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@copado/agentia-cli",
   "description": "Command-line interface for Agentia",
-  "version": "0.95.0-alpha.0",
+  "version": "0.96.0-alpha.0",
   "author": "Copado Solutions",
   "bin": {
     "agentia": "./bin/run.js"
@@ -137,6 +137,9 @@
       "cicd:job:log": {
         "description": "Inspect Copado job execution logs"
       },
+      "cicd:job:result-file": {
+        "description": "Inspect Files linked to Copado job Results"
+      },
       "cicd:metadata": {
         "description": "Inspect and compare Copado metadata"
       },

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

@@ -13,6 +13,8 @@ Use this reference for Copado CICD JobExecution commands under `agentia cicd job
 | `job list` | Search job executions | Filter by `--status`, `--type`, `--parent`, `--context`, `--mine`, cursor, and page size. |
 | `job get ID` | Inspect a job and ordered steps | Read before action commands or log lookup. |
 | `job log get ID` | Read execution logs | Use `--step <step-id>` when a specific step is needed. |
+| `job result-file list RESULT_ID` | Discover files linked to a job-step Result | Returns file metadata; use its `fileId` with `get`. |
+| `job result-file get RESULT_ID --file-id CONTENT_VERSION_ID` | Retrieve one Result-linked Salesforce File | Use `--output-file <path>` to write validated decoded bytes; JSON and MCP return Base64 content. |
 | `job run ID` | Run all steps | Use `--restart` only when the user asks to restart from the beginning. |
 | `job resume ID` | Resume outstanding steps | Good after a paused or partially completed job. |
 | `job pause ID` | Pause/cancel resumably | Confirm intent before interrupting active work. |
@@ -25,6 +27,8 @@ Examples:
 agentia cicd job list --status "In Progress" --json
 agentia cicd job get <job-execution-id> --json
 agentia cicd job log get <job-execution-id> --step <step-id> --json
+agentia cicd job result-file list <result-id> --json
+agentia cicd job result-file get <result-id> --file-id <content-version-id> --output-file ./artifact.zip
 agentia cicd job resume <job-execution-id> --json
 ```
 
@@ -33,10 +37,13 @@ agentia cicd job resume <job-execution-id> --json
 1. Use `job list --mine --status "In Progress" --json` or use the job ID returned by another command.
 2. Run `job get <id> --json` to inspect status and step ordering.
 3. Use `job log get <id> --step <step-id>` only when logs are needed for diagnosis.
-4. Use `resume`, `pause`, `kill`, or `run --restart` only after confirming the current status and user intent.
+4. Use `job result-file list <result-id> --json` to discover artifacts for a completed step, then retrieve only the selected `fileId`.
+5. Use `resume`, `pause`, `kill`, or `run --restart` only after confirming the current status and user intent.
 
 ## Gotchas
 
 - Some job tools require user and organization context at the gateway layer. If the CLI reports missing context, inspect auth and user context before retrying.
 - Logs can be large. Prefer a specific step when available.
+- Result-file commands require the job-step Result ID, not the JobExecution ID. They accept only 15- or 18-character Salesforce IDs and never derive output paths from remote filenames.
+- `--output-file` can replace an existing file after Base64 validation. Use an explicitly controlled destination; malformed content leaves an existing target unchanged.
 - Do not use CICD job commands for Robot Framework builds; use the `agentia-testing` skill for CRT run status and logs.