Wire cron engine: app/archied composition, sink adapter, Start/Stop lifecycle #780
Notifications
Due Date
No due date set.
Depends on
Reference: sam/archie#780
Reference in new issue
Block a user
Composition slice that connects the four siblings: instantiates the ticker engine in
internal/app/archied/over the job store and the router, with the configuredEngineConfigfrom the translator; registers it with the daemon's existing Start/Stop lifecycle (Start on boot, bounded-during Stop) and wires the events-bus sink so emittedKindJobRun/KindJobErrorevents reach the bus subjects the rest of the system already listens on.This is the last bead before the epic's acceptance scenario — daily-status-summary cron, persists across restarts, dangerous commands refused — is end-to-end runnable by a fresh operator.
Acceptance criteria
engine.Startcalled during daemon boot, with the configured interval.engine.Stop(ctx)called during daemon shutdown, bounded by the same grace deadline the rest of the daemon uses (matchestaskrun/workflow engine shutdown pattern).scheduling.Sinkadapts to the events bus emitter so dashboard / dashboard timeline surfaces running and failed jobs with the sameKind/Detail/Datashape the rest of the system uses.Close reason
setupScheduling wires store+router+engine with Start at boot (bootstrap.go:1708) and bounded Stop via addCleanup; cronevents bus sink; TestSetupScheduling* green. Epic-level e2e acceptance still gated on .3/.4
Imported from beads
archie-core-1786637496320-249-be6d9a20.6· GitHub #675 · type feature · priority P2 · created 2026-08-27 · closed 2026-09-18