From 101061031cf03b6500bbf4392c1151a4c73d9e63 Mon Sep 17 00:00:00 2001 From: Hare Date: Tue, 9 Jun 2026 19:12:32 +0900 Subject: [PATCH] ticket: defer attention field cleanup routing --- .../artifacts/orchestration-plan.jsonl | 1 + .yoi/tickets/20260609-095518-001/item.md | 6 ++-- .yoi/tickets/20260609-095518-001/thread.md | 32 +++++++++++++++++++ 3 files changed, 37 insertions(+), 2 deletions(-) create mode 100644 .yoi/tickets/20260609-095518-001/artifacts/orchestration-plan.jsonl diff --git a/.yoi/tickets/20260609-095518-001/artifacts/orchestration-plan.jsonl b/.yoi/tickets/20260609-095518-001/artifacts/orchestration-plan.jsonl new file mode 100644 index 00000000..6c2cbe29 --- /dev/null +++ b/.yoi/tickets/20260609-095518-001/artifacts/orchestration-plan.jsonl @@ -0,0 +1 @@ +{"id":"orch-plan-20260609-101207-1","ticket_id":"20260609-095518-001","kind":"waiting_capacity_note","note":"Defer while `20260609-093050-001` ToolExecutionContext API migration is active. This Ticket touches Ticket schema/tool API/panel behavior and should run after the core tool execution API migration lands to avoid overlapping broad tool/Ticket surface changes.","author":"orchestrator","at":"2026-06-09T10:12:07Z"} diff --git a/.yoi/tickets/20260609-095518-001/item.md b/.yoi/tickets/20260609-095518-001/item.md index 53ba45d0..2e8af110 100644 --- a/.yoi/tickets/20260609-095518-001/item.md +++ b/.yoi/tickets/20260609-095518-001/item.md @@ -1,9 +1,11 @@ --- title: 'action_requiredとattention_requiredをTicket schemaから削除する' -state: 'ready' +state: 'queued' created_at: '2026-06-09T09:55:18Z' -updated_at: '2026-06-09T10:02:25Z' +updated_at: '2026-06-09T10:12:07Z' assignee: null +queued_by: 'workspace-panel' +queued_at: '2026-06-09T10:11:38Z' --- ## 背景 diff --git a/.yoi/tickets/20260609-095518-001/thread.md b/.yoi/tickets/20260609-095518-001/thread.md index b72b0801..bf370749 100644 --- a/.yoi/tickets/20260609-095518-001/thread.md +++ b/.yoi/tickets/20260609-095518-001/thread.md @@ -21,3 +21,35 @@ LocalTicketBackend によって作成されました。 Intake classified this Ticket as ready to queue: the purpose, schema/tool/panel/doc scope, non-goals, acceptance criteria, validation expectations, and migration/compatibility boundary are explicit enough for Orchestrator routing. --- + + + +## State changed + +Ticket を `workspace-panel` が queued にしました。 + + +--- + + + +## Decision + +Routing decision: waiting_for_active_tool_api_migration + +This Ticket is queued and appears implementation-ready, but I am intentionally not accepting it to `inprogress` yet. + +Reason: +- `20260609-093050-001` (`Tool実行にToolExecutionContextを渡す`) is already active, with Coder Pod `coder-tool-execution-context` running in `.worktree/tool-execution-context`. +- This Ticket touches Ticket schema, Ticket tool API output/input, and Panel action behavior. +- Running it in parallel with a core Tool execution API migration would create avoidable conflict across tool/Ticket surfaces and make review less reliable. + +State decision: +- Leave this Ticket `queued`. +- Do not create a worktree or spawn a coder yet. + +Next action: +- Complete and merge `20260609-093050-001` first. +- Re-read this Ticket after that lands, then accept from queued if still unblocked. + +---