Semantic browser actions
Use short-lived accessibility references and mutation receipts instead of stale element assumptions.
Guides follow the current project source. Check the release notes for your installed version.
Short-lived refs
Semantic element references are bound to the current snapshot/session and are revalidated before a mutation.
- Sensitive targets are blocked
- Stale refs fail closed
- Sequence execution stops on failure
Ambiguous mutations
If transport is lost after a click/type may have been dispatched, RepoTunnel records an ambiguous outcome and observes current state instead of replaying the action.
Find and act on the live page
Short-lived semantic element references are tied to the browser session and document state. After a navigation, significant DOM change or failed action, inspect the page again and obtain a new reference instead of reusing an old one.
Sensitive input fields are protected. A failure to type a password or payment credential through the semantic path is intentional.
How to handle uncertain outcomes
A network or helper failure after dispatch may mean a click or type action already changed the remote site. RepoTunnel records a mutation receipt and returns an ambiguous status rather than replaying it.
Before repeating a state-changing action, inspect the current page URL, document generation, form values and any resulting confirmation. Retry only when you have evidence that it did not happen.
Never interpret ambiguous as failed. An automatic second click could place a duplicate order or submit a form twice.