Public: anyone can read this; the crew can change it.

Log each showing and the buyer agent's feedback on the listing, and see the count on the home list #81

shipped production is serving it opened this has it

Landed in pull #89 · 2 runs · run

opened this

Intent: after every showing the agent writes down who came and what they said, so the listing page answers "how is it showing?" in the meeting and the seller conversation has facts.

Done looks like:

Files: src/db.ts (a showings table keyed to the listing), a new src/showings.ts, src/actions.ts, src/routes.ts, src/mcp.ts, src/pages/listing.ts, src/pages/home.ts, src/sample.ts, README.md, a new src/showings.test.ts.

Risks: showings hold third-party names, so they must never reach the public property page, the email or the flyer; keep it out of the audit resource's reach except as a listing update; deleting a listing removes its showings.

Suggested crew: a builder (mason's brief fits).

the crew's run was interrupted: restart, resumes on the next pass — cancelled
commented

Reviewed pull #89 at its head: ticked The listing page /listings/:id has a Showings section (author only to add): date (defaults to today, not in the future), buyer's agent name (optional, up to 80 chars), interest (Not interested / Maybe / Interested / Offer likely) and one feedback line (up to 280 chars, plain text, no control characters). Saved with a plain form POST that works without JavaScript; newest first.; Feedback is Fair Housing checked like typed words and a flagged line shows its finding beside it; showings are never shown on the public property page.; The author can remove a showing they logged. Anyone else (anon, another user) gets 403/404 from the form and the API, decided through permit as an update of the listing; no change to contract.json.; The home list shows "5 showings" beside each listing that has any; GET /api/listings/:id carries showings; POST /api/listings/:id/showings and an MCP log_showing tool add one with the same validation (422 with the field named).; The sample listings come with two or three showings each so the meeting has something to look at.; Tests (a new src/showings.test.ts): add, list order, remove, a future date refused, an over-long or hostile line refused/escaped, another user refused, not on the property page, the count on the home list; the speed test still passes.; README's agent section says it in a realtor's words..

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs