## 作成 LocalTicketBackend によって作成されました。 --- ## Plan ## Intake refinement readiness は `implementation_ready`。目的、対象 surface、非目標、受け入れ条件、検証観点がすでに具体的で、Orchestrator が routing できる。 ### Binding decisions / invariants - `TicketList` は selection / triage / backlog overview 用の bounded summary として扱い、routing / close / planning return / implementation acceptance の authority にはしない。 - 詳細判断の authority は `TicketShow ` の body/thread/artifacts とする。 - LLM-facing `TicketList` tool の default result は軽量・bounded にし、item body / thread / artifacts の詳細を漏らさない。 - CLI human output も default では巨大な JSON/Markdown を出さず、人間可読性と context safety を両立する。 - `state=all` や closed を含む一覧は特に context blow-up を起こしにくい default/max limit を持つ。 - long title / diagnostics / attention hint は bounded に切り詰める。 - Ticket backend schema、TicketShow の詳細性、Ticket relation / Objective / OrchestrationPlan の設計はこの Ticket の範囲外。 ### Implementation latitude - 1 Ticket あたりの summary field、timestamp の選択、title truncation 長、default/max limit の具体値は実装者が current UI/LLM usage を見て決めてよい。 - detail-heavy mode は必要がある場合だけ明示 opt-in として追加してよいが、default tool result は軽量に保つ。 - CLI と tool output は同じ内部 summary model を共有してもよいし、human readability のために表示整形だけ分けてもよい。 - Docs/tool description/workflow guidance の更新範囲は、`TicketList` を selection/overview 用、`TicketShow` を詳細 authority と明示するために必要な範囲に限定してよい。 ### Escalation conditions - Orchestrator が `TicketList` だけで routing authority を持つ設計に変える必要が出た場合。 - Summary を削ることで panel / CLI / role workflow の既存の必須操作が成立しなくなる場合。 - Detail-heavy mode 追加が新しい public API / plugin / capability boundary の判断を要する場合。 - `limit` / truncation の方針が Ticket identity/base32 migration Ticket と衝突し、先後関係の判断が必要になった場合。 ### Validation focus - long title truncation。 - large list の default/max limit behavior。 - `state=all` / closed を含む listing cap。 - JSON/tool output shape が bounded summary であること。 - `TicketList` output に body/thread/artifacts の本文が漏れないこと。 - CLI list output が default で巨大化しないこと。 - `target/debug/yoi ticket doctor`、focused tests、`cargo fmt --check`、`git diff --check`。コード・resource 変更が入るため完了前に `nix build .#yoi` も確認する。 Open questions: なし。 Risk flags: `tool-output`, `context-budget`, `cli-ux`, `ticket-tools`, `docs-workflows`。 Related work: `00001KTNMN02R` は Ticket/Objective ID 形式変更で非ブロッキング関連。ID 長や表示が変わっても、本 Ticket の summary/truncation 方針は canonical ID を不透明文字列として扱えば成立する。 --- ## Intake summary TicketList の default output を LLM/context に安全な bounded summary へ軽量化する concrete work item として整理済み。詳細 authority は TicketShow に残し、List は selection/overview 用とする。Open questions はなく、risk flags は tool-output / context-budget / cli-ux / ticket-tools / docs-workflows。関連する ID 形式変更 Ticket は非ブロッキングで、canonical id は不透明文字列として扱う。 --- ## State changed Intake refinement により、目的・受け入れ条件・binding decisions / invariants・implementation latitude・escalation conditions・validation focus が揃ったため、Orchestrator が routing できる ready に移行する。 --- ## State changed Ticket を `workspace-panel` が queued にしました。 --- ## Decision Routing decision: waiting_for_tool_execution_context This Ticket remains queued for now. Reason: - `00001KTNVGT8G` (`Tool実行にToolExecutionContextを渡す`) changes the core tool execution API. - This Ticket changes `TicketList`, which is an LLM tool surface and should target the stable post-migration execution context API. - Running both in parallel would create avoidable conflicts across tool schema/execution code. State decision: - Leave this Ticket `queued`. - Do not create a worktree or spawn a coder yet. Next action: - Complete and merge `00001KTNVGT8G` first. - Re-read this Ticket and accept from queued if still unblocked. --- ## State changed Accepted queued implementation under the updated parallel-capacity policy. The active ToolExecutionContext branch changes core Tool execution plumbing, while this Ticket changes the bounded TicketList output surface. There may be a small mechanical conflict around the TicketList tool implementation, but it is expected to be localized and manageable, so parallel work is preferred. --- ## Decision Routing decision: implementation_ready_parallel Updated user instruction: prefer parallel work when Tickets are independent or expected conflicts are small/manageable. Reason: - This Ticket changes `TicketList` output/tool/CLI/workflow guidance. - `00001KTNVGT8G` changes the core Tool execution context API. The overlap is expected to be a localized mechanical merge in tool execution signatures / TicketList implementation, not a design conflict. - Running this in parallel should improve throughput while preserving separate worktrees and explicit review. IntentPacket: Intent: - Make `TicketList` a lightweight bounded overview/selection surface and keep detailed authority in `TicketShow`. Binding decisions / invariants: - Default `TicketList` output must not include body/thread/artifact details. - Per-Ticket summary must be short and bounded: canonical id, title, state, minimal timestamp, and short attention/blocking hints if any. - Long titles/diagnostics must be truncated. - Default/max limits should be smaller and context-safe, especially for `state=all` / closed-inclusive listing. - Tool output is the priority for context safety; CLI should remain human-readable without huge default JSON/Markdown. - `TicketList` is not routing/close/implementation authority; Orchestrator must read `TicketShow` for decisions. - Do not change Ticket backend schema, TicketShow detail, Ticket relation/Objectives/OrchestrationPlan design. Reviewer focus: - Verify no body/thread/artifact prose leaks into list output. - Verify output remains useful for selection and backlog overview. - Verify default limits and truncation are bounded and tested. - Watch for small merge interactions with the ToolExecutionContext branch; resolve by using the new context API without expanding scope. Validation: - Focused tests for long-title truncation, large-list limits, all/closed cap, JSON/tool output shape, no body/thread leakage. - CLI list output tests. - `cargo fmt --check`, `git diff --check`, `cargo run -q -p yoi -- ticket doctor`, `cargo check --workspace`, `nix build .#yoi`. --- ## Implementation report Implementation routing started in parallel with the active ToolExecutionContext migration. Worktree/branch: - Worktree: `.worktree/ticketlist-output-lightweight` - Branch: `ticketlist-output-lightweight` - Base/routing commit: `d95b3ff ticket: route parallel ticketlist and panel work` Spawned sibling Coder Pod: - `coder-ticketlist-output-lightweight` - Scope: non-recursive read on parent workspace root plus recursive write limited to the child worktree. Parallel-routing rationale: - User asked to prefer parallel work when conflicts are absent or expected small. - Overlap with ToolExecutionContext should be localized/mechanical around tool execution signatures and TicketList implementation. - Any non-mechanical design conflict should be escalated rather than broadened. --- ## Implementation report Coder implementation completed and is ready for sibling review. Coder Pod: - `coder-ticketlist-output-lightweight` - Commit: `7368416e54609517c2252beb6ae98f73fb7935ee ticket: lighten ticket list output` - Worktree status before review: clean branch `ticketlist-output-lightweight` - Stopped after collecting output to reclaim delegated worktree scope. Summary/output design: - `TicketList` default limit is now 50, max limit 100. - JSON/tool output is a short summary only: `id`, truncated `title`, `state`, `updated_at`, and short `hints`. - Output includes `count`, `returned`, `truncated`, and `limit` metadata. - `body`, `thread`, `events`, `artifacts`, and `resolution` content are not emitted from `TicketList`. - CLI `yoi ticket list` uses the same bounded policy and adds `--limit ` with cap/truncation note. - `TicketShow` detail output is unchanged. Changed files: - `crates/ticket/src/tool.rs` - `crates/yoi/src/ticket_cli.rs` - `crates/pod/src/feature/builtin/ticket.rs` - `docs/development/work-items.md` Coder validation reported passed: - `cargo test -p ticket ticket_list_tool` - `cargo test -p yoi ticket_cli_list` - `cargo test -p yoi ticket_cli_create_list_show_comment_review_state_close_and_doctor` - `cargo fmt --check` - `git diff --check` - `cargo run -q -p yoi -- ticket doctor` - `cargo check --workspace` - `nix build .#yoi` Coder reports no conflict with the ToolExecutionContext branch. --- ## Review: approve ## Review result: approve Reviewed commit `7368416e54609517c2252beb6ae98f73fb7935ee` on branch `ticketlist-output-lightweight` in worktree `.worktree/ticketlist-output-lightweight`. ### Evidence - `TicketList` tool output is now a summary model (`state_filter`, `count`, `returned`, `truncated`, `limit`, `tickets`) where each ticket contains only `id`, truncated `title`, `state`, `updated_at`, and optional short `hints`. - `TicketList` does not serialize item body, thread/events, artifacts, or resolution content. The focused leak test creates sentinel body/thread/artifact/resolution strings and asserts none appear in list output, and also asserts forbidden keys are absent from each ticket entry. - Limits are bounded with default `50` and max `100`; tests cover default truncation, excessive requested limit capping, and `all`/`closed` default cap behavior. - Long title and hint truncation are covered for the LLM-facing tool output and CLI title truncation is covered separately. - CLI `yoi ticket list` is a bounded tabular overview with `--limit` and a truncation note that points users to `yoi ticket show ` for details; it does not dump Markdown/JSON bodies by default. - `TicketShow` remains detailed: tool `TicketShow` still returns bounded body, recent thread events, artifact metadata, relations, and resolution; CLI `show` remains the detailed Markdown-oriented output. - Tool descriptions and `docs/development/work-items.md` now explicitly state List is overview/selection and Show is the detailed authority before routing/close/planning/implementation decisions. - No Ticket backend schema, relation, Objective, or OrchestrationPlan design changes were found in the reviewed diff. ### Validation run - `cargo test -p ticket ticket_list_tool` — passed (`4` tests). - `cargo test -p yoi ticket_cli_list` — passed (`2` tests). - `cargo test -p yoi ticket_cli_create_list_show_comment_review_state_close_and_doctor` — passed. - `cargo test -p ticket ticket_tools_create_list_show_and_doctor` — passed. - `cargo fmt --check` — passed. - `git diff --check` — passed. - `cargo run -q -p yoi -- ticket doctor` — passed (`doctor: ok`). - `cargo check --workspace` — passed. - `nix build .#yoi` — passed. - Manual CLI smoke check: `cargo run -q -p yoi -- ticket list --state all --limit 3` returned only `state/id/title/updated_at/hints` rows plus a truncation note. ### Residual risks - If the parallel ToolExecutionContext branch lands first, final merge may need a small mechanical adaptation around tool execution plumbing, but this implementation's TicketList data-shape and policy are sound. - CLI `--limit 0` is parsed as zero while the tool clamps limits to at least one; this is not a context-safety or leakage issue and is not blocking for this Ticket's requirements. --- ## Review: approve Review result: approve Evidence: - `TicketList` tool output is a bounded overview model with `state_filter`, `count`, `returned`, `truncated`, `limit`, and `tickets`. - Each ticket entry includes only `id`, truncated `title`, `state`, `updated_at`, and short `hints`. - `body`, `thread/events`, `artifacts`, and `resolution` content are not emitted from `TicketList`. - Sentinel tests verify body/thread/artifact/resolution strings do not leak into list output and forbidden detailed keys are absent from entries. - Default limit is 50 and max limit is 100, including `state=all` / closed-inclusive listing tests. - Long title and hint truncation are tested; CLI title truncation and truncation note are covered. - CLI `yoi ticket list` remains a bounded table and points detailed use to `yoi ticket show `. - `TicketShow` remains detailed and includes body, recent thread events, artifact metadata, relations, and resolution. - Docs/tool descriptions preserve `List = overview/selection` and `Show = detailed authority`. - No Ticket backend schema, TicketRelation, Objective, or OrchestrationPlan design change was introduced. Reviewer validation: - `cargo test -p ticket ticket_list_tool` - `cargo test -p yoi ticket_cli_list` - `cargo test -p yoi ticket_cli_create_list_show_comment_review_state_close_and_doctor` - `cargo test -p ticket ticket_tools_create_list_show_and_doctor` - `cargo fmt --check` - `git diff --check` - `cargo run -q -p yoi -- ticket doctor` - `cargo check --workspace` - `nix build .#yoi` - manual CLI smoke: `cargo run -q -p yoi -- ticket list --state all --limit 3` All passed. Residual note: if ToolExecutionContext lands first, final merge may need mechanical API adjustment around tool execution plumbing. This does not affect the bounded TicketList output policy. --- ## State changed Ticket を closed にしました。 --- ## 完了 Implemented, reviewed, merged, and validated. Summary: - Made `TicketList` a lightweight bounded overview/selection surface. - Default/max limit is bounded; output includes short metadata such as canonical id, truncated title, state, updated timestamp, and hints. - Tool output includes count/returned/truncated/limit metadata. - `body`, thread/event text, artifact content/details, and resolution content are not emitted from `TicketList`. - CLI `yoi ticket list` uses the same bounded policy and `--limit` support. - `TicketShow` remains the detailed authority for routing/implementation/close decisions. Implementation: - Coder commit: `7368416 ticket: lighten ticket list output` - Reviewer approved with no blocking findings. - Merge commit: `b6ac36e merge: lighten ticket list output` - Follow-up mechanical fix after ToolExecutionContext landed: `f2cdb6f fix: align ticket list tests with tool context` Validation after merge: - `cargo test -p ticket ticket_list_tool` - `cargo test -p yoi ticket_cli_list` - `cargo test -p yoi ticket_cli_create_list_show_comment_review_state_close_and_doctor` - `cargo test -p ticket ticket_tools_create_list_show_and_doctor` - `cargo fmt --check` - `git diff --check` - `cargo run -q -p yoi -- ticket doctor` - `cargo check --workspace` - `nix build .#yoi` ---