fix(pull-requests): refresh data after thread turns

[maria-rcks]

Note

Written by gpt-5.6-sol on behalf of Maria

Pull request data could stay stale after an agent changed the branch.

Primary turn.completed and turn.aborted events now advance one pull request cache revision and publish one scalar refresh signal. Tool calls do not refresh pull request data. The server does not fetch host data during the terminal event; mounted readers re-read from the signal.

Periodic refreshes remain for changes outside an agent turn. Open lists, details, linked summaries, and mounted diffs keep their existing intervals.

Verification:

• 122 focused server tests passed
• client refresh test passed
• server, contracts, client-runtime, web, and mobile typechecks passed
• scoped formatting, lint, and git diff --check passed
• a mounted pull request row picked up the pushed diff after a real turn completed, without manual refresh
• the mounted code tab issued five /api/pull-requests/diff requests from a baseline of two, covering both the turn trigger and interval refresh

Before: the mounted pull request panel remained stale after its branch changed.

After: completing a real thread turn refreshed the same mounted panel without changing threads.

Built with gpt-5.6-sol through the Codex harness.

Note

Refresh pull-request cache and client views after terminal turns in CheckpointReactor

• CheckpointReactor now tracks pending turn starts per thread and invokes PullRequestService.refreshAfterTurn only for qualifying completed or aborted turns, ignoring unrelated auxiliary turn events. Aborted turns skip checkpoint capture.
• PullRequestService exposes a refresh-revision stream and a refreshAfterTurn effect that strands existing listing and reference cache entries by bumping a global turn-refresh epoch, then publishes a monotonically increasing revision to subscribers.
• A new streaming WebSocket RPC WsPullRequestsSubscribeRefreshesRpc lets authorized clients subscribe to refresh revisions; it requires the orchestration read scope in RpcAuthorization.ts.
• Client runtime state (pullRequests.ts) and web components (PullRequestsRouteView, PullRequestDetailPanel) subscribe to the revision stream and revalidate list, detail, activity, and stats queries on change. Cursor-based list pages are excluded from the refresh trigger.
• Risk: CheckpointReactor turn-tracking logic in CheckpointReactor.ts relies on matching runtime turn IDs to pending domain requests; a missed or spurious match could cause a stale or extra pull-request refresh.

^{Macroscope summarized 951ad84.}

---

Note

Medium Risk
Changes orchestration turn handling (including aborted turns skipping checkpoints) and global PR cache epochs; incorrect turn matching could refresh too often or miss updates, but there is no direct auth or payment impact.

Overview
Pull request UI could stay stale after an agent finished a turn and changed the branch. This PR wires turn completion to cache invalidation and client re-fetch, without calling the host during the terminal event.

Server: CheckpointReactor now tracks per-thread turn state (startedTurns, pending) and, on eligible turn.completed or turn.aborted runtime events, calls PullRequestService.refreshAfterTurn. Auxiliary/tool turns are ignored via the same tracking rules tests assert. turn.aborted still bumps PR refresh but skips post-turn checkpoint capture; session.exited clears tracking. PullRequestService adds a global turnRefreshEpoch (invalidates listings and per-PR cache keys), refreshAfterTurn, and a subscribeRefreshes stream. New RPC pullRequests.subscribeRefreshes (read auth) is exposed over WebSocket.

Client: Query atoms gain optional refreshTrigger (Atom.makeRefreshOnSignal); PR list/detail/activity/stats/linked summary subscribe to the refresh revision. Paginated list reads with cursors are excluded so turn refresh does not reset pagination. Web detail panel combines turn refresh with live refresh for the code tab; the PR list page refetches when any environment publishes a new revision.

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

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — The PR introduces a cross-layer refresh protocol that changes turn-event handling, cache invalidation, WebSocket authorization, and pull-request UI refresh behavior. It also modifies an auth-directory file, so the change warrants human review.

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

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

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

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