Cron delivery runner + router: dispatch due jobs to chat/task targets #776

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

Slice 2 of the cron/scheduling epic (archie-core-1786637496320-249-be6d9a20). Implements scheduling.Runner and 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.Channel gateway, so the channel choice stays the operator's, not the cron's) and WorkflowTask (submits a workintake envelope 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

  • At least two Runner implementations: ChatCourier (renders the job's templated body through the channel layer) and WorkflowTask (submits a workintake envelope carrying the cron identity and body so the existing workflow domain runs the rest).
  • A Router that maps Job.Kind to a Runner; an unrecognised kind emits KindJobError phase="dispatch" and is otherwise a no-op — refused at the gate, not silently dropped.
  • Every Runner honours ctx.Done() so the engine's bounded shutdown actually drains in flight.
  • The epic's headline scenario ('daily status summary') is exercisable end-to-end through the ChatCourier runner with a hard-coded template; the blueprints slice replaces this with parameterisation.

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

Slice 2 of the cron/scheduling epic (archie-core-1786637496320-249-be6d9a20). Implements `scheduling.Runner` and 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.Channel` gateway, so the channel choice stays the operator's, not the cron's) and WorkflowTask (submits a `workintake` envelope 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 - At least two `Runner` implementations: `ChatCourier` (renders the job's templated body through the channel layer) and `WorkflowTask` (submits a `workintake` envelope carrying the cron identity and body so the existing workflow domain runs the rest). - A `Router` that maps `Job.Kind` to a Runner; an unrecognised kind emits `KindJobError` `phase="dispatch"` and is otherwise a no-op — refused at the gate, not silently dropped. - Every Runner honours `ctx.Done()` so the engine's bounded shutdown actually drains in flight. - The epic's headline scenario ('daily status summary') is exercisable end-to-end through the ChatCourier runner with a hard-coded template; the blueprints slice replaces this with parameterisation. ### 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_
sam added the mediumfeature labels 2026-10-27 13:37:42 +00:00
sam self-assigned this 2026-10-27 13:37:42 +00:00
sam closed this issue 2026-10-27 13:37:42 +00:00
sam added a new dependency 2026-10-27 13:42:10 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Reference: sam/archie#776