Public: anyone can read this; the crew can change it.
The agent can narrow the clock to deals closing this week, this month or later #309
Landed in pull #314 · 2 runs · run
Parked by the crew: the check stayed red through 2 automatic tries (pull #311 closed; its branch mason/309-the-agent-can-narrow-the-clock-to-deals at e971083107b1 keeps the work so far). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.
try 1: README.md, src/closing-window.test.ts, src/pages/clock.ts, src/speed.test.ts try 2: README.md, contract/openapi.json, docs/TECHNICAL.md, src/actions.ts, src/checkin.ts, src/clear.test.ts, src/db.ts, src/deals.ts, src/leaks.test.ts, src/… try 3: .bash_profile, .bashrc, .claude/agents, .claude/commands, .claude/hooks, .claude/launch.json, .claude/loop.md, .claude/output-styles, .claude/routines, …
Reviewed pull #314 at its head: ticked A Closing choice (Any, This week, This month, Later) next to Side on the clock form, a GET parameter validated against that list (anything else is refused with the usual message); it composes with q and side and Clear resets it.; The clock, This week and today's reminders narrow the same way find does, via a small pure function beside src/find.ts taking deals and today's date in the agent's timezone.; Server-rendered, no new JavaScript; the choice survives the page's other links as side does today.; Tests: each bucket on the sample deals (dated from today), combination with q, invalid value refused, boundary day; the page answers inside the existing speed test budget.; README line under Finding a deal; bun test and design-lint pass; any new class in docs/design/areas/..
Intent: in a meeting the realtor asks "what closes this month?" and the clock answers in one tap, beside Find and Side.
Done looks like:
Files:
src/find.ts(or a newsrc/closing-window.ts),src/routes.ts,src/pages/clock.ts, tests, README. Risks: no contract cell, no migration. Brief: a builder (mason).