fix(honcho): extend local client timeout

[DomGrieco]

Summary

• increase the Honcho SDK timeout to 300 seconds for local/self-hosted Honcho base URLs only
• keep the existing default timeout behavior for cloud Honcho unchanged
• add a focused unit test covering the local timeout override

Why

Local/self-hosted Honcho deployments can take longer than the SDK's default 60 second HTTP timeout for dialectic-style calls. When Hermes is pointed at a localhost/127.0.0.1 Honcho instance, this can cause Hermes to give up before Honcho responds even though the local server is still working.

This change keeps the scope narrow:

• only applies when Hermes has already classified the resolved Honcho base URL as local
• does not change cloud Honcho behavior
• uses the Honcho SDK's existing timeout= parameter rather than introducing Hermes-specific retry logic

Test Plan

• /Users/dgrieco/.hermes/hermes-agent/venv/bin/python -m py_compile plugins/memory/honcho/client.py tests/honcho_plugin/test_client.py
• /Users/dgrieco/.hermes/hermes-agent/venv/bin/python -m pytest tests/honcho_plugin/test_client.py -q

[himanshikothari30]

I am still learning, but I noticed that some checks are failing. Maybe we should fix them before merging.

[DomGrieco]

I am still learning, but I noticed that some checks are failing. Maybe we should fix them before merging.

These failures come from other upstream changes, not related to the changes introduced in this PR.

[teknium1]

Thanks for the focused local-Honcho fix. Current main still gives an unconfigured loopback client the generic 30-second default at plugins/memory/honcho/client.py:859-862, so the underlying local-timeout concern remains relevant.

Problems

• The proposed unconditional timeout=300.0 assignment predates current timeout precedence. Main resolves explicit timeout settings from Honcho config/environment at plugins/memory/honcho/client.py:460-464 and config.yaml at :842-855; a salvage should not overwrite an operator-supplied local timeout.
• The new test patches the optional honcho module without the availability guard used by neighboring construction tests at tests/honcho_plugin/test_client.py:614-617.

Suggested changes

• Apply the loopback value only as the unresolved default, before the existing generic fallback at plugins/memory/honcho/client.py:859-862; preserve explicit values.
• Cover loopback default, explicit loopback override, and cloud default, using the existing SDK skip convention.

Automated hermes-sweeper review.

[teknium1]

Superseded by configuration: after #66052 (commit b170f52) merged #57437 by @liuhao1024 and #61675 by @Elektrofussel, self-hosted users can set a long timeout in config.yaml (honcho.timeout) and it now takes effect live in long-lived processes — and local-host detection covers LAN/VPN addresses, not just localhost. That covers the slow-local-model case this PR targeted without a hardcoded blanket 300s override. Your diagnosis that local dialectic calls can exceed 60s was right and informed the direction — thanks @DomGrieco!