Two additional CI failures surfaced when the first PR ran through GHA —
both were pre-existing but blocked merge.
1) tests/cron/test_scheduler.py::TestRunJobWakeGate (3 tests)
run_job calls resolve_runtime_provider BEFORE constructing AIAgent, so
patching run_agent.AIAgent alone isn't enough — the resolver raises
'No inference provider configured' in hermetic CI (no API keys) and
the test never reaches the mocked AIAgent. Added autouse fixture
that stubs resolve_runtime_provider with a fake openrouter runtime.
2) tests/hermes_cli/test_update_check.py::test_get_update_result_timeout
Observed on CI: assert 4950 is None. A background update-check
thread (from an earlier test or hermes_cli.main's own
prefetch_update_check call) raced a real git-fetch result
(4950 commits behind origin/main) into banner._update_result during
this test's wait(0.1). Wrap the test in patch.object(banner,
'check_for_updates', return_value=None) so any in-flight thread
writes None rather than a real value.
Validation:
Under CI-parity env (env -i, no creds): 6/6 pass
Broader suite (tests/hermes_cli + cron + gateway + run_agent/streaming
+ toolsets + discord_tool): 6033 passed, pre-existing failures in
telegram_approval_buttons (3) and internal_event_bypass_pairing (1)
are unrelated.
ad4680cf74