Land the Issues tab in the Repository pane as its own branch

[Defmon3]

Seen on: work/stack-6315-refresh-20260829

What it fixes

The Repository pane has History and Pull Requests but no Issues. Once upstream ships an issues workspace, a user still has to leave the thread to read the issue the work is about. This piece adds the Issues sub-tab, reusing upstream's issue list and detail views, with a link from an issue to its pull request that opens in the Pull Requests sub-tab.

Why we need it

It is PR 11 of the series in the Git History series issue (#8), the end state. It is the only piece that waits on upstream, and it is tiny once the pane exists.

How to fix it

Cut a fresh branch on top of the Repository pane carrying the Issues sub-tab that mounts upstream's issues panel in project scope, the linked-pull-request handoff, and their tests. Deferred until upstream's issues workspace exists in some form.

[Defmon3]

Technical appendix: Land the Issues tab in the Repository pane as its own branch

Investigated on branch work/stack-6315-refresh-20260829 at commit 23578f462, and on the upstream PR it depends on, on 2026-09-04.

Findings

• On the stacked proposal, RepositoryPanel.tsx mounts the issues workspace's IssuesPanel from apps/web/src/components/issue/IssuesPanel.tsx in project scope. The proposal's only change to that component is an optional onOpenLinkedPullRequest callback, threaded to the issue detail so a linked pull request opens in the pane's Pull Requests sub-tab.
• The stacked proposal also removes the MAX_QUERY_LENGTH constant from IssuesPanel.tsx while a use remains, so the branch does not typecheck. Verified by running the web typecheck.
• The Issues sub-tab unmounts on switch and loses its search; see the Repository pane issue.
• Upstream dependency: feat: add pluggable issue adapters and workspace pingdotgg/t3code#6315 "feat: add pluggable issue adapters and workspace" was closed on 2026-08-28 as too large to review and reopened the same day; it has not been split. Nothing in upstream main at a6797b3 provides an issues panel to mount.
• Size: under 100 source lines plus tests.

The problem

Observed: the Repository pane has no Issues sub-tab, and upstream has no issues workspace yet.

Once done: a branch on top of the Repository pane adds an Issues sub-tab that shows upstream's issue list and details for the project and opens a linked pull request in the Pull Requests sub-tab.