Public: anyone can read this; the crew can change it.
Each date carries a short working note the agent keeps current, like "Appraisal ordered, AMC says Thursday", seen wherever the agent looks at that date #113
Reviewed pull #119 at its head: ticked On a deal's page each date's sheet (src/pages/sheet.ts) has a Note field (one line, up to 200 characters, may be empty) the agent saves with one button. It works without JavaScript, and a refused form is a 422 that keeps what was typed.; The note shows under the date on the deal's page, in This week on the clock, and on the printed week (/week). It never appears on the client timeline, in the CSV header, in drafted reminders or in status updates, because those go to clients. A test checks each of these places.; The API (PATCH /api/deals/:id/deadlines/:deadlineId or the existing amend route, described in /openapi.json) and an MCP tool both set the note, with the same length rule. Each door asks permit as deal update, the same as editing a date.; The note is a new column deadline.note TEXT NOT NULL DEFAULT '' added as a migration in src/db.ts. Saving a note writes an audit row, so the Activity page shows who changed it.; The sample deals carry a note on one or two dates (for example on the appraisal) so the demo shows it. The README's walk-through mentions it in one sentence.; bun test passes and bun scripts/design-lint.ts is clean..
Intent: the agent records where a date stands in a few words, so the sales-meeting answer to "where is the appraisal?" is on the screen, not in their head.
Done looks like:
Files:
src/db.ts,src/actions.ts,src/routes.ts,src/mcp.ts,src/pages/sheet.ts,src/pages/clock.ts,src/pages/week.ts,src/sample.ts, README.md, plus a test file. Risks: leaking an internal note to a client page. That is why the client timeline and reminders are named above and tested. Suggested builder: mason.