Teknium 28cc6599df test: pin cua-driver resolver in CLI-fallback sanitization test ... The test passed on dev boxes where a cua-driver binary is on PATH but failed in hermetic CI: _call_tool_via_cli hit resolve_cua_driver_cmd()'s install-hint early exit before reaching the spawn-env assertion. Pin the resolver so the test exercises the code path it actually asserts.		2026-07-29 11:35:33 -07:00
..
test_cua_atexit_teardown.py	fix(computer_use): stop the cua-driver child on exit	2026-07-26 03:38:23 -05:00
test_cua_cli_fallback_env.py	fix: resolve cua-driver across computer-use surfaces	2026-07-23 00:42:46 -05:00
test_cua_no_overlay.py	fix(computer_use): default --no-overlay on macOS for idle CPU	2026-07-23 00:45:26 -05:00
test_cua_perf_knobs.py	perf(computer_use): cap capture size and cache vision routing	2026-07-23 00:52:43 -05:00
test_cua_spawn_env_sanitization.py	test: pin cua-driver resolver in CLI-fallback sanitization test	2026-07-29 11:35:33 -07:00
test_cua_telemetry.py
test_cua_wsl_manifest_path.py	fix(computer-use): normalize Windows manifest paths in WSL	2026-07-29 11:35:33 -07:00
test_doctor.py	fix(computer_use): surface CLI --version when health_report version lies	2026-07-29 11:09:08 -07:00
test_permissions_resolution.py	fix: resolve cua-driver across computer-use surfaces	2026-07-23 00:42:46 -05:00