daemon: delete assigned-but-unread composition fields (Curators, CapabilityHost, ToolRegistry) #1545

Closed
opened 2026-10-27 13:40:49 +00:00 by sam · 0 comments
Owner

Three exported daemon.Daemon fields are wired by the composition root and never read anywhere: Curators (*curator.Registry), CapabilityHost (*plugin.Host), ToolRegistry (*tools.Registry). None has a production reader (grep for .Curators/.CapabilityHost/.ToolRegistry finds no field access outside the declarations), and git history shows no read ever existed. The curator registry/runtime is boot-owned (the curator isolation invariant makes curator lifecycle independent of the agent loop), the capability host is lifecycle-owned by the composition root and consumed by the control plane, and the tool registry is consumed by chat/curator/MCP wiring -- not by the daemon. The daemon package imports the plugin and curator packages solely for these dead field types. Decision: delete each field and its composition assignment, and drop the now-unused imports; the host_contract wiring test currently demands the string CapabilityHost: in the daemon composition and must be updated so it no longer enshrines the unread field. Acceptance: fields and assignments gone; scoped build/test/lint clean; no unread field remains.

Acceptance criteria

Curators/CapabilityHost/ToolRegistry fields, their composition assignments and now-unused imports are removed; daemon package builds; a guard test or documented evidence line records the per-field decision

Close reason

Shipped in f69ce1db: the assigned-but-unread Curators/CapabilityHost/ToolRegistry handles are gone from daemon.Daemon and bootstrap, with the host contract test refusing a CapabilityHost handle.


Imported from beads archie-core-r771 · GitHub #1454 · type bug · priority P2 · created 2026-10-02 · closed 2026-10-02

Three exported daemon.Daemon fields are wired by the composition root and never read anywhere: Curators (*curator.Registry), CapabilityHost (*plugin.Host), ToolRegistry (*tools.Registry). None has a production reader (grep for .Curators/.CapabilityHost/.ToolRegistry finds no field access outside the declarations), and git history shows no read ever existed. The curator registry/runtime is boot-owned (the curator isolation invariant makes curator lifecycle independent of the agent loop), the capability host is lifecycle-owned by the composition root and consumed by the control plane, and the tool registry is consumed by chat/curator/MCP wiring -- not by the daemon. The daemon package imports the plugin and curator packages solely for these dead field types. Decision: delete each field and its composition assignment, and drop the now-unused imports; the host_contract wiring test currently demands the string CapabilityHost: in the daemon composition and must be updated so it no longer enshrines the unread field. Acceptance: fields and assignments gone; scoped build/test/lint clean; no unread field remains. ### Acceptance criteria Curators/CapabilityHost/ToolRegistry fields, their composition assignments and now-unused imports are removed; daemon package builds; a guard test or documented evidence line records the per-field decision ### Close reason Shipped in f69ce1db: the assigned-but-unread Curators/CapabilityHost/ToolRegistry handles are gone from daemon.Daemon and bootstrap, with the host contract test refusing a CapabilityHost handle. --- _Imported from beads `archie-core-r771` · GitHub #1454 · type bug · priority P2 · created 2026-10-02 · closed 2026-10-02_
sam added the mediumbug labels 2026-10-27 13:40:49 +00:00
sam self-assigned this 2026-10-27 13:40:49 +00:00
sam closed this issue 2026-10-27 13:40:49 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#1545