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

Opening a deal at an address that already has an open deal says so and links to it, and opens a second one only when the agent says so #86

shipped production is serving it opened this has it

Landed in pull #91 · 2 runs · run

opened this

Intent: typing the same listing twice in the meeting must not leave two clocks for one house.

Today plan and insertDeal in src/deals.ts check only the address's length, so the same address can be opened twice.

Done looks like:

Files: src/deals.ts, src/pages/deal.ts (or the new-deal page), src/routes.ts, src/mcp.ts, src/tty.ts, src/openapi.ts, tests, docs/TECHNICAL.md.

Risks: Restore the sample deals inserts samples directly; make sure it is not refused by its own guard. Keep the date preview step working with the warning.

Suggested: mason.

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

Reviewed pull #91 at its head: ticked plan (or insertDeal) finds an open deal whose address matches after trimming, collapsing spaces and ignoring case and a trailing period; when there is one and the input does not say openAnyway: true, it fails as a named conflict naming the existing deal.; The New deal form shows "1418 Alder Lane is already open" with a link to that deal, keeps everything typed, and offers an "Open a second deal anyway" checkbox that sends it through.; The API answers 409 with the existing deal's id; MCP open_deal and the terminal's new-deal flow say the same and accept the same override.; A closed deal at that address does not block (a house can sell again).; Tests: same address in another case/spacing is refused with the link, the override opens it, a closed deal does not block, and the API and MCP carry the refusal.; docs/TECHNICAL.md documents openAnyway and the 409..

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs