- Uploadable reception logo (Settings, PNG/JPEG, public GET so the kiosk
can show it without a staff login) — shown top-center on the kiosk
login and idle screens, Welcome copy centered underneath.
- Tablet-sized styling pass on all kiosk views for a ~10" tablet (bigger
touch targets, base text, spacing) rather than the general app's
desktop-first sizing.
- New booking-confirm step (name/arrive/nights/depart/rate name(s)/rate
total) replaces the old partial review step.
- Contact details, car registration and marketing merged into one step
(was 3 separate steps) — 5 steps down to 3 overall.
- Email handling now matches the legacy system's confirmed behaviour:
excluded-domain (OTA/agent relay) addresses are filtered out of what's
shown as 'on file' entirely, not just flagged, and a new
excluded_email_domains Settings field (CSV) replaces the old hardcoded
domain list so any OTA/agent domain can be added without a code change.
- Single email field design: only pre-filled when there's exactly one
valid existing email, left blank (not guessed) when there are several —
marketing opt-in only ever touches whatever's in that one field, never
blanket-subscribes multiple pre-existing emails (project_checkin memory,
2026-09-01 'stay in touch' note).
- Car registration now allows multiple additions — add/remove list UI,
buildContactDetails appends each new one not already on file rather
than the old single-slot overwrite.
- Signature now required to actually complete (tracked live via
SignatureCanvas onEnd, not just caught on submit) alongside accepted
terms — Complete Check-In stays disabled until both are true.
- T&C block is height-capped with its own internal scroll (keeps the step
on one non-scrolling screen) and now renders basic HTML (<b>, <br>,
<p>, <ul> etc) instead of plain text — content is admin-authored
(settings capability required), same trust boundary as any other
setting. PDF generation strips tags back to plain text since pdfkit
can't render HTML.
- PDF and booking-confirm screen both surface tariff name(s) (deduped
across tariffs_quoted in case the rate changed mid-stay) and nights,
not just the total.
- Also fixed: injected extension buttons could hang forever on 'Loading
tablets…' with no feedback if the extension was reloaded without also
refreshing the NewBook tab (stale content script) — now surfaces a
clear 'Extension was reloaded — refresh this page' message instead.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
- Options page gains a 'Default tablet for this machine' picker,
populated from the device list once base URL + terminal key are
configured, auto-saved on change (small enough setting not to warrant
its own Save button).
- Popup pre-selects the default in its device dropdown but still shows
the full picker — opening the popup is already a deliberate action, so
staff can still override it there.
- Injected buttons (row + banner) skip the dropdown entirely when a
default is configured — one click pushes straight to it. Only falls
back to the full picker if that specific push comes back busy (409),
with a note explaining why it's asking despite a default being set.
background.js's pushBooking() now returns the HTTP status alongside
ok/error so this can be detected reliably rather than string-matching
the error message.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
New injection point on bookings_view pages — NewBook's own 'This Booking
is due to Arrive today. Do you want to go to Check-In?' banner
(.newbook_message.plain), confirmed from a real sample 2026-09-01. Shares
the row-injection's button/panel logic rather than duplicating it;
makeSendButton/togglePanel now take a variant ('block' for the list row's
table cell, 'inline' for this banner's flowing text context). Booking ID
extraction differs per shape: the list row has a checkbox value, this
banner's Check In button only carries it inside its onclick attribute's
URL, no separate structured attribute.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
- location /tablet-checkin/api/devices/ (trailing slash, proxy_pass) made
nginx auto-redirect the bare /api/devices list endpoint, and since this
inner nginx sits behind NPM's TLS termination it built that redirect as
http:// even over an https:// request — browsers block that as mixed
content, surfacing as a bare 'Failed to fetch' on the Devices admin page
with no other clue. Dropped the trailing slash on both the location
pattern and proxy_pass target; still correctly prefix-matches every
/devices/:id/... sub-route, no more auto-redirect at all.
- pushNavigate/send() now only reports delivered:true if a write
demonstrably succeeded, not just because a stream entry exists for the
device — a stale-but-not-formally-closed connection can silently accept
a write that never reaches the far end.
- pushBookingToDevice can now self-heal a device stuck 'busy' with no live
session behind it (session already expired unused) rather than requiring
an admin to manually click Reset first. Real failure mode hit testing on
a physical tablet 2026-09-01: two pushes worked end-to-end, a third's
navigate event never reached the tablet (SSE connection silently died
during an idle gap), leaving the device stuck with no way to recover
except a manual admin reset.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Backend CORS is disabled by default (origin: false), and an unpacked
extension's ID isn't fixed/predictable per install anyway, so allowlisting
it server-side would be awkward. options.js now calls
chrome.permissions.request() for the entered base URL on Save — once
granted, the extension's own fetches bypass CORS entirely for that origin.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
- setBookingCustomFields: use bookings_update's own custom_fields array
(confirmed from the real legacy plugin code) instead of
instance_custom_fields_set, which was only ever proven for a different,
unrelated plugin
- online_checkin_complete is now a configurable per-hotel custom field
(online_checkin_complete_custom_field_id setting), not a bogus top-level
bookings_update field NewBook would silently ignore
- Fix field-name mismatches vs a real live NewBook booking response:
booking_arrival/departure/length, guest address (street/city/state/
postcode/country, not a single field), phone/mobile (in contact_details,
not top-level), and pickPrimaryGuest now checks primary_client (was
checking fields that don't exist in the real API)
- Bundle the standalone push extension into backend/extension-src/, add
GET /api/extension/download (zips on request via archiver) and a
download button on the Settings page
- Remove newbook_hotel_id — vestigial from the legacy system's multi-hotel
routing model, never actually reached NewBook's API, this stack is
single-hotel-per-deployment so there's nothing to route between
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
