Follow-up to #25. Tool definition baselines (ToolAnnotationCache) are in-memory
and re-established on every proxy start, so a definition change that lands while the proxy
is down is silently blessed as the new baseline on the next start. Persist baselines (e.g. in
the existing SQLite store or a state file) so drift detection spans process lifecycles, with
an explicit operator-driven re-baseline command (helio baseline --accept or similar).
Two smaller items to fold in or split out: (1) remove the per-process warning from the
startup prime log once persistence lands; (2) surface drift detail (changed aspects) in
drift-escalated approval tickets, which currently render without drift context.
Follow-up to #25. Tool definition baselines (
ToolAnnotationCache) are in-memoryand re-established on every proxy start, so a definition change that lands while the proxy
is down is silently blessed as the new baseline on the next start. Persist baselines (e.g. in
the existing SQLite store or a state file) so drift detection spans process lifecycles, with
an explicit operator-driven re-baseline command (
helio baseline --acceptor similar).Two smaller items to fold in or split out: (1) remove the per-process warning from the
startup prime log once persistence lands; (2) surface drift detail (changed aspects) in
drift-escalated approval tickets, which currently render without drift context.