fix(web): reuse pull request list data while loading

[maria-rcks]

Opening a loaded pull request discarded its row metadata and replaced the panel with a full skeleton while the richer detail request ran. This reuses the matching list entry immediately while retaining the detail request only for fields absent from the list. Verified with the web typecheck, targeted lint, diff checks, and the exact list-to-detail browser transition.

Before

play the before video

After

play the after video

Built by gpt-5.6-sol in the Codex harness.

---

Note

Low Risk
Presentation-only loading UX; no changes to fetch logic, actions, or security-sensitive paths.

Overview
Opening a pull request from the list no longer swaps the detail panel to a full skeleton while the richer detail request runs. The pull-requests page now passes the matching list row into PullRequestDetailPanel, which only accepts it when project, repository (case-insensitive), and number align with the panel reference.

While detail is still pending, PullRequestDetailGhost can take that row as a seed and render real header/summary fields—title, author, branches, diff stats, checks, labels, and similar—instead of placeholder bars, and it skips the skeleton pulse when seeded. Areas that still need detail (e.g. description body, lower sections) keep ghost bars until load completes.

Deep links or opens without a list row behave as before: an unseeded ghost with the animated skeleton.

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

Note

Reuse pull request list data while loading PullRequestDetailPanel

Adds an optional pull-request list entry prop to PullRequestDetailPanel. The component validates that the entry matches the requested project, repository, and number (repository names compared case-insensitively), then seeds the loading ghost with the list row's identity and summary data while the full detail is pending.

• Risk: mismatched entries fall back to the previous unseeded ghost, so no data corruption occurs, but reviewers should verify the match logic in PullRequestDetailPanel.tsx covers all list-vs-detail key combinations.

^{Macroscope summarized d1df036.}

[cursor]

Cursor Bugbot has reviewed your changes using default 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 5e61e63. Configure here.}

[macroscopeapp]

Approvability

Verdict: Approved at d1df036

Macroscope's review found this PR approvable — This is a localized, self-contained loading-state improvement that reuses already-visible pull-request row data while leaving detail fetching and actions unchanged. A known transient conflict-status presentation gap remains in the seeded ghost, but its impact is limited to the loading display.

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.}

[maria-rcks]

Opening a loaded pull request discarded its row metadata and replaced the panel with a full skeleton while the richer detail request ran. This reuses the matching list entry immediately while retaining the detail request only for fields absent from the list. Verified with the web typecheck, targeted lint, diff checks, and the exact list-to-detail browser transition.

Before

play the before video

After

play the after video

Built by gpt-5.6-sol in the Codex harness.

---

Note

Low Risk
Presentation-only loading UX; no changes to fetch logic, actions, or security-sensitive paths.

Overview
Opening a pull request from the list no longer swaps the detail panel to a full skeleton while the richer detail request runs. The pull-requests page now passes the matching list row into PullRequestDetailPanel, which only accepts it when project, repository (case-insensitive), and number align with the panel reference.

While detail is still pending, PullRequestDetailGhost can take that row as a seed and render real header/summary fields—title, author, branches, diff stats, checks, labels, and similar—instead of placeholder bars, and it skips the skeleton pulse when seeded. Areas that still need detail (e.g. description body, lower sections) keep ghost bars until load completes.

Deep links or opens without a list row behave as before: an unseeded ghost with the animated skeleton.

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

Note

Reuse pull request list data while loading PullRequestDetailPanel

Adds an optional pull-request list entry prop to PullRequestDetailPanel. The component validates that the entry matches the requested project, repository, and number (repository names compared case-insensitively), then seeds the loading ghost with the list row's identity and summary data while the full detail is pending.

• Risk: mismatched entries fall back to the previous unseeded ghost, so no data corruption occurs, but reviewers should verify the match logic in PullRequestDetailPanel.tsx covers all list-vs-detail key combinations.

^{Macroscope summarized d1df036.}

[cursor]

Cursor Bugbot has reviewed your changes using default 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 5e61e63. Configure here.}

[macroscopeapp]

Approvability

Verdict: Approved at d1df036

Macroscope's review found this PR approvable — This is a localized, self-contained loading-state improvement that reuses already-visible pull-request row data while leaving detail fetching and actions unchanged. A known transient conflict-status presentation gap remains in the seeded ghost, but its impact is limited to the loading display.

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.}

