Change bar not rendering in source editor gutter — Xcode 27.0 (27A266a)

Summary:
The source control change bar no longer appears in the source editor gutter,
even though all relevant settings are enabled and the working copy is correctly
recognized. This is a regression from earlier Xcode versions.

Steps to Reproduce:

  1. Create a fresh test project that is fully independent of any existing codebase:
    mkdir /tmp/changebar-test && cd /tmp/changebar-test
    swift package init --type executable --name ChangeBarTest
    git init && git add -A && git commit -m "init"
  2. Open Package.swift in Xcode 27.0.
    Confirm the branch name (e.g. main) is shown in the bottom status bar,
    which indicates the working copy is correctly established.
  3. Confirm Settings > Source Control > "Show source control changes" is checked.
  4. Open Sources/ChangeBarTest/ChangeBarTest.swift.
  5. Add a new line, e.g. print("test"), and save with Cmd-S.

Expected Results:
A change bar appears in the gutter next to the modified line (thin blue bar for
uncommitted local changes), as it did in previous Xcode versions.

Actual Results:
No change bar appears anywhere in the gutter. Hovering over the gutter region
produces no highlight and no popup.

Additional Evidence:

  • IDESourceControlShowChangeBar is set to 1 (verified via defaults read com.apple.dt.Xcode).
  • IDEEditorDefaultCodeReviewPreference is 0.
  • The Source Control navigator correctly lists the repository, the current branch,
    and three uncommitted commits, so SCM integration itself is functional.
  • Reproduces with a brand-new Swift Package (no CMake, no .gitignore, no
    third-party dependencies), so this is not project-specific.
  • Switching between built-in appearance presets (Default Dark, Dusk) does not help.
  • Toggling "Show source control changes" off and on, restarting Xcode, and
    clearing UserInterfaceState.xcuserstate do not help.
  • The Xcode 27 Release Notes contain no mention of change bar or gutter behavior
    changes, so this appears to be an undocumented regression.

Impact:
Developers lose the primary at-a-glance indication of which lines they have
modified before committing. Reviewing local changes now requires opening the
comparison editor or running git diff externally, which significantly slows
down the edit-review-commit loop.