Summary

The gateway cache signature only fingerprints Honcho peer-mapping fields today, but HonchoSessionManager freezes a wider config subset at init. As a result, some honcho.json edits are ignored until an unrelated cache eviction or restart rebuilds the cached agent.

This patch extends the Honcho cache-busting subset to include the manager-scoped settings that are baked into HonchoSessionManager construction, and adds regression coverage for those settings.

Problem

HonchoSessionManager snapshots settings like:

• contextTokens
• writeFrequency
• dialecticReasoningLevel
• dialecticDynamic
• dialecticMaxChars
• observation-derived booleans
• messageMaxChars
• dialecticMaxInputChars

But the gateway cache signature only covered peer routing / identity fields. That meant editing those manager-scoped settings in honcho.json would not take effect on the next gateway message if the cached agent was reused.

Fix

Extend GatewayRunner._extract_cache_busting_config() to fingerprint the manager-scoped Honcho settings that are frozen by HonchoSessionManager at init.

Add regression coverage verifying that changing each of these settings changes both:

1. the extracted Honcho cache-busting subset
2. the final agent config signature

Tests

Ran:

• tests/honcho_plugin/test_pin_peer_name.py
• tests/gateway/test_agent_cache.py

Precedent

This follows the same cache-busting pattern established in:

• 6feb2afd5 fix(honcho): plug pinPeerName transition gaps
• 1a8e67076 fix(honcho): cover pinUserPeer + aiPeer edge cases in setup, clone, and gateway cache