[maria-rcks]

Opening a loaded pull request discarded its row metadata and replaced the panel with a full skeleton while the richer detail request ran. This reuses the matching list entry immediately while retaining the detail request only for fields absent from the list. Verified with the web typecheck, targeted lint, diff checks, and the exact list-to-detail browser transition.

Before

play the before video

After

play the after video

Built by gpt-5.6-sol in the Codex harness.

---

Note

Low Risk
Presentation-only loading UX; no changes to fetch logic, actions, or security-sensitive paths.

Overview
Opening a pull request from the list no longer swaps the detail panel to a full skeleton while the richer detail request runs. The pull-requests page now passes the matching list row into PullRequestDetailPanel, which only accepts it when project, repository (case-insensitive), and number align with the panel reference.

While detail is still pending, PullRequestDetailGhost can take that row as a seed and render real header/summary fields—title, author, branches, diff stats, checks, labels, and similar—instead of placeholder bars, and it skips the skeleton pulse when seeded. Areas that still need detail (e.g. description body, lower sections) keep ghost bars until load completes.

Deep links or opens without a list row behave as before: an unseeded ghost with the animated skeleton.

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

Note

Reuse pull request list data while loading PullRequestDetailPanel

Adds an optional pull-request list entry prop to PullRequestDetailPanel. The component validates that the entry matches the requested project, repository, and number (repository names compared case-insensitively), then seeds the loading ghost with the list row's identity and summary data while the full detail is pending.

• Risk: mismatched entries fall back to the previous unseeded ghost, so no data corruption occurs, but reviewers should verify the match logic in PullRequestDetailPanel.tsx covers all list-vs-detail key combinations.

^{Macroscope summarized d1df036.}

[cursor]

Cursor Bugbot has reviewed your changes using default 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 5e61e63. Configure here.}

[macroscopeapp]

Approvability

Verdict: Approved at d1df036

Macroscope's review found this PR approvable — This is a localized, self-contained loading-state improvement that reuses already-visible pull-request row data while leaving detail fetching and actions unchanged. A known transient conflict-status presentation gap remains in the seeded ghost, but its impact is limited to the loading display.

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.}

[maria-rcks]

Opening a loaded pull request discarded its row metadata and replaced the panel with a full skeleton while the richer detail request ran. This reuses the matching list entry immediately while retaining the detail request only for fields absent from the list. Verified with the web typecheck, targeted lint, diff checks, and the exact list-to-detail browser transition.

Before

play the before video

After

play the after video

Built by gpt-5.6-sol in the Codex harness.

---

Note

Low Risk
Presentation-only loading UX; no changes to fetch logic, actions, or security-sensitive paths.

Overview
Opening a pull request from the list no longer swaps the detail panel to a full skeleton while the richer detail request runs. The pull-requests page now passes the matching list row into PullRequestDetailPanel, which only accepts it when project, repository (case-insensitive), and number align with the panel reference.

While detail is still pending, PullRequestDetailGhost can take that row as a seed and render real header/summary fields—title, author, branches, diff stats, checks, labels, and similar—instead of placeholder bars, and it skips the skeleton pulse when seeded. Areas that still need detail (e.g. description body, lower sections) keep ghost bars until load completes.

Deep links or opens without a list row behave as before: an unseeded ghost with the animated skeleton.

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

Note

Reuse pull request list data while loading PullRequestDetailPanel

Adds an optional pull-request list entry prop to PullRequestDetailPanel. The component validates that the entry matches the requested project, repository, and number (repository names compared case-insensitively), then seeds the loading ghost with the list row's identity and summary data while the full detail is pending.

• Risk: mismatched entries fall back to the previous unseeded ghost, so no data corruption occurs, but reviewers should verify the match logic in PullRequestDetailPanel.tsx covers all list-vs-detail key combinations.

^{Macroscope summarized d1df036.}

[cursor]

Cursor Bugbot has reviewed your changes using default 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 5e61e63. Configure here.}

[macroscopeapp]

Approvability

Verdict: Approved at d1df036

Macroscope's review found this PR approvable — This is a localized, self-contained loading-state improvement that reuses already-visible pull-request row data while leaving detail fetching and actions unchanged. A known transient conflict-status presentation gap remains in the seeded ghost, but its impact is limited to the loading display.

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.}

