Model Retraining and Cutover

The model was fine: a 3-second P99 at 740K ops/sec was reads queueing behind writes

One engineer's trading app hit a three-second P99 tail while average latency looked healthy. The cause sat in Postgres and the feature lookups, not the model, and cache tuning could not reach it.