Save a product and its accounting setup from the console
What It Does
The shared console editor saves the common product, then changed accounting, then any supplied host-application extension. Each request has its own permission checks, version and commit outcome.
The Flow
When Something Fails
A failed stage stops later requests and leaves earlier successes committed. The editor retains returned baselines so an unchanged retry can skip completed work. First creation may therefore leave a product without its setup or extension. Setup serialization drops revenue-share identities, causing the service to generate new ones.
Open Design Questions
The staged contract remains the observed implementation. Product must decide whether to add a combined save and how to reconcile stricter browser accounting validation with service-valid records.