Build an Extensions center with typed Skills, Workflows, Tools/MCP, Plugins, and Integrations inventories. Add a compiled bundled catalog whose optional capabilities are disabled by default, required core capabilities are non-disableable, configuration-backed enablement requires restart, and runtime state distinguishes available, enabled, active, degraded, skipped, and pending restart. Keep plugin.Plugin metadata-only and use family-owned controllers.
Acceptance Criteria
Extensions inventories reconcile configured, bundled, discovered, and active state truthfully. Optional bundled capabilities can be enabled or disabled through safe configuration saves; core capabilities cannot. Provider failures and capability health are visible, integrations link to Configuration, and no remote/arbitrary-URL installation path exists. Architecture guard, tests, UI build, task check, viewport inspection, and fresh adversarial review pass.
Close reason
Superseded by docs/prds/store.md:3-5, which states that the approved Store PRD supersedes docs/prds/extensions-center.md.
Imported from beads archie-core-1786637490708-35-38424ead · GitHub #56 · type feature · priority P2 · created 2026-08-08 · closed 2026-09-29
Build an Extensions center with typed Skills, Workflows, Tools/MCP, Plugins, and Integrations inventories. Add a compiled bundled catalog whose optional capabilities are disabled by default, required core capabilities are non-disableable, configuration-backed enablement requires restart, and runtime state distinguishes available, enabled, active, degraded, skipped, and pending restart. Keep plugin.Plugin metadata-only and use family-owned controllers.
### Acceptance Criteria
Extensions inventories reconcile configured, bundled, discovered, and active state truthfully. Optional bundled capabilities can be enabled or disabled through safe configuration saves; core capabilities cannot. Provider failures and capability health are visible, integrations link to Configuration, and no remote/arbitrary-URL installation path exists. Architecture guard, tests, UI build, task check, viewport inspection, and fresh adversarial review pass.
### Close reason
Superseded by docs/prds/store.md:3-5, which states that the approved Store PRD supersedes docs/prds/extensions-center.md.
---
_Imported from beads `archie-core-1786637490708-35-38424ead` · GitHub #56 · type feature · priority P2 · created 2026-08-08 · closed 2026-09-29_
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.
Build an Extensions center with typed Skills, Workflows, Tools/MCP, Plugins, and Integrations inventories. Add a compiled bundled catalog whose optional capabilities are disabled by default, required core capabilities are non-disableable, configuration-backed enablement requires restart, and runtime state distinguishes available, enabled, active, degraded, skipped, and pending restart. Keep plugin.Plugin metadata-only and use family-owned controllers.
Acceptance Criteria
Extensions inventories reconcile configured, bundled, discovered, and active state truthfully. Optional bundled capabilities can be enabled or disabled through safe configuration saves; core capabilities cannot. Provider failures and capability health are visible, integrations link to Configuration, and no remote/arbitrary-URL installation path exists. Architecture guard, tests, UI build, task check, viewport inspection, and fresh adversarial review pass.
Close reason
Superseded by docs/prds/store.md:3-5, which states that the approved Store PRD supersedes docs/prds/extensions-center.md.
Imported from beads
archie-core-1786637490708-35-38424ead· GitHub #56 · type feature · priority P2 · created 2026-08-08 · closed 2026-09-29