swipium 1.5.0 → 2.0.1

package/CHANGELOG.md

@@ -2,6 +2,189 @@
 
 All notable public changes to Swipium are documented here.
 
+## 2.0.1 - 2026-09-30
+
+A small maintenance release. No behavior changes for agents or flows.
+
+### Fixed
+
+- SARIF exports (`qa_report format:"sarif"`) link the tool to the real repository, `https://github.com/GeroPalombo/swipium`. The old link pointed at a GitHub account that doesn't exist, which code-scanning pages show to users.
+
+### Changed
+
+- Test fixtures no longer contain paths from a developer's machine.
+
+## 2.0.0 - 2026-09-30
+
+Swipium 2.0.0 fixes the typing, gesture, and secret-handling defects in the core test loop, makes iOS Simulator sessions and background jobs more reliable, adds CI report exports and one visual tool, and narrows the public surface from 60 to 55 tools (6 removed, `qa_visual` added). **It removes and renames public tools and tightens several defaults.** Work through the upgrade checklist before upgrading.
+
+### Upgrade checklist
+
+Items tagged **You** need an action from you. Items tagged **Automatic** happen on their own and are listed so they don't surprise you.
+
+1. **You:** restart your MCP client (or reload its server list) after upgrading. A client still holding the 1.5.x tool list gets `STALE_CLIENT` errors that name the replacement call.
+2. **You:** rename the environment variables your flows and `.swipium/fixtures.json` read through `${VAR}` so they start with `SWIPIUM_`. Other names no longer resolve from the server environment. See [README.md](README.md#configuration--environment-variables).
+3. **You:** in CI, install the app yourself (for example `adb install -r -g app.apk`) before the agent step. Every Swipium install now asks for consent, and nobody can approve it in CI. [docs/ci-reports.md](docs/ci-reports.md#github-actions-recipe-android) has a complete recipe.
+4. **You:** replace calls to removed tools using the [migration table](#migrating-from-150), and remove arguments a tool does not declare. They are now rejected with `INVALID_ARGUMENT` instead of being ignored.
+5. **You:** if you use a remote (non-loopback) WebDriverAgent, `ios.wda.allowNonLoopbackUrls` in `.swipium/config.json` no longer pre-approves it. Pass `allowNonLoopback: true` and approve the consent prompt, or set `SWIPIUM_ALLOW_REMOTE_WDA` to the exact URL in the MCP server environment.
+6. **You:** scripts that call `swipium <word>` with a word that is not a subcommand now exit with status `2` instead of starting a server. Use `swipium` or `swipium serve`.
+7. **You:** stop any Metro bundler or WebDriverAgent that a 1.5.x server started and left running. 2.0 only cleans up processes it recorded with a start-time and command fingerprint, and 1.5.x recorded none.
+8. **Automatic:** when a call has no `projectRoot`, no MCP roots, and no `SWIPIUM_PROJECT_ROOT` or `CLAUDE_PROJECT_DIR`, the server's working directory becomes the project root if it contains a project marker (see Breaking changes).
+9. **Automatic:** old session folders under `~/.swipium/runs` are pruned (see Added). Set `SWIPIUM_RETENTION_DAYS=off` to keep them.
+
+### Breaking changes
+
+- **Removed and renamed tools.** See the migration table below (also at the end of `docs/tools.md`). A client still running a pre-upgrade server, or a saved prompt that calls a removed tool, gets a typed `STALE_CLIENT` error that names the replacement.
+- **Environment variables in flows and fixtures.** Flows and `.swipium/fixtures.json` resolve `${VAR}` from the server environment only for names starting with `SWIPIUM_`. Explicit `variables` and inputs stored in the session still work. Generated flows and suites use `SWIPIUM_TEST_*` for stored inputs and `SWIPIUM_SECRET_N` for other secrets. `swipium init flows` templates use `SWIPIUM_TEST_EMAIL`, `SWIPIUM_TEST_PASSWORD` and `SWIPIUM_TEST_DEEP_LINK` (was `TEST_DEEP_LINK`). Rename any other variables your flows read from the environment.
+- **Every app install asks for consent**, including an APK inside the project (Android now matches iOS). Only an app already installed on a running emulator skips the prompt.
+- **Unknown tool arguments are rejected** with `INVALID_ARGUMENT`, which lists the accepted parameters, and nothing runs. They used to be ignored silently, so a call such as `qa_app_control {appId:"other.app"}` ran against the session's app.
+- **Remote WebDriverAgent.** A repository config can no longer pre-approve a non-loopback WDA: `ios.wda.allowNonLoopbackUrls` is ignored as an approval. Use `allowNonLoopback: true` with consent, or the user-level `SWIPIUM_ALLOW_REMOTE_WDA`.
+- **Project root from the server's working directory.** 1.5.0 never used the working directory: without `projectRoot` or MCP roots it asked for a path. 2.0 falls back to `SWIPIUM_PROJECT_ROOT`, then `CLAUDE_PROJECT_DIR`, then the working directory when it is not `/` or `$HOME` and contains a project marker. A server launched inside an app directory now works in that directory without asking. The result's `rootSource` says which one was used.
+- **Physical devices.** A single USB phone is no longer bound automatically, and `preferRealDevice: true` or an iOS build that installs only on real hardware returns `PHYSICAL_DEVICE_UNSUPPORTED` (was `BACKEND_UNSUPPORTED`). `qa_resolve_target` no longer plans a real device. See [docs/physical-devices.md](docs/physical-devices.md).
+- **Consent risk of source builds.** `build_from_source` is `high` risk (was `medium`), and `start_metro` is `medium` (was `low`). Prompts and the mutation ledger show the new level, and an executed high-risk build lowers the report's readiness score.
+- **CLI:** an unknown subcommand prints usage and exits `2` instead of starting the server. Unknown `--flags` (such as `--stdio`) still start the server, with a warning.
+
+### Migrating from 1.5.0
+
+| 1.5.0 call | Now |
+| --- | --- |
+| `qa_agent_brief`, `qa_capabilities` | Server `instructions` (sent at connect), or `qa_status` without `sessionId` |
+| `qa_next_best_action {sessionId, goal}` | `qa_status {sessionId, goal}` (always returns `nextBestAction`) |
+| `qa_detect_context` | `qa_resolve_target {include:["context"]}` |
+| `qa_plan {sessionId}` | `qa_resolve_target {sessionId, include:["plan"]}` |
+| `qa_assert_visual` | `qa_visual {mode:"assert", assertion, pass}` |
+| `qa_ios action:"wda_status"` / `"wda_attach"` | `qa_wda action:"status"` / `"attach"` |
+| `qa_ios action:"screenshot"` | `qa_screenshot` |
+| `qa_wait {for:"job_done"}` | `qa_job_status {jobId, waitMs}` |
+| `qa_wda {udid}` | `qa_wda {device}` (`udid` still accepted) |
+| `qa_suite_generate {creativityLevel}` | `qa_suite_generate {creativity}` (`creativityLevel` still accepted) |
+| `qa_mobile_audit {waitForCompletion}` | removed; passing it returns `INVALID_ARGUMENT` |
+
+### Added
+
+- `qa_visual`: one screenshot-based tool with `mode:"assert"|"baseline"|"diff"|"find_text"|"find_image"`. Because it needs only screenshots, it also works on an iOS Simulator without WebDriverAgent, where `qa_snapshot` and `qa_act` are unavailable. `find_text` and `find_image` return tappable device coordinates (points on iOS) and can tap them (`tap:true`, through `idb` on a simulator without WebDriverAgent). Those taps are recorded and budgeted like `qa_act` taps. `find_text` is consent-gated and needs a local OCR command (`SWIPIUM_OCR_CMD` or `ocrCommand` in `.swipium/config.json`). Without one it returns `OCR_NOT_CONFIGURED` with the provider contract and a tesseract example.
+- `qa_issue_log` lifecycle: `mode:"history"` (default, the 1.5.0 behavior), `"log"`, `"mark_fixed"` (`fixedInCommit`, `fixedInVersion`, `howFixed`), `"verify_fixed"` (`evidenceUris`), `"suppress"` (`suppressionScope`, a `suppressedUntil` expiry, and `unsuppress:true`), and `"metrics"` (`groupBy`). A manually logged issue is identified by its title, category and platform, and a title with no identifying words returns `ISSUE_LOG_TOO_VAGUE`. Lifecycle errors are typed: `ISSUE_NOT_FOUND`, `ISSUE_STATE_INVALID`, `ISSUE_EVIDENCE_REQUIRED`. An issue marked fixed and seen again is classified as a regression.
+- CI exports: `qa_report format:"junit"|"sarif"|"github-summary"`, and a `swipium report` CLI (`--latest --format … --out … --fail-on-gate`) that renders the last saved report and exits `1` when the `.swipium/policy.json` release gate blocks. SARIF results point at real repository files so GitHub code scanning shows them. `docs/ci-reports.md` has a complete GitHub Actions recipe (Android emulator, headless Claude Code, report, SARIF upload, JUnit).
+- `qa_act observe:"diff"|"full"|"none"`, and `warnings[]` in `qa_act` results.
+- `qa_job_status waitMs` long-polls until the job leaves `running` (up to 120 s). `qa_status` accepts `goal` to bias `nextBestAction`.
+- `qa_test_this`: `responseMode`, and a compact report summary in the terminal result.
+- `qa_explain_blocker` accepts `sessionId`, so `qa_status` moves past the blocker it explained.
+- `qa_app_control` results carry `changedState`, which is `false` when the call failed before changing anything.
+- MCP tool annotations on every tool. Read-only tools carry `readOnlyHint: true` and `openWorldHint: false`; every other tool also sets `destructiveHint` and `idempotentHint`. Clients can use them to auto-approve read-only calls. The server also sends `instructions` with the operating guide.
+- MCP resource listing for session artifacts and app-map sections, scoped to the current project and excluding sensitive-mode sessions.
+- Consent through MCP elicitation: on clients that support it, privileged actions are approved in a real user prompt. A declined prompt returns `CONSENT_DECLINED`, and the mutation ledger records how each action was approved (`elicitation`, `client-assertion`, or `policy`). `SWIPIUM_REQUIRE_ELICITATION=1` refuses every consent-gated action on clients without elicitation (`CONSENT_REFUSED`).
+- CLI: `swipium --help`, `--version`, `swipium serve`, `swipium init cursor`, `swipium init vscode`, and `init --cwd <dir>`.
+- Disk retention: when the session registry is first loaded, Swipium prunes, in the background, `~/.swipium/runs` session folders older than 30 days that are not in the session registry and are not among the newest 20 of their project. `SWIPIUM_RETENTION_DAYS=0|off` disables the prune, and `SWIPIUM_RETENTION_KEEP` sets how many recent sessions per project are kept. If `~/.swipium/registry.json` cannot be read, nothing is deleted. `swipium gc [--dry-run] [--days N] [--keep N]` reclaims space on demand, and `~/.swipium/projects.json` drops entries for deleted projects.
+- `qa_device_info` on iOS Simulators returns name, runtime, state, and screen size. `qa_resolve_target include:["context"]` lists booted and available iOS Simulators.
+- `qa_wda build` and `start` find an Appium-installed WebDriverAgent project (under `$APPIUM_HOME`, `~/.appium`, or the global npm roots) when `wdaProjectPath` is not given.
+
+### Changed
+
+- Project root resolution: explicit `projectRoot` > MCP roots > `SWIPIUM_PROJECT_ROOT` > `CLAUDE_PROJECT_DIR` > the server's working directory, which is used only when it is not `/` or `$HOME` and contains a project marker (`package.json`, `app.json`, `pubspec.yaml`, Gradle or Xcode files, `Podfile`, `android/`, `ios/`). Results report where the root came from (`rootSource`). An unresolved root fails with `PROJECT_ROOT_UNRESOLVED`. `qa_flow_check` and `qa_flow_run mode:"plan"` resolve the root the same way. See [docs/concepts.md](docs/concepts.md#project-root).
+- **`qa_status`** without `sessionId` returns first-call orientation instead of an error. With a session, it follows the last job: after a finished run it recommends that run's next action (read the report, explain the blocker, answer the question) instead of `qa_smoke` again, and it stops repeating advice that was already followed.
+- **`qa_test_this`:**
+  - It never installs on a physical phone. With a phone connected it waits for the emulator it planned to boot; when a phone is the only option it returns `PHYSICAL_DEVICE_UNSUPPORTED`.
+  - `needs_input` is a terminal job state. A credentials question found during a run is returned instead of dropped.
+  - On iOS without WebDriverAgent it no longer blocks by default. It skips suite generation and exploration and runs a visual-only smoke. It still blocks when you explicitly ask for work that needs WebDriverAgent.
+- **Response format in normal mode:** the JSON block in the text channel is compact and omits keys the text above it already shows; `renderedAbove` lists the omitted keys (a 32-element `qa_snapshot` is under half its 1.5.0 size). `responseMode: "verbose"` restores every key, and `structuredContent` always carries the full payload. `qa_act` returns only the elements that changed once a snapshot exists (`observe:"diff"`), and falls back to the full list when most of the screen changed.
+- Consent challenges (`consentId`) expire after 30 minutes, and at most 200 are pending at once. See [docs/concepts.md](docs/concepts.md#consent).
+- An unknown `sessionId` returns `INVALID_ARGUMENT`.
+- `qa_prepare_target` with several devices online and no `device` returns `MULTIPLE_DEVICES`.
+- `qa_network` on an iOS Simulator returns `BACKEND_UNSUPPORTED` (airplane-mode control is Android-only). A toggle that fails on the device leaves no restore record behind.
+- Flow and fixture variables whose names contain `code` (such as `SWIPIUM_VERIFICATION_CODE`) are treated as secrets, like names containing `pass`, `secret`, `token`, `otp`, `pin`, `cvv` or `key`.
+- `swipium init` writes a portable `npx -y swipium` command for project-scoped registrations (shared `.mcp.json`, Gemini project settings, Cursor, VS Code). Absolute paths are used only for user or local scope. Codex registrations include `startup_timeout_sec = 30` and `tool_timeout_sec = 600`.
+- `adb` and `emulator` are found through `ANDROID_HOME`, `ANDROID_SDK_ROOT`, or the OS default SDK location when they are not on `PATH` (useful for GUI-launched clients). See [docs/mcp-server.md](docs/mcp-server.md#requirements).
+- `qa_doctor` checks both platforms by default on macOS, and checks the Node version against `engines`.
+- `qa_mobile_audit` `resilience` and `release_gate` profiles ask for network-change consent before toggling airplane mode, and restore its original state afterwards.
+- `qa_continue_from_blocker` returns `ignored[]` for answers the resumed tool cannot use, and replays the goal and flags of the interrupted `qa_test_this` call.
+- `qa_flow_repair` proposes elements of the same kind ranked by text similarity and refuses to apply low-confidence repairs. A failed `qa_flow_run` points to it.
+- `qa_report` merges identical findings into one with a count, and reports `DEGRADED` tool status when tools failed during the run. Cancelled calls, unknown sessions, invalid app IDs, and deliberate refusals do not count as tool errors.
+- `qa_generate` returns `NO_RECORDED_ACTIONS` for every target when the session has recorded no actions.
+- Errors that returned `UNKNOWN` now carry typed codes (`INVALID_ARGUMENT`, `FLOW_NOT_FOUND`, `KEYBOARD_NOT_DISMISSIBLE`, `CAPTURE_WITHHELD_SECURE`, `SENSITIVE_MODE_REFUSED`, `NO_DEVICE`, `CANCELLED`).
+- Fewer device round trips per action: adaptive settle interval, bounded screen-dump timeouts, a cheaper foreground and health check, longer-lived screen-size caches, and one keyboard lookup per action.
+
+### Fixed
+
+**Android**
+
+- Typing escapes every shell metacharacter (including `{ } [ ]`), types a literal `%s` correctly, and treats empty text as a no-op. Characters `adb input text` cannot deliver fail with `TEXT_INPUT_UNSUPPORTED`, and replace-mode typing refuses them before clearing the field.
+- Deep links and launch extras containing `&`, spaces, or `;` reach the app intact.
+- An emulator that is still booting is no longer bound automatically (`DEVICE_NOT_READY`). Network-attached emulators (such as `localhost:5555`) are accepted. A missing `adb` returns `ADB_NOT_FOUND`.
+- Snapshots skip rows Android reports as scrolled off the list or that lie off-screen, so `scroll untilVisible` no longer reports an off-screen row as found and taps no longer land on the list edge.
+- Apps whose package name contains `debug` or `alert` no longer show false banner or snackbar overlays.
+
+**Gestures and actions (both platforms)**
+
+- Swipe and scroll geometry comes from the live screen size, accounts for rotation, and keeps clear of screen edges. The old fixed 1080×2400 coordinates were off-screen on iOS.
+- Scrolls start inside the scrollable list rather than the screen center, a plain `scroll` performs one swipe, and `changed` also reflects content that moved. `scroll untilVisible` checks before the first swipe and reports `endOfList` only when the list stopped moving.
+- Tapping a control hidden under the soft keyboard no longer types into the field. When the keyboard covers the target, Swipium hides the keyboard, finds the target again, and returns `KEYBOARD_OBSTRUCTION` if it is still covered. When the keyboard area is unknown, it taps and returns a warning.
+- Tapping a switch or checkbox is detected as a change instead of being retried and toggled back.
+- Navigation bars, list rows, and text fields are no longer reported as banner or snackbar overlays. A password field's show/hide button keeps its label in snapshots; only secure values are masked.
+- Flow `clearOverlay` no longer presses BACK on a plain screen (which could leave the app). It dismisses dialogs, sheets, and dev overlays (iOS alerts through the alert API) and reports when there was nothing to clear.
+
+**iOS**
+
+- A resumed iOS session is rebound to its own simulator (through WebDriverAgent when it was attached), never to another device, and reuses the running app instead of relaunching it.
+- A managed WebDriverAgent started by a previous server run is adopted at startup when it is healthy and less than 12 hours old, so a resumed session keeps structured automation. It is recognized even though Xcode's `xcodebuild` shim re-executes under its full path, and `qa_wda stop` can stop it, including when its registry entry was lost.
+- Recovery from an expired WebDriverAgent session no longer relaunches or terminates the app, every WebDriverAgent call has a request timeout, and a brief outage while resuming no longer downgrades the session permanently.
+- A session that fell back to visual-only on one slow screen returns to structured mode once screen dumps work again. `qa_status` reports a simulator session without WebDriverAgent as `visual-only`.
+- `qa_ios launch` and `terminate` work while WebDriverAgent is attached. `qa_app_control background` waits for the home screen and reports the real foreground app, or `unknown` when WebDriverAgent cannot tell.
+- `press key:"back"` taps the navigation bar's back button or swipes from the left edge. It reuses the last settled screen dump only for 3 s, and never after the screen changed, so it does not press a back button that is no longer there.
+- Snapshots include accessibility identifiers and search and text fields, so typed values can be read back. Keyboard detection works through WebDriverAgent.
+- After `qa_ios boot`, next steps point at iOS tools, and target plans count simulators.
+
+**Sessions and jobs**
+
+- Cancelling one call no longer cancels another: each tool call and background job carries its own cancel signal. Cancelled calls and jobs return `CANCELLED` and are never recorded as tool errors or findings.
+- App-map and session state writes are atomic and locked. A stale lock is taken over safely (the lock can no longer spin forever and block startup), long app-map scans run outside the lock, and a corrupt `app-map.json` is restored from history.
+- Fixtures are reloaded from `.swipium/fixtures.json` on resume instead of being replayed as `«redacted»` after a restart.
+- Monorepos: answering the "which app?" question selects that app instead of being treated as a device ID, and the question is not asked again.
+- An orphaned Metro started through `npx` is cleaned up after a crash, including on Linux when it was recorded while its `#!/usr/bin/env node` launcher was still starting. A child process that exits before reading its stdin can no longer crash the server.
+
+**Generation**
+
+- Generated Appium suites perform real scroll and swipe gestures, and a scroll recorded without a target replays in the right direction. Steps that cannot be generated fail with `UNEMITTABLE_STEP` instead of producing no-op code.
+- Generated JavaScript suites contain no TypeScript-only syntax, and JavaScript and Python suites compile when element labels are keywords, start with digits, or contain quotes or backslashes. The Python generator passes its own validation.
+- Generated suites default to the session's platform (iOS sessions get XCUITest), and `qa_visual mode:"assert"` steps become marked manual checks.
+- Common-word passwords ("test", "password") no longer rewrite selectors or block generation on template text.
+- Suite files from `qa_test_this generateSuite:true` are fetchable `swipium://` artifacts.
+
+**Reports and issues**
+
+- JUnit exports are always well-formed XML, and failures the release-gate policy ignores are reported as skipped. GitHub step summaries stay below GitHub's 1 MiB limit.
+- The issue ledger is locked across processes, and issues recorded by 1.5.x keep their identity.
+- The documented tesseract OCR setup works: the provider runs from the project root, a crashing provider returns `OCR_PROVIDER_FAILED`, and screenshots are written where macOS tesseract can read them.
+
+**CLI**
+
+- `swipium scan` writes nothing when it cannot identify a project, and the docs and CLI no longer mention the nonexistent `swipium plan` and `swipium ci` commands.
+
+### Security
+
+- A consent prompt the user dismisses or leaves unanswered is a refusal (`CONSENT_CANCELLED`); the agent cannot approve that action itself, and an open prompt cannot be bypassed with `approve:true`. Consent prompts strip control characters and are bound to the session that requested them.
+- A cloned repository is treated as untrusted input. Flows and `.swipium/fixtures.json` cannot read server environment variables outside `SWIPIUM_*`, and values read from the environment are treated as secrets. An `openUrl` containing a variable is consent-gated. Consent shows the exact commands of flow seed steps and of repository-configured OCR and mask commands, labelled as unreviewed. A repository config can no longer pre-approve a non-loopback WebDriverAgent (the user can set `SWIPIUM_ALLOW_REMOTE_WDA` to allow specific URLs).
+- Secrets never appear in error messages: a failed `adb input text` no longer echoes the typed value, and `qa_act` and flow errors are redacted.
+- Values typed into secure fields (passwords, PINs, OTPs, CVVs) are redacted regardless of length with whole-token matching. JSON and XML artifacts are redacted structurally so they stay valid. Secrets shorter than 3 characters are reported as not redacted instead of blanking unrelated text, and a session resumed after a restart is flagged `redactionDegraded` in `qa_report`.
+- Report exports (JUnit, SARIF, GitHub summary, Markdown, JSON) are redacted field by field before rendering, so escaping cannot defeat redaction.
+- A value typed through a native selector into a secure field, or a registered secret typed into an ordinary field, is recorded as a secret (generated flows use `${SWIPIUM_TEST_PASSWORD}` instead of the plaintext), and every generator checks its output against the session's secrets: generation fails with `SECRET_IN_GENERATED_OUTPUT` and writes nothing rather than emit one. `state.json`, `test-suite.json`, and test cases no longer store secret values.
+- `qa_visual` baseline names and template paths are confined to the project (`VISUAL_PATH_REFUSED`), and artifact names cannot escape the session directory. On screens Swipium cannot inspect, OCR results that look like credentials are withheld.
+- Orphan-process cleanup only signals a process whose recorded start time and command still match, so a reused process ID can no longer be killed.
+- App IDs are validated and quoted for the device shell. Sensitive mode suppresses screenshots in flows and smoke runs. `qa_issue_log` redacts session secrets before writing the ledger. Session folders and files are private (`0700` / `0600`), and OCR temp files live in private per-call directories.
+- `THREAT_MODEL.md` documents the limits of the re-call consent convention and the stronger elicitation path.
+- GitHub Actions in this repository's workflows are pinned to commit SHAs. Production dependencies are updated for advisories in transitive MCP SDK dependencies (`fast-uri`, `hono`, `@hono/node-server`, `body-parser`).
+
+### Known issues
+
+- The first time an iOS session from a pre-2.0 WebDriverAgent run is rebound after upgrading, the app may be relaunched once.
+- Stale-client hints (`STALE_CLIENT` for removed tools) depend on an internal of the MCP SDK. If a future SDK changes it, Swipium logs a warning and those calls get the SDK's plain "tool not found" error instead.
+- Fixtures passed inline to `qa_start_session` come back without their values after a server restart. Fixtures in `.swipium/fixtures.json` are reloaded.
+- On slow emulators a tap that navigates to a new screen can take several seconds, most of it spent on screen dumps.
+
+### Removed
+
+- The tools listed in the migration table.
+- Unregistered pre-1.5.0 tool modules that still shipped in `dist/`. `qa_seed`, `qa_permissions`, `qa_screen_info`, and `qa_locator_suggest` moved to `src/tools/deferred/`, which is excluded from the build and the npm package.
+
 ## 1.5.0 - 2026-07-03
 
 Swipium 1.5.0 is the production consolidation release. It narrows the MCP surface from 95 to 60 public tools, keeps the main simulator QA workflows, and moves lower-level/internal helpers out of the public contract so agents have fewer overlapping choices.