3 Commits

Include renames

Author	SHA1	Message	Date
pj	6d03c5788a	fix(chrome): emit data-testid so both resolvers name the same element ... The V8 host names a web target by data-testid and TapSelector translates that selector into a CSS attribute match, but the dump carried no such attribute and no alias could supply one, since an alias only redirects to a key that already holds the value. tree.Find was therefore always nil for exactly the selectors examples/folio-web tags with. Claude-Session: https://claude.ai/code/session_01A5KmftdEJ49A9z5mF5ESrX	2026-08-15 13:59:17 +05:30
pj	8a98915118	test(chrome): drive the live-page parity test through both selector forms	2026-08-13 00:41:23 +05:30
pj	c77b78d63b	test(chrome): compare both selector matchers over one live page ... Selector matching is written once per runtime: internal/hierarchy over the dump, web-runtime.ts over the DOM. Nothing made the two agree, and a selector that resolves on one and not the other is silent, since an empty match yields no action and the run still passes.	2026-08-13 00:28:16 +05:30