Launch proof
Bring one request into launch review
Carry one representative request into the launch review so procurement, security, and delivery teams can inspect the same route reason, settled cost, and cache boundaries.
Keep one X-Request-Id from the workload that already reflects the target model mix.
Reopen the settled record after streaming instead of relying on transient headers alone.
Separate prompt-cache discounts from durable response-cache replay before rollout goes live.