Jeroen UbbinkandClaude Opus 5 fec229e1f4 fix(pricing): ask the shared rate question when reading a feed price ...

The feed-price coercion rejected `NaN`/`inf` but returned a negative unchanged,
and the catalog import filter that would have caught one inspects only prompt
and completion. A negative cache rate was the one malformed value still
reaching a stored price, where it prices cached input tokens at a credit.

Both resolver rungs now ask `is_usable_rate` rather than spelling the rule out
again, so a feed price is held to the same standard as one arriving at the
admin edge. The both-zero rejection stays: that is a free price, not a
malformed one, and it is a separate question.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011cKHVF5LA7TR5QuYi6ErLM

2026-08-25 20:47:48 +02:00

..

integration

test(pricing): pin rate validation to every billable rate, not the token pair

2026-08-25 20:28:16 +02:00

unit

fix(pricing): ask the shared rate question when reading a feed price

2026-08-25 20:47:48 +02:00

conftest.py

test: add return type annotations to cache fixtures for strict mypy

2026-08-17 23:26:52 +02:00

run_integration.py

dump wip stash

2025-08-06 20:31:55 -03:00