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

Each deal shows how far along it is, as "4 of 7 dates done · closes in 12 days", on the clock and its page #81

shipped production is serving it opened this has it

Landed in pull #87 · run

opened this

Intent: in the meeting the agent glances at a deal and sees how far along it is, without counting rows.

Today a lane on the clock (src/pages/clock.ts:68) shows only the closing date and any "out of order" count. The deal page (src/pages/deal.ts) lists the dates but gives no summary.

Done when:

Files: src/deals.ts or a new src/progress.ts, src/pages/clock.ts, src/pages/deal.ts, src/routes.ts/src/openapi.ts, static/app.css, tests, docs/design/areas/clock.md.

Risks: the bar must not shift layout when live updates arrive, so reserve its height. Keep it one query per page, not one per deal.

Suggested: mason.

commented

Reviewed pull #87 at its head: ticked One function (in src/deals.ts or a new src/progress.ts) takes a deal and returns plain data: dates done, dates total, dates overdue, and days to closing. The clock lane head, the deal page heading and GET /api/deals/:id (as a progress object, also in openapi.json) all use it.; The clock lane and the deal page show "N of M dates done", plus "· K overdue" when K > 0, next to the closing text. They also show a thin progress bar that is decorative (aria-hidden); the text carries the meaning. A closed deal reads "All done · closed <date>".; A removed date does not count. Reopening a date lowers the count again, and the live update (deal.changed) refreshes it without a reload.; Tests cover the function (no dates, all done, some overdue, closed), and check that the clock and the deal page render the line for a sample deal.; The clock still answers in under 50 ms with 200 deals (src/speed.test.ts stays green), and bun scripts/design-lint.ts passes. Any new class is named in docs/design/areas/clock.md..

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs