## 作成 LocalTicketBackend によって作成されました。 --- ## Plan ## Intake refinement 既存 Ticket は新規 umbrella Ticket 廃止の方針・背景・要件・受け入れ条件・非目標をすでに含んでおり、新規 Ticket 作成ではなくこの Ticket の refinement で足りる。 ### Binding decisions / invariants - 新規の長期 umbrella Ticket / progress container は作らない方針として文書化する。 - Ticket は単独で実装・レビュー・検証・完了判断できる concrete work item として扱う。 - 広い依頼の分割時は、進捗コンテナとしての umbrella を残すのではなく、concrete Tickets、Objective、typed Ticket relations、thread/decision 記録に責務を分ける。 - 既存 umbrella の退役 close は「関連作業がすべて完了した」ではなく「umbrella container の役割を退役した」ことを表す。 - `typed-ticket-relation-metadata` と `objective-records-for-medium-term-goals` の設計実装はこの Ticket の範囲外に残す。 ### Implementation latitude - 具体的な変更箇所は実装時の調査で選んでよいが、少なくとも開発/workflow docs、Intake/Planning guidance、Orchestrator guidance に umbrella Ticket を作らない・退役する方針が反映されている必要がある。 - 既存 umbrella の扱いは、代表例として `workspace-panel-orchestrator-queue-automation` に migration/close recommendation を残すか、明示的な follow-up に接続すればよい。 ### Escalation conditions - Objective または typed relation の current schema をこの作業内で設計・実装する必要が出た場合は scope creep として Orchestrator/人間判断へ戻す。 - 既存 Ticket の大量移行や historical thread rewrite が必要に見える場合は、この Ticket の非目標に反するため判断を戻す。 - umbrella 廃止方針が initial planning Ticket まで禁止する表現になりそうな場合は、受け入れ条件の「deprecated pattern is the long-lived umbrella progress container」を優先して調整する。 ### Readiness - readiness: implementation_ready - risk_flags: [ticket, workflow, documentation, planning, orchestration] - blocking open questions: none Validation は既存 acceptance criteria の通り、`target/debug/yoi ticket doctor` と `git diff --check` を含める。実装が runtime resource / prompt / package source に触れる場合は通常の repository guidance に従って `nix build .#yoi` も検討する。 --- ## Intake summary 既存 Ticket を refinement し、新規 umbrella Ticket 作成ではなくこの Ticket を concrete documentation/workflow cleanup として進める方針を確認した。新規の長期 umbrella/progress-container Ticket を非推奨化し、広い依頼は concrete Tickets、Objective、typed Ticket relations、thread/decision 記録へ責務分離する。Objective/typed relation の設計実装、大量 historical migration、thread rewrite は範囲外。blocking open question はなく、implementation_ready として Orchestrator が routing 可能。 --- ## State changed Intake refinement により、意図・受け入れ条件・binding decisions / invariants・implementation latitude・escalation conditions が揃ったため ready に遷移します。 --- ## Decision ## Decision: no hierarchy relations Umbrella Ticket deprecation also means not replacing umbrellas with Ticket hierarchy relations. Do not introduce or use these relation concepts for current Ticket work: - `parent` / `child`; - `sub-ticket`; - `umbrella`; - `part_of` / `contains` decomposition semantics. Concrete split work should become separate implementable Tickets. Medium-term context belongs in Objectives. Ticket relations should stay non-hierarchical: dependency, blocking, related, supersedes, duplicate/replacement, and similar direct relations. --- ## State changed Ticket を `workspace-panel` が queued にしました。 --- ## Decision Routing decision: defer_pending_policy_merge This Ticket is queued and appears implementation-ready, but I am intentionally not accepting it to `inprogress` yet. Reason: - There is an approved merge-ready workflow/docs branch pending: `orchestrator-return-to-planning-context-policy` at commit `8576615`. - `deprecate-umbrella-tickets` is also a workflow/docs/planning policy cleanup and is likely to touch adjacent files such as Orchestrator/Intake/Planning guidance and work-item docs. - Running it before the pending policy branch is merged or otherwise resolved would create unnecessary conflict/review risk across the same maintained policy surfaces. State decision: - Leave this Ticket `queued`. - Do not create a worktree or spawn a coder yet. Next action: - After `orchestrator-return-to-planning-context-policy` is merged/closed/cleaned up or explicitly held back, re-read this Ticket and accept it from queued if still unblocked. --- ## State changed Accepted queued implementation after re-reading the Ticket and current workspace state. The earlier deferral condition has been resolved: `orchestrator-return-to-planning-context-policy` was merged, validated, closed, and cleaned up, so there is no longer a pending adjacent policy branch blocking this work. --- ## Decision Routing decision: implementation_ready Evidence checked: - Ticket body and thread, including Intake refinement and the explicit `no hierarchy relations` decision. - Current workspace/worktree state after merging and cleaning up `orchestrator-return-to-planning-context-policy`. - Current open worktree list: no active implementation worktree remains. - The prior `defer_pending_policy_merge` blocker is resolved. Reason: - This is a bounded workflow/docs/planning policy cleanup. - It does not require implementing Objective records or typed relation metadata. - Requirements and acceptance criteria are concrete, including the migration/close recommendation for `workspace-panel-orchestrator-queue-automation`. IntentPacket: Intent: - Deprecate long-lived umbrella/progress-container Tickets and align Intake/Planning/Orchestrator/work-item guidance around concrete Tickets, Objectives, and non-hierarchical relation concepts. Binding decisions / invariants: - Do not create or endorse new umbrella Tickets for broad multi-Ticket efforts. - Tickets should be concrete work items that can be implemented, reviewed, validated, and closed on their own terms. - Splitting broad requests should produce concrete implementable Tickets and durable decision context, not parent/child or umbrella containers. - Do not introduce or use hierarchy/container relations such as parent/child, sub-ticket, umbrella, part_of, or contains as replacements. - Typed Ticket relation design/implementation remains out of scope; relation wording must stay non-hierarchical and defer implementation details to `typed-ticket-relation-metadata`. - Objective record design/implementation remains out of scope; Objective references may be conceptual/policy guidance only. - Existing umbrella Tickets may be closed as superseded/decomposed once concrete follow-up Tickets/Objective context exists; that close means the container role is retired, not that all related future concerns are complete. - Preserve the ability to create an initial concrete planning/design/investigation Ticket when the user asks for a concrete work item; the deprecated pattern is the long-lived progress container. - Do not rewrite historical thread history or migrate every historical umbrella immediately. Implementation latitude: - Update maintained workflow docs, resource prompts/workflows, and development docs narrowly. - Add or update focused validation where practical. If there is no resource-test harness, focused grep/resource validation plus `git diff --check`, `ticket doctor`, and Nix build is acceptable for docs/workflow-only changes. - For `workspace-panel-orchestrator-queue-automation`, either record a clear migration/close recommendation in that Ticket thread or create a narrow follow-up if direct closure is not appropriate. Escalate if: - The implementation requires changing Ticket backend schema/workflow states. - Objective records or typed Ticket relation metadata must be implemented to express the policy. - The wording would accidentally prohibit concrete initial planning/design/investigation Tickets. - Broad historical migration or thread rewriting appears necessary. Validation: - Focused text validation for: no new umbrella/progress-container guidance; no parent/child/sub-ticket/part_of hierarchy replacement; concrete planning Ticket carve-out preserved; existing umbrella retirement guidance present. - `git diff --check`. - `cargo run -q -p yoi -- ticket doctor` or equivalent current binary Ticket doctor. - `nix build .#yoi` if workflows/resources/docs included in package inputs are touched. ---