Push snapshot updates without breaking client builds

Roll improvements out to existing client accounts safely: know exactly what a push overwrites, protect client customizations, and verify after landing.

1. 1

   Version your snapshots

   Every meaningful improvement to the master build becomes a new snapshot version (medspa-v4) with a changelog note of what changed. Unversioned snapshots make rollback guesswork.

2. 2

   Understand push semantics

   A push offers your linked accounts the updated assets. The danger zone is assets clients have customized: their edited version versus your update collide. Know which assets each client touched before pushing.

3. 3

   Stage on a canary account

   Push to one internal or friendly test account first. Verify the updated workflows, funnels, and fields landed correctly and nothing regressed.

4. 4

   Communicate before the fleet push

   Tell affected clients what is improving and when. An unannounced change to a workflow a client watches daily is a support ticket with feelings.

5. 5

   Push in waves

   Fleet-wide in one shot means fleet-wide problems in one shot. Push in cohorts, verify each, proceed.

6. 6

   Verify per account

   After each wave: spot-check the changed assets, confirm workflows remain in their intended publish state, and run one test lead through the core flow.