Repository navigation
feat(github-issues): linked issues expand, collapse, and show type and labels - #2025
Merged
Merged
Conversation
…d labels Fork-Domain: github-issues Fork-Tier: qol
🩺 Aftercare
|
| Head | Result | Time | Check |
|---|---|---|---|
3144270 |
✅ clear · 1 fixed | 3 min | run |
03e7912 |
🔴 1 open · 1 new | 5 min | run |
…fter mount Fork-Domain: github-issues Fork-Tier: qol
rsi-software-agent Bot
pushed a commit
that referenced
this pull request
Nov 9, 2026
…d labels (#2025) ## Problem The Linked issues panel shows **no issue type or labels**. Sub-issues sit behind a **Show sub-issues** button, with **no way to collapse** a tree. ## Change **Snapshot:** - **Adds `labels` and `issueType`**; same GraphQL read - **Keys omitted** when empty - **Schema-derived equality** for snapshots **UI:** - **Chevron** expands or collapses sub-issues - **Open by default** while a sub-issue is linked - **Guide line** marks each nesting level - **Type and label chips** on every linked row - **One label-chip component** for both lists **MCP:** - **`list_thread_issues`** adds `issueType`, `labels` ## Scope and approval **Fork-owned `github-issues` domain**; requested by the maintainer as the follow-up to #2024. ## Verification **Checks:** - `vp run check:changed origin/hyprws` → exit 0 - `vp run fork:ci` → ok on `3144270` - Web and server `vp run build` → exit 0 - **62 server** and **75 web** issue tests pass - **Late parent snapshot** keeps its child shown **Not checked:** - **No eval run**; no issue-tool eval case exists **Grounded** in Chrome with fixture links: `biomejs/biome#4726`, `biomejs/biome#5242`, `astral-sh/uv#18506`. Before, the panel looked like the #2024 captures. Expanded: **linked `pingdotgg#5242` nests** under `pingdotgg#4726` with its **type and labels**.  Collapsed: **progress and chips** stay on the row.  Claude Opus 5.5 via Claude Code, in T3 Code. ## Fork trailers Fork-Domain: github-issues Fork-Tier: qol Co-authored-by: donjor <[email protected]>
rsi-software-agent Bot
pushed a commit
that referenced
this pull request
Nov 9, 2026
…d labels (#2025) ## Problem The Linked issues panel shows **no issue type or labels**. Sub-issues sit behind a **Show sub-issues** button, with **no way to collapse** a tree. ## Change **Snapshot:** - **Adds `labels` and `issueType`**; same GraphQL read - **Keys omitted** when empty - **Schema-derived equality** for snapshots **UI:** - **Chevron** expands or collapses sub-issues - **Open by default** while a sub-issue is linked - **Guide line** marks each nesting level - **Type and label chips** on every linked row - **One label-chip component** for both lists **MCP:** - **`list_thread_issues`** adds `issueType`, `labels` ## Scope and approval **Fork-owned `github-issues` domain**; requested by the maintainer as the follow-up to #2024. ## Verification **Checks:** - `vp run check:changed origin/hyprws` → exit 0 - `vp run fork:ci` → ok on `3144270` - Web and server `vp run build` → exit 0 - **62 server** and **75 web** issue tests pass - **Late parent snapshot** keeps its child shown **Not checked:** - **No eval run**; no issue-tool eval case exists **Grounded** in Chrome with fixture links: `biomejs/biome#4726`, `biomejs/biome#5242`, `astral-sh/uv#18506`. Before, the panel looked like the #2024 captures. Expanded: **linked `pingdotgg#5242` nests** under `pingdotgg#4726` with its **type and labels**.  Collapsed: **progress and chips** stay on the row.  Claude Opus 5.5 via Claude Code, in T3 Code. ## Fork trailers Fork-Domain: github-issues Fork-Tier: qol Co-authored-by: donjor <[email protected]>
rsi-software-agent Bot
pushed a commit
that referenced
this pull request
Nov 9, 2026
…d labels (#2025) ## Problem The Linked issues panel shows **no issue type or labels**. Sub-issues sit behind a **Show sub-issues** button, with **no way to collapse** a tree. ## Change **Snapshot:** - **Adds `labels` and `issueType`**; same GraphQL read - **Keys omitted** when empty - **Schema-derived equality** for snapshots **UI:** - **Chevron** expands or collapses sub-issues - **Open by default** while a sub-issue is linked - **Guide line** marks each nesting level - **Type and label chips** on every linked row - **One label-chip component** for both lists **MCP:** - **`list_thread_issues`** adds `issueType`, `labels` ## Scope and approval **Fork-owned `github-issues` domain**; requested by the maintainer as the follow-up to #2024. ## Verification **Checks:** - `vp run check:changed origin/hyprws` → exit 0 - `vp run fork:ci` → ok on `3144270` - Web and server `vp run build` → exit 0 - **62 server** and **75 web** issue tests pass - **Late parent snapshot** keeps its child shown **Not checked:** - **No eval run**; no issue-tool eval case exists **Grounded** in Chrome with fixture links: `biomejs/biome#4726`, `biomejs/biome#5242`, `astral-sh/uv#18506`. Before, the panel looked like the #2024 captures. Expanded: **linked `pingdotgg#5242` nests** under `pingdotgg#4726` with its **type and labels**.  Collapsed: **progress and chips** stay on the row.  Claude Opus 5.5 via Claude Code, in T3 Code. ## Fork trailers Fork-Domain: github-issues Fork-Tier: qol Co-authored-by: donjor <[email protected]>
rsi-software-agent Bot
pushed a commit
that referenced
this pull request
Nov 10, 2026
…2024) ## Problem A thread that links a **parent or tracker issue** shows **no sub-issue progress** or hierarchy. Agents reading `list_thread_issues` **cannot see the children** either. ## Change **Snapshot:** - **Adds `subIssues` and `parent`** - **Keys omitted** when empty - **Optional fields**; old snapshots still decode **Sync:** - **Same GraphQL read**; no extra request - **Deleted the second read** for child close reasons - **One issue URL parser**, shared from contracts - **A child's state change** rereads its linked parent - **Child edits** count as a snapshot change **UI:** - **Linked children nest** under a linked parent - **Other children** open with **Show sub-issues** - **Progress** (`2/6`) on row, badge, and details - **Parent meta** (`↰ #N`) on a root row - **Stale cycles** fall back to roots **MCP:** - **`list_thread_issues`** adds `subIssues`, `parent` ## Scope and approval **Fork-owned `github-issues` domain**; requested by the maintainer in the thread that did the work. ## Verification **Checks:** - `vp run check:changed origin/hyprws` → exit 1 - **11 browser files** failed on module fetch; **all pass** on rerun - `vp run fork:ci` → ok on `1843b1e` - Web and server `vp run build` → exit 0 - Server, contracts, and web typecheck → exit 0 - **62 server**, **74 web**, **6 contracts** issue tests pass **Not checked:** - **No eval run**; no issue-tool eval case exists **Grounded** in Chrome against `astral-sh/uv` fixture links; before, none of these surfaces showed sub-issues. Collapsed: **progress** and **linked children nested**.  Expanded: **Show sub-issues** lists the rest.  Root child: **parent meta**.  Badge hover: **progress** in the mini list.  Details panel: **progress** on the issue row.  Claude Opus 5.5 via Claude Code, in T3 Code. ## Fork trailers Squashes: - c3c6084144 feat(github-issues): linked issues nest and track their sub-issues (#2024) (#2024) - 16f839c3ae feat(github-issues): linked issues expand, collapse, and show type and labels (#2025) (#2025) Fork-Domain: github-issues Fork-Tier: qol Co-authored-by: donjor <[email protected]>
rsi-software-agent Bot
pushed a commit
that referenced
this pull request
Nov 10, 2026
…2024) ## Problem A thread that links a **parent or tracker issue** shows **no sub-issue progress** or hierarchy. Agents reading `list_thread_issues` **cannot see the children** either. ## Change **Snapshot:** - **Adds `subIssues` and `parent`** - **Keys omitted** when empty - **Optional fields**; old snapshots still decode **Sync:** - **Same GraphQL read**; no extra request - **Deleted the second read** for child close reasons - **One issue URL parser**, shared from contracts - **A child's state change** rereads its linked parent - **Child edits** count as a snapshot change **UI:** - **Linked children nest** under a linked parent - **Other children** open with **Show sub-issues** - **Progress** (`2/6`) on row, badge, and details - **Parent meta** (`↰ #N`) on a root row - **Stale cycles** fall back to roots **MCP:** - **`list_thread_issues`** adds `subIssues`, `parent` ## Scope and approval **Fork-owned `github-issues` domain**; requested by the maintainer in the thread that did the work. ## Verification **Checks:** - `vp run check:changed origin/hyprws` → exit 1 - **11 browser files** failed on module fetch; **all pass** on rerun - `vp run fork:ci` → ok on `1843b1e` - Web and server `vp run build` → exit 0 - Server, contracts, and web typecheck → exit 0 - **62 server**, **74 web**, **6 contracts** issue tests pass **Not checked:** - **No eval run**; no issue-tool eval case exists **Grounded** in Chrome against `astral-sh/uv` fixture links; before, none of these surfaces showed sub-issues. Collapsed: **progress** and **linked children nested**.  Expanded: **Show sub-issues** lists the rest.  Root child: **parent meta**.  Badge hover: **progress** in the mini list.  Details panel: **progress** on the issue row.  Claude Opus 5.5 via Claude Code, in T3 Code. ## Fork trailers Squashes: - c3c6084144 feat(github-issues): linked issues nest and track their sub-issues (#2024) (#2024) - 16f839c3ae feat(github-issues): linked issues expand, collapse, and show type and labels (#2025) (#2025) Fork-Domain: github-issues Fork-Tier: qol Co-authored-by: donjor <[email protected]>
rsi-software-agent Bot
pushed a commit
that referenced
this pull request
Nov 10, 2026
…2024) ## Problem A thread that links a **parent or tracker issue** shows **no sub-issue progress** or hierarchy. Agents reading `list_thread_issues` **cannot see the children** either. ## Change **Snapshot:** - **Adds `subIssues` and `parent`** - **Keys omitted** when empty - **Optional fields**; old snapshots still decode **Sync:** - **Same GraphQL read**; no extra request - **Deleted the second read** for child close reasons - **One issue URL parser**, shared from contracts - **A child's state change** rereads its linked parent - **Child edits** count as a snapshot change **UI:** - **Linked children nest** under a linked parent - **Other children** open with **Show sub-issues** - **Progress** (`2/6`) on row, badge, and details - **Parent meta** (`↰ #N`) on a root row - **Stale cycles** fall back to roots **MCP:** - **`list_thread_issues`** adds `subIssues`, `parent` ## Scope and approval **Fork-owned `github-issues` domain**; requested by the maintainer in the thread that did the work. ## Verification **Checks:** - `vp run check:changed origin/hyprws` → exit 1 - **11 browser files** failed on module fetch; **all pass** on rerun - `vp run fork:ci` → ok on `1843b1e` - Web and server `vp run build` → exit 0 - Server, contracts, and web typecheck → exit 0 - **62 server**, **74 web**, **6 contracts** issue tests pass **Not checked:** - **No eval run**; no issue-tool eval case exists **Grounded** in Chrome against `astral-sh/uv` fixture links; before, none of these surfaces showed sub-issues. Collapsed: **progress** and **linked children nested**.  Expanded: **Show sub-issues** lists the rest.  Root child: **parent meta**.  Badge hover: **progress** in the mini list.  Details panel: **progress** on the issue row.  Claude Opus 5.5 via Claude Code, in T3 Code. ## Fork trailers Squashes: - c3c6084144 feat(github-issues): linked issues nest and track their sub-issues (#2024) (#2024) - 16f839c3ae feat(github-issues): linked issues expand, collapse, and show type and labels (#2025) (#2025) Fork-Domain: github-issues Fork-Tier: qol Co-authored-by: donjor <[email protected]>
rsi-software-agent Bot
pushed a commit
that referenced
this pull request
Nov 10, 2026
…2024) ## Problem A thread that links a **parent or tracker issue** shows **no sub-issue progress** or hierarchy. Agents reading `list_thread_issues` **cannot see the children** either. ## Change **Snapshot:** - **Adds `subIssues` and `parent`** - **Keys omitted** when empty - **Optional fields**; old snapshots still decode **Sync:** - **Same GraphQL read**; no extra request - **Deleted the second read** for child close reasons - **One issue URL parser**, shared from contracts - **A child's state change** rereads its linked parent - **Child edits** count as a snapshot change **UI:** - **Linked children nest** under a linked parent - **Other children** open with **Show sub-issues** - **Progress** (`2/6`) on row, badge, and details - **Parent meta** (`↰ #N`) on a root row - **Stale cycles** fall back to roots **MCP:** - **`list_thread_issues`** adds `subIssues`, `parent` ## Scope and approval **Fork-owned `github-issues` domain**; requested by the maintainer in the thread that did the work. ## Verification **Checks:** - `vp run check:changed origin/hyprws` → exit 1 - **11 browser files** failed on module fetch; **all pass** on rerun - `vp run fork:ci` → ok on `1843b1e` - Web and server `vp run build` → exit 0 - Server, contracts, and web typecheck → exit 0 - **62 server**, **74 web**, **6 contracts** issue tests pass **Not checked:** - **No eval run**; no issue-tool eval case exists **Grounded** in Chrome against `astral-sh/uv` fixture links; before, none of these surfaces showed sub-issues. Collapsed: **progress** and **linked children nested**.  Expanded: **Show sub-issues** lists the rest.  Root child: **parent meta**.  Badge hover: **progress** in the mini list.  Details panel: **progress** on the issue row.  Claude Opus 5.5 via Claude Code, in T3 Code. ## Fork trailers Squashes: - c3c6084144 feat(github-issues): linked issues nest and track their sub-issues (#2024) (#2024) - 16f839c3ae feat(github-issues): linked issues expand, collapse, and show type and labels (#2025) (#2025) Fork-Domain: github-issues Fork-Tier: qol Co-authored-by: donjor <[email protected]>
rsi-software-agent Bot
pushed a commit
that referenced
this pull request
Nov 10, 2026
…2024) ## Problem A thread that links a **parent or tracker issue** shows **no sub-issue progress** or hierarchy. Agents reading `list_thread_issues` **cannot see the children** either. ## Change **Snapshot:** - **Adds `subIssues` and `parent`** - **Keys omitted** when empty - **Optional fields**; old snapshots still decode **Sync:** - **Same GraphQL read**; no extra request - **Deleted the second read** for child close reasons - **One issue URL parser**, shared from contracts - **A child's state change** rereads its linked parent - **Child edits** count as a snapshot change **UI:** - **Linked children nest** under a linked parent - **Other children** open with **Show sub-issues** - **Progress** (`2/6`) on row, badge, and details - **Parent meta** (`↰ #N`) on a root row - **Stale cycles** fall back to roots **MCP:** - **`list_thread_issues`** adds `subIssues`, `parent` ## Scope and approval **Fork-owned `github-issues` domain**; requested by the maintainer in the thread that did the work. ## Verification **Checks:** - `vp run check:changed origin/hyprws` → exit 1 - **11 browser files** failed on module fetch; **all pass** on rerun - `vp run fork:ci` → ok on `1843b1e` - Web and server `vp run build` → exit 0 - Server, contracts, and web typecheck → exit 0 - **62 server**, **74 web**, **6 contracts** issue tests pass **Not checked:** - **No eval run**; no issue-tool eval case exists **Grounded** in Chrome against `astral-sh/uv` fixture links; before, none of these surfaces showed sub-issues. Collapsed: **progress** and **linked children nested**.  Expanded: **Show sub-issues** lists the rest.  Root child: **parent meta**.  Badge hover: **progress** in the mini list.  Details panel: **progress** on the issue row.  Claude Opus 5.5 via Claude Code, in T3 Code. ## Fork trailers Squashes: - c3c6084144 feat(github-issues): linked issues nest and track their sub-issues (#2024) (#2024) - 16f839c3ae feat(github-issues): linked issues expand, collapse, and show type and labels (#2025) (#2025) Fork-Domain: github-issues Fork-Tier: qol Co-authored-by: donjor <[email protected]>
rsi-software-agent Bot
pushed a commit
that referenced
this pull request
Nov 11, 2026
…2024) ## Problem A thread that links a **parent or tracker issue** shows **no sub-issue progress** or hierarchy. Agents reading `list_thread_issues` **cannot see the children** either. ## Change **Snapshot:** - **Adds `subIssues` and `parent`** - **Keys omitted** when empty - **Optional fields**; old snapshots still decode **Sync:** - **Same GraphQL read**; no extra request - **Deleted the second read** for child close reasons - **One issue URL parser**, shared from contracts - **A child's state change** rereads its linked parent - **Child edits** count as a snapshot change **UI:** - **Linked children nest** under a linked parent - **Other children** open with **Show sub-issues** - **Progress** (`2/6`) on row, badge, and details - **Parent meta** (`↰ #N`) on a root row - **Stale cycles** fall back to roots **MCP:** - **`list_thread_issues`** adds `subIssues`, `parent` ## Scope and approval **Fork-owned `github-issues` domain**; requested by the maintainer in the thread that did the work. ## Verification **Checks:** - `vp run check:changed origin/hyprws` → exit 1 - **11 browser files** failed on module fetch; **all pass** on rerun - `vp run fork:ci` → ok on `1843b1e` - Web and server `vp run build` → exit 0 - Server, contracts, and web typecheck → exit 0 - **62 server**, **74 web**, **6 contracts** issue tests pass **Not checked:** - **No eval run**; no issue-tool eval case exists **Grounded** in Chrome against `astral-sh/uv` fixture links; before, none of these surfaces showed sub-issues. Collapsed: **progress** and **linked children nested**.  Expanded: **Show sub-issues** lists the rest.  Root child: **parent meta**.  Badge hover: **progress** in the mini list.  Details panel: **progress** on the issue row.  Claude Opus 5.5 via Claude Code, in T3 Code. ## Fork trailers Squashes: - c3c6084144 feat(github-issues): linked issues nest and track their sub-issues (#2024) (#2024) - 16f839c3ae feat(github-issues): linked issues expand, collapse, and show type and labels (#2025) (#2025) Fork-Domain: github-issues Fork-Tier: qol Co-authored-by: donjor <[email protected]>
rsi-software-agent Bot
pushed a commit
that referenced
this pull request
Nov 11, 2026
…2024) ## Problem A thread that links a **parent or tracker issue** shows **no sub-issue progress** or hierarchy. Agents reading `list_thread_issues` **cannot see the children** either. ## Change **Snapshot:** - **Adds `subIssues` and `parent`** - **Keys omitted** when empty - **Optional fields**; old snapshots still decode **Sync:** - **Same GraphQL read**; no extra request - **Deleted the second read** for child close reasons - **One issue URL parser**, shared from contracts - **A child's state change** rereads its linked parent - **Child edits** count as a snapshot change **UI:** - **Linked children nest** under a linked parent - **Other children** open with **Show sub-issues** - **Progress** (`2/6`) on row, badge, and details - **Parent meta** (`↰ #N`) on a root row - **Stale cycles** fall back to roots **MCP:** - **`list_thread_issues`** adds `subIssues`, `parent` ## Scope and approval **Fork-owned `github-issues` domain**; requested by the maintainer in the thread that did the work. ## Verification **Checks:** - `vp run check:changed origin/hyprws` → exit 1 - **11 browser files** failed on module fetch; **all pass** on rerun - `vp run fork:ci` → ok on `1843b1e` - Web and server `vp run build` → exit 0 - Server, contracts, and web typecheck → exit 0 - **62 server**, **74 web**, **6 contracts** issue tests pass **Not checked:** - **No eval run**; no issue-tool eval case exists **Grounded** in Chrome against `astral-sh/uv` fixture links; before, none of these surfaces showed sub-issues. Collapsed: **progress** and **linked children nested**.  Expanded: **Show sub-issues** lists the rest.  Root child: **parent meta**.  Badge hover: **progress** in the mini list.  Details panel: **progress** on the issue row.  Claude Opus 5.5 via Claude Code, in T3 Code. ## Fork trailers Squashes: - c3c6084144 feat(github-issues): linked issues nest and track their sub-issues (#2024) (#2024) - 16f839c3ae feat(github-issues): linked issues expand, collapse, and show type and labels (#2025) (#2025) Fork-Domain: github-issues Fork-Tier: qol Co-authored-by: donjor <[email protected]>
rsi-software-agent Bot
pushed a commit
that referenced
this pull request
Nov 11, 2026
…2024) ## Problem A thread that links a **parent or tracker issue** shows **no sub-issue progress** or hierarchy. Agents reading `list_thread_issues` **cannot see the children** either. ## Change **Snapshot:** - **Adds `subIssues` and `parent`** - **Keys omitted** when empty - **Optional fields**; old snapshots still decode **Sync:** - **Same GraphQL read**; no extra request - **Deleted the second read** for child close reasons - **One issue URL parser**, shared from contracts - **A child's state change** rereads its linked parent - **Child edits** count as a snapshot change **UI:** - **Linked children nest** under a linked parent - **Other children** open with **Show sub-issues** - **Progress** (`2/6`) on row, badge, and details - **Parent meta** (`↰ #N`) on a root row - **Stale cycles** fall back to roots **MCP:** - **`list_thread_issues`** adds `subIssues`, `parent` ## Scope and approval **Fork-owned `github-issues` domain**; requested by the maintainer in the thread that did the work. ## Verification **Checks:** - `vp run check:changed origin/hyprws` → exit 1 - **11 browser files** failed on module fetch; **all pass** on rerun - `vp run fork:ci` → ok on `1843b1e` - Web and server `vp run build` → exit 0 - Server, contracts, and web typecheck → exit 0 - **62 server**, **74 web**, **6 contracts** issue tests pass **Not checked:** - **No eval run**; no issue-tool eval case exists **Grounded** in Chrome against `astral-sh/uv` fixture links; before, none of these surfaces showed sub-issues. Collapsed: **progress** and **linked children nested**.  Expanded: **Show sub-issues** lists the rest.  Root child: **parent meta**.  Badge hover: **progress** in the mini list.  Details panel: **progress** on the issue row.  Claude Opus 5.5 via Claude Code, in T3 Code. ## Fork trailers Squashes: - c3c6084144 feat(github-issues): linked issues nest and track their sub-issues (#2024) (#2024) - 16f839c3ae feat(github-issues): linked issues expand, collapse, and show type and labels (#2025) (#2025) Fork-Domain: github-issues Fork-Tier: qol Co-authored-by: donjor <[email protected]>
rsi-software-agent Bot
pushed a commit
that referenced
this pull request
Nov 11, 2026
…2024) ## Problem A thread that links a **parent or tracker issue** shows **no sub-issue progress** or hierarchy. Agents reading `list_thread_issues` **cannot see the children** either. ## Change **Snapshot:** - **Adds `subIssues` and `parent`** - **Keys omitted** when empty - **Optional fields**; old snapshots still decode **Sync:** - **Same GraphQL read**; no extra request - **Deleted the second read** for child close reasons - **One issue URL parser**, shared from contracts - **A child's state change** rereads its linked parent - **Child edits** count as a snapshot change **UI:** - **Linked children nest** under a linked parent - **Other children** open with **Show sub-issues** - **Progress** (`2/6`) on row, badge, and details - **Parent meta** (`↰ #N`) on a root row - **Stale cycles** fall back to roots **MCP:** - **`list_thread_issues`** adds `subIssues`, `parent` ## Scope and approval **Fork-owned `github-issues` domain**; requested by the maintainer in the thread that did the work. ## Verification **Checks:** - `vp run check:changed origin/hyprws` → exit 1 - **11 browser files** failed on module fetch; **all pass** on rerun - `vp run fork:ci` → ok on `1843b1e` - Web and server `vp run build` → exit 0 - Server, contracts, and web typecheck → exit 0 - **62 server**, **74 web**, **6 contracts** issue tests pass **Not checked:** - **No eval run**; no issue-tool eval case exists **Grounded** in Chrome against `astral-sh/uv` fixture links; before, none of these surfaces showed sub-issues. Collapsed: **progress** and **linked children nested**.  Expanded: **Show sub-issues** lists the rest.  Root child: **parent meta**.  Badge hover: **progress** in the mini list.  Details panel: **progress** on the issue row.  Claude Opus 5.5 via Claude Code, in T3 Code. ## Fork trailers Squashes: - c3c6084144 feat(github-issues): linked issues nest and track their sub-issues (#2024) (#2024) - 16f839c3ae feat(github-issues): linked issues expand, collapse, and show type and labels (#2025) (#2025) Fork-Domain: github-issues Fork-Tier: qol Co-authored-by: donjor <[email protected]>
rsi-software-agent Bot
pushed a commit
that referenced
this pull request
Nov 11, 2026
…2024) ## Problem A thread that links a **parent or tracker issue** shows **no sub-issue progress** or hierarchy. Agents reading `list_thread_issues` **cannot see the children** either. ## Change **Snapshot:** - **Adds `subIssues` and `parent`** - **Keys omitted** when empty - **Optional fields**; old snapshots still decode **Sync:** - **Same GraphQL read**; no extra request - **Deleted the second read** for child close reasons - **One issue URL parser**, shared from contracts - **A child's state change** rereads its linked parent - **Child edits** count as a snapshot change **UI:** - **Linked children nest** under a linked parent - **Other children** open with **Show sub-issues** - **Progress** (`2/6`) on row, badge, and details - **Parent meta** (`↰ #N`) on a root row - **Stale cycles** fall back to roots **MCP:** - **`list_thread_issues`** adds `subIssues`, `parent` ## Scope and approval **Fork-owned `github-issues` domain**; requested by the maintainer in the thread that did the work. ## Verification **Checks:** - `vp run check:changed origin/hyprws` → exit 1 - **11 browser files** failed on module fetch; **all pass** on rerun - `vp run fork:ci` → ok on `1843b1e` - Web and server `vp run build` → exit 0 - Server, contracts, and web typecheck → exit 0 - **62 server**, **74 web**, **6 contracts** issue tests pass **Not checked:** - **No eval run**; no issue-tool eval case exists **Grounded** in Chrome against `astral-sh/uv` fixture links; before, none of these surfaces showed sub-issues. Collapsed: **progress** and **linked children nested**.  Expanded: **Show sub-issues** lists the rest.  Root child: **parent meta**.  Badge hover: **progress** in the mini list.  Details panel: **progress** on the issue row.  Claude Opus 5.5 via Claude Code, in T3 Code. ## Fork trailers Squashes: - c3c6084144 feat(github-issues): linked issues nest and track their sub-issues (#2024) (#2024) - 16f839c3ae feat(github-issues): linked issues expand, collapse, and show type and labels (#2025) (#2025) Fork-Domain: github-issues Fork-Tier: qol Co-authored-by: donjor <[email protected]>
rsi-software-agent Bot
pushed a commit
that referenced
this pull request
Nov 11, 2026
…2024) ## Problem A thread that links a **parent or tracker issue** shows **no sub-issue progress** or hierarchy. Agents reading `list_thread_issues` **cannot see the children** either. ## Change **Snapshot:** - **Adds `subIssues` and `parent`** - **Keys omitted** when empty - **Optional fields**; old snapshots still decode **Sync:** - **Same GraphQL read**; no extra request - **Deleted the second read** for child close reasons - **One issue URL parser**, shared from contracts - **A child's state change** rereads its linked parent - **Child edits** count as a snapshot change **UI:** - **Linked children nest** under a linked parent - **Other children** open with **Show sub-issues** - **Progress** (`2/6`) on row, badge, and details - **Parent meta** (`↰ #N`) on a root row - **Stale cycles** fall back to roots **MCP:** - **`list_thread_issues`** adds `subIssues`, `parent` ## Scope and approval **Fork-owned `github-issues` domain**; requested by the maintainer in the thread that did the work. ## Verification **Checks:** - `vp run check:changed origin/hyprws` → exit 1 - **11 browser files** failed on module fetch; **all pass** on rerun - `vp run fork:ci` → ok on `1843b1e` - Web and server `vp run build` → exit 0 - Server, contracts, and web typecheck → exit 0 - **62 server**, **74 web**, **6 contracts** issue tests pass **Not checked:** - **No eval run**; no issue-tool eval case exists **Grounded** in Chrome against `astral-sh/uv` fixture links; before, none of these surfaces showed sub-issues. Collapsed: **progress** and **linked children nested**.  Expanded: **Show sub-issues** lists the rest.  Root child: **parent meta**.  Badge hover: **progress** in the mini list.  Details panel: **progress** on the issue row.  Claude Opus 5.5 via Claude Code, in T3 Code. ## Fork trailers Squashes: - c3c6084144 feat(github-issues): linked issues nest and track their sub-issues (#2024) (#2024) - 16f839c3ae feat(github-issues): linked issues expand, collapse, and show type and labels (#2025) (#2025) Fork-Domain: github-issues Fork-Tier: qol Co-authored-by: donjor <[email protected]>
rsi-software-agent Bot
pushed a commit
that referenced
this pull request
Nov 12, 2026
…2024) ## Problem A thread that links a **parent or tracker issue** shows **no sub-issue progress** or hierarchy. Agents reading `list_thread_issues` **cannot see the children** either. ## Change **Snapshot:** - **Adds `subIssues` and `parent`** - **Keys omitted** when empty - **Optional fields**; old snapshots still decode **Sync:** - **Same GraphQL read**; no extra request - **Deleted the second read** for child close reasons - **One issue URL parser**, shared from contracts - **A child's state change** rereads its linked parent - **Child edits** count as a snapshot change **UI:** - **Linked children nest** under a linked parent - **Other children** open with **Show sub-issues** - **Progress** (`2/6`) on row, badge, and details - **Parent meta** (`↰ #N`) on a root row - **Stale cycles** fall back to roots **MCP:** - **`list_thread_issues`** adds `subIssues`, `parent` ## Scope and approval **Fork-owned `github-issues` domain**; requested by the maintainer in the thread that did the work. ## Verification **Checks:** - `vp run check:changed origin/hyprws` → exit 1 - **11 browser files** failed on module fetch; **all pass** on rerun - `vp run fork:ci` → ok on `1843b1e` - Web and server `vp run build` → exit 0 - Server, contracts, and web typecheck → exit 0 - **62 server**, **74 web**, **6 contracts** issue tests pass **Not checked:** - **No eval run**; no issue-tool eval case exists **Grounded** in Chrome against `astral-sh/uv` fixture links; before, none of these surfaces showed sub-issues. Collapsed: **progress** and **linked children nested**.  Expanded: **Show sub-issues** lists the rest.  Root child: **parent meta**.  Badge hover: **progress** in the mini list.  Details panel: **progress** on the issue row.  Claude Opus 5.5 via Claude Code, in T3 Code. ## Fork trailers Squashes: - c3c6084144 feat(github-issues): linked issues nest and track their sub-issues (#2024) (#2024) - 16f839c3ae feat(github-issues): linked issues expand, collapse, and show type and labels (#2025) (#2025) Fork-Domain: github-issues Fork-Tier: qol Co-authored-by: donjor <[email protected]>
rsi-software-agent Bot
pushed a commit
that referenced
this pull request
Nov 12, 2026
…2024) ## Problem A thread that links a **parent or tracker issue** shows **no sub-issue progress** or hierarchy. Agents reading `list_thread_issues` **cannot see the children** either. ## Change **Snapshot:** - **Adds `subIssues` and `parent`** - **Keys omitted** when empty - **Optional fields**; old snapshots still decode **Sync:** - **Same GraphQL read**; no extra request - **Deleted the second read** for child close reasons - **One issue URL parser**, shared from contracts - **A child's state change** rereads its linked parent - **Child edits** count as a snapshot change **UI:** - **Linked children nest** under a linked parent - **Other children** open with **Show sub-issues** - **Progress** (`2/6`) on row, badge, and details - **Parent meta** (`↰ #N`) on a root row - **Stale cycles** fall back to roots **MCP:** - **`list_thread_issues`** adds `subIssues`, `parent` ## Scope and approval **Fork-owned `github-issues` domain**; requested by the maintainer in the thread that did the work. ## Verification **Checks:** - `vp run check:changed origin/hyprws` → exit 1 - **11 browser files** failed on module fetch; **all pass** on rerun - `vp run fork:ci` → ok on `1843b1e` - Web and server `vp run build` → exit 0 - Server, contracts, and web typecheck → exit 0 - **62 server**, **74 web**, **6 contracts** issue tests pass **Not checked:** - **No eval run**; no issue-tool eval case exists **Grounded** in Chrome against `astral-sh/uv` fixture links; before, none of these surfaces showed sub-issues. Collapsed: **progress** and **linked children nested**.  Expanded: **Show sub-issues** lists the rest.  Root child: **parent meta**.  Badge hover: **progress** in the mini list.  Details panel: **progress** on the issue row.  Claude Opus 5.5 via Claude Code, in T3 Code. ## Fork trailers Squashes: - c3c6084144 feat(github-issues): linked issues nest and track their sub-issues (#2024) (#2024) - 16f839c3ae feat(github-issues): linked issues expand, collapse, and show type and labels (#2025) (#2025) Fork-Domain: github-issues Fork-Tier: qol Co-authored-by: donjor <[email protected]>
rsi-software-agent Bot
pushed a commit
that referenced
this pull request
Nov 12, 2026
…2024) ## Problem A thread that links a **parent or tracker issue** shows **no sub-issue progress** or hierarchy. Agents reading `list_thread_issues` **cannot see the children** either. ## Change **Snapshot:** - **Adds `subIssues` and `parent`** - **Keys omitted** when empty - **Optional fields**; old snapshots still decode **Sync:** - **Same GraphQL read**; no extra request - **Deleted the second read** for child close reasons - **One issue URL parser**, shared from contracts - **A child's state change** rereads its linked parent - **Child edits** count as a snapshot change **UI:** - **Linked children nest** under a linked parent - **Other children** open with **Show sub-issues** - **Progress** (`2/6`) on row, badge, and details - **Parent meta** (`↰ #N`) on a root row - **Stale cycles** fall back to roots **MCP:** - **`list_thread_issues`** adds `subIssues`, `parent` ## Scope and approval **Fork-owned `github-issues` domain**; requested by the maintainer in the thread that did the work. ## Verification **Checks:** - `vp run check:changed origin/hyprws` → exit 1 - **11 browser files** failed on module fetch; **all pass** on rerun - `vp run fork:ci` → ok on `1843b1e` - Web and server `vp run build` → exit 0 - Server, contracts, and web typecheck → exit 0 - **62 server**, **74 web**, **6 contracts** issue tests pass **Not checked:** - **No eval run**; no issue-tool eval case exists **Grounded** in Chrome against `astral-sh/uv` fixture links; before, none of these surfaces showed sub-issues. Collapsed: **progress** and **linked children nested**.  Expanded: **Show sub-issues** lists the rest.  Root child: **parent meta**.  Badge hover: **progress** in the mini list.  Details panel: **progress** on the issue row.  Claude Opus 5.5 via Claude Code, in T3 Code. ## Fork trailers Squashes: - c3c6084144 feat(github-issues): linked issues nest and track their sub-issues (#2024) (#2024) - 16f839c3ae feat(github-issues): linked issues expand, collapse, and show type and labels (#2025) (#2025) Fork-Domain: github-issues Fork-Tier: qol Co-authored-by: donjor <[email protected]>
rsi-software-agent Bot
pushed a commit
that referenced
this pull request
Nov 12, 2026
…2024) ## Problem A thread that links a **parent or tracker issue** shows **no sub-issue progress** or hierarchy. Agents reading `list_thread_issues` **cannot see the children** either. ## Change **Snapshot:** - **Adds `subIssues` and `parent`** - **Keys omitted** when empty - **Optional fields**; old snapshots still decode **Sync:** - **Same GraphQL read**; no extra request - **Deleted the second read** for child close reasons - **One issue URL parser**, shared from contracts - **A child's state change** rereads its linked parent - **Child edits** count as a snapshot change **UI:** - **Linked children nest** under a linked parent - **Other children** open with **Show sub-issues** - **Progress** (`2/6`) on row, badge, and details - **Parent meta** (`↰ #N`) on a root row - **Stale cycles** fall back to roots **MCP:** - **`list_thread_issues`** adds `subIssues`, `parent` ## Scope and approval **Fork-owned `github-issues` domain**; requested by the maintainer in the thread that did the work. ## Verification **Checks:** - `vp run check:changed origin/hyprws` → exit 1 - **11 browser files** failed on module fetch; **all pass** on rerun - `vp run fork:ci` → ok on `1843b1e` - Web and server `vp run build` → exit 0 - Server, contracts, and web typecheck → exit 0 - **62 server**, **74 web**, **6 contracts** issue tests pass **Not checked:** - **No eval run**; no issue-tool eval case exists **Grounded** in Chrome against `astral-sh/uv` fixture links; before, none of these surfaces showed sub-issues. Collapsed: **progress** and **linked children nested**.  Expanded: **Show sub-issues** lists the rest.  Root child: **parent meta**.  Badge hover: **progress** in the mini list.  Details panel: **progress** on the issue row.  Claude Opus 5.5 via Claude Code, in T3 Code. ## Fork trailers Squashes: - c3c6084144 feat(github-issues): linked issues nest and track their sub-issues (#2024) (#2024) - 16f839c3ae feat(github-issues): linked issues expand, collapse, and show type and labels (#2025) (#2025) Fork-Domain: github-issues Fork-Tier: qol Co-authored-by: donjor <[email protected]>
rsi-software-agent Bot
pushed a commit
that referenced
this pull request
Nov 13, 2026
…2024) ## Problem A thread that links a **parent or tracker issue** shows **no sub-issue progress** or hierarchy. Agents reading `list_thread_issues` **cannot see the children** either. ## Change **Snapshot:** - **Adds `subIssues` and `parent`** - **Keys omitted** when empty - **Optional fields**; old snapshots still decode **Sync:** - **Same GraphQL read**; no extra request - **Deleted the second read** for child close reasons - **One issue URL parser**, shared from contracts - **A child's state change** rereads its linked parent - **Child edits** count as a snapshot change **UI:** - **Linked children nest** under a linked parent - **Other children** open with **Show sub-issues** - **Progress** (`2/6`) on row, badge, and details - **Parent meta** (`↰ #N`) on a root row - **Stale cycles** fall back to roots **MCP:** - **`list_thread_issues`** adds `subIssues`, `parent` ## Scope and approval **Fork-owned `github-issues` domain**; requested by the maintainer in the thread that did the work. ## Verification **Checks:** - `vp run check:changed origin/hyprws` → exit 1 - **11 browser files** failed on module fetch; **all pass** on rerun - `vp run fork:ci` → ok on `1843b1e` - Web and server `vp run build` → exit 0 - Server, contracts, and web typecheck → exit 0 - **62 server**, **74 web**, **6 contracts** issue tests pass **Not checked:** - **No eval run**; no issue-tool eval case exists **Grounded** in Chrome against `astral-sh/uv` fixture links; before, none of these surfaces showed sub-issues. Collapsed: **progress** and **linked children nested**.  Expanded: **Show sub-issues** lists the rest.  Root child: **parent meta**.  Badge hover: **progress** in the mini list.  Details panel: **progress** on the issue row.  Claude Opus 5.5 via Claude Code, in T3 Code. ## Fork trailers Squashes: - c3c6084144 feat(github-issues): linked issues nest and track their sub-issues (#2024) (#2024) - 16f839c3ae feat(github-issues): linked issues expand, collapse, and show type and labels (#2025) (#2025) Fork-Domain: github-issues Fork-Tier: qol Co-authored-by: donjor <[email protected]>
rsi-software-agent Bot
pushed a commit
that referenced
this pull request
Nov 13, 2026
…2024) ## Problem A thread that links a **parent or tracker issue** shows **no sub-issue progress** or hierarchy. Agents reading `list_thread_issues` **cannot see the children** either. ## Change **Snapshot:** - **Adds `subIssues` and `parent`** - **Keys omitted** when empty - **Optional fields**; old snapshots still decode **Sync:** - **Same GraphQL read**; no extra request - **Deleted the second read** for child close reasons - **One issue URL parser**, shared from contracts - **A child's state change** rereads its linked parent - **Child edits** count as a snapshot change **UI:** - **Linked children nest** under a linked parent - **Other children** open with **Show sub-issues** - **Progress** (`2/6`) on row, badge, and details - **Parent meta** (`↰ #N`) on a root row - **Stale cycles** fall back to roots **MCP:** - **`list_thread_issues`** adds `subIssues`, `parent` ## Scope and approval **Fork-owned `github-issues` domain**; requested by the maintainer in the thread that did the work. ## Verification **Checks:** - `vp run check:changed origin/hyprws` → exit 1 - **11 browser files** failed on module fetch; **all pass** on rerun - `vp run fork:ci` → ok on `1843b1e` - Web and server `vp run build` → exit 0 - Server, contracts, and web typecheck → exit 0 - **62 server**, **74 web**, **6 contracts** issue tests pass **Not checked:** - **No eval run**; no issue-tool eval case exists **Grounded** in Chrome against `astral-sh/uv` fixture links; before, none of these surfaces showed sub-issues. Collapsed: **progress** and **linked children nested**.  Expanded: **Show sub-issues** lists the rest.  Root child: **parent meta**.  Badge hover: **progress** in the mini list.  Details panel: **progress** on the issue row.  Claude Opus 5.5 via Claude Code, in T3 Code. ## Fork trailers Squashes: - c3c6084144 feat(github-issues): linked issues nest and track their sub-issues (#2024) (#2024) - 16f839c3ae feat(github-issues): linked issues expand, collapse, and show type and labels (#2025) (#2025) Fork-Domain: github-issues Fork-Tier: qol Co-authored-by: donjor <[email protected]>
rsi-software-agent Bot
pushed a commit
that referenced
this pull request
Nov 13, 2026
…2024) ## Problem A thread that links a **parent or tracker issue** shows **no sub-issue progress** or hierarchy. Agents reading `list_thread_issues` **cannot see the children** either. ## Change **Snapshot:** - **Adds `subIssues` and `parent`** - **Keys omitted** when empty - **Optional fields**; old snapshots still decode **Sync:** - **Same GraphQL read**; no extra request - **Deleted the second read** for child close reasons - **One issue URL parser**, shared from contracts - **A child's state change** rereads its linked parent - **Child edits** count as a snapshot change **UI:** - **Linked children nest** under a linked parent - **Other children** open with **Show sub-issues** - **Progress** (`2/6`) on row, badge, and details - **Parent meta** (`↰ #N`) on a root row - **Stale cycles** fall back to roots **MCP:** - **`list_thread_issues`** adds `subIssues`, `parent` ## Scope and approval **Fork-owned `github-issues` domain**; requested by the maintainer in the thread that did the work. ## Verification **Checks:** - `vp run check:changed origin/hyprws` → exit 1 - **11 browser files** failed on module fetch; **all pass** on rerun - `vp run fork:ci` → ok on `1843b1e` - Web and server `vp run build` → exit 0 - Server, contracts, and web typecheck → exit 0 - **62 server**, **74 web**, **6 contracts** issue tests pass **Not checked:** - **No eval run**; no issue-tool eval case exists **Grounded** in Chrome against `astral-sh/uv` fixture links; before, none of these surfaces showed sub-issues. Collapsed: **progress** and **linked children nested**.  Expanded: **Show sub-issues** lists the rest.  Root child: **parent meta**.  Badge hover: **progress** in the mini list.  Details panel: **progress** on the issue row.  Claude Opus 5.5 via Claude Code, in T3 Code. ## Fork trailers Squashes: - c3c6084144 feat(github-issues): linked issues nest and track their sub-issues (#2024) (#2024) - 16f839c3ae feat(github-issues): linked issues expand, collapse, and show type and labels (#2025) (#2025) Fork-Domain: github-issues Fork-Tier: qol Co-authored-by: donjor <[email protected]>
rsi-software-agent Bot
pushed a commit
that referenced
this pull request
Nov 13, 2026
…2024) ## Problem A thread that links a **parent or tracker issue** shows **no sub-issue progress** or hierarchy. Agents reading `list_thread_issues` **cannot see the children** either. ## Change **Snapshot:** - **Adds `subIssues` and `parent`** - **Keys omitted** when empty - **Optional fields**; old snapshots still decode **Sync:** - **Same GraphQL read**; no extra request - **Deleted the second read** for child close reasons - **One issue URL parser**, shared from contracts - **A child's state change** rereads its linked parent - **Child edits** count as a snapshot change **UI:** - **Linked children nest** under a linked parent - **Other children** open with **Show sub-issues** - **Progress** (`2/6`) on row, badge, and details - **Parent meta** (`↰ #N`) on a root row - **Stale cycles** fall back to roots **MCP:** - **`list_thread_issues`** adds `subIssues`, `parent` ## Scope and approval **Fork-owned `github-issues` domain**; requested by the maintainer in the thread that did the work. ## Verification **Checks:** - `vp run check:changed origin/hyprws` → exit 1 - **11 browser files** failed on module fetch; **all pass** on rerun - `vp run fork:ci` → ok on `1843b1e` - Web and server `vp run build` → exit 0 - Server, contracts, and web typecheck → exit 0 - **62 server**, **74 web**, **6 contracts** issue tests pass **Not checked:** - **No eval run**; no issue-tool eval case exists **Grounded** in Chrome against `astral-sh/uv` fixture links; before, none of these surfaces showed sub-issues. Collapsed: **progress** and **linked children nested**.  Expanded: **Show sub-issues** lists the rest.  Root child: **parent meta**.  Badge hover: **progress** in the mini list.  Details panel: **progress** on the issue row.  Claude Opus 5.5 via Claude Code, in T3 Code. ## Fork trailers Squashes: - c3c6084144 feat(github-issues): linked issues nest and track their sub-issues (#2024) (#2024) - 16f839c3ae feat(github-issues): linked issues expand, collapse, and show type and labels (#2025) (#2025) Fork-Domain: github-issues Fork-Tier: qol Co-authored-by: donjor <[email protected]>
rsi-software-agent Bot
pushed a commit
that referenced
this pull request
Nov 14, 2026
…2024) ## Problem A thread that links a **parent or tracker issue** shows **no sub-issue progress** or hierarchy. Agents reading `list_thread_issues` **cannot see the children** either. ## Change **Snapshot:** - **Adds `subIssues` and `parent`** - **Keys omitted** when empty - **Optional fields**; old snapshots still decode **Sync:** - **Same GraphQL read**; no extra request - **Deleted the second read** for child close reasons - **One issue URL parser**, shared from contracts - **A child's state change** rereads its linked parent - **Child edits** count as a snapshot change **UI:** - **Linked children nest** under a linked parent - **Other children** open with **Show sub-issues** - **Progress** (`2/6`) on row, badge, and details - **Parent meta** (`↰ #N`) on a root row - **Stale cycles** fall back to roots **MCP:** - **`list_thread_issues`** adds `subIssues`, `parent` ## Scope and approval **Fork-owned `github-issues` domain**; requested by the maintainer in the thread that did the work. ## Verification **Checks:** - `vp run check:changed origin/hyprws` → exit 1 - **11 browser files** failed on module fetch; **all pass** on rerun - `vp run fork:ci` → ok on `1843b1e` - Web and server `vp run build` → exit 0 - Server, contracts, and web typecheck → exit 0 - **62 server**, **74 web**, **6 contracts** issue tests pass **Not checked:** - **No eval run**; no issue-tool eval case exists **Grounded** in Chrome against `astral-sh/uv` fixture links; before, none of these surfaces showed sub-issues. Collapsed: **progress** and **linked children nested**.  Expanded: **Show sub-issues** lists the rest.  Root child: **parent meta**.  Badge hover: **progress** in the mini list.  Details panel: **progress** on the issue row.  Claude Opus 5.5 via Claude Code, in T3 Code. ## Fork trailers Squashes: - c3c6084144 feat(github-issues): linked issues nest and track their sub-issues (#2024) (#2024) - 16f839c3ae feat(github-issues): linked issues expand, collapse, and show type and labels (#2025) (#2025) Fork-Domain: github-issues Fork-Tier: qol Co-authored-by: donjor <[email protected]>
rsi-software-agent Bot
pushed a commit
that referenced
this pull request
Nov 14, 2026
…2024) ## Problem A thread that links a **parent or tracker issue** shows **no sub-issue progress** or hierarchy. Agents reading `list_thread_issues` **cannot see the children** either. ## Change **Snapshot:** - **Adds `subIssues` and `parent`** - **Keys omitted** when empty - **Optional fields**; old snapshots still decode **Sync:** - **Same GraphQL read**; no extra request - **Deleted the second read** for child close reasons - **One issue URL parser**, shared from contracts - **A child's state change** rereads its linked parent - **Child edits** count as a snapshot change **UI:** - **Linked children nest** under a linked parent - **Other children** open with **Show sub-issues** - **Progress** (`2/6`) on row, badge, and details - **Parent meta** (`↰ #N`) on a root row - **Stale cycles** fall back to roots **MCP:** - **`list_thread_issues`** adds `subIssues`, `parent` ## Scope and approval **Fork-owned `github-issues` domain**; requested by the maintainer in the thread that did the work. ## Verification **Checks:** - `vp run check:changed origin/hyprws` → exit 1 - **11 browser files** failed on module fetch; **all pass** on rerun - `vp run fork:ci` → ok on `1843b1e` - Web and server `vp run build` → exit 0 - Server, contracts, and web typecheck → exit 0 - **62 server**, **74 web**, **6 contracts** issue tests pass **Not checked:** - **No eval run**; no issue-tool eval case exists **Grounded** in Chrome against `astral-sh/uv` fixture links; before, none of these surfaces showed sub-issues. Collapsed: **progress** and **linked children nested**.  Expanded: **Show sub-issues** lists the rest.  Root child: **parent meta**.  Badge hover: **progress** in the mini list.  Details panel: **progress** on the issue row.  Claude Opus 5.5 via Claude Code, in T3 Code. ## Fork trailers Squashes: - c3c6084144 feat(github-issues): linked issues nest and track their sub-issues (#2024) (#2024) - 16f839c3ae feat(github-issues): linked issues expand, collapse, and show type and labels (#2025) (#2025) Fork-Domain: github-issues Fork-Tier: qol Co-authored-by: donjor <[email protected]>
rsi-software-agent Bot
pushed a commit
that referenced
this pull request
Nov 14, 2026
…2024) ## Problem A thread that links a **parent or tracker issue** shows **no sub-issue progress** or hierarchy. Agents reading `list_thread_issues` **cannot see the children** either. ## Change **Snapshot:** - **Adds `subIssues` and `parent`** - **Keys omitted** when empty - **Optional fields**; old snapshots still decode **Sync:** - **Same GraphQL read**; no extra request - **Deleted the second read** for child close reasons - **One issue URL parser**, shared from contracts - **A child's state change** rereads its linked parent - **Child edits** count as a snapshot change **UI:** - **Linked children nest** under a linked parent - **Other children** open with **Show sub-issues** - **Progress** (`2/6`) on row, badge, and details - **Parent meta** (`↰ #N`) on a root row - **Stale cycles** fall back to roots **MCP:** - **`list_thread_issues`** adds `subIssues`, `parent` ## Scope and approval **Fork-owned `github-issues` domain**; requested by the maintainer in the thread that did the work. ## Verification **Checks:** - `vp run check:changed origin/hyprws` → exit 1 - **11 browser files** failed on module fetch; **all pass** on rerun - `vp run fork:ci` → ok on `1843b1e` - Web and server `vp run build` → exit 0 - Server, contracts, and web typecheck → exit 0 - **62 server**, **74 web**, **6 contracts** issue tests pass **Not checked:** - **No eval run**; no issue-tool eval case exists **Grounded** in Chrome against `astral-sh/uv` fixture links; before, none of these surfaces showed sub-issues. Collapsed: **progress** and **linked children nested**.  Expanded: **Show sub-issues** lists the rest.  Root child: **parent meta**.  Badge hover: **progress** in the mini list.  Details panel: **progress** on the issue row.  Claude Opus 5.5 via Claude Code, in T3 Code. ## Fork trailers Squashes: - c3c6084144 feat(github-issues): linked issues nest and track their sub-issues (#2024) (#2024) - 16f839c3ae feat(github-issues): linked issues expand, collapse, and show type and labels (#2025) (#2025) Fork-Domain: github-issues Fork-Tier: qol Co-authored-by: donjor <[email protected]>
rsi-software-agent Bot
pushed a commit
that referenced
this pull request
Nov 14, 2026
…2024) ## Problem A thread that links a **parent or tracker issue** shows **no sub-issue progress** or hierarchy. Agents reading `list_thread_issues` **cannot see the children** either. ## Change **Snapshot:** - **Adds `subIssues` and `parent`** - **Keys omitted** when empty - **Optional fields**; old snapshots still decode **Sync:** - **Same GraphQL read**; no extra request - **Deleted the second read** for child close reasons - **One issue URL parser**, shared from contracts - **A child's state change** rereads its linked parent - **Child edits** count as a snapshot change **UI:** - **Linked children nest** under a linked parent - **Other children** open with **Show sub-issues** - **Progress** (`2/6`) on row, badge, and details - **Parent meta** (`↰ #N`) on a root row - **Stale cycles** fall back to roots **MCP:** - **`list_thread_issues`** adds `subIssues`, `parent` ## Scope and approval **Fork-owned `github-issues` domain**; requested by the maintainer in the thread that did the work. ## Verification **Checks:** - `vp run check:changed origin/hyprws` → exit 1 - **11 browser files** failed on module fetch; **all pass** on rerun - `vp run fork:ci` → ok on `1843b1e` - Web and server `vp run build` → exit 0 - Server, contracts, and web typecheck → exit 0 - **62 server**, **74 web**, **6 contracts** issue tests pass **Not checked:** - **No eval run**; no issue-tool eval case exists **Grounded** in Chrome against `astral-sh/uv` fixture links; before, none of these surfaces showed sub-issues. Collapsed: **progress** and **linked children nested**.  Expanded: **Show sub-issues** lists the rest.  Root child: **parent meta**.  Badge hover: **progress** in the mini list.  Details panel: **progress** on the issue row.  Claude Opus 5.5 via Claude Code, in T3 Code. ## Fork trailers Squashes: - c3c6084144 feat(github-issues): linked issues nest and track their sub-issues (#2024) (#2024) - 16f839c3ae feat(github-issues): linked issues expand, collapse, and show type and labels (#2025) (#2025) Fork-Domain: github-issues Fork-Tier: qol Co-authored-by: donjor <[email protected]>
rsi-software-agent Bot
pushed a commit
that referenced
this pull request
Nov 15, 2026
…2024) ## Problem A thread that links a **parent or tracker issue** shows **no sub-issue progress** or hierarchy. Agents reading `list_thread_issues` **cannot see the children** either. ## Change **Snapshot:** - **Adds `subIssues` and `parent`** - **Keys omitted** when empty - **Optional fields**; old snapshots still decode **Sync:** - **Same GraphQL read**; no extra request - **Deleted the second read** for child close reasons - **One issue URL parser**, shared from contracts - **A child's state change** rereads its linked parent - **Child edits** count as a snapshot change **UI:** - **Linked children nest** under a linked parent - **Other children** open with **Show sub-issues** - **Progress** (`2/6`) on row, badge, and details - **Parent meta** (`↰ #N`) on a root row - **Stale cycles** fall back to roots **MCP:** - **`list_thread_issues`** adds `subIssues`, `parent` ## Scope and approval **Fork-owned `github-issues` domain**; requested by the maintainer in the thread that did the work. ## Verification **Checks:** - `vp run check:changed origin/hyprws` → exit 1 - **11 browser files** failed on module fetch; **all pass** on rerun - `vp run fork:ci` → ok on `1843b1e` - Web and server `vp run build` → exit 0 - Server, contracts, and web typecheck → exit 0 - **62 server**, **74 web**, **6 contracts** issue tests pass **Not checked:** - **No eval run**; no issue-tool eval case exists **Grounded** in Chrome against `astral-sh/uv` fixture links; before, none of these surfaces showed sub-issues. Collapsed: **progress** and **linked children nested**.  Expanded: **Show sub-issues** lists the rest.  Root child: **parent meta**.  Badge hover: **progress** in the mini list.  Details panel: **progress** on the issue row.  Claude Opus 5.5 via Claude Code, in T3 Code. ## Fork trailers Squashes: - c3c6084144 feat(github-issues): linked issues nest and track their sub-issues (#2024) (#2024) - 16f839c3ae feat(github-issues): linked issues expand, collapse, and show type and labels (#2025) (#2025) Fork-Domain: github-issues Fork-Tier: qol Co-authored-by: donjor <[email protected]>
rsi-software-agent Bot
pushed a commit
that referenced
this pull request
Nov 15, 2026
…2024) ## Problem A thread that links a **parent or tracker issue** shows **no sub-issue progress** or hierarchy. Agents reading `list_thread_issues` **cannot see the children** either. ## Change **Snapshot:** - **Adds `subIssues` and `parent`** - **Keys omitted** when empty - **Optional fields**; old snapshots still decode **Sync:** - **Same GraphQL read**; no extra request - **Deleted the second read** for child close reasons - **One issue URL parser**, shared from contracts - **A child's state change** rereads its linked parent - **Child edits** count as a snapshot change **UI:** - **Linked children nest** under a linked parent - **Other children** open with **Show sub-issues** - **Progress** (`2/6`) on row, badge, and details - **Parent meta** (`↰ #N`) on a root row - **Stale cycles** fall back to roots **MCP:** - **`list_thread_issues`** adds `subIssues`, `parent` ## Scope and approval **Fork-owned `github-issues` domain**; requested by the maintainer in the thread that did the work. ## Verification **Checks:** - `vp run check:changed origin/hyprws` → exit 1 - **11 browser files** failed on module fetch; **all pass** on rerun - `vp run fork:ci` → ok on `1843b1e` - Web and server `vp run build` → exit 0 - Server, contracts, and web typecheck → exit 0 - **62 server**, **74 web**, **6 contracts** issue tests pass **Not checked:** - **No eval run**; no issue-tool eval case exists **Grounded** in Chrome against `astral-sh/uv` fixture links; before, none of these surfaces showed sub-issues. Collapsed: **progress** and **linked children nested**.  Expanded: **Show sub-issues** lists the rest.  Root child: **parent meta**.  Badge hover: **progress** in the mini list.  Details panel: **progress** on the issue row.  Claude Opus 5.5 via Claude Code, in T3 Code. ## Fork trailers Squashes: - c3c6084144 feat(github-issues): linked issues nest and track their sub-issues (#2024) (#2024) - 16f839c3ae feat(github-issues): linked issues expand, collapse, and show type and labels (#2025) (#2025) Fork-Domain: github-issues Fork-Tier: qol Co-authored-by: donjor <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The Linked issues panel shows no issue type or labels.
Sub-issues sit behind a Show sub-issues button, with no way to collapse a tree.
Change
Snapshot:
labelsandissueType; same GraphQL readUI:
MCP:
list_thread_issuesaddsissueType,labelsScope and approval
Fork-owned
github-issuesdomain; requested by the maintainer as the follow-up to #2024.Verification
Checks:
vp run check:changed origin/hyprws→ exit 0vp run fork:ci→ ok on3144270vp run build→ exit 0Not checked:
Grounded in Chrome with fixture links:
biomejs/biome#4726,biomejs/biome#5242,astral-sh/uv#18506.Before, the panel looked like the #2024 captures.
Expanded: linked
#5242nests under#4726with its type and labels.Collapsed: progress and chips stay on the row.
Claude Opus 5.5 via Claude Code, in T3 Code.
Fork trailers
Fork-Domain: github-issues
Fork-Tier: qol