[Bug]: Escape does not return to the previous thread from Pull Requests or Usage

Before submitting

• I searched existing issues and did not find a duplicate for the Pull Requests page.
• I included enough detail to reproduce or investigate the problem.

Area

apps/web

Steps to reproduce

1. Open a thread in T3 Code.
2. Navigate to the Pull Requests page or the Usage page.
3. With no dialog or popover open, press Escape.
4. Repeat for the other page.
5. Compare with opening Settings from a thread and pressing Escape.

Expected behavior

Escape should return to the thread I was working in, consistent with Settings. If a dialog or popover is open, Escape should dismiss it first without leaving the page.

Actual behavior

Escape does not return from either Pull Requests or Usage to the previous thread. The same action works from Settings, making keyboard navigation inconsistent.

Impact

Minor bug or occasional failure. Returning to the thread requires manual navigation.

Related work

• #1350 requested the existing Escape-to-go-back behavior in Settings.
• Open PR #10158 already adds Escape navigation to Usage. This report records the current inconsistency on both pages; the Usage portion overlaps with that PR, while Pull Requests remains uncovered.

Workaround

Select the previous thread in the sidebar.

Start in apps/web by comparing Escape handling on Pull Requests and Usage with the working Settings behavior, and review the overlap with PR #10158. Verify that Escape first dismisses an open dialog or popover, otherwise returns to the previous thread from both pages, without breaking the existing Settings behavior.