yoi/.yoi/tickets/00001KTR81P9X/thread.md

作成

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

---

Decision

決定:

• pod::feature は API / contribution substrate として扱い、Plugin や MCP の権限管理を担わせない。
• Plugin は pod::feature をユーザー向け package/config/runtime 形式で使わせる層であり、Plugin permission / trust policy は Plugin layer で定義する。
• MCP は pod::feature 上に protocol-backed integration layer を構築するが、MCP server enablement / command-env-secret policy / trust boundary / MCP-specific permission は MCP layer が独自に持つ。
• MCP local stdio server の OS-level side effects は Yoi feature authority では制御できないため、feature-layer authority / grant を MCP や Plugin の permission model に流用しない。

反映:

• 00001KTR81P9X は authority ではなく provider lifecycle / dynamic contribution / normal ToolRegistry path / untrusted normalization に絞る。
• 00001KTR82RB7 は MCP 固有の explicit config と trust model を持つ。
• 00001KSXRQ4G8 と 00001KT0Z4BK8 は Plugin permission を Plugin layer として扱い、MCP を初期 Plugin packaging/runtime から分離する。

---

Intake summary

Marked ready by yoi ticket state.

---

State changed

Marked ready by yoi ticket state.

---

State changed

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

---

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.

---

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.

---

Implementation report

Implemented provider feature API for Ticket 00001KTR81P9X.

Summary:

• Extended pod::feature descriptors with ProtocolProviderDeclaration and provider lifecycle state/diagnostic reporting.
• Added ProtocolProviderContribution and FeatureInstallContext::protocol_providers() so startup-discovered provider tools, services, and background task declarations register through the existing feature install pipeline.
• Provider tools are materialized once at startup and then installed as ordinary Worker tool definitions, preserving stable schemas for the run and normal permission/history/bounded-result execution paths.
• Unavailable providers record lifecycle diagnostics and skip discovered contributions without adding a separate feature authority layer.
• Added focused tests for ready providers, failed providers, undeclared providers, and stable dynamic tool metadata.

Validation:

• PASS: cargo fmt --check
• PASS: cargo test -p pod feature::tests
• PASS: cargo check --workspace --all-targets
• PASS: git diff --check
• FAIL (pre-existing/unrelated prompt assertion): cargo test -p pod fails in prompt::catalog::tests::pod_orchestration_guidance_section_renders_resource_body and prompt::system::tests::pod_orchestration_guidance_is_included_for_pod_management_tools, both expecting the phrase worktree status, diff, and test results.
• FAIL (environment/resource): nix build --no-link .#yoi compiles through the Rust crates but fails during final binary link with No space left on device.

Risks/notes:

• This does not implement MCP protocol, MCP trust policy, plugin permissions, subprocess management, or a replacement HostAuthority-style grant layer.
• Provider metadata and diagnostics remain install-report data; actual provider tool execution goes through the normal Worker/tool machinery.

---