Latest contest visible to the PWA runtime status endpoint.
Application scheduler
Scheduler Control
Generated from `/runtime/scheduler-status.json` with app-owned job state.
History sync, context collectors, and lakehouse build run as separate application-owned jobs.
Data Slash owns job state, next-run calculation, history, and runtime publication.
Managed jobs
Refresh jobs
Operations
Command center
Production runbook
App scheduler process
Application API
/api/scheduler/*
The GUI controls loop start, loop stop, interval changes, and job actions through the application API.
Controller state
data/scheduler/controller.json
Persists whether the scheduler loop should be running, its interval, and the last controller error.
Scheduler state
data/scheduler/state.json
Persists enabled jobs, status, last run, next run, errors, and run counts.
History log
data/scheduler/history.jsonl
Records every manual and scheduled run event with result summaries.
A process manager may still keep the application daemon alive, but scheduling decisions, timer interval, and operator actions now belong to the application control API rather than shell scripts or external timers.