feat(ui): add read-only interactive issue browser

[camopy]

Summary

Add a read-only docket ui that gives docket a keyboard-first terminal browser with list, board, and synced issue detail views.

Why

docket is effective for direct commands and automation, but browsing issues as a human still takes multiple commands. This PR introduces a lightweight interactive TUI so people can inspect work quickly without changing the existing CLI model.
This PR is also meant as a direction check before expanding the full read-only TUI roadmap.

Related: #7

What Changed

• added docket ui
• added default list view
• added board view
• added synced issue detail pane
• extracted shared read loaders into internal/app
• reused those loaders from existing CLI read commands
• fixed a board-view terminal input freeze seen under cmux/ghostty
• added targeted regression tests for the freeze path

Scope

This PR is intentionally read-only.
Included:

• browse issues in list
• browse issues in board
• inspect selected issue details
• refresh and keyboard navigation
  Not included:
• create/edit/move/comment
• search/filter UI
• vote views
• next, plan, stats, config, version
• graph/log/comments/files dedicated screens

Testing

Ran:

• go test ./internal/tui ./internal/app ./internal/cli
• targeted regression tests for board freeze behavior
  Notes:
• regression tests now cover probe-key filtering, board-to-list switching, help after board load, and stale detail message handling

[erikreinert]

This is awesome!

I love the idea of a TUI - it's nice to see what the agent is doing in real-time. I tried solving this with a --watch flag but the TUI may be a better approach.

Feedback

• docket ui -> docket tui
• more real-time (include auto-updating option)
• sort capabilities (by default sorted desc on ticket number)
• include name with type of ticket (bug, epic)
• include status in list too
• include a bit more styling (colors, icons, etc)
• explore how to display epics (issues with sub-issues) (maybe colors, etc)

Bugs

• possible bug with a lot of issues (and types) using h or j to go up and down the list frequently