ticket: accept next queued batch

.yoi/tickets/00001KTR81P9X/artifacts/orchestration-plan.jsonl

@@ -0,0 +1 @@
+{"id":"orch-plan-20260614-061002-1","ticket_id":"00001KTR81P9X","kind":"accepted_plan","accepted_plan":{"summary":"Implement feature-layer dynamic provider/service lifecycle and startup dynamic tool contribution substrate after HostAuthority cleanup, preserving normal ToolRegistry/permission/history paths and leaving MCP/Plugin policy out of scope.","branch":"ticket-00001KTR81P9X-feature-provider-api","worktree":"/home/hare/Projects/yoi/.worktree/feature-provider-api","role_plan":"Coder works on pod feature API and mock provider tests; Reviewer focuses on no authority-layer regression, dynamic schema stability, permission denial path, result bounding, and provider failure diagnostics."},"author":"orchestrator","at":"2026-06-14T06:10:02Z"}

.yoi/tickets/00001KTR81P9X/item.md

@@ -1,8 +1,8 @@
 ---
 title: 'Extend pod::feature API for external protocol-backed capability providers'
-state: 'queued'
+state: 'inprogress'
 created_at: '2026-06-10T07:48:14Z'
-updated_at: '2026-06-14T06:08:25Z'
+updated_at: '2026-06-14T06:10:45Z'
 assignee: null
 readiness: 'implementation_ready'
 risk_flags: ['feature-api', 'tool-registry', 'permission-scope', 'prompt-context', 'dynamic-registry', 'service-lifecycle']

.yoi/tickets/00001KTR81P9X/thread.md

@@ -48,4 +48,37 @@ Marked ready by `yoi ticket state`.
 Ticket を `workspace-panel` が queued にしました。
 
 
+---
+
+<!-- event: decision author: orchestrator at: 2026-06-14T06:10:02Z -->
+
+## Decision
+
+Routing decision: implementation_ready
+
+Reason:
+- Ticket is queued and requirements/acceptance criteria for feature-layer provider/service lifecycle and dynamic contributions are specified.
+- Outgoing `depends_on 00001KV0SP0TY` is satisfied: HostAuthority cleanup is done and merged.
+- Relation/orchestration plan checks show no remaining blocker.
+- Scope is API/contribution substrate only; Plugin/MCP permission/trust policy remains out of scope.
+
+IntentPacket:
+- Extend `pod::feature` so protocol-backed providers can contribute startup-discovered tools/services/background lifecycle diagnostics through ordinary ToolRegistry / Worker / permission / history / bounded-result paths.
+
+Binding invariants:
+- Do not introduce `HostAuthority` or replacement feature-layer authority grants.
+- Do not implement MCP protocol/trust policy or Plugin permission policy here.
+- Dynamic schemas must be stable for a run; provider metadata/output is untrusted; tool calls must go through normal permission/history/result paths.
+
+Validation:
+- focused feature/provider tests, affected crate tests, `cargo fmt --check`, `git diff --check`, `cargo check --workspace --all-targets`, and `nix build .#yoi` if feasible.
+
+---
+
+<!-- event: state_changed author: orchestrator at: 2026-06-14T06:10:45Z from: queued to: inprogress reason: orchestrator_acceptance_unblocked field: state -->
+
+## State changed
+
+Ticket evidence, satisfied dependency on HostAuthority cleanup, relation records, orchestration plan, and clean workspace state were checked. No blockers remain; accept for implementation before worktree/spawn side effects.
+
 ---