Issue 15023 runtime reproduction on main b5a226e49c
Environment: Linux x86_64, Node v24.21.0, web dev server 6451 / server 14491, Chromium T3 collaborative preview 1280x800.
Commands:
  git init /tmp/issue-15023-fork
  git -C /tmp/issue-15023-fork remote add origin https://github.com/juliusmarminge/t3code.git
  git -C /tmp/issue-15023-fork remote add upstream https://github.com/pingdotgg/t3code.git
  git -C /tmp/issue-15023-fork config remote.origin.gh-resolved base
  git -C /tmp/issue-15023-fork -c user.name=Triage -c user.email=triage@example.invalid commit --allow-empty -m 'repro fixture'
  vp run dev (in /home/ubuntu/wt/issue-15023; isolated worktree .t3)
Browser actions: pair; Add project > Local folder > /tmp/issue-15023-fork; Pull Requests > Filters > Project > issue-15023-fork.
Observed: project-filtered list contains upstream pingdotgg/t3code pull requests. For example the rendered repository labels are pingdotgg/t3code, despite origin being juliusmarminge/t3code and remote.origin.gh-resolved=base.
No PR was created, merged, closed or modified during this reproduction. No provider turn was started.
Literal-step deviations: initialized a disposable checkout with real public fork/parent remotes rather than cloning all content; wrote the exact gh set-default config marker via git, because forge reads must use cafe. Reproduced the reported project PR list symptom; PR creation, automatic linking and merge/close actions not exercised.