Source Control panel shows "no Git repository" despite git extension successfully detecting repo

The Source Control panel displays "The folder currently open doesn't have a Git repository" and offers to initialize one, even though the Git Output log confirms the repository was successfully opened.

Git Output log shows:

[Model][openRepository] Opened repository (path): d:\Development\AWS.Integration
[Model][doInitialScan] Initial repository scan completed - repositories (1)
All git commands (status, fetch, diff, for-each-ref) execute successfully
Troubleshooting steps attempted:

Confirmed .git directory exists and is valid
Set git.path to C:\Program Files\Git\cmd\git.exe
Enabled git.autoRepositoryDetection
Removed hidden attribute from .git directory
Removed core.worktree from git config
Removed git.scanRepositories (warned about absolute paths not supported)
Multiple window reloads
Environment:

OS: Windows
Git: 2.53.0.windows.3
Repo hosted on Azure DevOps
Azure Repos extension installed
Repo has many branch entries in .git/config (~60+)
The git extension backend works correctly (all commands succeed from terminal). Only the Source Control panel UI fails to render the repository view.

Start by reproducing the issue in the Source Control panel on Windows with the repository and environment described, then compare the panel state with the Git Output log showing a successful repository scan. Trace where the Git extension's opened repository is passed to the Source Control UI. Done means the repository view renders instead of offering initialization while Git commands continue to succeed.

Written by the indexing model from the issue text.