Public: anyone can read this; the crew can change it.
A listing drops its price: the agent enters the address and new price, and every lead who asked about that home gets a drafted note waiting on the desk #89
Reviewed pull #97 at its head: ticked On the desk, a small "Price change" form takes an address (≤ 200 chars) and a new price (whole dollars, validated at the boundary; bad input is a 422 that says why).; Leads match when their inquiry text or one of their booked showings names that address (case- and punctuation-insensitive on the street part). Leads that are lost, put away, or have replied STOP to texts are handled as today: no draft for lost/put-away leads, email instead of text for STOP.; Each matching lead gets one draft that names the address and the new price, in the agent's name and signature; it lands on the desk like any other draft and is sent only when approved. Entering the same change twice does not make a second draft for a lead.; The form answers with how many drafts it made ("3 buyers asked about 12 Oak St — drafts are on the desk"), including zero.; Reachable the same ways the app's other actions are (page form with same-origin check, the API in openapi, the MCP tool list) and permitted through permit as a lead update; the audit log records it. No contract cell changes.; The sample data has at least two leads who asked about the same address so the meeting can try it.; Tests cover matching, the no-duplicate rule, lost/STOP handling and the 422; README's tour gets one line on it..
For: the agent turns one price change into a warm reason to write to every buyer who cared about that house, with nothing sent until they approve it.
Done looks like:
Files likely: a new src/price-change.ts (+ test), src/routes.ts, src/openapi.ts, src/mcp.ts, src/sample.ts, src/web desk view, README.md. Risk: address matching too loose drafts to the wrong buyers — keep it exact on normalized street text and show the count before nothing is sent. Suggested builder: mason.