[FEATURE] Make issue numbers in just gh-issues table clickable links

[gerchowl]

Description

Enhance the # column in the just gh-issues overview table so that issue numbers are clickable links. Ideally, clicking an issue number should open it directly in VS Code / Cursor (using a vscode:// URI), with a fallback to the GitHub web URL for terminals that don't support custom URI schemes.

Problem Statement

Currently the # column in the issue and PR tables rendered by scripts/gh_issues.py displays plain text numbers (e.g. 42). Users who want to view an issue must manually copy the number and run gh issue view or navigate to GitHub. Adding clickable hyperlinks would eliminate this friction.

Proposed Solution

Use Rich's built-in hyperlink support ([link=URL]text[/link]) to make the # column entries clickable in terminals that support OSC 8 hyperlinks (iTerm2, Windows Terminal, most modern terminal emulators, and Cursor's integrated terminal).

Two link targets to evaluate (in order of preference):

1. Cursor/VS Code URI — vscode://file/... or a cursor:// URI that opens the issue in the editor's GitHub integration (if a reliable scheme exists)
2. GitHub web URL — https://github.com/{owner}/{repo}/issues/{number} as a reliable fallback that works universally

The owner_repo string is already fetched in main() and can be threaded to _build_table / _build_pr_table.

Alternatives Considered

• Keep plain numbers, add a separate "open issue" just recipe — more keystrokes, doesn't leverage terminal hyperlink capabilities
• Use gh issue view --web shortcut hint — informational but not interactive

Additional Context

• Related: [FEATURE] Add unit and container integration tests for scripts/gh_issues.py #99 (parent — test coverage for gh_issues.py)
• Rich hyperlinks docs: [link=https://...]text[/link] markup
• OSC 8 terminal hyperlink support is widespread in modern terminals
• The PR table # column should also get the same treatment

Impact

• Quality-of-life improvement for all developers using just gh-issues
• Backward-compatible — terminals without OSC 8 support simply render plain text
• Minor change (~5-10 lines in _build_table and _build_pr_table)

Changelog Category

Changed

[gerchowl]

The PR table should also display its CI status (e.g. passing/failing/pending) alongside the clickable link, so developers can see at a glance whether a PR's checks are green without leaving the terminal.

[gerchowl]

Implementation Plan

Issue: #104
Branch: feature/104-clickable-issue-numbers

Tasks

• Task 1: RED — Write test asserting _build_table renders issue numbers as [link=https://github.com/{owner_repo}/issues/{num}] hyperlinks — tests/test_gh_issues.py (new) — verify: just test (test fails)
• Task 2: GREEN — Thread owner_repo into _build_table and wrap # column value with Rich [link=...] markup — scripts/gh_issues.py — verify: just test (test passes)
• Task 3: RED — Write test asserting _build_pr_table renders PR numbers as [link=https://github.com/{owner_repo}/pull/{num}] hyperlinks — tests/test_gh_issues.py — verify: just test (test fails)
• Task 4: GREEN — Thread owner_repo into _build_pr_table and wrap # column value with Rich [link=...] markup — scripts/gh_issues.py — verify: just test (test passes)
• Task 5: RED — Write test asserting issue cross-ref cells (Issues column) in the PR table are clickable links — tests/test_gh_issues.py — verify: just test (test fails)
• Task 6: GREEN — Thread owner_repo into the issues-cell rendering in _build_pr_table and wrap each #N with [link=...] — scripts/gh_issues.py — verify: just test (test passes)
• Task 7: Update CHANGELOG.md — add entry under ## Unreleased / Changed — verify: visual check

Notes

• Link format for issues: https://github.com/{owner_repo}/issues/{num}
• Link format for PRs: https://github.com/{owner_repo}/pull/{num}
• owner_repo is already fetched in main() — just needs to be passed down to _build_table and _build_pr_table
• The PR table's Issues column currently renders #N styled text — these should also become clickable links to the corresponding issues
• CI status in the PR table (from issue comment) is out of scope — suggest a separate issue