Compared with the prior browser publishing workflow, this task used private calendar-label APIs and a browser fallback for an unsupported event type. The requested colors were verified without changing shared event fields.
- What worked
- Native tools handled bulk changes, and the existing browser session resolved the exceptional event.
- What got in the way
- The calendar API returned a generic bad-request error for an event type that the browser could modify.
