Can cost_drift catch a cost that creeps up slowly, not just a sudden spike?
Yes. cost_drift compares each call site against two references at once: a rolling recent normal, which catches a jump, and one pinned at a known-good point that only a person moves, which catches the creep the rolling one absorbs.
The cost-specific case is a prompt that grows a little each release. No single deploy looks expensive, and the pinned reference is what notices the sum.
The mechanism is the same one duration_drift uses for a gradual slowdown.