offpeak 0.2.1

Price sheet correction. The bundled OpenAI rows were that provider's batch tab stored as list prices — all three models, not just one. Receipts for OpenAI models in 0.1.1–0.2.0 therefore understated both the list cost they compared against and the batch price actually billed: a 1M-in/1M-out gpt-5.6-sol job derived $1.25/$7.50 against a true batch price of $2.00/$10.00. Anthropic's rows were unaffected, and the amounts run so far are sub-cent — recorded regardless, because a receipt that quietly moves is not a receipt.

Corrected standard rows (per developers.openai.com/api/docs/pricing, short context): gpt-5.6-sol 4.00/20.00, gpt-5.6-terra 2.00/12.00, gpt-5.6-luna 0.20/1.20. The −50% batch rule survives intact and now reproduces the provider's own batch tab exactly, asserted per model by test.

The fast tier, and the 4× urgency spread. The sheet now carries what a venue charges for haste as well as for patience: urgency_spread("gpt-5.6-sol") returns 4.0 — $8/$40 per 1M on OpenAI's fast tier against $2/$10 on its batch tier, the same model at the same venue, priced for the hour alone. Promotional list prices carry their own expiry (PROMO_NOTES, promo_decay()): sol's standard rate runs at least through 2026-11-21, $5/$30 after, so the ratio outlives the dollars.

Assumed output on quote(). quote(jobs, deadline=..., assumed_output_ratio=0.25), or metadata={"expected_output_tokens": n} per job, prices output that a pre-trade quote cannot know — marked EST on the card, distinct from FLOOR. Opt-in only: without one, nothing is assumed on your behalf and the default stays the floor.

Also: main carries a dev version between releases; the night board publishes the cited 4× alongside the 2.0× batch spread, and its docs page corrects two stale claims (US zones are wired; ERCOT Houston marked 3.94× on 2026-08-20).