room-planner/frontend
jtricerolph b66b3a7854 Room planner: fix spans_next, night counter, and B2B booking priority
spans_next was using departure > viewDate (today), which made any 1-night
booking extend the card to the right. Fixed to departure > tomorrow so the
card only extends when it's also active tomorrow.

Night counter used Date.parse() on NewBook datetime strings, which browsers
parse as local time and shift off by hours in BST. Replaced with utcDay()
which slices the YYYY-MM-DD prefix and calls Date.UTC() — always correct.

When multiple bookings overlap today, prefer the one arriving today so an
arriving guest takes priority over a stale stopover. Also treat a co-active
non-arriving booking as the B2B departing context.

Force previous-day bracket to show as "departed" (purple) when that booking
departs today, without waiting for NewBook to update its status field.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-07-04 11:31:29 +00:00
..
src Room planner: fix spans_next, night counter, and B2B booking priority 2026-07-04 11:31:29 +00:00
Dockerfile fix: serve frontend via root + slug subdir, not alias — assets 404/fallback 2026-07-03 16:32:45 +00:00
index.html fix: correct index.html script src — Vite prepends base path, don't include it manually 2026-07-03 13:15:30 +00:00
nginx.conf fix: serve frontend via root + slug subdir, not alias — assets 404/fallback 2026-07-03 16:32:45 +00:00
package.json feat: add room-planner app — 3-day HK room view with NewBook integration 2026-07-03 13:07:00 +00:00
tsconfig.json feat: add room-planner app — 3-day HK room view with NewBook integration 2026-07-03 13:07:00 +00:00
vite.config.ts feat: add room-planner app — 3-day HK room view with NewBook integration 2026-07-03 13:07:00 +00:00