Design, activate and own a custom object
What It Does
The designer moves a custom category from draft to active and then applies ownership. Draft owner choices currently survive only in the browser that saved them.
The Flow
When Something Fails
Display a definition refusal; browser-storage failure can silently discard the pending owner. A saved draft can lack the owner choice in this browser. Refuse activation and report incomplete settings without changing status. The draft and recipes remain unchanged on refusal. Show an ownership failure and retain the pending choice for another save. The object may already be active with no owner, or an unselected type may exist. Reject the owner definition and let the designer report that activation already succeeded. The active object remains without completed ownership. Ignore retirement refused because another object still uses that type; report other failures after the object save. The former type and its links can remain active.
Open Design Questions
Shared persistence for draft ownership is needed before activation can apply it reliably across browsers.