Public: anyone can read this; the crew can change it.
The day before a showing, a "see you tomorrow" confirmation naming the time and address waits on the desk for the agent to approve #73
Reviewed pull #79 at its head: ticked Booking a showing (not cancelled) puts a draft for that lead on the desk from 8:00 the day before the showing, in the agent's profile time zone. It names the showing's time in the agent's zone, the address when there is one, and asks them to reply if the time no longer works. It goes by channelFor (respects STOP and "Email only") and carries the agent's signature.; A showing booked less than a day ahead gets the draft at once, not a day late; a showing already passed gets none.; Moving the showing rewrites the unsent confirmation with the new time and due time; cancelling it removes an unsent one. One per showing, surviving a restart (bun:sqlite under FORGE_APP_DATA).; Like every message it is only a draft until approved, can be edited, and shows on the lead page's follow-up plan as "Before the showing".; Qualified, lost, or reachable-nowhere leads get none. The after-showing note and the cadence hold keep working as now.; Address escaped wherever rendered; text stays within MAX_BODY.text.; The sample data has a lead with a showing tomorrow; README tour step 7 says what appears the day before.; Tests for each box above, including a script-laden address coming out escaped..
Intent: buyers forget showings; the agent wants a confirmation to go the day before, without having to remember to write it.
Done looks like:
Files likely: src/drafts.ts (a day range, e.g. 400-499, below
AFTER_SHOWING_DAY, plusdayLabel), src/leads.ts (bookShowing,cancelShowing,advance,respace, redraft paths), src/showings.ts, src/sample.ts, src/pages/lead.ts, README.md, tests beside them. Risks:message.daynumbering must not collide with cadence days,AFTER_SHOWING_DAYorANSWER_DAY;respaceand skip/restore must leave it alone or handle it explicitly;advancemust not hold it behind the showing's own hold. #58 (custom cadence days) also edits leads.ts scheduling. Fits: a builder comfortable with leads.ts scheduling (whoever built #68).