ARCHITECTURE.md's plugin engine rule (around 'plugin-engine-rule-strict') states every typed engine family owning resources 'must expose start, health, and stop semantics.' PR #882 deleted Health from internal/tools/provider.Engine (and Registry.Health/safeHealth) because nothing consumed it in production -- the mcp and builtin providers manage real subprocess/tool state but no longer report health at all. memory and curator engine families still comply with rule #3. Either update rule #3 to describe tools/provider as an accepted exception (no consumer exists yet), or decide whether tool-provider health should eventually feed something (e.g. the /status PRD's phase 2, docs/prds/status-health-surface.md) and re-add Engine.Health wired to a real consumer at that point. Do not re-add unreachable Health surface speculatively.
Close reason
Verified: fixed in code or doc/file no longer exists (see burndown 2026-10-13)
Imported from beads archie-core-jnx6 · GitHub #955 · type chore · priority P3 · created 2026-09-19 · closed 2026-10-12
ARCHITECTURE.md's plugin engine rule (around 'plugin-engine-rule-strict') states every typed engine family owning resources 'must expose start, health, and stop semantics.' PR #882 deleted Health from internal/tools/provider.Engine (and Registry.Health/safeHealth) because nothing consumed it in production -- the mcp and builtin providers manage real subprocess/tool state but no longer report health at all. memory and curator engine families still comply with rule #3. Either update rule #3 to describe tools/provider as an accepted exception (no consumer exists yet), or decide whether tool-provider health should eventually feed something (e.g. the /status PRD's phase 2, docs/prds/status-health-surface.md) and re-add Engine.Health wired to a real consumer at that point. Do not re-add unreachable Health surface speculatively.
### Close reason
Verified: fixed in code or doc/file no longer exists (see burndown 2026-10-13)
---
_Imported from beads `archie-core-jnx6` · GitHub #955 · type chore · priority P3 · created 2026-09-19 · closed 2026-10-12_
sam
added the lowchore labels 2026-10-27 13:40:14 +00:00
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.
ARCHITECTURE.md's plugin engine rule (around 'plugin-engine-rule-strict') states every typed engine family owning resources 'must expose start, health, and stop semantics.' PR #882 deleted Health from internal/tools/provider.Engine (and Registry.Health/safeHealth) because nothing consumed it in production -- the mcp and builtin providers manage real subprocess/tool state but no longer report health at all. memory and curator engine families still comply with rule #3. Either update rule #3 to describe tools/provider as an accepted exception (no consumer exists yet), or decide whether tool-provider health should eventually feed something (e.g. the /status PRD's phase 2, docs/prds/status-health-surface.md) and re-add Engine.Health wired to a real consumer at that point. Do not re-add unreachable Health surface speculatively.
Close reason
Verified: fixed in code or doc/file no longer exists (see burndown 2026-10-13)
Imported from beads
archie-core-jnx6· GitHub #955 · type chore · priority P3 · created 2026-09-19 · closed 2026-10-12