Use the template override contract

Template overrides are the last customization lane after documented hooks, components and public CSS roots. The closed catalog is owned by Hotel Booking Free and includes core templates such as Rooms, Room Detail, Book Now, Confirmation and Room Catalogue, plus Pro customer, policy and review views. An override is valid only when its declared template version exactly matches the active catalog and its Theme Contract version uses the current major.

Safe resolution

1. Place the file under the documented hotel-booking/ or hotel-booking/pro/ logical path.
2. Include Hotel Booking Template, Template Package, Template Version and Theme Contract headers. The literal Template Version header must remain on one metadata line.
3. Keep the child-first resolution order: child theme, parent theme, plugin default. An unsafe path, unreadable file, identity mismatch, outdated version or future version is skipped and falls through safely.
4. Preserve all canonical fields, form actions, notices, payment steps and accessibility attributes. Do not add repositories, services or database writes to a view.

Admin, email and invoice views are excluded. When a plugin template changes, update the override deliberately; do not copy an old view simply because it looks familiar. A rejected override should leave the plugin default usable.

Next: register components and design tokens.