80b836fa9e
The preflight rough-estimate seed used 'last >= 0' semantics, so any provider that reports real prompt_tokens got its reading replaced by the schema/reasoning-inflated rough estimate whenever the estimate was larger. last_prompt_tokens feeds both the CLI context meter (cli.py) and the post-response compression gate (conversation_loop.py), so one seed made the bar jump to an inflated number AND could push the real-usage gate over threshold on estimator noise. Observed in a production CLI session on a 1M-token window with a reasoning-heavy history: the status bar showed ~492K real provider prompt tokens; the next turn's preflight estimated ~685K (rough estimates can inflate 1.4-2.5x on reasoning-heavy sessions, #81481) and seeded it into last_prompt_tokens; compression then fired at ~69% of the window while real usage was ~49%. Policy change: a real provider reading (>0) always wins. The seed now only fills the 0 state ('no reading yet'), keeping the status bar live for usage-less providers (#34282's motivation); -1 remains protected as the post-compression sentinel (#36718). Updates TestPreflightSentinelGuard to encode the new policy and adds a regression test with the measured 492K/685K numbers.