Replace the inert metadata-only daemon plugin inventory with a capability host that validates plugin manifests and coordinates lifecycle without adding generic domain hooks. The host owns module identity/API compatibility/dependency ordering/start/health/stop state; typed family registries remain responsible for capability registration. Wire it into archied startup/shutdown and expose status without passing *daemon.Daemon to plugins.
Design
Keep plugin.Plugin exactly Name/Version. Add a validated Manifest and lifecycle vocabulary in internal/plugin plus a Host that manages manifests and lifecycle only. Capability packages receive narrow typed registrars; the host must not become an any-typed service locator. Start in dependency order, roll back a partially failed start, stop in reverse order, isolate panics/errors, and return immutable health snapshots. Preserve existing Yaegi loading through an adapter or manifest synthesis for metadata-only legacy plugins.
Acceptance Criteria
Manifest validation covers stable ID, semantic version, host API compatibility, declared capability kinds, dependencies, permissions, and optional config schema. Duplicate IDs, missing dependencies, cycles, incompatible API versions, and invalid manifests fail deterministically. Host lifecycle tests prove dependency-ordered start, rollback, reverse stop, health aggregation, idempotent shutdown, and panic/error isolation. archied owns one host and starts/stops it. plugin.Plugin remains metadata-only and architecture tests pass. task check and lint are green apart from explicitly identified concurrent baseline failures; fresh adversarial review has no surviving findings.
Imported from beads archie-core-1786637497847-306-524508fd · GitHub #327 · type feature · priority P2 · created 2026-08-08 · closed 2026-08-08
Replace the inert metadata-only daemon plugin inventory with a capability host that validates plugin manifests and coordinates lifecycle without adding generic domain hooks. The host owns module identity/API compatibility/dependency ordering/start/health/stop state; typed family registries remain responsible for capability registration. Wire it into archied startup/shutdown and expose status without passing *daemon.Daemon to plugins.
### Design
Keep plugin.Plugin exactly Name/Version. Add a validated Manifest and lifecycle vocabulary in internal/plugin plus a Host that manages manifests and lifecycle only. Capability packages receive narrow typed registrars; the host must not become an any-typed service locator. Start in dependency order, roll back a partially failed start, stop in reverse order, isolate panics/errors, and return immutable health snapshots. Preserve existing Yaegi loading through an adapter or manifest synthesis for metadata-only legacy plugins.
### Acceptance Criteria
Manifest validation covers stable ID, semantic version, host API compatibility, declared capability kinds, dependencies, permissions, and optional config schema. Duplicate IDs, missing dependencies, cycles, incompatible API versions, and invalid manifests fail deterministically. Host lifecycle tests prove dependency-ordered start, rollback, reverse stop, health aggregation, idempotent shutdown, and panic/error isolation. archied owns one host and starts/stops it. plugin.Plugin remains metadata-only and architecture tests pass. task check and lint are green apart from explicitly identified concurrent baseline failures; fresh adversarial review has no surviving findings.
---
_Imported from beads `archie-core-1786637497847-306-524508fd` · GitHub #327 · type feature · priority P2 · created 2026-08-08 · closed 2026-08-08_
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Replace the inert metadata-only daemon plugin inventory with a capability host that validates plugin manifests and coordinates lifecycle without adding generic domain hooks. The host owns module identity/API compatibility/dependency ordering/start/health/stop state; typed family registries remain responsible for capability registration. Wire it into archied startup/shutdown and expose status without passing *daemon.Daemon to plugins.
Design
Keep plugin.Plugin exactly Name/Version. Add a validated Manifest and lifecycle vocabulary in internal/plugin plus a Host that manages manifests and lifecycle only. Capability packages receive narrow typed registrars; the host must not become an any-typed service locator. Start in dependency order, roll back a partially failed start, stop in reverse order, isolate panics/errors, and return immutable health snapshots. Preserve existing Yaegi loading through an adapter or manifest synthesis for metadata-only legacy plugins.
Acceptance Criteria
Manifest validation covers stable ID, semantic version, host API compatibility, declared capability kinds, dependencies, permissions, and optional config schema. Duplicate IDs, missing dependencies, cycles, incompatible API versions, and invalid manifests fail deterministically. Host lifecycle tests prove dependency-ordered start, rollback, reverse stop, health aggregation, idempotent shutdown, and panic/error isolation. archied owns one host and starts/stops it. plugin.Plugin remains metadata-only and architecture tests pass. task check and lint are green apart from explicitly identified concurrent baseline failures; fresh adversarial review has no surviving findings.
Imported from beads
archie-core-1786637497847-306-524508fd· GitHub #327 · type feature · priority P2 · created 2026-08-08 · closed 2026-08-08