Switching a branch makes the build out of date, which moves the card out
of "Up to date" and somewhere else entirely on a list of ten. The list
now scrolls to it -- only when it is actually off screen, since moving
something the reader can already see is a jump nobody asked for. The two
frames before reading the position are load-bearing: the entry has just
been applied, so the first frame carries the composition and the second
reports the layout it produced, and reading sooner gives where the card
was.
The other half is why a switched branch showed no commits and no Pull.
The build machine drops what it knew about that checkout's remote and
asks again, but the answer lands after the response -- and startCheckout
read the entry exactly once, so the card kept a pending check for ever.
It waits on awaitCheck now, the same poll the card's own Refresh uses.
Reproduced against a clone of ai-app before changing anything:
immediately after the move newCommits false with checkPending true,
three seconds later newCommits true, and nothing asking again in
between.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
irisandClaude Opus 5
07639ed14d