fix(git): resolve PR badges for untracked prNNNN checkouts by number

[omegent-app]

Closes the last gap in the PR-badge chain: threads whose agents check out a PR with
git fetch origin <head-branch>:prNNNN — a renamed local branch, no upstream tracking.

The problem

The badge lookup finds a thread's PR by head selector: the local branch name, or the head branch
its tracking points to. A pr2182-style checkout has neither — the local name matches no PR's head,
and there is no tracking to derive the real one from. The thread reviewing PR pingdotgg#2182 was the live
case: gh pr list --head pr2182 correctly returns nothing, so the row showed no badge for the very
PR it existed to review. It only lit up after hand-setting branch.pr2182.merge on the worktree.

The fix

In findLatestPrForHeadContext, when the selector search finds nothing and the branch has no
tracking-derived head (headBranch === localBranch) and the name matches ^pr[-_]?\d+$, resolve
the PR by that number via the provider's existing getChangeRequest (gh pr view N /
glab mr show N — provider-neutral). A failed by-number lookup degrades to "no PR", exactly as
before.

The tracking gate matters: a tracked branch that happens to be named pr123 keeps the precise
selector path, so the number can never override a real head selector — covered by the negative test.

Tests

• status resolves the PR by number for an untracked prNNNN checkout — fails on the pre-fix
  implementation (verified by stashing the fix), passes after; also asserts the pr view 2182 call
  actually happened.
• status does not resolve by number once a prNNNN branch gains tracking — asserts pr view is
  never called and the row stays badge-less when the tracked head genuinely has no PR.
• Full GitManager.test.ts: 84 pass. Typecheck clean.

Retroactive by design: existing worktrees need no touch-up — the fallback keys off state the server
reads on every sweep.

Co-authored by @patroza

opened by Patrick Roza in chat thread Discord · Discord · T3

[patroza]

@omegent I would first question why agents setup branches like these without tracking, and see if we can address that

[omegent-app]

I’ve patched the status fallback to try to reattach the branch to the real PR head branch once the PR number is known. Next I’m adding a regression test that proves the branch stops being “untracked by design” after the first successful lookup.

gpt-5.4 · ↑52k ↓1.8k

[omegent-app]

Closes the last gap in the PR-badge chain: threads whose agents check out a PR with
git fetch origin <head-branch>:prNNNN — a renamed local branch, no upstream tracking.

The problem

The badge lookup finds a thread's PR by head selector: the local branch name, or the head branch
its tracking points to. A pr2182-style checkout has neither — the local name matches no PR's head,
and there is no tracking to derive the real one from. The thread reviewing PR pingdotgg#2182 was the live
case: gh pr list --head pr2182 correctly returns nothing, so the row showed no badge for the very
PR it existed to review. It only lit up after hand-setting branch.pr2182.merge on the worktree.

The fix

In findLatestPrForHeadContext, when the selector search finds nothing and the branch has no
tracking-derived head (headBranch === localBranch) and the name matches ^pr[-_]?\d+$, resolve
the PR by that number via the provider's existing getChangeRequest (gh pr view N /
glab mr show N — provider-neutral). A failed by-number lookup degrades to "no PR", exactly as
before.

The tracking gate matters: a tracked branch that happens to be named pr123 keeps the precise
selector path, so the number can never override a real head selector — covered by the negative test.

Tests

• status resolves the PR by number for an untracked prNNNN checkout — fails on the pre-fix
  implementation (verified by stashing the fix), passes after; also asserts the pr view 2182 call
  actually happened.
• status does not resolve by number once a prNNNN branch gains tracking — asserts pr view is
  never called and the row stays badge-less when the tracked head genuinely has no PR.
• Full GitManager.test.ts: 84 pass. Typecheck clean.

Retroactive by design: existing worktrees need no touch-up — the fallback keys off state the server
reads on every sweep.

Co-authored by @patroza

opened by Patrick Roza in chat thread Discord · Discord · T3

[patroza]

@omegent I would first question why agents setup branches like these without tracking, and see if we can address that

[omegent-app]

I’ve patched the status fallback to try to reattach the branch to the real PR head branch once the PR number is known. Next I’m adding a regression test that proves the branch stops being “untracked by design” after the first successful lookup.

