v3.6.2

When two routine directories share one routine id, the daemon now loads the first in path order, skips the other with a warning naming it, and writes back to that same directory. Before, it silently loaded one copy and could write it into the other copy's directory, overwriting it.

Stop recreating a routine's routine.toml after it was deleted from disk while the daemon runs (for example by a git pull after the routine moved into a folder on another machine). Triggers, snoozes, flags, updates and the circuit breaker now refuse to write a routine whose file is gone instead of resurrecting a stale copy at its old path.