Added#
The window and the ledger reach every rendering. --markdown-out states
the window as the user typed it — rendering the internal exclusive bound would
print the next day and disagree with the terminal — with the undated count as
a loud blockquote, and carries the never-came-back claims with the same
fact/ceiling split, decided by the slice's own reads. The MCP's
profile_usage gains since/until under the CLI's rules (a window matching
nothing is an error naming what the log covers; clockless calls counted out
loud) and speaks both single-turn claims. The web Bill tab renders them in the
cache card, loud only when the slice read nothing.
Cache writes by conversations that never came back. A one-turn session
pays the write premium for reuse its own conversation never makes, and it
hides inside healthy totals: long sessions' reads pay for the cache overall
while every drive-by bleeds. singleTurnCacheWrites names the slices, prices
those writes at the bill's own rates, and the rendering makes the honesty
split the provider's prefix-keyed cache forces: with cache reads anywhere in
the slice the figure is a ceiling named as one — another conversation
sharing the prefix may have read the write, and the log cannot see whose
write a read hit — and with zero reads the ceiling collapses into a loud
fact: those writes bought nothing. Session keys group turns and are never
printed, as everywhere. The guard is mutation-tested and every dollar is hand
arithmetic.
profile --since / --until, the drill-down in time. A UTC day or a full
ISO 8601 timestamp; a bare --until date includes that whole day, because a
window that excludes the day it names is a trap sprung on everyone who reads
dates the way humans do. Internally half-open [since, until), so adjacent
windows share no record. The honesty rules carry the feature: a call with no
ts cannot be placed inside or outside a window, so it is excluded and
counted out loud — the window's figures are a floor on the period, and the
report says so; a window matching nothing is an error naming what the log does
cover, never a $0 report that would pass a --max-usd gate over a period the
log does not contain; a window over a clockless log is an error for the
--max-growth-usd-without---against reason. With --against, both logs get
the same window, and the gates gate the window — profile yesterday against the
day before, with a budget, in one line of CI.