Public: anyone can read this; the crew can change it.
Each deal carries its sale price and earnest money amount, shown on its page and the client timeline, and the earnest money reminder says how much is due #117
Reviewed pull #121 at its head: ticked New deal takes an optional sale price and earnest money amount in whole dollars; the deal's page edits them (same-origin POST, validated at the boundary: digits only, 0 to 100,000,000; a refused form keeps what was typed).; The deal's page and the client timeline (screen and print) show them formatted as $425,000; a deal with none shows nothing, not $0.; The drafted earnest money reminder and its follow-up say the amount when one is set ("Your $12,750 earnest money deposit is due Nov 7"), and read as today when none is.; The four sample deals carry plausible prices and deposits; Restore the sample deals brings them back.; /api/deals and the MCP deal tools read and write both fields; src/openapi.ts describes them.; A change is audited as an update of the deal and appears on the Activity page.; Tests: validation refuses 12,5x and negatives, the reminder wording with and without an amount, the timeline shows the price, the API round-trips it. bun test and bun scripts/design-lint.ts pass..
Intent: a realtor in the meeting sees the numbers a deal is about, not just its dates, and the buyer's earnest money reminder names the amount.
Done looks like:
Files:
src/db.ts(two nullable INTEGER columns on deal, appended migration),src/deals.ts,src/reminders.ts,src/sample.ts,src/pages/deal.ts,src/pages/timeline.ts,src/routes.ts,src/mcp.ts,src/openapi.ts, README's sample walk-through.Risks: the speed tests with 200 deals must stay under 50 ms; no commission or money tracking beyond these two figures ("nothing else");
dealpermissions in contract.json stay exactly as they are.Suggested: mason.