c0495c6bce
On reasoning models a long tool loop replays the current turn's thinking + scaffolding on every request, so the LAST request's prompt_tokens can exceed the durable transcript by hundreds of K — all of which evaporates at the turn boundary. The status bar and /context breakdown rendered that raw figure, so users watched 'context' jump (e.g.) 850K -> 600K across a turn boundary and read it as a broken compaction. - conversation_loop: capture a turn-base usage anchor from the turn's FIRST provider response (api_call_count == 1), where replay is minimal. - anchored_context_tokens: new charge_stale_thinking kwarg forwarded to the delta estimate (stale reasoning excluded on all but the newest assistant message). - cli status snapshot + context_breakdown: prefer the turn-base anchored figure; fall back to last-response anchor / raw last_prompt_tokens. - All _usage_anchor invalidation sites also clear _turn_base_usage_anchor. Display-only: compression trigger math keeps using real last-request usage (the inflated request is what actually risks the window mid-loop).