What goes in your eval checklist before shipping?

Latency budget first. Nobody cares about clever output if the spinner lasts forever.

I always add one adversarial example per happy path now.

Style drift matters more than people admit once support teams start reading the output.

We diff schema compliance between model versions before we look at tone.