pj 48425e113f fix(hierarchy): bounds is a raw attribute, not a cross-platform key ...

Every native dump writes the rectangle out as a string under bounds, and
no DOM element carries an attribute of that name, so the key resolved
against the dump and matched nothing on web on every page there is. It
is accepted, so no unknown-key error said so, and no mapping can be
invented for it: there is no DOM fact to map it to.

Off the accepted list the web runtime raises the unknown-key error
instead of matching nothing in silence, and the key still resolves
wherever a producer writes it, through the escape hatch every other raw
attribute already uses: a key some element carries is a key that can
match, on both sides.

2026-08-19 10:13:52 +05:30

..

host-parity-golden.json

fix ltl semantics and unify action enumeration (#71)

2026-08-12 18:06:04 +05:30

parity-golden.json

fix(trace): an action names the generator that produced it

2026-08-18 17:58:38 +05:30

pcg-golden.json

UX refactor (#52)

2026-06-02 09:52:53 +05:30

selector-keys.json

fix(hierarchy): bounds is a raw attribute, not a cross-platform key

2026-08-19 10:13:52 +05:30