<!-- event: create author: LocalTicketBackend at: 2026-06-08T13:22:30Z -->

## 作成

LocalTicketBackend によって作成されました。

---

<!-- event: plan author: intake at: 2026-06-09T00:16:33Z -->

## 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` も検討する。

---

<!-- event: intake_summary author: intake at: 2026-06-09T00:16:38Z -->

## 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 可能。

---

<!-- event: state_changed author: intake at: 2026-06-09T00:16:38Z from: planning to: ready reason: intake_ready field: workflow_state -->

## State changed

Intake refinement により、意図・受け入れ条件・binding decisions / invariants・implementation latitude・escalation conditions が揃ったため ready に遷移します。

---

<!-- event: decision author: hare at: 2026-06-09T01:00:46Z -->

## 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.

---

<!-- event: state_changed author: workspace-panel at: 2026-06-09T01:14:14Z from: ready to: queued reason: queued field: workflow_state -->

## State changed

Ticket を `workspace-panel` が queued にしました。


---

<!-- event: decision author: orchestrator at: 2026-06-09T01:14:47Z -->

## 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.

---

<!-- event: state_changed author: orchestrator at: 2026-06-09T01:19:38Z from: queued to: inprogress reason: orchestrator_acceptance field: workflow_state -->

## 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.

---

<!-- event: decision author: orchestrator at: 2026-06-09T01:19:38Z -->

## 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.

---

<!-- event: implementation_report author: orchestrator at: 2026-06-09T01:20:28Z -->

## Implementation report

Implementation routing started after the previously blocking policy branch was merged and cleaned up.

Worktree/branch:
- Worktree: `.worktree/deprecate-umbrella-tickets`
- Branch: `deprecate-umbrella-tickets`
- Base/routing commit: `8db8d7d ticket: route umbrella deprecation`

Spawned sibling Coder Pod:
- `coder-deprecate-umbrella-tickets`
- Scope: non-recursive read on parent workspace root plus recursive write limited to the child worktree.

Routing context:
- `orchestrator-return-to-planning-context-policy` is merged, validated, closed, and cleaned up.
- This Ticket is now the active routed policy/workflow implementation work.

---

<!-- event: implementation_report author: orchestrator at: 2026-06-09T01:33:23Z -->

## Implementation report

Coder implementation completed and is ready for sibling review.

Coder Pod:
- `coder-deprecate-umbrella-tickets`
- Commit: `1349a75 ticket: deprecate umbrella containers`
- Worktree status before review: clean branch `deprecate-umbrella-tickets`
- Stopped after collecting output to reclaim delegated worktree scope.

Implementation summary:
- Updated workflow/docs guidance to deprecate long-lived umbrella/progress-container Tickets.
- Clarified that Tickets should be concrete work items implementable/reviewable/validatable/closable on their own terms.
- Added broad-request split guidance: create concrete Tickets, record split decisions, use Objective context for medium-term strategy, and keep future typed relations non-hierarchical.
- Prohibited parent/child, sub-ticket, umbrella, part-of, contains, and similar hierarchy/container relation substitutes.
- Preserved the carve-out for initial concrete planning/design/investigation Tickets.
- Added existing-umbrella retirement guidance: close as superseded/decomposed once concrete follow-up Tickets and Objective context exist, with a resolution that lists completed concrete work and remaining follow-ups.
- Recorded a migration/close recommendation on `workspace-panel-orchestrator-queue-automation`.

Changed files:
- `docs/development/work-items.md`
- `.yoi/workflow/ticket-intake-workflow.md`
- `.yoi/workflow/ticket-orchestrator-routing.md`
- `.yoi/workflow/ticket-preflight-workflow.md`
- `.yoi/workflow/multi-agent-workflow.md`
- `.yoi/tickets/open/20260607-020215-workspace-panel-orchestrator-queue-automation/thread.md`

Coder validation reported passed:
- Focused text validation for umbrella/progress-container deprecation, hierarchy-relation prohibition, concrete planning carve-out, and existing umbrella retirement guidance.
- `git diff --check`
- `cargo run -q -p yoi -- ticket doctor`
- `nix build .#yoi`

Coder did not run `cargo check --workspace` because only docs/workflow/Ticket thread files changed.

---

<!-- event: review author: reviewer at: 2026-06-09T01:36:52Z status: approve -->

## Review: approve

Reviewed commit `1349a75` (`ticket: deprecate umbrella containers`) against the Ticket invariants.

Evidence checked:

- Changed files are limited to maintained docs/workflow guidance plus the requested migration note thread: `docs/development/work-items.md`, `.yoi/workflow/{ticket-intake-workflow,ticket-orchestrator-routing,ticket-preflight-workflow,multi-agent-workflow}.md`, and `.yoi/tickets/open/20260607-020215-workspace-panel-orchestrator-queue-automation/thread.md`.
- `docs/development/work-items.md` now defines Tickets as concrete work items that can be implemented/reviewed/validated/closed independently, disallows new broad umbrella/progress-container Tickets, explicitly forbids parent/child, sub-ticket, umbrella, part-of, contains, and hierarchy/container substitutes, preserves the carve-out for concrete planning/design/investigation Tickets, and documents superseded/decomposed retirement guidance for existing umbrellas.
- Intake/Planning workflow guidance now avoids creating umbrella/progress-container Tickets and hierarchy/container relations during split/refinement while still allowing concrete investigation/design/planning Tickets when requested.
- Orchestrator routing guidance now routes broad splits to concrete implementable Tickets / Objective context / split decision records, includes existing umbrella retirement/close-resolution guidance, and disallows hierarchy/container substitutes.
- `multi-agent-workflow` clarifies that Pod delegation and multi-Ticket coordination are not Ticket hierarchy and should use concrete Tickets plus Objective/non-hierarchical relation context.
- `workspace-panel-orchestrator-queue-automation` has an explicit migration/close recommendation saying to close the existing umbrella as superseded/decomposed once concrete follow-up Tickets/Objectives are confirmed, and that this does not implement backend schema, workflow_state, Objective records, or typed relations.
- Focused grep over maintained docs/workflows found no conflicting active umbrella/parent-child guidance outside historical Ticket records/artifacts.

