qa-targets

QA targets

Browser QA runs against a target: local (the Docker env orc-env-provisioner boots) or a remote URL such as staging or a preview deploy. Targets live in <repo>/.orc/targets.json (gitignored, repo-level — not per branch), managed by orc-targets (plugin bin/, on PATH while orc is enabled).

Announce at start: "I'm using the qa-targets skill to resolve where browser QA runs."

Registry shape

{ "schema": 1, "targets": {
  "local":   { "kind": "local",  "baseUrl": null, "healthPath": "/", "guard": false, "users": {}, "login": null },
  "staging": { "kind": "remote", "baseUrl": "https://staging.example.com", "healthPath": "/healthz", "guard": true,
               "users": { "admin": { "username": "env:STAGING_ADMIN_USER", "password": "op://Eng/staging-admin/password" } },
               "login": { "path": "/login", "usernameField": "Email", "passwordField": "Password", "submit": "Sign in", "successPath": "/dashboard" } } } }

• kind — local is provisioned by orc:browser-qa Step 0 (today's path, unchanged); remote is probed, never provisioned.
• guard: true — a shared environment. The planner is told to tag mutating scenarios @mutating; on a guarded target those run as skipped with note guarded target — never silently dropped, never executed.
• users.<name>.{username,password} — references, not values: a literal, op://vault/item/field (1Password CLI, op read), or env:VAR. orc-targets resolve <name> substitutes them at run time and prints JSON for ORC_TARGET_JSON; the resolved JSON is never written to disk. Unresolvable ⇒ exit 3 ⇒ an escalation, not a skip.
• login — the recipe tests/auth.setup.ts follows once per run in the video-off setup project; the session is saved as storageState and reused by every scenario. Field hints match by label or placeholder text.

Resolution order (every caller, same order)

1. --target <name> flag → use it silently (orc-state decision set target <name> --provenance flag).
2. --web <url> flag (kept for compatibility) → an ad-hoc remote target: orc-targets resolve local --base-url <url>; recorded as target=adhoc:<url>.
3. A settled target decision in the session → reuse silently; re-runs keep it.
4. Otherwise the Target gate below. guided/full autopilot: local (policy decision, printed one-liner) — a remote target is a judgment call and is never auto-picked.