Web member/guest booking and the shared mobile appointment API now recover an
already saved matching booking before checking current prices or availability.
New bookings still obey the venue's payment requirements and named-staff choices.
The venue, client and original booking details remain bound to the retry.

This is server-side candidate work, not a deployed feature or completed native
rollout. The public booking form still needs persistent retry state, and the
Business/Consumer/Branded configuration matrix remains under verification.
Older Any bookings without saved choice evidence require explicit recovery
guidance; the server will not guess or create a replacement. New-booking price
and duration confirmation, grouped visits and room-based paid booking remain
separate unfinished work.

No customer booking, notification, hosted setting, migration or release was run.
This does not certify Nailtech ready or fully silent.