Public: anyone can read this; the crew can change it.
Each week, get a seller update email to approve: what went out for their listing, what is scheduled next, and the property page link #75
Reviewed pull #86 at its head: ticked A launched listing's page has a 'Seller update' section with a drafted email: the listing's address and status, every asset approved this week (with who approved it and when, from the approvals already stored), what the launch-week schedule has coming in the next seven days, any open house dates, and the property page link.; The draft is plain words addressed to the seller by the agent's name, checked by the Fair Housing check like every other asset, editable, and carries the same Approve / Withdraw control; until approved it wears the 'Draft — not approved' band and its Copy is the same Copy the other assets have.; Editing the listing's facts or status clears its approval, as for every other asset.; The 412 Alder Lane sample shows a sensible update (it is fully approved, so the update lists six assets).; Tests: the update lists only this week's approvals, names next week's schedule, escapes typed fields (extend the hostile test), and cannot be approved over MCP (only a person approves).; README's meeting walkthrough gains one line on it..
Intent: after the launch, the agent owes the seller a weekly note; the app drafts it from what it already knows, and a person approves it before it can be copied or sent.
Done looks like:
Files likely: src/report.ts or a new src/update.ts (one concept), src/pages/listing.ts, src/routes.ts, src/schedule.ts (read only), tests beside them, README.md. Risks: do not loosen any contract.json cell; reuse the approval flow rather than inventing a second one; no new dependency. Suggested crew: a builder (mason's brief fits).