[maria-rcks]

Opening a loaded pull request discarded its row metadata and replaced the panel with a full skeleton while the richer detail request ran. This reuses the matching list entry immediately while retaining the detail request only for fields absent from the list. Verified with the web typecheck, targeted lint, diff checks, and the exact list-to-detail browser transition.

Before

play the before video

After

play the after video

Built by gpt-5.6-sol in the Codex harness.

---

Note

Low Risk
Presentation-only loading UX; no changes to fetch logic, actions, or security-sensitive paths.

Overview
Opening a pull request from the list no longer swaps the detail panel to a full skeleton while the richer detail request runs. The pull-requests page now passes the matching list row into PullRequestDetailPanel, which only accepts it when project, repository (case-insensitive), and number align with the panel reference.

While detail is still pending, PullRequestDetailGhost can take that row as a seed and render real header/summary fields—title, author, branches, diff stats, checks, labels, and similar—instead of placeholder bars, and it skips the skeleton pulse when seeded. Areas that still need detail (e.g. description body, lower sections) keep ghost bars until load completes.

Deep links or opens without a list row behave as before: an unseeded ghost with the animated skeleton.

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

Note

Reuse pull request list data while loading PullRequestDetailPanel

Adds an optional pull-request list entry prop to PullRequestDetailPanel. The component validates that the entry matches the requested project, repository, and number (repository names compared case-insensitively), then seeds the loading ghost with the list row's identity and summary data while the full detail is pending.

• Risk: mismatched entries fall back to the previous unseeded ghost, so no data corruption occurs, but reviewers should verify the match logic in PullRequestDetailPanel.tsx covers all list-vs-detail key combinations.

^{Macroscope summarized d1df036.}

[cursor]

Cursor Bugbot has reviewed your changes using default 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 5e61e63. Configure here.}

[macroscopeapp]

Approvability

Verdict: Approved at d1df036

Macroscope's review found this PR approvable — This is a localized, self-contained loading-state improvement that reuses already-visible pull-request row data while leaving detail fetching and actions unchanged. A known transient conflict-status presentation gap remains in the seeded ghost, but its impact is limited to the loading display.

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.}

[maria-rcks]

Opening a loaded pull request discarded its row metadata and replaced the panel with a full skeleton while the richer detail request ran. This reuses the matching list entry immediately while retaining the detail request only for fields absent from the list. Verified with the web typecheck, targeted lint, diff checks, and the exact list-to-detail browser transition.

Before

play the before video

After

play the after video

Built by gpt-5.6-sol in the Codex harness.

---

Note

Low Risk
Presentation-only loading UX; no changes to fetch logic, actions, or security-sensitive paths.

Overview
Opening a pull request from the list no longer swaps the detail panel to a full skeleton while the richer detail request runs. The pull-requests page now passes the matching list row into PullRequestDetailPanel, which only accepts it when project, repository (case-insensitive), and number align with the panel reference.

While detail is still pending, PullRequestDetailGhost can take that row as a seed and render real header/summary fields—title, author, branches, diff stats, checks, labels, and similar—instead of placeholder bars, and it skips the skeleton pulse when seeded. Areas that still need detail (e.g. description body, lower sections) keep ghost bars until load completes.

Deep links or opens without a list row behave as before: an unseeded ghost with the animated skeleton.

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

Note

Reuse pull request list data while loading PullRequestDetailPanel

Adds an optional pull-request list entry prop to PullRequestDetailPanel. The component validates that the entry matches the requested project, repository, and number (repository names compared case-insensitively), then seeds the loading ghost with the list row's identity and summary data while the full detail is pending.

• Risk: mismatched entries fall back to the previous unseeded ghost, so no data corruption occurs, but reviewers should verify the match logic in PullRequestDetailPanel.tsx covers all list-vs-detail key combinations.

^{Macroscope summarized d1df036.}

[cursor]

Cursor Bugbot has reviewed your changes using default 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 5e61e63. Configure here.}

[macroscopeapp]

Approvability

Verdict: Approved at d1df036

Macroscope's review found this PR approvable — This is a localized, self-contained loading-state improvement that reuses already-visible pull-request row data while leaving detail fetching and actions unchanged. A known transient conflict-status presentation gap remains in the seeded ghost, but its impact is limited to the loading display.

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.}

