@copado/agentia-cli 0.112.0-alpha.0 → 0.114.0-alpha.0

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@copado/agentia-cli",
   "description": "Command-line interface for Agentia",
-  "version": "0.112.0-alpha.0",
+  "version": "0.114.0-alpha.0",
   "author": "Copado Solutions",
   "bin": {
     "agentia": "./bin/run.js"
@@ -17,11 +17,13 @@
     "@resvg/resvg-js": "^2.6.2",
     "@xmldom/xmldom": "^0.9.12",
     "beautiful-mermaid": "^1.1.3",
+    "exceljs": "^4.4.0",
     "ink": "5.2.1",
     "react": "18.3.1",
     "semver": "^7.8.5",
     "tty-table": "^5.0.0",
     "uuid": "^14.0.1",
+    "ws": "^8.21.3",
     "zod": "^4.4.3"
   },
   "devDependencies": {
@@ -33,6 +35,7 @@
     "@types/node": "^18",
     "@types/react": "18.3.18",
     "@types/semver": "^7.8.0",
+    "@types/ws": "^8.18.1",
     "chai": "^4",
     "eslint": "^9",
     "eslint-config-oclif": "^6",
@@ -208,9 +211,17 @@
       },
       "testing": {
         "description": "Manage Copado Robotic Testing projects, tests, runs, logs, and variables"
+      },
+      "testing:live": {
+        "description": "Manage Copado Robotic Testing live sessions"
       }
     }
   },
