dev-task-scheduler

Cross-platform scheduled task management uses a vault-backed registry as the single source of truth. This registry stores task schedules, enabled flags, and prompts, then installs corresponding entries directly into macOS launchd or Linux cron to prevent sprawl.

A registry-first approach for task scheduling loads the central vault registry before creating, updating, or removing tasks. This enforces idempotent writes and prevents duplicate scheduled tasks or conflicts across macOS launchd and Linux cron.

To add a cron job without duplicates, provide the task name, schedule, and description to register it in the vault registry. The system performs idempotent writes and duplicate name detection to safely install the OS scheduler entry without overlap.

Yes, cross-platform task scheduling supports installing OS scheduler entries from the registry for Windows schtasks, in addition to macOS launchd and Linux cron, ensuring broad automation coverage across operating systems.

To clean up stale disabled tasks, use the lifecycle flow to enable, disable, or remove tasks, which includes automated safety checks. This ensures the OS scheduler remains synchronized with the vault registry and prevents sprawl.

Updating recurring automations without checking the registry first risks creating duplicates and conflicts. The system enforces registry-first mutations, requiring the vault to be loaded before any create, update, or remove action to ensure idempotent writes.