The row stored the change key before its refresh callback ran, and the callback
skipped while the first comparison was still loading. An edit landing during that
load was marked handled, so the row kept the stale totals once the load settled.
Each comparison now remembers the change key it was last fetched against: the first
look relies on the query's own mount revalidation, a later key waits for any
in-flight fetch to settle and then refreshes, and a remount refreshes only when the
workspace changed while the row was unmounted.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>