gpt-5.4 · ↑52k ↓1.8k

[omegent-app]

Closes the last gap in the PR-badge chain: threads whose agents check out a PR with
git fetch origin <head-branch>:prNNNN — a renamed local branch, no upstream tracking.

The problem

The badge lookup finds a thread's PR by head selector: the local branch name, or the head branch
its tracking points to. A pr2182-style checkout has neither — the local name matches no PR's head,
and there is no tracking to derive the real one from. The thread reviewing PR pingdotgg#2182 was the live
case: gh pr list --head pr2182 correctly returns nothing, so the row showed no badge for the very
PR it existed to review. It only lit up after hand-setting branch.pr2182.merge on the worktree.

The fix

In findLatestPrForHeadContext, when the selector search finds nothing and the branch has no
tracking-derived head (headBranch === localBranch) and the name matches ^pr[-_]?\d+$, resolve
the PR by that number via the provider's existing getChangeRequest (gh pr view N /
glab mr show N — provider-neutral). A failed by-number lookup degrades to "no PR", exactly as
before.

The tracking gate matters: a tracked branch that happens to be named pr123 keeps the precise
selector path, so the number can never override a real head selector — covered by the negative test.

Tests

• status resolves the PR by number for an untracked prNNNN checkout — fails on the pre-fix
  implementation (verified by stashing the fix), passes after; also asserts the pr view 2182 call
  actually happened.
• status does not resolve by number once a prNNNN branch gains tracking — asserts pr view is
  never called and the row stays badge-less when the tracked head genuinely has no PR.
• Full GitManager.test.ts: 84 pass. Typecheck clean.

Retroactive by design: existing worktrees need no touch-up — the fallback keys off state the server
reads on every sweep.

Co-authored by @patroza

opened by Patrick Roza in chat thread Discord · Discord · T3

[patroza]

@omegent I would first question why agents setup branches like these without tracking, and see if we can address that

[omegent-app]

I’ve patched the status fallback to try to reattach the branch to the real PR head branch once the PR number is known. Next I’m adding a regression test that proves the branch stops being “untracked by design” after the first successful lookup.

gpt-5.4 · ↑52k ↓1.8k

[omegent-app]

Closes the last gap in the PR-badge chain: threads whose agents check out a PR with
git fetch origin <head-branch>:prNNNN — a renamed local branch, no upstream tracking.

The problem

The badge lookup finds a thread's PR by head selector: the local branch name, or the head branch
its tracking points to. A pr2182-style checkout has neither — the local name matches no PR's head,
and there is no tracking to derive the real one from. The thread reviewing PR pingdotgg#2182 was the live
case: gh pr list --head pr2182 correctly returns nothing, so the row showed no badge for the very
PR it existed to review. It only lit up after hand-setting branch.pr2182.merge on the worktree.

The fix

In findLatestPrForHeadContext, when the selector search finds nothing and the branch has no
tracking-derived head (headBranch === localBranch) and the name matches ^pr[-_]?\d+$, resolve
the PR by that number via the provider's existing getChangeRequest (gh pr view N /
glab mr show N — provider-neutral). A failed by-number lookup degrades to "no PR", exactly as
before.

The tracking gate matters: a tracked branch that happens to be named pr123 keeps the precise
selector path, so the number can never override a real head selector — covered by the negative test.

Tests

• status resolves the PR by number for an untracked prNNNN checkout — fails on the pre-fix
  implementation (verified by stashing the fix), passes after; also asserts the pr view 2182 call
  actually happened.
• status does not resolve by number once a prNNNN branch gains tracking — asserts pr view is
  never called and the row stays badge-less when the tracked head genuinely has no PR.
• Full GitManager.test.ts: 84 pass. Typecheck clean.

Retroactive by design: existing worktrees need no touch-up — the fallback keys off state the server
reads on every sweep.

Co-authored by @patroza

opened by Patrick Roza in chat thread Discord · Discord · T3

[patroza]

@omegent I would first question why agents setup branches like these without tracking, and see if we can address that

[omegent-app]

I’ve patched the status fallback to try to reattach the branch to the real PR head branch once the PR number is known. Next I’m adding a regression test that proves the branch stops being “untracked by design” after the first successful lookup.