+  "overrides": {
+    "exceljs": {
+      "uuid": "11.1.1"
+    }
+  },
   "repository": "Copado/agentia-cli",
   "scripts": {
     "build": "node scripts/build.mjs",

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

@@ -1,26 +1,26 @@
 ---
 name: agentia-testing
-description: Use this skill when creating, updating, running, inspecting, or troubleshooting Copado Robotic Testing tests with the Agentia CLI, especially commands under `agentia testing test`, CRT projects, robots, jobs, builds, logs, variables, PAT authentication, Git-backed test storage, and Robot Framework execution.
+description: Use this skill when creating, updating, running, inspecting, or troubleshooting Copado Robotic Testing with the Agentia CLI, including projects, permissions, robots, jobs, builds, schedules, data tables, variables, user parameters, live testing, Git-backed storage, and Robot Framework execution.
 ---
 
 <!-- Agentia managed skill file: agentia setup skills -->
 
 # Agentia Testing
 
-Use this skill to operate Copado Robotic Testing through Agentia without confusing CRT projects, robots, jobs, tests, and builds.
+Use this skill to operate Copado Robotic Testing through Agentia without confusing CRT resources, executions, live sessions, and Copado CICD records.
 
 Prefer Agentia MCP tools when they are available and match the task. Use CLI examples as the fallback, and add `--json` whenever the result will be parsed or reused.
 
 ## Start Here
 
 1. Confirm CRT auth with `agentia auth get --crt --json`. Configure missing credentials with `agentia auth set --crt ...` or the supported `AGENTIA_CRT_*` environment variables.
-2. Identify or create the CRT Project and Robot before creating or running tests.
+2. Identify or create the CRT Project and Robot before creating or running tests. Use explicit project and job IDs; do not invent hidden active-resource defaults.
 3. Use `testing test ...` as the canonical namespace for test workflows. The shorter `testing run|logs|status|create|update` forms exist for compatibility.
-4. Never expose PATs, organization secrets, or generated log content that contains secrets.
+4. Never expose PAKs, session cookies, viewer keys, variable values, or generated log content that contains secrets.
 
 ## Reference
 
-- CRT test creation, updates, execution, status, logs, and related project/robot/job/build prerequisites: [references/tests.md](references/tests.md)
+- CRT lifecycle, execution, schedules, data tables, live testing, and safety rules: [references/tests.md](references/tests.md)
 
 ## General Rules
 
@@ -28,7 +28,10 @@ Prefer Agentia MCP tools when they are available and match the task. Use CLI exa
 - `agentia testing job` manages CRT job/test definitions. It is different from `agentia cicd job`, which manages Copado CICD JobExecution records.
 - Use `--wait-for-result` on `testing test run` when the agent must return the final build result in one turn.
 - Use Git-backed job flags only when the user or project clearly uses repository-backed CRT test storage.
+- In JSON or non-interactive CLI calls, destructive actions require `--yes`; matching MCP tools require `confirm: true`.
+- Prefer `--value-stdin` and `--git-password-stdin` over putting secrets in process arguments.
+- Use the currently configured CRT credential context for validation. Test14 credentials belong to CICD and must not be substituted for CRT credentials.
 
 ## Report Back
 
-Report the CRT project, robot, job/test ID, build ID when present, final status, and where logs were written or fetched. Do not include PATs or other secrets.
+Report the CRT project, robot, job/test ID, build or live-session ID when present, final status, cleanup, and where outputs were written. Do not include PAKs or other secrets.

package/templates/skills/agentia-testing/references/tests.md

@@ -2,64 +2,98 @@
 
 # CRT Testing Reference
 
-Use this reference for `agentia testing test ...` and related Copado Robotic Testing commands.
+Use this reference for Copado Robotic Testing commands under `agentia testing`.
 
 ## Authentication And Context
 
-Configure CRT once:
-
 ```sh
 agentia auth set --crt <pak> --crt-domain <domain> --crt-org <organization-id>
 agentia auth get --crt --json
 ```
 
-CRT commands resolve authentication from `agentia auth set`, supported `AGENTIA_CRT_*` environment variables, or the configured profile. Do not print PAT values.
-
-## Canonical Test Workflow
+Proceed only when the CRT credential entry reports `ready: true`. CRT commands resolve the configured CRT keychain context or supported `AGENTIA_CRT_*` process overrides. Do not pass PAKs in URLs or report them in output. Test14 is a CICD environment and is not a substitute for CRT credentials.
 
-1. List or create a project: `agentia testing project list --json`
-2. List or create a robot: `agentia testing robot list --json`
-3. Create or update a test: `agentia testing test create ... --json`
-4. Run the test: `agentia testing test run <job-id> --project <project-id> --wait-for-result --json`
-5. Inspect status and logs: `agentia testing test status ... --json` and `agentia testing test logs ... --json`
+Use explicit `--project` and `--job` context. Agentia does not reproduce the legacy CLI's hidden active project/job selection.
 
-## Test Commands
-
-| Command | Use For | Notes |
-| --- | --- | --- |
-| `testing test create` | Create a CRT test and upload Robot files | Requires project, robot, name, and `--file` or `--dir`. |
-| `testing test update ID` | Update files for a test | Use `--add`, `--remove`, `--replace`, or Git branch options. |
-| `testing test run ID` | Run a CRT test | Use `--project`; use `--wait-for-result` when the final status is required. |
-| `testing test status` | List build/run status | Filter by project, job, and status. |
-| `testing test logs ID` | Fetch build logs | Use `--project`, `--job`, and optional `--output`. |
+## Canonical Test Workflow
 
-Examples:
+1. Discover or create a project and robot.
+2. Create a job/test using snapshot files or validated Git-backed storage.
+3. Run through `testing test run` and optionally wait for the terminal build.
+4. Inspect build detail, search, logs, artifacts, or xUnit.
+5. Update the job or data inputs as needed.
+6. Clean up regression-owned resources in reverse order with explicit confirmation.
 
 ```sh
+agentia testing project list --json
+agentia testing robot list --json
 agentia testing test create --project <project-id> --robot <robot-id> --name "Smoke" --file tests/smoke.robot --json
 agentia testing test run <job-id> --project <project-id> --wait-for-result --json
+agentia testing build get <build-id> --project <project-id> --job <job-id> --json
 agentia testing test logs <build-id> --project <project-id> --job <job-id> --output ./crt.log --json
 ```
 
-## Related CRT Commands
+## Command Areas
+
+| Area | Commands |
+| --- | --- |
+| Projects | `testing project list|get|create|update|delete`; `project permission list|get|set|update` |
+| Robots | `testing robot list|get|create|update|delete` |
+| Jobs | `testing job list|get|create|update|delete|run|files|refs|upload|download` |
+| Schedules | `testing job schedule get|set|remove` |
+| Builds | `testing build run|list|get|latest|search|logs|abort` |
+| Variables | `testing variable list|get|create|update|delete` |
+| User parameters | `testing user-parameter list|get|create|update|delete` |
+| Data tables | `testing data-table list|get|create|update|delete|export` |
+| Live testing | `testing live start|stop|status|execute|continue|interrupt|inspect|screenshot|reports|set-options|history|view|recorder` |
+
+`testing create|update|run|status|logs` remain compatibility aliases. Prefer `testing test` for test workflows and canonical resource commands for new automation.
+
+## Execution And Builds
+
+- Use `--wait-for-result` when the result must include terminal build data.
+- `--timeout` bounds waiting; `--no-exit-code` keeps a failed remote run from failing the local command when explicitly desired.
+- `--save-artifacts` and `--xunit` write only to validated explicit paths.
+- `--stream-logs` and `--watch` are human-only and cannot be combined with `--json`.
+- Repeated `--datatable TABLE_ID:SELECTION` starts data-driven batch execution. It cannot be combined with wait, stream, artifact-save, or xUnit modes.
+- Use build `get`, `latest`, and `search` instead of assuming list order.
+
+## Schedules And Data Tables
+
+Schedules support get, set with cron/timezone/record policy, and remove. Data tables accept CSV, TSV, JSON, and XLSX imports and support bounded preview and dataset selection. Export supports CSV, TSV, and XLSX.
+
+Data-table create/update/delete and existing-file overwrite are protected operations. Never overwrite or delete without user intent.
+
+## Live Testing
+
+Use a regression-owned job:
+
+```sh
+agentia testing live start <job-id> --project <project-id> --json
+agentia testing live status --project <project-id> --json
+agentia testing live execute --project <project-id> --line "GoTo  https://example.com" --json
+agentia testing live inspect --project <project-id> --json
+agentia testing live stop --project <project-id> --yes --json
+```
+
+Live viewer secrets remain in the keychain. Session cookies and XSRF values are in-memory only. `view` opens an authenticated page without putting secrets in the URL. `recorder` is long-running and uses an owner-scoped local lock; neither `view` nor `recorder` is exposed through MCP.
+
+## Secret Inputs And Redaction
 
-| Area | Commands | Use For |
-| --- | --- | --- |
-| Projects | `testing project list/create/get/delete` | Top-level CRT project lifecycle. |
-| Robots | `testing robot list/create/get/delete` | Robot worker definitions. |
-| Jobs | `testing job list/create/get/update/delete/files/upload/download` | CRT job/test definitions and file storage. |
-| Builds | `testing build run/list/logs/abort` | Lower-level run/build management. |
-| Variables | `testing variable list/create/update/delete` | CRT variables, with value redaction in output. |
+- Prefer `--value-stdin`/`--value-file` for variable values.
+- Prefer `--git-password-stdin`/`--git-password-file` or a CRT domain credential for Git authentication.
+- Sensitive variable and user-parameter values must remain redacted in human, JSON, MCP, debug, and error output.
+- Validate local paths, remote paths, and Git refs before mutation.
 
-Use related commands to discover IDs needed by `testing test`.
+## Confirmation
 
-## Git-Backed Tests
+Destructive or protected CLI actions prompt in an interactive TTY. JSON and non-TTY calls require `--yes`. Matching MCP tools require `confirm: true`, not a `yes` field.
 
-Some CRT tests store Robot files in Git. Use Git-backed flags only when the project already expects Git storage or the user asks for it. Preserve branch, path, and credential values from existing job details when updating.
+This applies to resource deletion, build abort, schedule removal, live stop, protected data-table imports/deletion, and output overwrite.
 
 ## Gotchas
 
-- The `testing test` namespace and the shorter `testing` namespace overlap. Prefer `testing test` in generated guidance because it makes the CRT domain explicit.
-- There is no `testing test get` or `testing test delete`; use `testing job get` or `testing job delete` for CRT job/test definitions.
-- `testing test run --wait-for-result` can poll until a terminal build status. Without it, the command may return only the started build.
-- Log commands may write files. In JSON mode, keep stdout structured and report the output path instead of mixing log text with JSON.
+- `testing job` is a CRT test definition; `cicd job` is a Copado CICD JobExecution.
+- There is no `testing test get` or `testing test delete`; use `testing job get` and `testing job delete`.
+- CRT tenant users, organizations, groups, roles, licenses, and cross-region migration are intentionally not Agentia testing commands.
+- Log, artifact, data-table, DOM, screenshot, and report commands may write files. Keep JSON stdout structured and report only sanitized output metadata.