[maria-rcks]

Opening a loaded pull request discarded its row metadata and replaced the panel with a full skeleton while the richer detail request ran. This reuses the matching list entry immediately while retaining the detail request only for fields absent from the list. Verified with the web typecheck, targeted lint, diff checks, and the exact list-to-detail browser transition.

Before

play the before video

After

play the after video

Built by gpt-5.6-sol in the Codex harness.

---

Note

Low Risk
Presentation-only loading UX; no changes to fetch logic, actions, or security-sensitive paths.

Overview
Opening a pull request from the list no longer swaps the detail panel to a full skeleton while the richer detail request runs. The pull-requests page now passes the matching list row into PullRequestDetailPanel, which only accepts it when project, repository (case-insensitive), and number align with the panel reference.

While detail is still pending, PullRequestDetailGhost can take that row as a seed and render real header/summary fields—title, author, branches, diff stats, checks, labels, and similar—instead of placeholder bars, and it skips the skeleton pulse when seeded. Areas that still need detail (e.g. description body, lower sections) keep ghost bars until load completes.

Deep links or opens without a list row behave as before: an unseeded ghost with the animated skeleton.

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

Note

Reuse pull request list data while loading PullRequestDetailPanel

Adds an optional pull-request list entry prop to PullRequestDetailPanel. The component validates that the entry matches the requested project, repository, and number (repository names compared case-insensitively), then seeds the loading ghost with the list row's identity and summary data while the full detail is pending.

• Risk: mismatched entries fall back to the previous unseeded ghost, so no data corruption occurs, but reviewers should verify the match logic in PullRequestDetailPanel.tsx covers all list-vs-detail key combinations.

^{Macroscope summarized d1df036.}

[cursor]

Cursor Bugbot has reviewed your changes using default 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 5e61e63. Configure here.}

[macroscopeapp]

Approvability

Verdict: Approved at d1df036

Macroscope's review found this PR approvable — This is a localized, self-contained loading-state improvement that reuses already-visible pull-request row data while leaving detail fetching and actions unchanged. A known transient conflict-status presentation gap remains in the seeded ghost, but its impact is limited to the loading display.

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.}

[maria-rcks]

Opening a loaded pull request discarded its row metadata and replaced the panel with a full skeleton while the richer detail request ran. This reuses the matching list entry immediately while retaining the detail request only for fields absent from the list. Verified with the web typecheck, targeted lint, diff checks, and the exact list-to-detail browser transition.

Before

play the before video

After

play the after video

Built by gpt-5.6-sol in the Codex harness.

---

Note

Low Risk
Presentation-only loading UX; no changes to fetch logic, actions, or security-sensitive paths.

Overview
Opening a pull request from the list no longer swaps the detail panel to a full skeleton while the richer detail request runs. The pull-requests page now passes the matching list row into PullRequestDetailPanel, which only accepts it when project, repository (case-insensitive), and number align with the panel reference.

While detail is still pending, PullRequestDetailGhost can take that row as a seed and render real header/summary fields—title, author, branches, diff stats, checks, labels, and similar—instead of placeholder bars, and it skips the skeleton pulse when seeded. Areas that still need detail (e.g. description body, lower sections) keep ghost bars until load completes.

Deep links or opens without a list row behave as before: an unseeded ghost with the animated skeleton.

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

Note

Reuse pull request list data while loading PullRequestDetailPanel

Adds an optional pull-request list entry prop to PullRequestDetailPanel. The component validates that the entry matches the requested project, repository, and number (repository names compared case-insensitively), then seeds the loading ghost with the list row's identity and summary data while the full detail is pending.

• Risk: mismatched entries fall back to the previous unseeded ghost, so no data corruption occurs, but reviewers should verify the match logic in PullRequestDetailPanel.tsx covers all list-vs-detail key combinations.

^{Macroscope summarized d1df036.}

[cursor]

Cursor Bugbot has reviewed your changes using default 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 5e61e63. Configure here.}

[macroscopeapp]

Approvability

Verdict: Approved at d1df036

Macroscope's review found this PR approvable — This is a localized, self-contained loading-state improvement that reuses already-visible pull-request row data while leaving detail fetching and actions unchanged. A known transient conflict-status presentation gap remains in the seeded ghost, but its impact is limited to the loading display.

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.}