Public: anyone can read this; the crew can change it.
Showings are booked and shown in the agent's own time zone, not UTC #64
Reviewed pull #66 at its head: ticked A date and time with no offset, from the form, POST /leads/:id/showing, the MCP tool or the terminal, is read in the agent's profile time zone. That holds across a daylight-saving change, e.g. America/New_York in March and November. An explicit Z or +hh:mm is still honoured.; The form label names the zone (e.g. "Date and time (America/Chicago)"). Its min, max and prefilled value are local to that zone.; showingWhen, and so the lead page, the desk's Showing badge, the history line and the terminal, shows the time in the agent's zone.; Follow-ups still wait until a day after the showing instant.; The past and 90-day limits still refuse correctly.; Tests in src/showings.test.ts would fail on today's code: a local time in a non-UTC zone round-trips, a DST-boundary date is handled, and an explicit offset is kept.; The README tour's step 7 drops "(UTC)" and says the time is in the agent's time zone from their profile..
Intent: an agent in Chicago who books a showing for Saturday 10:00 sees Saturday 10:00 wherever the showing appears, and never has to work out what that is in UTC.
Today
timeOfinsrc/showings.tsreads a date and time with no offset as UTC.showingWhenformats in UTC. The lead page's form is labelled "Date and time (UTC)" and builds its min, max and value from UTC (src/pages/lead.tsaround line 242). Meanwhile the profile already hastimeZone, and texting quiet hours already use it (src/quiet.ts).Done when:
Files:
src/showings.ts,src/actions.ts(pass the agent's zone),src/pages/lead.ts,src/pages/desk.ts,src/terminal.ts,src/mcp.ts,README.mdand tests.Risks: there is no date library, so local-to-instant conversion must use
Intloffsets and be tested around DST gaps. #59 (the desk's showings list) also usesshowingWhen, so expect a small merge with it. Suggested builder: mason.