The fleet view keeps your selected tab and cached statuses across a remount.
What's wrong with this entry?
All of the fleet view's state now lives in a single host object built by a new factory, which callers can create once and pass back in. That lets the selected tab, cached job statuses, worktrees and the set of already-reported results survive a remount instead of being rebuilt.
- The host holds jobs, earlier entries, loop kicks, statuses and their timestamps, PR statuses, the active tab (defaulting to "local"), remote jobs, child repos, repo worktrees, templates, skills, routines, and a block tracking which results have already been seen.
- Both fleet view entry points now use a caller-supplied host if given, otherwise build a fresh one.
createFleetViewHost
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Background task notifications arrive inside a system-reminder
Both mention background task
-
v2.1.235
Several finished background tasks now report as one line
Both mention background task
-
v2.1.236
Background-task notices no longer look like user approval
Both mention background task