Saving Business identity now changes only the submitted business type and legal setup. It no longer resubmits the page's booking mode or rewrites the venue's settings JSON. Booking-product changes remain deliberate actions in the separate Booking products card, using the existing offering authority and commercial checks.

Older explicit callers of the legacy-named action remain supported. When they submit terminology, it is merged against fresh settings using the existing compare-and-set helper, preserving concurrent notification, review, product and unrelated terminology updates from participating writers. This is not a repository-wide atomicity guarantee: writers that do not advance the helper's token remain outside that guarantee.

The compatibility action can still have multiple persistence steps. It reports known saved parts and uncertain outcomes instead of pretending an earlier product or terminology save was undone by a later error. Confirmed changes trigger independent cache updates and audit attempts; an unsuccessful follow-up returns a saved warning. This source change does not modify any hosted venue configuration or send client communications.