Design: docs/prds/extensions-center.md#config-backed-enablement. Add typed enabled bool fields per family config element (e.g. MCPServer.Enabled), default true for anything already configured so no upgrade silently disables an existing entry. Core capabilities get no such field at all -- structural non-disableability, not a runtime check that could be bypassed. Typed fields, not a generic map, so tools/docsgen keeps generating from them. config.example.toml documents each new field and its default.
Acceptance criteria
Each optional family's config struct has a typed Enabled field with documented default. No enable/disable field exists on any core-capability config type. docs:check passes with the new fields.
Notes
Suggested council lens: lens-contract (config field is a wire contract tools/docsgen generates from).
Close reason
Superseded by docs/prds/store.md:3-5, which states that the approved Store PRD supersedes docs/prds/extensions-center.md; per-family Enabled fields from the old Extensions design are no longer approved scope.
Imported from beads archie-core-1786637490708-35-38424ead.2 · GitHub #930 · type task · priority P2 · created 2026-09-19 · closed 2026-09-29
Design: docs/prds/extensions-center.md#config-backed-enablement. Add typed enabled bool fields per family config element (e.g. MCPServer.Enabled), default true for anything already configured so no upgrade silently disables an existing entry. Core capabilities get no such field at all -- structural non-disableability, not a runtime check that could be bypassed. Typed fields, not a generic map, so tools/docsgen keeps generating from them. config.example.toml documents each new field and its default.
### Acceptance criteria
Each optional family's config struct has a typed Enabled field with documented default. No enable/disable field exists on any core-capability config type. docs:check passes with the new fields.
### Notes
Suggested council lens: lens-contract (config field is a wire contract tools/docsgen generates from).
### Close reason
Superseded by docs/prds/store.md:3-5, which states that the approved Store PRD supersedes docs/prds/extensions-center.md; per-family Enabled fields from the old Extensions design are no longer approved scope.
---
_Imported from beads `archie-core-1786637490708-35-38424ead.2` · GitHub #930 · type task · priority P2 · created 2026-09-19 · 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.
Design: docs/prds/extensions-center.md#config-backed-enablement. Add typed enabled bool fields per family config element (e.g. MCPServer.Enabled), default true for anything already configured so no upgrade silently disables an existing entry. Core capabilities get no such field at all -- structural non-disableability, not a runtime check that could be bypassed. Typed fields, not a generic map, so tools/docsgen keeps generating from them. config.example.toml documents each new field and its default.
Acceptance criteria
Each optional family's config struct has a typed Enabled field with documented default. No enable/disable field exists on any core-capability config type. docs:check passes with the new fields.
Notes
Suggested council lens: lens-contract (config field is a wire contract tools/docsgen generates from).
Close reason
Superseded by docs/prds/store.md:3-5, which states that the approved Store PRD supersedes docs/prds/extensions-center.md; per-family Enabled fields from the old Extensions design are no longer approved scope.
Imported from beads
archie-core-1786637490708-35-38424ead.2· GitHub #930 · type task · priority P2 · created 2026-09-19 · closed 2026-09-29