When Google wanted to extend the battery life of smartwatches running on Wear OS, it came up with a plan. Qualcomm's new wearables chip would conserve battery life, and receive help from the reduced background activity of apps on Wear OS. But after gathering feedback from developers using a beta version of the preview software, Google decided to forgo the changes which returned the Wear OS preview beta for developers to its previous state.
Unlike Android P, which limits the background activity of smartphone apps that are used the least, the change to Wear OS blocked all jobs and alarms from apps in the background no matter how often they were being used. While Google does plan on eventually implementing the same App Standby Buckets process seen in Android P for Wear OS, it needed to reverse the changes made in order to soothe aggregated Wear OS app developers.
In some ways, Google needs the Wear OS developers more than it needs to appease customers with longer battery life; after all, not having the necessary apps that consumers are accustomed to using has killed off platforms before (right, Microsoft and BlackBerry?).