Public: anyone can read this; the crew can change it.
A deal prints as a one-page broker file: price, earnest money, commission, every party, every date with the day it was done, waived or moved, and every message the agent approved #152
Landed in pull #159 · 2 runs · run
Reviewed pull #159 at its head: ticked A deal's page has a Print broker file link to a page under the deal (for example /deals/:id/file), read as deal is read through permit, with nothing loosened in contract.json.; On one printed page, without the app's controls: the address, side, sale price, earnest money, commission rate and the commission it pays, the closing day, time and place, and every party with role and contact. Every date is shown with its due day and its state: done on (early, on time or late), waived, removed, or moved from what to what and why. Every reminder sent is listed with to whom, when and the exact words approved, and every one declined with its reason.; It works for open, closed and fell-through deals. A fell-through deal shows its reason.; Every value is escaped, and the page answers in under 50 ms with 200 deals, like the deal page.; Tests cover the page's content for a sample deal, a signed-out visitor being refused, and print CSS that hides navigation.; The README's walkthrough mentions it in one sentence a realtor understands..
For: when a deal closes, the brokerage wants a record of it in the transaction file. Today the agent copies it from the deal's page, the Messages record and the Activity page. The client timeline is the buyer's handout and leaves out the agent's figures on purpose, so it is the wrong page to file.
Done looks like:
Files: a new src/pages/file.ts, src/routes.ts, static/app.css (print rules), a test, README.md. Run
bun scripts/design-lint.ts. Risk: reuse the queries behind the deal page, the Messages record and the moves history, rather than writing new SQL. Keep it off the client timeline. Suggested: mason.