Erosika e4cdd8d9ad fix(honcho): delegate the config.yaml timeout read to load_config_readonly ... The staleness check's bespoke mtime memo keyed only on the user config.yaml, but load_config() merges the managed-scope config (HERMES_MANAGED_DIR/config.yaml, /etc/hermes) whose leaf keys win. A managed honcho.timeout with no user config.yaml made the memo cache 'no timeout' while _build resolved the managed value — the same perpetual-rebuild mismatch this PR fixes for honcho.json. A managed timeout edit was likewise invisible while the user file's mtime stayed put. load_config_readonly() is already cached on both files' signatures plus the env-ref snapshot, so use it instead of duplicating that invalidation logic; the defensive deepcopy the old memo existed to avoid is skipped by the readonly variant. Drive the rebuild test through a real config.yaml and add a HERMES_MANAGED_DIR regression test covering stable reuse and managed-timeout edits.		2026-07-17 13:20:16 -07:00
..
__init__.py
test_async_memory.py
test_cli.py
test_client.py
test_empty_profile_hint.py
test_oauth.py
test_oauth_flow.py
test_pin_peer_name.py
test_query_rewrite.py
test_session.py