GL 18 pre-release testing

[d13]

• Report issues in this checklist
• Graph Details Empty WIP Rebase Action - more gap needed between the two rebase option buttons (Rebase/Merge) and Merge should be text, not icon. Also, Rebase action should have an icon on the left like the others (verify all actions have an icon on left) Ramin completed it
• Graph Details Empty WIP Launchpad - Spacing is not good when items are present and sometimes does not match Launchpad icon state in status bar (Unable to load items vs. You are all caught up) Keith working on it
• Graph Details Empty WIP Start Work - Use agent version when AI enabled Keith working on it
• Graph Details Amend commit - Button shows fully clickable, but no-ops on click when the commit message section is cleared. Needs to be disabled like its non-amend version.
• Graph Details commit button - Both commit and amend commit need hover tooltips when disabled explaining what the user needs to provide for them to work
• Scoped graph on old branches doesn't show any commits PR Ian working on it
• It would be nice to show a folder name for folders that are not a repository (Sergei is working on it):
  

[d13]

Feedback from @IvanCorton:

• [CRITICAL — @eamodio NOT CRITICAL, and not for this release] PR does not auto-link to the origin issue
  After starting work on issue [request] Provide some debug info when things fail #2 via "Start Work on an Issue", running the agent, composing, publishing and creating the PR, the PR body has no Closes #2 and the PR's GraphQL closingIssuesReferences returns []. Merge won't close the issue. GitLens already knows the issue context (it shows the [request] Provide some debug info when things fail #2 badge in the working changes panel) but doesn't propagate it.

• [HIGH] Agents tab stays empty after running an agent
  The Agents tab seems intended to track agent activity, but it shows "No items"
  even right after running Claude Code via Start Work in an Agent. Could be by
  design (reserved for remote/async agents only?), but right now an in-IDE agent
  spawned from GitLens does not appear there. Cannot repro - Keith, Sergei

• [MEDIUM — @eamodio not for this release] Composer omits issue reference in the commit message
  Generated commit: feat: make counter step configurable. No body, no (#2), no
  Closes #2. Independent from the critical bug above: GitHub's PR-side Linked
  Issues surface is computed from PR title and body, not from commit messages, so
  fixing this alone wouldn't repair the PR auto-link (commit-level closing keywords
  only kick in once they land on main, and even that depends on merge strategy).
  This is more about the git log trail and cross-layer consistency: git log
  won't show any reference to issue [request] Provide some debug info when things fail #2 either. Too complex to fit in this release, requires deep thought/consideration - Ramin

• [MEDIUM] Cold-start: first Compose click in a fresh Composer panel does nothing
  Opening the Composer for the first time on a new repo, hitting Compose, going
  through the provider/model/consent pickers, then Compose again silently no-ops:
  UI returns to the previous state, no error, no commit. Closing and reopening the
  Composer panel fully resets the state and from there Compose works as expected.
  Looks like a state-init bug on cold-start of the panel. Cannot repro - asked for more info - Ramin

• [MEDIUM] Blue bar in the Composer has no tooltip or onboarding hint
  The blue bar between unstaged changes and the existing commits is the control
  that sets the rewrite target for the Compose. Dragging it onto the root commit
  triggers "Cannot rewrite commit X — it has no parent (root commit). Rewriting
  the root commit is not currently supported." The error UX itself is fine (clear
  message, Go Back / Retry), but the bar has no tooltip and no onboarding hint
  despite being the most powerful control in the panel. New users can easily
  trigger history rewrites in shared branches without understanding the bar is
  what they're acting on. Ramin completed this

• [LOW] SHA mismatch in the base branch picker
  When choosing the base for a new branch, the picker lists main :left_right_arrow: origin/main
  with SHA 853256f, then origin/main remote branch with SHA 0bec1d5. Same
  branch, two different SHAs visible. Display glitch. @IvanCorton main and origin/main are different branches which could easily have different SHAs — were you seeing something else?