Desktop app: duplicate stale "Commit changes" chips persist after clean tree, session deletion, and app restart

Environment

• Claude Code desktop app on Windows 11 Enterprise (10.0.26200)
• Git repo on a GitHub Enterprise remote

Bug
The project/session list shows TWO identical "Commit changes" chips for the same project + branch, both reading +1,788 −419. That diff corresponds to a change set that was committed and pushed earlier — the working tree is verifiably clean.

Verified via git

• git status: clean, branch in sync with origin
• git stash list: empty
• No other sessions open on the project

The chips persist after:

1. Committing + pushing everything (tree clean)
2. Deleting all other sessions for the project
3. Fully restarting the desktop app

Expected: chips disappear once the working tree has no uncommitted changes, and one chip per change set, not duplicates.

Context that may matter for repro: the session history involved multiple concurrent sessions on the same repo, several branch switches (test ↔ master) including an app-created stash ("Stashing uncommitted changes before performing a checkout"), a large merge, and commits made both from sessions and externally (IDE/terminal). The stale chip values match the pre-commit diff, suggesting the chip state is cached per snapshot and never invalidated against live git status.