[abrichr]

Bug 18 from the second-installation work (#1548).

Problem

qualify refused Medplum's save with "save step has no structural selector". The web fault driver, and the qualification precondition in front of it, required a CSS selector for the save control. The recorder captures a selector only for a unique #id, and a React app such as Medplum seldom gives its save button one. The recorder keeps the button's ARIA role and accessible name instead, and the backend's resolver already finds an element by those.

Change

• WebFaultDriver._save_target accepts a role and a name when the locator has no selector.
  • The role and name must find exactly one element.
  • No match, or several matches (in one frame or across frames), means there is no target, and the fault declines. It never falls through to a looser match.
  • The selector path is unchanged.
• check_ready accepts a selector, or a role plus a name. A role alone is still refused, and the message says "structural locator".

Tests

tests/test_fault_driver_role_name.py:

• The precondition accepts a role plus a name, and refuses a role alone.
• In a real Chromium form, the driver finds the one "Create" button, and finds nothing with no Create button or with two.

Run locally: the qualification and fault selection (986 passed, 6 skipped), plus ruff, ruff format, mypy and strict mypy.

🤖 Generated with Claude Code

[abrichr]

AI review (coordinator): approved. Qualification only: the web fault driver and the precondition accept a role and name locator that resolves to exactly one element (get_by_role with exact=True), and decline on none or several, so a fault is never injected against an ambiguous target. No replay or save path changes. Auto-merge stays on.