Repository navigation
Expand file tree
/
Copy pathissues.json
More file actions
54 lines (54 loc) · 5.48 KB
/
Copy pathissues.json
File metadata and controls
54 lines (54 loc) · 5.48 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
{
"nextId": 8,
"issues": [
{
"id": 7,
"title": "Web rail filter/status-chip/sort state resets on the first / → /task/$taskId navigation",
"status": "done",
"created": "2026-06-11",
"body": "Pre-existing structural issue surfaced by the 2026-06-11 multi-agent review of the morning web waves. The `/` route renders <AppShell/> directly while /task/$taskId renders <TaskRoute> which wraps <AppShell/> one level deeper (routes/index.tsx vs routes/task.$taskId.tsx). At the Outlet these are different component types, so opening a task from the home route unmounts+remounts AppShell, resetting TaskRail's local useState — including the new statusFilter chip, the text query, and showArchived (sortMode is partially re-applied by the prefSort effect). Task→task hops stay within /task/$taskId so they persist; only the initial open from `/` clears it. RESOLVED 2026-06-11: lifted query/statusFilter/sortMode/showArchived into lib/rail-state.ts, a module store (tabs.ts pattern). Persistence semantics decided as in-memory ONLY — survives route nav (the bug), deliberately resets on full reload (a stale text query across visits would surprise; sortMode needs no storage since the TUI ui-prefs push re-seeds it). Bonus: applyPrefSort is rising-edge (tracks last applied pref), so an AppShell remount replaying the same TUI pref no longer stomps a local web-side sort toggle — only a genuinely changed pref does. 6 unit tests lock the contract; QA'd live (1/4 filtered count survives the / → /task hop)."
},
{
"id": 5,
"title": "Job-ify ensureWorktree: long daemon operations return a job id + push progress",
"status": "done",
"created": "2026-06-09",
"body": "Follow-up to the async-ExecHost fix (commit 'fix: exec — async ExecHost run/fs ops'). The daemon's event loop no longer freezes during git worktree add, but the CALLING client still awaits the full RPC (minutes on a 30GB repo) with no feedback. Make minute-class operations (ensureWorktree, future clone) jobs: RPC returns immediately with a job id, progress/completion pushed over the existing subscribe channel, UI shows a materializing state on the task row. Job table + existing push channel — no external MQ; that was the 'daemon 要不要 MQ' answer (2026-06-09 audit)."
},
{
"id": 6,
"title": "Sink worktree-changes collection into the daemon (single collector, push to panes)",
"status": "done",
"created": "2026-06-09",
"body": "Today every pane process polls git status itself through tui/lib/background-poll.ts (N panes x M tasks background processes, work duplicated per pane). Move collection into the daemon as the single collector and broadcast results over a new subscribe channel (worktree.changes), following the task.snapshot precedent; panes drop their git subprocesses entirely and just read pushes. Depends on nothing; pairs well with the job-ification issue. From the 2026-06-09 render-path/daemon audit."
},
{
"id": 4,
"title": "Per-client tmux sessions so two clients on the same window aren't letterboxed",
"status": "open",
"created": "2026-06-02",
"body": "aggressive-resize (shipped) makes each chat-tab window track its own current viewer, but two clients viewing the SAME task+window still share one tmux grid, so the larger terminal is letterboxed to the smaller. The only way to give same-window clients independent sizes is to stop sharing one session per task: give each attached client its own session in a session group (new-session -t <group>) and rework the switch-client task-switch model (direct.ts, tasks-pane/host.tsx, app.tsx, client.ts) to switch within the client's own session set. Larger refactor; ceiling is capped by tmux (grouped sessions still share window grids), so revisit only if same-window multi-client is a real use case. Deferred from the aggressive-resize fix; user chose the small A-tier fix first."
},
{
"id": 1,
"title": "Hover tooltip can flicker when the cursor moves onto it",
"status": "open",
"created": "2026-05-31",
"body": "The v1 sidebar hover tooltip (cf1cd56) anchors just below-right of the cursor. Moving the cursor down into the tooltip's area leaves the hovered row → onMouseOut clears it → the row beneath re-pops it, so chasing it flickers. In a full-width tmux Tasks pane there's no room to the right, so below is the only anchor. Option to evaluate: a fixed detail panel pinned to the bottom of the sidebar (no cursor follow, zero flicker) instead of a floating tooltip."
},
{
"id": 2,
"title": "Hover tooltip is always-on — consider showing only when info was truncated",
"status": "open",
"created": "2026-05-31",
"body": "The tooltip pops on every row hover, including on a wide pane where the branch + full title are already visible (only the worktree path is extra). Consider gating it to fire only when the responsive columns actually dropped the branch/changes or the title was ellipsised, so a wide pane stays quiet."
},
{
"id": 3,
"title": "Optional: CI check enforcing a changeset per PR",
"status": "open",
"created": "2026-05-31",
"body": "Now that Changesets is adopted, add a CI step (changeset status gate, or the changesets/action bot) that fails a PR with user-facing code changes but no .changeset/*.md, so entries can't be forgotten. Tooling-only changes opt out with an empty changeset. Deferred from the Changesets migration to keep that change focused."
}
]
}