v2.1.53

Commits

• f9fe86e release: 2.1.53
• 395c351 docs(T-10034): the ER entry goes under Unreleased with the T-10363 entry, not 2.1.52 (the rebase over the release placed it there)
• d8d83af docs(T-10034): the post-scroll wait and the settle are not bounded by the deadline, and their time shortens what the next resolution is handed (Codex round 7 LOW)
• 2c45e64 fix(T-10034): the fake decides JS-side branches by JS truthiness, and the deadline claim names only the shared resolution budget (Codex round 6 LOW, LOW)
• 78e8d15 fix(T-10034): the click scripts read the target only through native accessors, and connected() accepts only a literal true (Codex round 5 MED, LOW)
• b956258 docs(T-10034): the ER entry claims only what the code enforces; a page whose own isConnected getter clicks is the accepted boundary until T-10299 (Codex round 4 HIGH)
• d4904e1 fix(T-10034): the synthetic click answers with its own tokens, so a click() that throws false is never re-run (Codex re-review HIGH, LOW)
• 0c2a487 fix(T-10034): the synthetic click checks isConnected and clicks in ONE page-side call; its false is re-resolved, a failed call is never re-run (Codex review HIGH)
• 6db1b6f fix(T-10034): a node the page removed but still references is the element leaving, not a display:none target; re-resolved before any input, never clicked synthetically
• e27d93f fix(T-10034): the synthetic fallback and the re-run need ZERO input sent, recorded by click_target.InputSent; the re-runs spend one deadline (Codex review HIGH, MED)
• ae1ce91 fix(T-10034): an element the page replaced before any input is re-resolved and clicked once; one that leaves after input is never clicked twice; a listing drops a departed element without an ERROR (Sentry ER, EP)
• 3d931b8 fix(T-10363): an editable install reports Sentry environment=development; every other install passes production explicitly