ticket: close feature registry slice

This commit is contained in:
Keisuke Hirata 2026-06-05 07:26:40 +09:00
parent e3cb29982f
commit eea94ea4ba
No known key found for this signature in database
14 changed files with 12 additions and 2 deletions

View File

@ -2,12 +2,12 @@
id: 20260603-122317-plugin-feature-contribution-registry id: 20260603-122317-plugin-feature-contribution-registry
slug: plugin-feature-contribution-registry slug: plugin-feature-contribution-registry
title: Plugin: feature contribution registry for built-in and external capabilities title: Plugin: feature contribution registry for built-in and external capabilities
status: open status: closed
kind: feature kind: feature
priority: P1 priority: P1
labels: [plugin, registry, tools, hooks, orchestration] labels: [plugin, registry, tools, hooks, orchestration]
created_at: 2026-06-03T12:23:17Z created_at: 2026-06-03T12:23:17Z
updated_at: 2026-06-04T22:25:25Z updated_at: 2026-06-04T22:26:37Z
assignee: null assignee: null
legacy_ticket: null legacy_ticket: null
--- ---

View File

@ -0,0 +1 @@
Implemented the first Pod-layer feature contribution registry slice. Added pod::feature with descriptors, contribution registrars, host-authority model, service/background descriptor skeletons, notification/alert/diagnostic sinks, descriptor-approved contribution checks, once-materialized tool registration, and installed Task tools through the normal Worker tool path. External plugin loading, real approval resolver, full background/service runtime, and WorkItem/MCP integrations remain follow-up scope. Final external review approved. Merge validation passed: cargo test -p pod --lib feature::tests --no-fail-fast, cargo test -p pod --lib, cargo test -p llm-worker --lib, cargo fmt --check, cargo check --workspace --all-targets, ./tickets.sh doctor, git diff --check, nix build .#yoi, ./result/bin/yoi pod --help.

View File

@ -1296,4 +1296,13 @@ Commands run from `/home/hare/Projects/yoi/.worktree/plugin-feature-contribution
Residual risk is acceptable for this slice. The registry is still a skeleton for external plugins: background tasks, services, notification sinks, alert sinks, and authority grant resolution are represented but not fully connected to production host lifecycles or approval policy. That is consistent with the tickets first-slice scope as long as follow-up work does not treat this as external-plugin-ready without adding the real host policy, lifecycle, and bounded-output enforcement. Residual risk is acceptable for this slice. The registry is still a skeleton for external plugins: background tasks, services, notification sinks, alert sinks, and authority grant resolution are represented but not fully connected to production host lifecycles or approval policy. That is consistent with the tickets first-slice scope as long as follow-up work does not treat this as external-plugin-ready without adding the real host policy, lifecycle, and bounded-output enforcement.
---
<!-- event: close author: hare at: 2026-06-04T22:26:37Z status: closed -->
## Closed
Implemented the first Pod-layer feature contribution registry slice. Added pod::feature with descriptors, contribution registrars, host-authority model, service/background descriptor skeletons, notification/alert/diagnostic sinks, descriptor-approved contribution checks, once-materialized tool registration, and installed Task tools through the normal Worker tool path. External plugin loading, real approval resolver, full background/service runtime, and WorkItem/MCP integrations remain follow-up scope. Final external review approved. Merge validation passed: cargo test -p pod --lib feature::tests --no-fail-fast, cargo test -p pod --lib, cargo test -p llm-worker --lib, cargo fmt --check, cargo check --workspace --all-targets, ./tickets.sh doctor, git diff --check, nix build .#yoi, ./result/bin/yoi pod --help.
--- ---