Show each git fact once in the Info panel

[brsbl]

Human comments

What was wrong

The Info panel's Git status row mixed several facts into one label. "Dirty", "Untracked", "Clean", "Up to date", "Ahead", "Behind" and "Diverged" each answered two questions at once: are there uncommitted edits, and how does the branch compare to main. Two of those facts also showed elsewhere: ahead commits in Commits and uncommitted files in Changes. Changes also hid one of its two file lists behind an Uncommitted / Committed dropdown.

What changed

Each fact about the thread's code now appears once.

Fact	Where it shows
How the branch compares to its merge base	Git status: "Even with main", "6 ahead of main", "3 behind main", or "4 ahead, 2 behind main"
Commits on the branch	Commits
What those commits changed	Commits → Files changed: a subheading with a plain count after a dot ("Files changed · 32"), line totals, and the files
Edits not committed yet	Uncommitted files: its own section with count, line totals, and files
Workspace can't be read	Git status: a warning icon and the reason, e.g. "Workspace not found"

• Git status: shows only the branch comparison. The uncommitted icon and the state words are gone. It is hidden until the daemon reports a merge base. "Even with main" is GitHub's wording.
• Properties: one group: Parent, Project, Environment, Directory, Branch, Merge base, Git status, Pull request, Archived. Directory's value is muted. Dividers separate only the sections.
• Changes: the dropdown section is gone. Committed files sit under Commits, and uncommitted files have their own section. Each part is hidden when it has no files. Untracked-only files count as uncommitted.
• Mobile: on touch screens, list rows are one type step smaller than properties (13px vs 14px). Long commit subjects no longer outweigh the properties.
• Collapse ids: the synced infoPanel.collapsedSections preference uses uncommittedChanges in place of changes. The ids are documented in docs/configuration.md and the bb-cli settings reference. A collapsed Changes section shows Uncommitted files expanded once.
• Removed: the bucket dropdown (ChangedFilesBucketMenu, InfoMenuTrigger). The composer banner and commit dialog share getGitStatusDisplay, which is unchanged.

No API, CLI, SDK, or wire changes.

How you verified

Screenshots come from the branch web app (1440×900 and a 390×844 mobile view) and the right-panel/Info/Row/Git status Ladle story. Both revisions use the same fixture: a subthread 6 commits ahead of main with 32 committed files, captured with and without one uncommitted edit.

Before: df913a7 (merge base) · After: 6c9eb71 (PR head) · Captured at 2×

Screen / state	Viewport	Before	After
Info panel / one uncommitted file, 6 ahead	Desktop · 1440×900
Info panel / no uncommitted files, 6 ahead	Desktop · 1440×900
Info panel / one uncommitted file	Mobile · 390×844
Git status / every state (Ladle)	Story

• Tests cover formatBranchComparison for even, ahead, behind and diverged. They also check that the dirty-row render shows only the branch comparison, and that the comparison is empty when the daemon reports no merge base.
• CI runs remotely on the PR head. Tests, typecheck, and lint were not run locally.

QA: signed off by the user on the branch app.

Follow-ups (P2, not in this PR):

• Give Git status a hover title when its value is truncated.
• Add render tests for Commits → Files changed, Uncommitted files, and the warning fallback.
• On touch screens, list rows keep leading-5, so the 13px rows still use 20px line height. Drop the unused line-height override, or use the token's line height.
• If a branch has committed files but no commits, Commits shows "0" above an empty list. Render the commit list only when there are commits.
• Make the "Files changed" subheading a real heading for screen-reader navigation.

BB-Thread: Enhance info panel to thread navigation
BB-Thread-ID: thr_6ii952bx6f

AGENT GENERATED

🤖 Generated with Claude Code

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.