Backwards compatibility -- semver, deprecation, and migration

Breaking changes disrupt downstream users and erode trust.

Deprecation lifecycle: add new alongside old, mark deprecated with timeline, log warnings, remove in next major. Use semver. Never break published contracts without major bump.

Every breaking change forces every consumer to invest time. The cost multiplies with user count.