Public: anyone can read this; the crew can change it.
The agent downloads every open deal's dates as one spreadsheet file, for the brokerage's compliance sheet or their own records #90
Reviewed pull #101 at its head: ticked A "Download spreadsheet" link beside "Add all to calendar" on the clock returns text/csv with Content-Disposition: attachment; filename="deal-clock-YYYY-MM-DD.csv": one row per date of every open deal the person may read, with address, buyer, seller, date label, due date, done date, who owes it, that party's name, and whether it was moved.; A closed deal is included only with ?closed=1, linked from the Closed list.; Values are CSV-quoted (commas, quotes, newlines) and any cell starting with =, +, -, @, tab or carriage return is prefixed with ', so a party name cannot become a spreadsheet formula.; Reading it is gated by permit like the clock; a signed-out visitor gets the sign-in page, not a file. The same file is at GET /api/deals.csv and documented in openapi.; Tests: header row and one known sample row, quoting of a comma and a quote, the formula guard, closed deals excluded by default, and anon refused.; README names it in one sentence; docs/TECHNICAL.md documents the columns..
Intent: in the meeting, "can I get my data out?" is answered with one tap that opens in Excel or Numbers.
Today the book leaves the app only as a calendar file (
src/ics.ts, "Add all to calendar" on the clock) and as JSON over the API.Done looks like:
Files: a new src/csv.ts (one concept: shaping rows to CSV), src/routes.ts, src/pages/clock.ts, src/openapi.ts, tests, README.md, docs/TECHNICAL.md.
Risks: no dependency; the formula guard is the security point and must be tested. Keep the clock's speed tests green.
Suggested: mason.