Opening Hours Stack (PL-T185 + PL-T184)

The baseline lives on ChainVenueProfile as a WeeklyHours object — seven DayHours entries, each with HH:MM time strings for open and close plus an optional list of breaks (lunch service gap, kitchen-closed window, etc.). Seasonal overrides also live on the profile, scoping different weekly patterns to date ranges (e.g. summer hours June 15 to August 31, holiday-season hours December 23 to January 6). Single-date overrides are stored in a dedicated OpeningHoursOverride document keyed by (tenant_id, location_id, date) with a unique constraint preventing duplicates.

Each override has a mode — closed (the venue is shut entirely for the day) or modified (open with custom hours and optional breaks). The resolution function get_effective_opening_hours(date_range) walks the stack: for each date it first checks for an OpeningHoursOverride, then a matching seasonal override, and falls back to the weekly baseline. The booking engine calls this whenever it validates a slot — a midsummer-eve closure becomes a hard 409 on any attempted booking, and a kitchen-break window blocks meal-order submission for that interval.

The API exposes GET for ranged effective hours (used by both the customer CMS and the admin calendar) and POST for creating overrides. Operators typically use the admin UI to set holiday closures and seasonal swings; the customer CMS reads effective hours to render the booking wizard's available days and times.