ls-cron-orchestrator

To automate repo-local cron tasks from a manifest, define triggers and ordered tasks in a YAML manifest, then run the install command to generate a crontab fragment and a Python-based runner that executes tasks in sequence.

Scheduling nightly maintenance deterministically from a repository is best achieved by defining manifest-driven triggers and ordered tasks, which generates reproducible cron fragments and a Python runner respecting sequence_order and enabled flags.

Yes, you can use a YAML manifest to enable or disable specific scheduled tasks by toggling their enabled flags, and the Python-based runner will skip disabled tasks while executing the active ones in their specified sequence_order.

To add or remove tasks from an existing cron workflow manifest, use the dedicated add-task and remove-task commands, which automatically update the manifest and regenerate the Python runner and cron fragments accordingly.

A manifest-driven cron scheduler works by centralizing trigger definitions and task sequences into a single auditable YAML file, unlike standard crontab management which relies on manual entries and lacks built-in sequence_order enforcement.

A limitation of using a Python runner for cron task automation is the dependency on Python and the yaml library in the execution environment, which must be present for the runner to parse manifests and process scheduled triggers.