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

Add a date offers the dates contracts usually add, like HOA documents review, survey or repair request deadline, so the agent picks one instead of typing it #131

Closed opened this has it

Landed in pull #153 · run

opened this

Intent: the standard seven dates are built in, but every extra date is typed by hand today (src/pages/deal.ts, the Add a date form). In a meeting that is slow and gives "HOA docs", "HOA review" and "hoa" on three deals.

Done looks like:

Files: src/deadlines.ts, src/pages/deal.ts, src/routes.ts or src/actions.ts (wherever add-a-date is handled), src/mcp.ts, src/openapi.ts, tests. Risks: a datalist renders differently on iOS Safari. It must still be a plain text field that submits what was typed. Do not add a new kind to the Kind union. These stay custom dates. Suggested builder: mason.

commented

Reviewed pull #153 at its head: ticked The What field in Add a date suggests a short list of common extra dates: Seller disclosures due, HOA documents review ends, Survey due, Repair request deadline, Home warranty ordered, Lead paint inspection ends. Use a plain <datalist>: no JavaScript, and the agent can still type anything.; The list is plain data in one module (for example in src/deadlines.ts next to the standard dates). Each entry has its label and a suggested reminder lead in days. When the posted label matches an entry exactly and no lead is given, the date gets that entry's lead.; A page test checks the datalist is on a deal's page and that its options are escaped. A unit test checks that an exact-match label gets its lead and a typed label keeps the default.; The a11y test still passes: the field keeps its label. bun test passes and bun scripts/design-lint.ts is clean.. left open: The suggestions do the same for the add-a-date tool over MCP, through its description, and the API's add-a-date body in /openapi.json. Validation of the label (length, required) stays as it is. — MCP description is done, but /openapi.json has no add-a-date endpoint, so no body was documented there..

commented

Left open after pull #153 landed: 1 unticked item remains (The suggestions do the same for the add-a-date tool over MCP, through its description, and the API's add-a-date body in /openapi.json. Validation of the label (length, required) stays as it is.). 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.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs