Cron delivery runner + router: dispatch due jobs to chat/task targets #776
Notifications
Due Date
No due date set.
Blocks
Depends on
Reference: sam/archie#776
Reference in new issue
Block a user
Slice 2 of the cron/scheduling epic (archie-core-1786637496320-249-be6d9a20). Implements
scheduling.Runnerand the router that picks one runner per job kind.Without this slice, the ticker engine has no work to dispatch. Concrete target types to ship: ChatCourier (sends a templated message through the existing channel-agnostic
channels.Channelgateway, so the channel choice stays the operator's, not the cron's) and WorkflowTask (submits aworkintakeenvelope so the existing task lifecycle owns scheduling, retries, gates, and PR opening).Job store is a hard prerequisite. Composition wiring and lifecycle guard block the wiring slice, not this one.
Acceptance criteria
Runnerimplementations:ChatCourier(renders the job's templated body through the channel layer) andWorkflowTask(submits aworkintakeenvelope carrying the cron identity and body so the existing workflow domain runs the rest).Routerthat mapsJob.Kindto a Runner; an unrecognised kind emitsKindJobErrorphase="dispatch"and is otherwise a no-op — refused at the gate, not silently dropped.ctx.Done()so the engine's bounded shutdown actually drains in flight.Notes
PR #822 opened for review (branch feat/cron-delivery-runners, commits 213c642 + 754c406). Not merged; composition wiring (slice .6) still open.
Close reason
Landed in
82b28cd(PR #822); GitHub #679 already closed.Imported from beads
archie-core-1786637496320-249-be6d9a20.2· GitHub #679 · type feature · priority P2 · created 2026-08-27 · closed 2026-09-17