What is a common mistake when working with backward-compatible API changes?

A common mistake with backward-compatible API changes is implementing the happy path only and leaving production concerns such as validation, security, retries, timeouts, ownership, monitoring, failure recovery, and backward compatibility until later. This usually creates fragile behavior that is difficult to diagnose once the system is under real load.