The profile page reloaded its route after every write and only noticed
edits from other devices on navigation. Now writes and the node's
updates refetch the actor in place, like the rest of the cache.
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.
The repo list had its own TTL cache, a counter bumped by seeding and a
listener of its own, and release counts were fetched separately by the
sidebar and the releases page. Now they're queries like the rest, and
seeding invalidates the list like any other write. The head a loader
resolved is marked through `markLoading` too, so it needs no key of its
own.
Releases were the one COB with keys of their own that nothing listened
on: the release list, a release and the sidebar count now refresh when a
release changes, and the user's own release writes refresh them too.
The backend now tells the frontend whenever the notifications database
changes, which covers notifications the node writes as it fetches as well
as clears by another instance of the app or the `rad` CLI, which have no
node event. The inbox reloads in place, keeping the rows in view where
they are.
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.
The backend forwards the node's ref updates, and the cache refetches what
they affect while it is shown. Issues, patches, their lists, the repo's
counts and the notification count update in place, and without the node's
events they refetch on window focus. An issue's description stays as it is
until the user asks for the latest.
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.