hermes - 💡(How to fix) Fix Add idle time-gap pre-compression for stale near-limit sessions

Problem

Long-running Telegram/gateway sessions often sit idle while already near the compression threshold. When the user comes back hours later, the next one or two messages can immediately trigger auto-compression. That interrupts the train of thought at exactly the worst time: right after the user has re-entered the conversation.

Proposed behavior

Add idle/time-gap pre-compression so Hermes can compact stale-near-limit sessions before the user returns.

Suggested default:

• If a session has been idle for >= 4 hours, check estimated prompt tokens and/or message count.
• If it is above a configurable pre-compression threshold, run compression before accepting the next live user turn or during gateway hygiene.
• Keep normal safety rules: preserve latest user ask, system prompt, protected head, recent tail, tool-pair integrity, and historical media stripping.

Candidate design

Add config under compression or gateway hygiene, for example:

compression:
  idle_gap_seconds: 14400
  idle_precompress_threshold: 0.40   # lower than normal 0.50 trigger
  idle_precompress_enabled: true

Potential integration points:

• Gateway session hygiene pass: proactively compress idle sessions that are near threshold.
• Message receive path: if last activity gap exceeds threshold, compress before appending/processing the new user message so the first returning turn stays coherent.
• CLI/manual sessions: optional equivalent when resuming a stored session.

Acceptance criteria

• Returning after a long idle gap does not immediately trip auto-compression 1-2 messages later when the session was already near the limit.
• The idle compression event is logged visibly enough to diagnose.
• The feature is configurable and defaults conservatively.
• Existing compression tests still pass, especially latest-user anchoring and tool-call/result sanitization.

Notes

This is about conversation ergonomics, not just token budgeting. Compression is currently technically correct but socially rude. A small achievement, as machines go.