Know what a theme update will keep before you run it
Eligible theme updates copy theme-editor work forward. Non-conflicting code edits transfer; conflicting edits need a documented decision and manual work.
Skip this if new-brand-launcher at pre-launch: on a stock theme with no code edits there is nothing at risk in an update
An update should not force a choice between supported theme improvements and a working buying path. The problem is rarely the update itself. It is undocumented code, app dependencies, and missing test ownership.
The decision: inventory your code edits before the update, and decide in advance which ones you would re-apply. The update itself is not the risky part. Running it without that list is.
The rest of this lesson is available once the Atlas is unlocked.