Loading issues
Part of PAR-357.
ui/app/(app)/w/[workspace]/issues/[ref]/page.tsx):130-136).Plan (one PR, branch par-367-issue-detail, covers PAR-367, 369, 370, 371, 405; PAR-404 left as a slot):
milestone; ChildResponse gains assignee, votes, child totals and PR facts so the sub-issue tree can draw its rows and delivery track. Regenerate openapi + schema.packages/tasklie-design-system with stories.domains/issues detail screen (breadcrumb top bar, prev/next, copy link/branch, ⋯ menu with confirm, 2-column body, properties sidebar, click-to-edit title/description with autosave), sub-issues tree, timeline (relative times, collapsed event runs, description diff, copy comment link, guest sign-in), IssuePeek exported for list/board.PR open: https://github.com/ParadauxIO/taskl.ie/pull/63 (covers PAR-367, 369, 370, 371, 405). Layout, top bar, properties column, click-to-edit, guest view done.
✅ Decision (Rían, 2026-10-17): community voting stays prominent. This overrides the "shrink voting to a small chip" suggestion in the description. Don't keep the bulky Reddit-style box either. Instead, use a compact vote button (▲ count, filled when you've voted) in the issue header beside the title. Show voter avatars on hover, and show the vote count in the properties sidebar. Guests who click it get the sign-in prompt (PAR-397).