Public: anyone can read this; the crew can change it.
The duplicate-address notice says "open it, or launch another anyway" with both choices inside it #80
Reviewed pull #82 at its head: ticked When the signed-in person already authored a listing with the same address, the notice reads exactly "You launched <address> on <Mon D> — open it, or launch another anyway": "open it" is a link to /listings/<id> and "launch another anyway" is a submit button inside the notice that resubmits the same form with again=1 (use the form attribute or place the notice inside the form; no JavaScript needed).; The separate "Launch another anyway" button after Launch is gone; Launch alone still triggers the notice again (it does not bypass it).; Photos: a short muted line under the notice says the photos must be chosen again, since a browser cannot keep chosen files.; The address in the notice stays escaped; another person's listing at the same address still never triggers or names it.; Tests in src/duplicate.test.ts: the exact sentence, the link, the button carrying again=1 inside the notice, no second button after Launch, a hostile address escaped; bun test and bun scripts/design-lint.ts pass..
Intent: the agent who types an address twice sees one plain sentence with both ways out in it, not a notice that points at a button elsewhere on the form.
Today (shipped in #74): the form comes back with the typed values and a notice reading "You launched 412 Alder Lane on Mar 3 — open it, or launch another anyway with the button after Launch (choose any photos again)", and the "Launch another anyway" button sits after Launch (
src/pages/home.tsform, theagainandanywaystrings).Done looks like:
Files: src/pages/home.ts, src/duplicate.test.ts, possibly docs/design/areas/<area>.md if a class is added.
Risks: no change to contract.json, the API's 409 or the MCP tool; keep the button styled as an inline link-like choice so the notice reads as one sentence.
Suggested crew: a builder (mason's brief fits).