From af13abdaa7dae774412005ad2c056e2e019fa06a Mon Sep 17 00:00:00 2001 From: Hare Date: Mon, 8 Jun 2026 22:19:39 +0900 Subject: [PATCH] ticket: defer composer history routing --- .../item.md | 6 ++-- .../thread.md | 31 +++++++++++++++++++ 2 files changed, 35 insertions(+), 2 deletions(-) diff --git a/.yoi/tickets/open/20260601-021104-tui-composer-history-persistence/item.md b/.yoi/tickets/open/20260601-021104-tui-composer-history-persistence/item.md index 888fdabf..189e4091 100644 --- a/.yoi/tickets/open/20260601-021104-tui-composer-history-persistence/item.md +++ b/.yoi/tickets/open/20260601-021104-tui-composer-history-persistence/item.md @@ -6,10 +6,12 @@ status: open kind: task priority: P2 labels: [tui, composer, history, persistence] -workflow_state: 'ready' +workflow_state: 'queued' created_at: 2026-06-01T02:11:04Z -updated_at: '2026-06-08T13:14:53Z' +updated_at: '2026-06-08T13:19:31Z' assignee: null +queued_by: 'workspace-panel' +queued_at: '2026-06-08T13:19:06Z' --- ## Issue diff --git a/.yoi/tickets/open/20260601-021104-tui-composer-history-persistence/thread.md b/.yoi/tickets/open/20260601-021104-tui-composer-history-persistence/thread.md index 689f0731..66461969 100644 --- a/.yoi/tickets/open/20260601-021104-tui-composer-history-persistence/thread.md +++ b/.yoi/tickets/open/20260601-021104-tui-composer-history-persistence/thread.md @@ -36,3 +36,34 @@ Updated based on user direction: Intake 確認により、既存 Ticket は実装 routing 可能な状態です。未解決の blocking open question はありません。主な reviewer focus は user-data persistence 境界、private/secret 混入前提の非露出、workspace 分離、既存 TUI recall semantics の回帰防止です。 --- + + + +## State changed + +Ticket を `workspace-panel` が queued にしました。 + + +--- + + + +## Decision + +Routing decision: defer_parallel_tui_work + +This Ticket is queued and implementation-ready, but I am intentionally not accepting it to `inprogress` yet. + +Reason: +- There is already an active queued-route TUI implementation in progress: `tui-chat-markdown-table-rendering`, with Coder Pod `coder-tui-chat-markdown-table-rendering` running in `.worktree/tui-chat-markdown-table-rendering`. +- `tui-composer-history-persistence` also touches TUI composer/input behavior and likely adjacent tests/helpers. +- Running both TUI changes concurrently would raise conflict/review risk without a clear need; this Ticket can follow immediately after the table-rendering Ticket reaches merge-ready or lands. + +State decision: +- Leave this Ticket `queued`. +- Do not create a worktree or spawn a coder for it yet. + +Next action: +- Re-read this Ticket after `tui-chat-markdown-table-rendering` finishes review/merge routing, then accept it from queued if still unblocked. + +---