The appointment-completion candidate adds JWT-only GET/PATCH `/api/v1/admin/booking-offering`, requiring `settings.business`. The web settings action now delegates to the same explicit-organization service and uses that permission for reads as well as writes.

Owners can inspect their active products, retained lifecycle states and available transitions. The public commercial models remain Appointment Only and Classes & Appointments; internal classes-only configurations stay supported for grandfathered venues. An eligible offering change uses the existing transactional authority. Removing a product closes new sales while retaining outstanding obligations and history. This endpoint does not archive products, change a paid plan, produce a price quote, contact clients or charge anyone.

Writes require an organization/actor/body-bound idempotency key. Unconfirmed saves retain their logical operation; a proven refusal is distinguished from an unknown result. A failed cache refresh or acknowledgement must not falsely report that a known save failed. Paid-tier requirements return the canonical required plan keys, not invented pricing.

Business-native authoring and the separate reviewed paid-plan preview/acceptance workflow remain implementation requirements. Consumer and Branded use authoritative venue capabilities and historical rights, not these staff configuration controls; Consumer must continue supporting mixed venue types in one account. Published Sites, Studio and AI share the existing product lifecycle authority. This API does not rewrite customer-authored pages/navigation or prove their final rendered compatibility.

These are candidate source changes, not a deployment announcement or a claim of complete native/device parity. No schema, tenant configuration, customer transaction, provider operation or app publication is performed by this work.