fix(web): keep PR panel actions in the current thread

[Bil0000]

PR actions in the chat right panel could open a new thread when the displayed PR did not match the primary linked PR. The same flag controlled checkout visibility and composer selection.

Use the supplied composer for all agent handoffs. Resolve conflicts, fix findings/checks, ask/explain, and selected-code notes now stay in the current thread or draft. Standalone PR pages still open a new draft.

Added 24 panel action regression cases that check the real composer store, preserve existing draft text, and reject unintended thread creation or checkout. Twelve cases reproduced the bug before the fix.

Validation: 156 focused tests passed; web typecheck and formatting passed; targeted lint passed with existing component warnings. Tests use stubbed host queries and child controls; no browser pass was run.

Model: GPT-6. Harness: Codex.

---

Second commit: the context prop itself was the recurring failure. ChatView decided "is this the thread's own PR" from the single legacy linkedPullRequest field, which the server re-derives from the full link list and has changed nine times since August; any thread with a stack or a second link got context="page". The decision now lives in pullRequestPanelContext, fed the thread's full pullRequests list (legacy fields only as a fallback for old servers), and is tested from realistic fixtures: a five-layer stack whose legacy field names the top layer, a created+stack pair, an unsynced manual link, a dismissed stack member, another project's checkout of the same repository. The panel test derives its scenarios through the same function and now also asserts checkout-button visibility. String-presence tests in the pull request directory that could not catch any of this are removed.

Verified the new tests bite: with the link-list branch removed, three logic cases and the panel's checkout case fail. 143 tests in the two files pass; web typecheck clean.

Model: Claude Fable 5. Harness: Claude Code.

Summary by CodeRabbit

• Bug Fixes
  • Pull request actions such as resolving conflicts, asking questions, explaining a pull request, and fixing findings now place their content in the selected composer target.
  • Actions work consistently whether the composer is in the current thread, beside the pull request, associated with an unsent draft, or on a standalone pull request page.
  • Improved pull request context detection ensures actions and generated drafts are routed to the appropriate existing or newly created conversation.
  • Existing drafts are preserved when new pull request actions are initiated.

[macroscopeapp]

Approvability

Verdict: Approved at c409cba

Macroscope's review found this PR approvable — This is a narrowly scoped web bug fix that corrects pull-request panel context detection and keeps existing thread or draft actions in the appropriate composer, with focused regression coverage and no schema, infrastructure, security, billing, or default changes. A separate unresolved Medium-severity finding identifies an edge case involving all-dismissed links and should be handled by the repository’s correctness gate.

Notes:

• This verdict was updated automatically after the outstanding correctness findings were resolved. Macroscope did not re-review the code.

^{You can add or adjust custom eligibility rules. Learn more.}

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Advanced

Run ID: b8d0669a-0675-4211-8568-d4134940b527

📥 Commits

Reviewing files that changed from the base of the PR and between 1c17677 and c409cba.

📒 Files selected for processing (8)

• apps/web/src/components/ChatView.tsx
• apps/web/src/components/pullRequest/PullRequestDetailPanel.test.tsx
• apps/web/src/components/pullRequest/PullRequestListEmptyState.test.tsx
• apps/web/src/components/pullRequest/PullRequestsUnavailableState.test.tsx
• apps/web/src/components/pullRequest/pullRequestDetail.logic.test.ts
• apps/web/src/components/pullRequest/pullRequestDetail.logic.ts
• apps/web/src/components/pullRequest/pullRequestLinkContextMenu.test.ts
• apps/web/src/components/pullRequest/pullRequestPresentation.test.tsx

💤 Files with no reviewable changes (4)

• apps/web/src/components/pullRequest/pullRequestLinkContextMenu.test.ts
• apps/web/src/components/pullRequest/PullRequestsUnavailableState.test.tsx
• apps/web/src/components/pullRequest/pullRequestPresentation.test.tsx
• apps/web/src/components/pullRequest/PullRequestListEmptyState.test.tsx

Included review availability: Your plan provides up to 10 included reviews per hour; 9 remain after this review.

---

📝 Walkthrough

Walkthrough

The pull-request panel now derives context from visible thread links and routes supplied composer targets directly. Tests cover panel actions across stacked, unrelated, draft, and standalone contexts. Several unrelated component test files are removed.

Changes

Composer target routing

Layer / File(s)	Summary
Panel context detection apps/web/src/components/pullRequest/pullRequestDetail.logic.ts, apps/web/src/components/ChatView.tsx, apps/web/src/components/pullRequest/pullRequestDetail.logic.test.ts	pullRequestPanelContext matches project IDs and visible pull-request links, with host-aware matching and legacy fallback when no link list exists.
Direct composer target routing apps/web/src/components/pullRequest/PullRequestDetailPanel.tsx, apps/web/src/components/pullRequest/pullRequestDetail.logic.ts	PullRequestDetailPanel now uses composerDraftTarget directly. The obsolete pullRequestComposerTarget helper is removed.
Panel action coverage apps/web/src/components/pullRequest/PullRequestDetailPanel.test.tsx	Tests cover stacked, unrelated, draft, and standalone contexts. They verify checkout visibility, action content, draft preservation, thread preparation, and new-thread creation.
Removed unrelated test coverage apps/web/src/components/pullRequest/*State.test.tsx, apps/web/src/components/pullRequest/pullRequestLinkContextMenu.test.ts, apps/web/src/components/pullRequest/pullRequestPresentation.test.tsx	The listed empty-state, unavailable-state, context-menu, and avatar fallback test files are removed.

Priority: ⬇️ Low

Estimated code review effort: 3 (Moderate) | ~20 minutes

Change: Bug fix

Suggested reviewers: maria-rcks

Merge Risk: ⚪ Minimal · up to c409c

The updated panel routing preserves existing drafts when a target is supplied and still creates a new thread for standalone pages without one. No concrete merge-readiness risk remains.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 37.50% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 8 functions across 5 files.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title clearly identifies the main fix: keeping pull request panel actions in the current thread.
Description check	✅ Passed	The description explains what changed, why it changed, the affected interaction behavior, regression coverage, and validation results. It does not use the template headings or include the checklist, s…

• Fix all pre-merge checks with AI

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create a new PR

---

_{Comment @coderabbitai help to get the list of available commands.}

Dismissing prior approval to re-evaluate c409cba