[brsbl]

Human comments

What was wrong

The pull request row combined five independent facts into one colored label:

• lifecycle;
• checks;
• review;
• mergeability;
• merge automation.

That caused four problems:

• Checks appeared twice. Failing checks were a red ✗ badge and red "Checks failing" text.
• Some states had no label. Passing, missing and unknown checks showed nothing.
• "Blocked" was unexplained. It covered three different GitHub causes, one of which ("behind main") the Git status row also reports.
• Labels and colors mixed meanings. "Approved · Checks pending" combined review and checks. Amber meant both "waiting" and "good news" ("Auto-merge on", "Queued").

What changed

getPullRequestNextStep replaces getPullRequestAttentionDisplay.

• One next step: the row names the single next step, in the server's existing priority order:
  • Checks failing
  • Changes requested
  • Conflicts with main
  • Behind main / Blocked by rules / Blocked by hooks
  • Checks running
  • Review requested / Review required
  • Queued to merge
  • Ready to merge
  • otherwise the checks state (Checks passing / No checks / Checks unknown)
• Color only for action: red marks steps you must act on, and green marks the one positive step, "Ready to merge". Everything else is muted.
• Checks in one place: in the Info panel, checks appear only in the label; the GitHub icon no longer carries a badge. The composer banner keeps its badge because it has no room for a label.
• Checks icons: checks steps start with a state icon: ✓ passing, ✗ failing, a clock while running, an empty circle for no checks, and a question mark when unknown. "Checks running" shimmers.
• Auto-merge: when auto-merge is on, a small ⚡ icon appears instead of replacing the label.
• Same wording everywhere: the composer banner and the PR status pill tooltip use the same next step.

No API, CLI, SDK, or wire changes; the server's attention value is unchanged.

How you verified

The screenshots come from a local Ladle story that renders the production Branch, Merge base, Git status and Pull request rows, in light theme at 2×, with the same fixture for every state. The story is not part of this PR.

Before: f9a26ab (#5006, PR row unchanged at its head 6c9eb71) · After: 4919bdb (PR head) · Captured at 2×

PR state	Before	After
Open · ready to merge
Open · checks passing
Open · no checks
Open · checks unknown
Open · checks failing
Open · checks pending
Open · changes requested
Open · review requested
Open · conflicts
Open · blocked
Draft · checks passing
Draft · checks failing
Draft · no checks
Draft · checks unknown
Draft · checks pending
Draft · changes requested
Merged
Closed

• Tests:
  • getPullRequestNextStep covers every attention state, the three blocked causes, review required vs requested, merged and closed, and keeps auto-merge out of the label.
  • The composer banner test now expects the next step plus the auto-merge icon.
• QA: signed off by the user on the branch app.
• Follow-ups (P2, not in this PR):
  • Decide whether open PRs without CI should show "No checks" as their next step.
  • Hide the ⚡ icon in a squeezed composer banner.
  • Add a render test for the Info panel PR row.
• Remote CI: runs on the PR head. Tests, typecheck, and lint were not run locally.

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.