An update that arrived while a route was still loading was lost, since the
loader's result then counted as fresh, so the events now invalidate through
the shared helper that marks such fetches stale. A repo arriving or renamed
without the update naming its refs left the sidebar list as it was, and
updates that changed nothing still dropped the hover caches.
A test now checks the frontend's ref update type against the generated
one.
Reviews and writes with announcing off or the node stopped never reach the
node's events, so each write command now invalidates the data it changes,
also when it fails partway. Views that pin data join that refetch instead
of starting another.
The node announces the user's own writes, and those of the `rad` CLI,
without saying which refs changed, so each one refetched the whole repo,
including a scan of every CI job. Comparing the announced signed refs
with the previous ones names them. Releases and boards get keys of their
own instead of falling back to the whole repo.
Every status chip of a repository shares one list of its jobs, which
refreshes when a job changes, at most every few seconds, since listing
them scans every job of the repository.
Core holds the keys of the data both apps read and maps a node's ref
updates to the keys they affect. The query cache wraps TanStack Query for
runes, as decided in ADRs 4 and 5.