@automatify-au/cli 0.1.16 → 0.1.18

package/README.md

@@ -74,8 +74,10 @@ Publish notes:
 Minimum:
 - `JIRA_BASE_URL`
 - At least one of `JIRA_PROJECT_KEY` or `JIRA_ISSUE_KEY`
-- `TESTOPS_FORGE_ENDPOINT` for commands that call Forge contracts (`doctor`, `ingest`, `run`, `sync`)
-- `TESTOPS_FORGE_AUTH_TOKEN` from the one-time token shown in Forge `Operations -> CLI access`
+- `TESTOPS_FORGE_ENDPOINT` for commands that call Forge contracts (`doctor`, `ingest`, `run`, `sync`); copy the installation-specific endpoint from Jira `Automatify TestOps -> CLI`
+- `TESTOPS_FORGE_AUTH_TOKEN`; create a CLI key in Jira `Automatify TestOps -> CLI` and copy the one-time token when it is shown
+
+Customer admins do not need the Forge developer CLI to obtain either value. The Jira CLI workspace resolves the webtrigger endpoint for the current app installation at runtime.
 
 Local Jira auth helper on macOS/Windows:
 ```bash
@@ -88,10 +90,10 @@ automatify testops auth status
 
 On Linux/CI, keep `JIRA_API_TOKEN` in the environment and run `auth login` without `--token-stdin`; the CLI stores only non-secret Jira settings. Use `automatify testops auth logout` to remove local Jira and Forge credentials while preserving non-secret URL/email settings. Environment variables are not modified by logout.
 
-Forge transport auth remains an advanced setting:
+Forge transport auth remains an advanced setting. First open the Jira project, go to `Automatify TestOps -> CLI`, copy the displayed CLI endpoint, create a CLI key, and copy its one-time token. Then configure the CLI:
 ```bash
 automatify testops config set projectKey DEV
-automatify testops config set forgeEndpoint "<webtrigger-url>"
+automatify testops config set forgeEndpoint "<endpoint-copied-from-jira>"
 printf "%s" "$TESTOPS_FORGE_AUTH_TOKEN" | automatify testops config set forgeAuthToken --stdin
 ```
 
@@ -110,6 +112,9 @@ All TestOps commands are invoked as `automatify testops <command>`:
 ### Core browse commands
 
 - `bdd`
+  - `automatify testops bdd scenarios list`
+  - `automatify testops bdd scenarios list --json`
+  - `automatify testops bdd scenarios list --project-key <PROJECT_KEY> --issue-key <ISSUE_KEY>`
   - `automatify testops bdd scenarios show --id <SCENARIO_ID>`
   - `automatify testops bdd scenarios show --id <SCENARIO_ID> --format feature`
   - `automatify testops bdd scenarios show --id <SCENARIO_ID|SC-4> --feature`
@@ -141,6 +146,15 @@ All TestOps commands are invoked as `automatify testops <command>`:
   - `automatify allure open ./allure-report.zip`
   - `automatify allure open ./allure-report.zip --no-open --port 8080`
 
+`bdd scenarios list` uses the configured project context or `--project-key`; `--issue-key` optionally narrows the Jira issue context. Human output is concise and selector-first:
+
+```text
+BDD scenarios (1) for project DEV:
+SC-14 | Guest payment | Feature: Checkout | Steps: 3 | Issues: DEV-2
+```
+
+With `--json`, the command emits one JSON object with stable action `bdd-scenarios-list`, `projectKey`, optional `issueKey`, `count`, and `items`.
+
 ### Advanced browse commands
 
 - `cases`
@@ -224,7 +238,7 @@ Secrets must come from stdin or safe environment references. Secret values are r
 ```bash
 export TESTOPS_GITHUB_PROVIDER_TOKEN="<github-app-installation-or-fine-grained-token>"
 export TESTOPS_GITHUB_ADMIN_TOKEN="<least-privilege-token-allowed-to-manage-actions-secrets>"
-export TESTOPS_FORGE_ENDPOINT="<forge-webtrigger-url>"
+export TESTOPS_FORGE_ENDPOINT="<endpoint-copied-from-jira-cli-workspace>"
 export TESTOPS_FORGE_AUTH_TOKEN="<one-time-project-cli-key>"
 
 automatify testops setup apply \
@@ -270,7 +284,8 @@ Doctor verifies the local workflow hash, GitHub workflow metadata/content at the
 
 Current authentication boundary:
 
-- `TESTOPS_FORGE_AUTH_TOKEN` is still a project-scoped, project-admin-created CLI key from Jira `Operations -> CLI access`.
+- `TESTOPS_FORGE_ENDPOINT` is copied from the installation-specific endpoint displayed in Jira `Automatify TestOps -> CLI`.
+- `TESTOPS_FORGE_AUTH_TOKEN` is a project-scoped, project-admin-created CLI key from the same Jira CLI workspace.
 - The key authorizes the current Forge webtrigger transport for that project; command groups are not separate security scopes.
 - Setup does not turn this into an all-user auth model. Customer-admin packaging and any future user-level authentication remain separate work.
 - The same callback key may be stored as a GitHub Actions repository secret only under the explicit `github-secrets` apply scope.
