nx_cron.nx

nx_cron.nx -- JOB-REGISTRY + DISPATCH-LOOP layer above the FULLY_WIRED nx_race_timing.nx primitive (sealed 8-mode timing taxonomy). Replaces /etc/crontab on Synology DSM. AUDIT-FIRST CORRECTION (2026-05-20, post-creation): user caught that I built this without checking for existing prior art. nx_race_timing.nx already ships the canonical sealed enum of 8 timing modes (MANUAL / EVENT / SCHEDULED / CONTINUOUS / IDLE / THRESHOLD / PROBABILISTIC / QUORUM) + the classifier helpers (is_reactive / needs_config / parse). My nx_cron 9-kind enum maps directly: NX_CRON_KIND_INTERVAL_SECONDS/MINUTES/HOURS -> NX_RACE_TIMING_CONTINUOUS NX_CRON_KIND_DAILY_AT_HOUR/WEEKLY_AT_DOW/MONTHLY_AT_DOM -> NX_RACE_TIMING_SCHEDULED NX_CRON_KIND_ON_EVENT -> NX_RACE_TIMING_EVENT NX_CRON_KIND_ON_DEMAND -> NX_RACE_TIMING_MANUAL NX_CRON_KIND_IDLE_OPPORTUNISTIC -> NX_RACE_TIMING_IDLE nx_cron does NOT replace nx_race_timing -- it COMPOSES against it. nx_race_timing classifies a timing mode; nx_cron registers + dispatches JOBS attached to those timing modes. Different layer: - nx_race_timing : WHAT timing mode is this? (taxonomy + classifier) - nx_cron : HOW do we run job X on schedule Y? (registry + loop) When graduated, nx_cron_register_job will call into nx_race_timing helpers (nx_race_timing_is_valid, nx_race_timing_needs_config) to validate the declared schedule before persisting the job. Also composes with the already-shipped nx_timerfd.nx for the actual fire-time wakeup. Per feedback-no-temporary-third-party-scaffolding-when-substrate-arc-exists audit-first rule: ls nxc2/runtime/ before authoring new primitives. module: nishi-core.ops.cron depends: nishi-core.race.timing + nishi-core.io.syscalls disk_kb: 5 capability: OPS wired_status: PARTIAL_WIRED WIRED (2026-06-13, W-RE-CRON-001 -- the in-memory DISPATCH CORE, gate-proven by nx_cms_schedule_gate -> a real schedule->publish): - JOB_REGISTRY (static in-memory job table; register/unregister/find