fix(web): sync sidebar PR state from open panel

[t3-code]

summary

• compare the fresh PR state shown in the thread panel with the same thread's sidebar state
• when they disagree, refresh the sidebar's actual source: linked PR detail for linked threads, or the VCS status stream for branch-inferred PRs
• explicit VCS refresh bypasses the slow PR lookup cache and failure backoff, publishes the result to existing sidebar subscribers, and primes the server settlement sweep
• dedupe refreshes by PR identity and observed state, and ignore unrelated PR panels

verification

• 330 focused sidebar and pull request tests passed
• web typecheck passed
• targeted lint and formatting passed

request provenance

• requested by: @maria-rcks

---

Note

Medium Risk
Changes how PR panel updates propagate into VCS and linked-PR queries; incorrect comparisons could cause extra refreshes or briefly stale sidebar state, but scope is limited to UI sync in chat.

Overview
Keeps the thread sidebar PR badge in sync when the open pull-request panel shows a newer state (e.g. merged) than what the sidebar still displays.

handlePullRequestTabStatusChange still updates tab status, but now runs threadPullRequestRefreshSource to compare panel vs thread PR (repo, number, state, linked flag). When they disagree on the same PR, it refreshes linkedPullRequestDetailAtom for linked threads or triggers vcsEnvironment.refreshStatus for branch-inferred PRs. Refreshes are deduped with sidebarPrRefreshKeyRef; unrelated panels or already-matching state are ignored. Repository matching is case-insensitive. Unit tests cover the refresh-source decision table.

^{Reviewed by Cursor Bugbot for commit b6a6374. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Sync sidebar PR state from open panel via threadPullRequestRefreshSource

• Adds threadPullRequestRefreshSource in ThreadStatusIndicators.tsx to compare panel PR repository, number, and state against the thread's sidebar PR; returns "linked-detail", "vcs", or null.
• Splits the PR tab status updater in ChatView.tsx into updatePullRequestTabStatusFromPanel (local state only) and handlePullRequestTabStatusChange, which triggers either a linked PR detail refresh or a VCS status refresh based on the computed source.
• Uses a sidebarPrRefreshKeyRef to dedupe redundant refresh requests per thread.
• Adds unit tests in ThreadStatusIndicators.test.ts covering linked, unlinked, unresolved, matched, and case-insensitive repository scenarios.

^{Macroscope summarized b6a6374.}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.1 KiB	13.2 KiB	+100 B (+0.7%)	15.1 KiB	✅
Codex	Thread snapshot wire	6.9 KiB	6.9 KiB	+2 B (+0.0%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.2 KiB	6.3 KiB	+98 B (+1.5%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	54.7 KiB	55.5 KiB	+822 B (+1.5%)	66.4 KiB	✅
Codex	Live turn messages	8	8	0 (0.0%)	21	✅
Claude	Total thread wire	13.2 KiB	13.3 KiB	+64 B (+0.5%)	15.1 KiB	✅
Claude	Thread snapshot wire	6.9 KiB	6.9 KiB	−9 B (−0.1%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.3 KiB	6.4 KiB	+73 B (+1.1%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	56.3 KiB	56.4 KiB	+88 B (+0.2%)	66.4 KiB	✅
Claude	Live turn messages	8	10	+2 (+25.0%)	21	✅

Baseline: 9d1879b · PR result: b6a6374 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 109.4 KiB
• Claude decoded thread snapshot: 110.1 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 2 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit fa7ff8d. Configure here.}

[macroscopeapp]

Approvability

Verdict: Approved at b6a6374

Macroscope's review found this PR approvable — This is a focused UI synchronization fix that reuses existing PR-detail and VCS refresh paths only for the active thread’s mismatched PR state. Its production impact is bounded, with targeted decision-table tests and no schema, deployment, security, or default-behavior changes.

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