dpaluy e2248045f5 fix(cron): drop stale env-var override of persisted provider ... Cron jobs were passing os.getenv("HERMES_INFERENCE_PROVIDER") as the "requested" arg to resolve_runtime_provider(), which short-circuited the resolver's own precedence (explicit arg → persisted config → env) and let stale shell/.env values outrank the user's saved provider. Long-lived cron daemons inherit env from the shell that launched them, so a since-changed provider (e.g. DeepSeek) could keep firing for jobs that don't pin provider/model. Same bug class as f0b763c74 fixed for the TUI /model switch. Pass only job.get("provider") and let resolve_requested_provider fall through to persisted config and env in the documented order. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>		2026-05-04 02:31:57 -07:00
..
__init__.py	docs: clarify gateway service scopes (#1378)	2026-03-14 21:17:41 -07:00
jobs.py	fix(cron): recover null next_run_at jobs and tolerate non-dict origin	2026-05-04 01:32:58 -07:00
scheduler.py	fix(cron): drop stale env-var override of persisted provider	2026-05-04 02:31:57 -07:00