Replacing Legacy Cron Jobs with Oneshot systemd Timers
Pairing a Type=oneshot service with OnUnitActiveSec=60s guarantees that the next interval is measured after the previous run completes rather than firing blindly on wall-clock boundaries.
Adding an explicit advisory lock via flock protects manual CLI invocations from racing with scheduled timer runs.