Three history sections rendered a centred CircularProgressIndicator
whenever their provider reloaded, replacing settled content mid-read.
Each sits in a scrolling detail page, so the swap collapses the
section's height and shifts everything below it — the same class of
jump as the task-detail work in #3585, from the opposite direction.

The reloads are routine, not rare: templateRecentReports,
soulVersionHistory and soulEvolutionSessionHistory all watch
agentUpdateStreamProvider, so any agent update re-runs them.

Note the distinction that decides this. AsyncValue.when already
defaults skipLoadingOnRefresh to true, so an explicit invalidate was
never the risky path; skipLoadingOnReload defaults to false, and a
reload is what a watched dependency changing produces. Only the second
flag changes behaviour here — the first is written alongside it for
symmetry.

The fourth site, templateVersionHistory, is guarded defensively rather
than fixed: it watches only a service, so nothing reloads it today. Its
soul-side twin does watch the update stream, which puts this section one
line away from the same bug, so the guard goes in now and says so.

Tests drive the update stream rather than calling invalidate, which is
what makes them fail without the fix. An earlier version used invalidate
and passed either way, as did a version that asserted after a single
pump — the first pump lets the reload propagate, the second lets the
widget rebuild, and asserting in between just reads the previous frame.
An empty-but-resolved list is enough to prove the point, since the
empty-state text would be replaced by the spinner just the same.

Addresses five further Codex findings on #3590, three of which are my
own errors from the previous revision.

Reverts the provider subscription changes entirely. Three reasons, in
order of severity:

The premise was wrong. I claimed a soul id never appears in a
notification set. It does — soul entities carry `agentId: soulId`
(soul_version_ops.dart, soul_evolution_workflow.dart), so both
persistedStateChangedNotifier and the sync handler already land the
soul's own id in the set. The two soul sections were correctly wired
all along, and their guards were live, not defensive.

The template edit landed in the wrong function. It matched the first
occurrence of the surrounding pattern, which is templateTokenUsage-
Records, not templateRecentReports — so the reports tab was never
actually resubscribed, and the token-usage tables gained a global
subscription nobody asked for. The tests did not catch it because their
overrides injected the dependency by hand, which is exactly the kind of
test that proves a wiring production does not have. They now watch the
id the real provider watches.

And the approach had blast radius I had not mapped: the same providers
back SoulEvolutionReviewPage and TemplateTokenUsageSection, whose `when`
calls still take the defaults, so a shared-topic subscription would
collapse those surfaces on unrelated agent activity — trading one jump
for two.

What remains is what this PR was scoped for: skipLoadingOnReload and
skipError on the four history sections. Both are still independently
load-bearing with the providers back at main — removing the first fails
three tests, the second one.

Also restores three CHANGELOG entries and four metainfo paragraphs that
a bad conflict resolution during the previous rebase dropped, and two
unrelated `skipLoadingOnReload` lines that a directory-wide sed deleted
from ai_summary_card and change_set_summary_card.

The README now documents the refresh reality rather than an aspiration:
soul sections reload on every soul write, the reports tab only on
template-scoped events, and template version history not at all. The
latter two are recorded as known gaps with the reason closing them is
not a one-liner.