3 people bd4ec3a11c Address review: the server ends the resolution watch, and a reconnect re-participates ...

Two ways a page's word could go stale after the resolve-before-claim
change: an element that mounts later than the quick re-checks, and an
EventSource reconnect that did not overlap the old connection (the server
drops that page's word on the close, replays the target, and the replay
guard ignored it, so the roll call waited on a word that never came).

A decline's answer now carries pending, like a denied claim does, so a page
that could not resolve the target reports the miss after the quick
re-checks (the roll call can complete on the other overlays' words) and
keeps re-checking once a second for as long as the server says the request
is pending, claiming the moment the element mounts; the server drops the
stale report on an eligible claim and ends the watch by answering
pending:false once the request resolved or timed out. The overlay tracks
its participation per target: a replayed target is ignored only while this
page is acting on it, and is otherwise handled again, so a busy or
unresolvable page re-declines (idempotent) and an idle page claims.

Unit, protocol, and contract cases updated; the decline answers now say
whether the request is still pending.

AI-assisted: implemented and tested with Claude Code under maintainer
direction.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

2026-09-15 05:45:49 +05:00

..

src

CLI: --version reports the npm package version (#731)

2026-09-04 13:52:32 -07:00

tests

Address review: the server ends the resolution watch, and a reconnect re-participates

2026-09-15 05:45:49 +05:00

Cargo.toml

The Rust engine: one binary replaces every script and the JS detector, fully open (#714)

2026-09-04 10:42:45 -07:00