agent-desktop/tests/conformance

Adapter Reliability Conformance

Every platform adapter must satisfy the same ref/action contract. The macOS adapter is the first implementation, but the tests are written against PlatformAdapter semantics so Windows UIA and Linux AT-SPI can reuse the same expectations.

The reusable command-path helper lives in tests/conformance/ref_action_contract.rs. The executable smoke harness in src/tests/conformance.rs uses it with a mock adapter; future Windows and Linux fixtures can call the same helper with real adapter-provided refs.

Required Gates

Area	Required behavior
Snapshot refs	Refs are depth-first, snapshot-scoped, and explicit snapshot IDs resolve directly
Strict resolve	A ref resolves only when identity still matches; stale refs return STALE_REF
Ambiguity	Multiple plausible matches return AMBIGUOUS_TARGET, never an arbitrary click
Actionability	Ref actions check live visibility, stability, enabled state, supported action, policy, and editability before dispatch
Wait recovery	wait --element can poll the latest session refmap when no snapshot is pinned, honors the caller timeout while resolving, and reports the last observed predicate state
Session latest scope	Commands that omit --snapshot read and write only the active session's latest refmap
Explicit snapshot scope	Passing --snapshot <id> resolves that pinned snapshot even when the caller omits the original session
Trace	With a trace: on session manifest (from session start), commands write per-process JSONL segments under the session directory; --trace <path> overrides to one file. Best-effort unless --trace-strict.
Session lifecycle	session start/end/list/gc manage manifests, the current-session pointer, and trace directories
FFI parity	FFI ref actions use strict resolve and actionability checks before adapter dispatch

Platform Matrix

Fixture	macOS AX	Windows UIA	Linux AT-SPI
Two identical buttons produce ambiguity	Required	Required	Required
Ref disappears after snapshot	Required	Required	Required
Disabled button blocks click before dispatch	Required	Required	Required
Text field supports value/type actionability	Required	Required	Required
Session A latest refmap is invisible to Session B	Required	Required	Required
Batch item session overrides inherited session	Required	Required	Required
FFI AdRefEntry preserves full identity envelope	Required	Required	Required

Adding Windows or Linux

Add adapter-specific integration fixtures, but keep expected errors and JSON shapes identical. Prefer semantic platform actions first (AXPress, UIA Invoke/Value/Selection patterns, AT-SPI actions). Coordinate input is a lower confidence fallback and must remain explicit in policy or command choice.

Windows Private-Storage Runtime Gate

Windows support must not be enabled from cross-compilation evidence alone. A native Windows integration suite must continuously rename or replace every ancestor of the private state directory while open, bounded read, append, lock, and atomic replace operations run. Each operation must either access the intended handle-bound file or fail closed; it must never follow a reparse point or escape the guarded ancestor chain.

The same gate must verify owner-only protected DACL creation and rejection, hardlink rejection, local-versus-remote storage detection, drive and UNC verbatim path encoding beyond MAX_PATH, and atomic replacement durability. Static Windows target checks are required before this suite, but are not a substitute for the native race test.