fb9b2c893f
Builds the escalation layer on top of HexLab98's heal-log windowing (salvaged from PR #96916): - Per-session heal counters (heal events + messages healed) tracked by the repair path in agent_runtime_helpers.py, session totals preserved across 10-minute log windows. - Threshold escalation: after N heals in a session window (default 3, configurable via agent.sanitizer_heal_escalation_threshold in config.yaml, 0 = off) log ONE ERROR carrying session id + heal pattern (events/messages/window/threshold), then stay quiet. - ONE-TIME out-of-band user notice queued at the threshold and delivered by the conversation loop through _emit_warning (status callback -> gateway status message / CLI print). Never injected into conversation context or the wire copy: prompt caching, role alternation, and durable history are untouched. Never re-arms on a new window; scoped per session. - Counters visible in diagnostics: get_sanitizer_heal_stats() rendered in the /debug share // hermes debug report, and the config key surfaced in hermes dump overrides. errors.log carries the ERROR line for `hermes logs errors`.