Give curator activity visibility: which curators are registered, when each last ran, what it changed, and why. Background agents mutating memory unobserved is the failure mode this epic most needs to avoid.
Acceptance Criteria
Registered curators, their schedule state, and their recent activity are inspectable at runtime. Each recorded action carries enough context to answer why it happened. Surfaced through the existing observability paths rather than a bespoke channel.
Notes
Half-built: the data this needs already exists but nothing surfaces it. internal/domain/curator/registry.go has Health(ctx) map[string]Health and Names() []string; every pass emits an Action (At/Type/Detail/Reason) and a run event through the curator's EventSink. daemon.Daemon.Curators *curator.Registry (internal/daemon/daemon.go:107-110) holds the live registry. But grep confirms no webui/API/dashboard code reads any of it -- internal/webui has zero curator-aware endpoints, ui/src has no curator surface. This issue is 'wire the existing Registry.Health/Names + action history into the existing observability paths (health endpoint / dashboard)', not 'build the data model from scratch'.
Close reason
Wired GET /api/curators (names, health, last-run, recent actions) backed by a new bounded in-memory activity tracker in internal/domain/curator, plus a Curators dashboard page at ui/src/curators/.
Imported from beads archie-core-1786637489932-6-1f803e02 · GitHub #27 · type feature · priority P2 · created 2026-08-08 · closed 2026-08-27
Give curator activity visibility: which curators are registered, when each last ran, what it changed, and why. Background agents mutating memory unobserved is the failure mode this epic most needs to avoid.
### Acceptance Criteria
Registered curators, their schedule state, and their recent activity are inspectable at runtime. Each recorded action carries enough context to answer why it happened. Surfaced through the existing observability paths rather than a bespoke channel.
### Notes
Half-built: the data this needs already exists but nothing surfaces it. internal/domain/curator/registry.go has Health(ctx) map[string]Health and Names() []string; every pass emits an Action (At/Type/Detail/Reason) and a run event through the curator's EventSink. daemon.Daemon.Curators *curator.Registry (internal/daemon/daemon.go:107-110) holds the live registry. But grep confirms no webui/API/dashboard code reads any of it -- internal/webui has zero curator-aware endpoints, ui/src has no curator surface. This issue is 'wire the existing Registry.Health/Names + action history into the existing observability paths (health endpoint / dashboard)', not 'build the data model from scratch'.
### Close reason
Wired GET /api/curators (names, health, last-run, recent actions) backed by a new bounded in-memory activity tracker in internal/domain/curator, plus a Curators dashboard page at ui/src/curators/.
---
_Imported from beads `archie-core-1786637489932-6-1f803e02` · GitHub #27 · type feature · priority P2 · created 2026-08-08 · closed 2026-08-27_
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.
Give curator activity visibility: which curators are registered, when each last ran, what it changed, and why. Background agents mutating memory unobserved is the failure mode this epic most needs to avoid.
Acceptance Criteria
Registered curators, their schedule state, and their recent activity are inspectable at runtime. Each recorded action carries enough context to answer why it happened. Surfaced through the existing observability paths rather than a bespoke channel.
Notes
Half-built: the data this needs already exists but nothing surfaces it. internal/domain/curator/registry.go has Health(ctx) map[string]Health and Names() []string; every pass emits an Action (At/Type/Detail/Reason) and a run event through the curator's EventSink. daemon.Daemon.Curators *curator.Registry (internal/daemon/daemon.go:107-110) holds the live registry. But grep confirms no webui/API/dashboard code reads any of it -- internal/webui has zero curator-aware endpoints, ui/src has no curator surface. This issue is 'wire the existing Registry.Health/Names + action history into the existing observability paths (health endpoint / dashboard)', not 'build the data model from scratch'.
Close reason
Wired GET /api/curators (names, health, last-run, recent actions) backed by a new bounded in-memory activity tracker in internal/domain/curator, plus a Curators dashboard page at ui/src/curators/.
Imported from beads
archie-core-1786637489932-6-1f803e02· GitHub #27 · type feature · priority P2 · created 2026-08-08 · closed 2026-08-27