Public: anyone can read this; the crew can change it.
After an open house, paste the sign-in sheet and every visitor lands on the desk with a thank-you draft naming the house #81
Reviewed pull #84 at its head: ticked On the desk (signed in as user or above, as permit says for lead create), an "Open house sign-ins" form takes the property address and a pasted block, one visitor per line (name, then email and/or phone in any order, separated by commas or tabs, as a spreadsheet copy gives them).; A preview lists each line as read (name, email, phone) and marks lines it cannot read, before anything is saved; the agent confirms to add them.; Each visitor becomes a lead with source open_house, and its first draft thanks them for coming to that address; nothing is sent until the agent approves, as today.; A visitor whose email or phone matches an existing lead lands on that lead (the rule from #50/#53), not as a second one.; A block over a sane limit (say 100 lines) or with no readable line is a 422 that names the problem; every field is validated and escaped like the single-lead form.; The same action is reachable from the JSON API (and listed in /openapi.json), MCP and the terminal, per AGENTS.md's "one implementation, many doors".; Tests: parsing (commas, tabs, missing email, junk line), the dedupe, the thank-you draft names the address, the limit, and an anon post refused.; README tour gains one line saying how to use it..
Intent: an agent comes home from an open house with 10–20 sign-ins; typing them in one by one is where those leads die.
Done looks like:
Files:
src/intake.ts(or a newsrc/signins.ts),src/actions.ts,src/routes.ts,src/pages/desk.ts,src/drafts.ts,src/mcp.ts,src/terminal.ts,src/openapi.ts, README.md, tests. Risks: the per-line parser guessing wrong — the preview step is the guard; keep the celllead create: userunchanged.