b1663edf2a
hermes-cron-tick.service starts without TELEGRAM_HOME_CHANNEL/DISCORD_HOME_CHANNEL in the unit env; the per-run load_hermes_dotenv reload lived only on the agent path (after the no_agent short-circuit returns), so every deliver=telegram/all script job failed with 'no delivery target resolved'. Load the dotenv at the top of the no_agent branch; override=False keeps the gateway's in-process tick behavior unchanged.