Public: anyone can read this; the crew can change it.
A deal's closing carries a time and a place, like "2:00 pm at Lakeside Title, 400 Main St", on its page, the client timeline, the closing reminders and the calendar file #122
Reviewed pull #126 at its head: ticked The deal's page sets an optional closing time (HH:MM, 15-minute steps, 7:00 am to 8:00 pm) and an optional place (1 to 200 characters), by same-origin POST validated at the boundary; a refused form keeps what was typed; clearing either is allowed.; The deal's page and the client timeline (screen and print) show "Closing Nov 21 · 2:00 pm · Lakeside Title, 400 Main St"; a deal with neither reads as today.; The drafted closing reminders (before and day of) and the final walk-through reminder name the time and place when set.; In both the deal's calendar file and Add all to calendar, closing is a timed one-hour event with LOCATION when a time is set (floating local time, no time zone invented); with no time it stays all-day as today. The place is escaped per RFC 5545 (commas, semicolons, newlines).; Moving the closing date keeps the time and place; the date-changed notice names them.; The sample deals give the deal closing this week a time and a title company; Restore the sample deals brings them back.; /api/deals, the MCP deal tools and src/openapi.ts read and write closing_time and closing_place; a change is audited and appears on the Activity page.; Tests: a bad time (25:00, 2pm) is a 422, the reminder wording with and without them, the .ics has DTSTART:20261121T140000 and an escaped LOCATION, an all-day closing remains VALUE=DATE. bun test passes..
Intent: the buyer, the seller and the agent's own calendar know exactly when and where to sign, not just the day.
Done looks like:
Files:
src/db.ts(two nullable columns on deal, appended migration),src/deals.ts,src/reminders.ts,src/ics.ts,src/sample.ts,src/pages/deal.ts,src/pages/timeline.ts,src/routes.ts,src/mcp.ts,src/openapi.ts, README.Risks: #118 and #120 also touch
src/deals.ts,src/db.tsand the sample deals, so rebase on whichever has landed; contract.json is untouched; the 50 ms speed tests must hold.Suggested: mason.