Publishing a review was the only patch write that didn't announce, so
other instances of the app on the same node never learned of it. A
review's summary now also stays as it is while someone else edits it,
showing that a newer one is available, as an issue's description does.
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 port lists, creates and renames boards, edits their columns, and
applies a batch of card moves and removals as one op, so a burst of
changes costs one update of the signed refs. Changes the board would
ignore are refused before writing and reported back, and boards are only
written on the test network or in private repositories for now.
Co-authored-by: Rūdolfs Ošiņš <rudolfs@osins.org>