gpt-5.4 · ↑52k ↓1.8k

[omegent-app]

Closes the last gap in the PR-badge chain: threads whose agents check out a PR with
git fetch origin <head-branch>:prNNNN — a renamed local branch, no upstream tracking.

The problem

The badge lookup finds a thread's PR by head selector: the local branch name, or the head branch
its tracking points to. A pr2182-style checkout has neither — the local name matches no PR's head,
and there is no tracking to derive the real one from. The thread reviewing PR pingdotgg#2182 was the live
case: gh pr list --head pr2182 correctly returns nothing, so the row showed no badge for the very
PR it existed to review. It only lit up after hand-setting branch.pr2182.merge on the worktree.

The fix

In findLatestPrForHeadContext, when the selector search finds nothing and the branch has no
tracking-derived head (headBranch === localBranch) and the name matches ^pr[-_]?\d+$, resolve
the PR by that number via the provider's existing getChangeRequest (gh pr view N /
glab mr show N — provider-neutral). A failed by-number lookup degrades to "no PR", exactly as
before.

The tracking gate matters: a tracked branch that happens to be named pr123 keeps the precise
selector path, so the number can never override a real head selector — covered by the negative test.

Tests

• status resolves the PR by number for an untracked prNNNN checkout — fails on the pre-fix
  implementation (verified by stashing the fix), passes after; also asserts the pr view 2182 call
  actually happened.
• status does not resolve by number once a prNNNN branch gains tracking — asserts pr view is
  never called and the row stays badge-less when the tracked head genuinely has no PR.
• Full GitManager.test.ts: 84 pass. Typecheck clean.

Retroactive by design: existing worktrees need no touch-up — the fallback keys off state the server
reads on every sweep.

Co-authored by @patroza

opened by Patrick Roza in chat thread Discord · Discord · T3

[patroza]

@omegent I would first question why agents setup branches like these without tracking, and see if we can address that

[omegent-app]

I’ve patched the status fallback to try to reattach the branch to the real PR head branch once the PR number is known. Next I’m adding a regression test that proves the branch stops being “untracked by design” after the first successful lookup.

gpt-5.4 · ↑52k ↓1.8k

[omegent-app]

Closes the last gap in the PR-badge chain: threads whose agents check out a PR with
git fetch origin <head-branch>:prNNNN — a renamed local branch, no upstream tracking.

The problem

The badge lookup finds a thread's PR by head selector: the local branch name, or the head branch
its tracking points to. A pr2182-style checkout has neither — the local name matches no PR's head,
and there is no tracking to derive the real one from. The thread reviewing PR pingdotgg#2182 was the live
case: gh pr list --head pr2182 correctly returns nothing, so the row showed no badge for the very
PR it existed to review. It only lit up after hand-setting branch.pr2182.merge on the worktree.

The fix

In findLatestPrForHeadContext, when the selector search finds nothing and the branch has no
tracking-derived head (headBranch === localBranch) and the name matches ^pr[-_]?\d+$, resolve
the PR by that number via the provider's existing getChangeRequest (gh pr view N /
glab mr show N — provider-neutral). A failed by-number lookup degrades to "no PR", exactly as
before.

The tracking gate matters: a tracked branch that happens to be named pr123 keeps the precise
selector path, so the number can never override a real head selector — covered by the negative test.

Tests

• status resolves the PR by number for an untracked prNNNN checkout — fails on the pre-fix
  implementation (verified by stashing the fix), passes after; also asserts the pr view 2182 call
  actually happened.
• status does not resolve by number once a prNNNN branch gains tracking — asserts pr view is
  never called and the row stays badge-less when the tracked head genuinely has no PR.
• Full GitManager.test.ts: 84 pass. Typecheck clean.

Retroactive by design: existing worktrees need no touch-up — the fallback keys off state the server
reads on every sweep.

Co-authored by @patroza

opened by Patrick Roza in chat thread Discord · Discord · T3

[patroza]

@omegent I would first question why agents setup branches like these without tracking, and see if we can address that

[omegent-app]

I’ve patched the status fallback to try to reattach the branch to the real PR head branch once the PR number is known. Next I’m adding a regression test that proves the branch stops being “untracked by design” after the first successful lookup.

gpt-5.4 · ↑52k ↓1.8k

