The tours calendar reads one month per building, and a tour with no date still shows
Month window off tour-calendar-index, plus the Needs a time card off each building's UNDATED# entries
24 Sept 2026 · branch origin/feat/tours-calendar-reads-index · captured against propflow-stage · at 69212788d2+local
Data note. Every name and balance below comes from propflow-stage, which is anonymized by construction (ADR-0097/0110 — phones in the impossible +1000 NPA, emails @example.test). The identical capture against prod would carry real tenants' names and balances and is not safe to attach anywhere, which is why the generator refuses to run against one.
1 · One month, one sandbox test building, and a tour with no date
Stage data, the sandbox company picked. The grid is the August 2026 month window, read from tour-calendar-index for each building in the selection (the month's padded six-week grid), never the whole tour partition. Below it, the Needs a time card lists a synthetic fixture tour with no date. That tour is in no month window, so the page reads it separately, from the building's sparse UNDATED# index entry (readUndatedTours). Before this round, #11043 removed the card, and such a tour vanished from the page.
Asserted in the captured DOM — August 2026 · Needs a time · Fixture Undated Tour. The month the server read, the card, and the undated fixture tour inside it.
What was staged
Stage only (propflow-stage), on the sandbox test building. Its four existing tours had never been stamped on stage, so they were stamped with the branch's own buildStampUpdate, which is what the production backfill already did. One synthetic undated fixture tour was added through tourIndexKeys, and it was deleted after this capture. Tests that pin the same behaviour without a browser: TourCalendarClient.window.test.tsx (the card), load-tour-calendar.test.ts (the undated read reaches the page), and tour-calendar-window.test.ts (UNDATED# is in no day window).