ozymandiashh 556b59d7d8 fix(parser): keep both halves of a midnight-straddling turn, and stop --provider leaking claude ... Ports upstream fixes for two defects this branch never received. **A turn that spans local midnight was filtered as a unit.** The range and day filter keyed on the turn's FIRST call, so every later call that landed in the requested day was discarded along with it. A long autonomous Codex run, or Claude work that crossed midnight, made `codeburn today` under-report until the turn ended, and multi-day totals attributed the whole turn to its start day. Range and day filters now slice inside the turn: only the calls inside the requested window survive, and the turn's timestamp re-anchors to its first surviving call so turn-anchored rollups — category, editTurns, oneShotTurns, the daily cache — land on the day the retained calls actually happened. Cost, calls, savings and tokens bucket under each call's own local day, so day N plus day N+1 conserves the whole-range total. A sliced turn is still classified from its FULL call list, because category, hasEdits and retries describe the whole exchange rather than the surviving slice — matching the Claude path. **The inverse leak hit provider-filtered runs.** `--provider <other>` still entered the claude scan, whose orphan pass read the entire cached claude section, treated every cached PR-bearing transcript as no-longer-discovered and re-injected it. By Project and By Model listed Anthropic spend under `--provider cursor` while the headline showed cursor alone. The scan is now guarded by an explicit in-scope check — deliberately not a directory-count check, so when claude IS in scope but every transcript has been pruned, PR-attributed orphans still survive. **The daily cache is bumped to 17**, because leaving it at 15 would double-count the post-midnight half of a straddling turn for an upgrading user. A v15 rollup finalized by the pre-fix binary holds the WHOLE turn on its start day, and the new slicing then also puts the post-midnight call on the next day — the same cost twice, in a cache whose ten-year retention never ages it out. The bump mints a fresh filename; adoption marks the merged result incomplete, so the next hydration re-derives every day whose sources survive under per-call bucketing and carries forward only what it cannot re-derive. 16 is deliberately skipped: main already spent it on the codex structural-discovery fix (eece4cf), so claiming 16 here would load a main-built v16 cache — which holds only the codex fix — as current and complete and the invalidation would never fire. Blast radius: daily-history rows, the JSON daily fallback and range-query session totals change shape for straddling days, as call-derived values move to the call's own day — the intended correction, asserted by this commit's tests. The session-cache FORMAT is unchanged. One caveat worth stating rather than leaving to be found. The multi-day all-provider By Activity rollup still derives today's slice from the unsliced range parse, so a straddling turn's category cost stays anchored on its start day and categories can sum below the headline on that surface; upstream has a follow-up for it.		2026-08-05 17:15:30 +03:00
..
cli	fix(parser): keep both halves of a midnight-straddling turn, and stop --provider leaking claude	2026-08-05 17:15:30 +03:00
core	chore: stop emitting declaration maps	2026-07-27 15:22:15 -07:00