[omegent-app]

Closes the last gap in the PR-badge chain: threads whose agents check out a PR with
git fetch origin <head-branch>:prNNNN — a renamed local branch, no upstream tracking.

The problem

The badge lookup finds a thread's PR by head selector: the local branch name, or the head branch
its tracking points to. A pr2182-style checkout has neither — the local name matches no PR's head,
and there is no tracking to derive the real one from. The thread reviewing PR pingdotgg#2182 was the live
case: gh pr list --head pr2182 correctly returns nothing, so the row showed no badge for the very
PR it existed to review. It only lit up after hand-setting branch.pr2182.merge on the worktree.

The fix

In findLatestPrForHeadContext, when the selector search finds nothing and the branch has no
tracking-derived head (headBranch === localBranch) and the name matches ^pr[-_]?\d+$, resolve
the PR by that number via the provider's existing getChangeRequest (gh pr view N /
glab mr show N — provider-neutral). A failed by-number lookup degrades to "no PR", exactly as
before.

The tracking gate matters: a tracked branch that happens to be named pr123 keeps the precise
selector path, so the number can never override a real head selector — covered by the negative test.

Tests

• status resolves the PR by number for an untracked prNNNN checkout — fails on the pre-fix
  implementation (verified by stashing the fix), passes after; also asserts the pr view 2182 call
  actually happened.
• status does not resolve by number once a prNNNN branch gains tracking — asserts pr view is
  never called and the row stays badge-less when the tracked head genuinely has no PR.
• Full GitManager.test.ts: 84 pass. Typecheck clean.

Retroactive by design: existing worktrees need no touch-up — the fallback keys off state the server
reads on every sweep.

Co-authored by @patroza

opened by Patrick Roza in chat thread Discord · Discord · T3

[patroza]

@omegent I would first question why agents setup branches like these without tracking, and see if we can address that

[omegent-app]

I’ve patched the status fallback to try to reattach the branch to the real PR head branch once the PR number is known. Next I’m adding a regression test that proves the branch stops being “untracked by design” after the first successful lookup.

gpt-5.4 · ↑52k ↓1.8k

[omegent-app]

Closes the last gap in the PR-badge chain: threads whose agents check out a PR with
git fetch origin <head-branch>:prNNNN — a renamed local branch, no upstream tracking.

The problem

The badge lookup finds a thread's PR by head selector: the local branch name, or the head branch
its tracking points to. A pr2182-style checkout has neither — the local name matches no PR's head,
and there is no tracking to derive the real one from. The thread reviewing PR pingdotgg#2182 was the live
case: gh pr list --head pr2182 correctly returns nothing, so the row showed no badge for the very
PR it existed to review. It only lit up after hand-setting branch.pr2182.merge on the worktree.

The fix

In findLatestPrForHeadContext, when the selector search finds nothing and the branch has no
tracking-derived head (headBranch === localBranch) and the name matches ^pr[-_]?\d+$, resolve
the PR by that number via the provider's existing getChangeRequest (gh pr view N /
glab mr show N — provider-neutral). A failed by-number lookup degrades to "no PR", exactly as
before.

The tracking gate matters: a tracked branch that happens to be named pr123 keeps the precise
selector path, so the number can never override a real head selector — covered by the negative test.

Tests

• status resolves the PR by number for an untracked prNNNN checkout — fails on the pre-fix
  implementation (verified by stashing the fix), passes after; also asserts the pr view 2182 call
  actually happened.
• status does not resolve by number once a prNNNN branch gains tracking — asserts pr view is
  never called and the row stays badge-less when the tracked head genuinely has no PR.
• Full GitManager.test.ts: 84 pass. Typecheck clean.

Retroactive by design: existing worktrees need no touch-up — the fallback keys off state the server
reads on every sweep.

Co-authored by @patroza

opened by Patrick Roza in chat thread Discord · Discord · T3

[patroza]

@omegent I would first question why agents setup branches like these without tracking, and see if we can address that

[omegent-app]

I’ve patched the status fallback to try to reattach the branch to the real PR head branch once the PR number is known. Next I’m adding a regression test that proves the branch stops being “untracked by design” after the first successful lookup.

gpt-5.4 · ↑52k ↓1.8k