Desktop app 'Resume Session' finds no sessions after app repair, while CLI `claude --resume` finds all of them

Environment: Windows 11, Claude Desktop, Claude Code CLI bundled in app 2.1.247 (standalone CLI 2.1.50)

What happened:
The Claude Desktop app was crashing repeatedly during normal use. I went into Windows Settings > Apps and ran a repair on the app. After restarting, the app ran through first-time setup again and I logged back into my account.

Observation:
AppData\Roaming\Claude was recreated as a fresh profile (confirmed via file creation timestamps — all files/folders dated to the moment of the repair). As a result, the app no longer had any record of my previous projects or sessions.

However, ~/.claude/projects/ on disk still contained all 32 of my previous session transcripts, fully intact (tens of MB of conversation history, spanning several weeks).

Bug:
In the Desktop app, "Claude Code" mode → typing /resume (or opening the "Resume Session" / "Reprendre une session" dialog, even with "All folders" selected) shows:

"No Claude Code session found on this computer" ("Aucune session Claude Code trouvée sur cet ordinateur")

Meanwhile, running claude --resume in PowerShell/CMD in the exact same directory correctly finds and lists all 32 sessions, with correct titles, timestamps, sizes, and folders.

Expected behavior:
The Desktop app's Claude Code resume feature should be able to find and list existing sessions from ~/.claude/projects/, the same way the standalone CLI does via claude --resume, rather than relying on a separate internal index that resets to empty whenever the app's own profile folder (AppData\Roaming\Claude) is recreated (e.g. after a repair/reinstall).

Impact:
A user can reasonably believe all their conversation history has been permanently lost after a routine app repair, when in fact the data is fully intact on disk. This is confusing and alarming, and shouldn't require dropping down to the CLI to discover that nothing was actually lost.