Local candidate; not deployed or a Nailtech readiness announcement.

The public service booking page and its embedded counterpart now clear the old
time when someone changes the date or professional. They wait for price and
member-pass checks before offering confirmation, show a retry when those reads
fail, and keep “Any available” as an automatic assignment instead of pretending
the client selected a named person. One eligible named person is still a choice.

Dates start on the venue's calendar day. Changing the server-resolved venue or
account resets contact fields and prevents delayed replies from populating the
replacement form. A same-page retry after an interrupted direct booking retains
the original request and operation identifier. Success means the appointment is
confirmed; it no longer claims an email or receipt was sent.

This is not complete recovery or app parity. Browser refresh/remount recovery,
immediate sign-in/sign-out observation, final price/duration agreement and paid
recovery still need completion. Business, Consumer Original/Universe and Branded
companions remain in the same programme. Venue permissions, canonical booking
and payment engines, service policy, notification settings, fees and plan
entitlements are not changed by this UI packet. No hosted settings or customer
notifications were changed or triggered.

Published Sites enter the same guarded booking route. Studio/AI authoring,
publishing, public team-list consent and theme workflows are unchanged. Existing
public Sites guide claims do not promise complete offline/refresh recovery, so
no guide claim is expanded. The local candidate requires final integration and
release-coordinator review before any operational handover.