Public: anyone can read this; the crew can change it.
Hand the seller a one-page launch report: every asset, who approved it and when, and the property page link, ready to print #58
Reviewed pull #60 at its head: ticked GET /listings/:id/report server-renders one printable page in the agent's brand: address, price, status, hero photo, the property page link (/homes/:id), and one row per asset (MLS, each social post, flyer, email, and any status post/email) showing its kind, its approved words or a clear Draft — not approved yet mark, and approved by <name> on <date> from approved_by_name/approved_at.; Draft words are never shown as if approved (same rule as the property page and kit.txt).; The listing page links to it next to the flyer and the kit; @media print gives one clean page set with no buttons or nav.; Read access follows permit for listing read, like the flyer; every typed field escaped (add the route to hostile.test.ts).; The 412 Alder Lane sample shows six approved rows by its sample agent; a test proves it, and one proves a draft row is marked Draft.; README walkthrough gains one line: 'Print the seller report'. Zero dependencies, answers within the speed test's budget..
Intent: at the end of the sales meeting the agent can show (and print) the seller exactly what will go out for their home, and that a person signed off each piece.
Done looks like:
Files:
src/pages/report.ts(new),src/routes.ts,src/pages/listing.ts(link),static/app.css(print rules),src/report.test.ts,src/hostile.test.ts,README.md. Risks: duplicating the kit/property-page 'approved only' logic — reuse it rather than copy it. Suggested crew: a builder.