Validation run:

- `git diff --check 1349a75^ 1349a75` passed.
- `cargo run -q -p yoi -- ticket doctor` passed (`doctor: ok`).
- Focused text validation for umbrella deprecation, hierarchy prohibition, concrete planning carve-out, existing umbrella retirement guidance, and the queue-automation migration note passed.
- `nix build .#yoi` passed.

Decision: approve. The implementation satisfies the documentation/workflow policy cleanup without introducing Objective record implementation, typed relation implementation, Ticket backend schema changes, workflow_state semantic changes, broad historical migration, or thread rewrites.

---

<!-- event: implementation_report author: orchestrator at: 2026-06-09T01:37:59Z -->

## Implementation report

Merge-ready dossier for human/orchestrator approval.

Status:
- Implementation branch: `deprecate-umbrella-tickets`
- Worktree: `.worktree/deprecate-umbrella-tickets`
- Commit under review: `1349a75 ticket: deprecate umbrella containers`
- Reviewer: `reviewer-deprecate-umbrella-tickets`
- Review result: approved; no blocking findings.

Intent / invariant check:
- Deprecates long-lived umbrella/progress-container Tickets in maintained workflow/docs guidance.
- Keeps Tickets as concrete work items that can be implemented, reviewed, validated, and closed on their own terms.
- Does not implement Objective records, typed Ticket relation metadata, backend schema changes, workflow_state semantics changes, broad historical migration, or thread rewrites.
- Preserves the carve-out for concrete planning/design/investigation Tickets when the user asks for a concrete work item.
- Prohibits hierarchy/container substitutes such as parent/child, sub-ticket, umbrella, part-of, and contains.

Implementation summary:
- Updated `docs/development/work-items.md` and workflow guidance to avoid creating new umbrella/progress-container Tickets.
- Aligned broad-request split guidance around concrete implementable Tickets, durable split decisions, Objective context, and future non-hierarchical typed relations.
- Added existing umbrella retirement guidance: close as superseded/decomposed once concrete follow-ups and Objective context exist; resolution should list completed concrete Tickets plus remaining follow-up Tickets/Objectives.
- Recorded a migration/close recommendation on `workspace-panel-orchestrator-queue-automation`, clarifying that retiring the container role does not mean all future concerns are complete.

Validation evidence:
- Coder reported pass:
  - focused text validation for umbrella/progress-container deprecation, hierarchy-relation prohibition, concrete planning carve-out, and existing umbrella retirement guidance
  - `git diff --check`
  - `cargo run -q -p yoi -- ticket doctor`
  - `nix build .#yoi`
- Reviewer independently passed:
  - `git diff --check 1349a75^ 1349a75`
  - `cargo run -q -p yoi -- ticket doctor`
  - focused text validation / grep
  - `nix build .#yoi`

Residual risks / notes:
- `cargo check --workspace` was intentionally not run because this is docs/workflow/Ticket-thread-only and `nix build .#yoi` covered package/resource integrity.
- Final merge/close/cleanup is intentionally not performed here without explicit merge approval.

---

<!-- event: state_changed author: hare at: 2026-06-09T02:04:39Z from: inprogress to: done reason: closed field: workflow_state -->

## State changed

Ticket closed; workflow_state を done に設定しました。


---

<!-- event: close author: hare at: 2026-06-09T02:04:40Z status: closed -->

## 完了

Implemented, reviewed, merged, and validated.

Summary:
- Deprecated long-lived umbrella/progress-container Tickets in maintained workflow/docs guidance.
- Clarified that Tickets should be concrete work items that can be implemented, reviewed, validated, and closed on their own terms.
- Updated broad-request split guidance to use concrete implementable Tickets, durable split decisions, Objective context, and future non-hierarchical typed relations rather than umbrella containers.
- Explicitly disallowed hierarchy/container substitutes such as parent/child, sub-ticket, umbrella, part-of, and contains.
- Preserved the carve-out for concrete planning/design/investigation Tickets.
- Added existing umbrella retirement guidance and recorded a migration/close recommendation on `workspace-panel-orchestrator-queue-automation`.

Implementation:
- Coder commit: `1349a75 ticket: deprecate umbrella containers`
- Reviewer approved with no blocking findings.
- Merge commit: `ee41ed9 merge: deprecate umbrella tickets`

Validation after merge:
- `cargo fmt --check`
- `git diff --check`
- `cargo run -q -p yoi -- ticket doctor`
- `nix build .#yoi`

`cargo check --workspace` was intentionally omitted because the merged implementation is docs/workflow/Ticket-thread-only and no Rust code/tests changed; Nix build covered package/resource integrity.

---
