docs(cache_stability): drop stale 'high-water mark' phrasing in README composition note

The mark re-baselines on a detected collapse, so it is no longer a monotonic
high-water mark; describe the per-run state as the per-key marks and timing,
matching the docs page.
This commit is contained in:
David SF
2026-07-17 10:43:09 -05:00
parent d97d2e6440
commit caf19e68bb
@@ -128,7 +128,7 @@ as the capability matures.
- The monitor only implements `for_run` and `after_model_request`; it adds no
tools, instructions, or model settings, so it composes with any other
capability, toolset, or `ToolSearch` setup without interference.
- Per-run state (the high-water mark) is materialized in `for_run`, so one
- Per-run state (the per-key marks and timing) is materialized in `for_run`, so one
`CacheStabilityMonitor` instance can be reused across many `Agent.run` calls --
each run is judged independently.