@@ -423,20 +438,18 @@ Required env/config for real upload mode:
 - `TESTOPS_FORGE_ENDPOINT`
 - `TESTOPS_FORGE_AUTH_TOKEN` for the repo-owned authenticated webtrigger transport
 
-One-time Forge transport setup:
-```bash
-cd apps/forge
-forge deploy
-forge install --upgrade --site automatify-com-au.atlassian.net --product Jira -e development --confirm-scopes --non-interactive
-forge webtrigger create --functionKey cli-transport-webtrigger --site automatify-com-au.atlassian.net --product Jira -e development
-```
+Customer CLI transport setup (no Forge developer CLI required):
+1. Open the Jira project and go to `Automatify TestOps -> CLI`.
+2. Copy the `CLI endpoint` displayed for the current installation.
+3. Create a project CLI key and copy the token immediately; it is shown once only.
+4. Configure those two values in the local shell, CI secret store, or CLI config.
 
-Then open the Jira project page, go to `Operations -> CLI access`, create a CLI key, and copy the token immediately. It is shown once only.
+Repository maintainers deploy/install the Forge app through the repository's controlled deployment workflow. That internal deployment process is separate from customer CLI onboarding.
 
-Export the webtrigger URL and the one-time token for CLI use:
+Export the installation endpoint and one-time token for CLI use:
 ```bash
-export TESTOPS_FORGE_ENDPOINT="<webtrigger-url>"
-export TESTOPS_FORGE_AUTH_TOKEN="<one-time-token-from-forge-ui>"
+export TESTOPS_FORGE_ENDPOINT="<endpoint-copied-from-jira>"
+export TESTOPS_FORGE_AUTH_TOKEN="<one-time-token-from-jira-cli-workspace>"
 export JIRA_BASE_URL="https://automatify-com-au.atlassian.net"
 export JIRA_PROJECT_KEY="DEV"
 ```
@@ -445,18 +458,19 @@ Or store the non-secret values in `.testops-cli.json`; on macOS the token is sto
 ```bash
 automatify testops config set baseUrl https://automatify-com-au.atlassian.net
 automatify testops config set projectKey DEV
-automatify testops config set forgeEndpoint "<webtrigger-url>"
+automatify testops config set forgeEndpoint "<endpoint-copied-from-jira>"
 printf "%s" "$TESTOPS_FORGE_AUTH_TOKEN" | automatify testops config set forgeAuthToken --stdin
 ```
 
 On Linux and CI, keep the token in environment variables. Windows users can use the same `config set forgeAuthToken --stdin` flow from PowerShell; see [WINDOWS.md](./WINDOWS.md).
 ```bash
-export TESTOPS_FORGE_AUTH_TOKEN="<one-time-token-from-forge-ui>"
+export TESTOPS_FORGE_AUTH_TOKEN="<one-time-token-from-jira-cli-workspace>"
 ```
 
 Transport notes:
 - Bearer auth is required for operator/CI use. Forge stores only the token hash plus metadata.
-- Tokens are project-scoped, shown once at creation time, and can be revoked from the Forge UI.
+- Tokens are project-scoped, shown once at creation time, and can be revoked from the Jira CLI workspace.
+- The endpoint is resolved by the Forge runtime for the current installation; customers do not configure a Forge-side endpoint variable.
 - Expired or revoked tokens are rejected by the transport.
 
 Scenario automation callback example:
@@ -545,6 +559,7 @@ Azure DevOps setup note:
 
 Core browse examples:
 ```bash
+automatify testops bdd scenarios list --project-key DEV --json
 automatify testops bdd scenarios show --project-key DEV --id <SCENARIO_ID> --json
 automatify testops bdd scenarios export --project-key DEV --id SC-4 --output-dir ./artifacts/scenario-export --json
 automatify testops bdd scenarios import --project-key DEV --file ./artifacts/scenario-export/SC-4.feature --json
@@ -570,6 +585,7 @@ automatify testops suites cases list --project-key DEV --key TS-1
 Recommended browse flow:
 ```bash
 # Path A: scenario-first browse
+automatify testops bdd scenarios list --project-key DEV --json
 automatify testops bdd scenarios show --project-key DEV --id <SCENARIO_ID> --json
 automatify testops runs show --project-key DEV --id <RUN_ID> --json
 
@@ -608,7 +624,7 @@ Feature export notes:
 - `bdd features export` writes one `.feature` file per stored BDD feature plus `manifest.json`.
 - with `--zip`, the CLI also writes `./artifacts/features-export.zip` next to the export directory.
 - pass `--issue-key DEV-2` to export only features visible in that Jira issue context.
-- `getSummaryExport` remains the reporting/export path for JSON/CSV summary snapshots and is separate from feature-file round-trip export.
+- `getSummaryExport` remains the reporting/export path for JSON/CSV summary snapshots and is separate from feature-file round-trip export/import.
 
 Coverage and readiness report via the Forge transport:
 ```bash