ticket: close ticket intake routing umbrella

work-items/closed/20260601-031252-builtin-work-item-intake-routing/item.md

@@ -2,12 +2,12 @@
 id: 20260601-031252-builtin-work-item-intake-routing
 slug: builtin-work-item-intake-routing
 title: Built-in Ticket intake and orchestration routing
-status: open
+status: closed
 kind: task
 priority: P1
 labels: [ticket, intake, orchestration]
 created_at: 2026-06-01T03:12:52Z
-updated_at: 2026-06-05T04:04:42Z
+updated_at: 2026-06-05T06:42:40Z
 assignee: null
 legacy_ticket: null
 ---

work-items/closed/20260601-031252-builtin-work-item-intake-routing/resolution.md

@@ -0,0 +1,43 @@
+Built-in Ticket intake and orchestration routing umbrella is complete.
+
+This umbrella was split into four implementation-sized child tickets, all of which are now closed:
+
+1. `ticket-local-files-backend`
+   - Added the low-level `ticket` crate, typed Ticket domain/backend, and `LocalTicketBackend` over current `work-items/` files.
+
+2. `ticket-built-in-feature-tools`
+   - Added built-in Ticket tools through typed backend authority and the Pod feature contribution path.
+   - Kept Ticket tool behavior in `crates/ticket` and Pod as a thin feature adapter.
+
+3. `ticket-intake-workflow`
+   - Added `.yoi/workflow/ticket-intake-workflow.md` for clarifying user requests and materializing agreed Tickets after user approval.
+
+4. `ticket-orchestrator-routing`
+   - Added `.yoi/workflow/ticket-orchestrator-routing.md` for classifying Tickets into requirements sync, preflight, spike, implementation, review, blocked/action-required, close-ready, defer/pending, or no-op paths.
+
+Terminology decision:
+
+- `Ticket` is the durable orchestration record concept.
+- `Task` remains session-local progress tracking.
+- `Assignment` is concrete Pod delegation.
+- `IntentPacket` is the implementation/review contract derived from a Ticket.
+- `work-items/` remains the current LocalTicketBackend storage path for now.
+
+Scope preserved:
+
+- The storage directory was not renamed.
+- `tickets.sh` remains compatible and in use.
+- Ticket authority is separate from delegated filesystem write scope.
+- Intake does not schedule implementation.
+- Orchestrator routing does not introduce an unattended scheduler/lease/queue system.
+- TUI spawned-Pod panel work was deprioritized and is not part of this path.
+
+Validation:
+
+- Child tickets were independently reviewed and validated.
+- Final child workflow validation passed `git diff --check` and `./tickets.sh doctor`.
+- `./tickets.sh doctor` passes for the umbrella close.
+
+Historical note:
+
+Older thread entries and artifacts may contain superseded `WorkItem` or old system-name wording as historical context. The current terminology and implementation use `Ticket`.

work-items/closed/20260601-031252-builtin-work-item-intake-routing/thread.md

@@ -317,4 +317,55 @@ Added current terminology/design artifact:
 The earlier `workitem-definition-and-api-shape-20260601.md` is now explicitly marked superseded and retained only as historical context.
 
 
+---
+
+<!-- event: close author: hare at: 2026-06-05T06:42:40Z status: closed -->
+
+## Closed
+
+Built-in Ticket intake and orchestration routing umbrella is complete.
+
+This umbrella was split into four implementation-sized child tickets, all of which are now closed:
+
+1. `ticket-local-files-backend`
+   - Added the low-level `ticket` crate, typed Ticket domain/backend, and `LocalTicketBackend` over current `work-items/` files.
+
+2. `ticket-built-in-feature-tools`
+   - Added built-in Ticket tools through typed backend authority and the Pod feature contribution path.
+   - Kept Ticket tool behavior in `crates/ticket` and Pod as a thin feature adapter.
+
+3. `ticket-intake-workflow`
+   - Added `.yoi/workflow/ticket-intake-workflow.md` for clarifying user requests and materializing agreed Tickets after user approval.
+
+4. `ticket-orchestrator-routing`
+   - Added `.yoi/workflow/ticket-orchestrator-routing.md` for classifying Tickets into requirements sync, preflight, spike, implementation, review, blocked/action-required, close-ready, defer/pending, or no-op paths.
+
+Terminology decision:
+
+- `Ticket` is the durable orchestration record concept.
+- `Task` remains session-local progress tracking.
+- `Assignment` is concrete Pod delegation.
+- `IntentPacket` is the implementation/review contract derived from a Ticket.
+- `work-items/` remains the current LocalTicketBackend storage path for now.
+
+Scope preserved:
+
+- The storage directory was not renamed.
+- `tickets.sh` remains compatible and in use.
+- Ticket authority is separate from delegated filesystem write scope.
+- Intake does not schedule implementation.
+- Orchestrator routing does not introduce an unattended scheduler/lease/queue system.
+- TUI spawned-Pod panel work was deprioritized and is not part of this path.
+
+Validation:
+
+- Child tickets were independently reviewed and validated.
+- Final child workflow validation passed `git diff --check` and `./tickets.sh doctor`.
+- `./tickets.sh doctor` passes for the umbrella close.
+
+Historical note:
+
+Older thread entries and artifacts may contain superseded `WorkItem` or old system-name wording as historical context. The current terminology and implementation use `Ticket`.
+
+
 ---