Public: anyone can read this; the crew can change it.
Launching an address you already launched asks first, and links to the listing you have #72
Landed in pull #74
Reviewed pull #74 at its head: ticked With again=1 it launches as today. Another person's listing at the same address never triggers the notice and is never named (no leak of who else listed it).; The JSON API and the MCP launch tool answer 409 duplicate_address with the existing id unless the request says again: true; the terminal asks once.; "Start a new one from this" on a sample still works without a notice when the address is changed.; Tests: the notice for the author, none for another user, again launches, API 409, a hostile address escaped in the notice; the speed test still passes.; README's agent section says it..
Left open after pull #74 landed: 1 unticked item remains (Launching from the form on / when the signed-in person already authored a listing with the same address (compared trimmed, case- and space-insensitive) answers with the form again, every typed value kept and escaped, and a notice: "You launched 412 Alder Lane on Mar 3 — open it, or launch another anyway", the first a link to /listings/<id>, the second a button that resubmits with again=1.). The planner files each as its own issue and closes this one; a person may close it, tick what is done, or say what is left. Until then the crew does not pick it again.
Intent: an agent who types an address twice in the meeting is sent to the listing they already made instead of quietly getting a second one.
Done looks like:
Files: src/actions.ts (the launch action), src/listing.ts (find by address for an author), src/routes.ts, src/pages/home.ts, src/mcp.ts, src/tty.ts, a new src/duplicate.test.ts, README.md.
Risks: no change to contract.json; the lookup reads only rows the person authored; keep the photo upload written with its row or not at all when the form comes back.
Suggested crew: a builder (mason's brief fits).