The clock says what changed since the agent last looked: dates moved, marked done or newly overdue #320

The clock now shows one quiet line above the book summary when something changed since your last visit, for example "Since yesterday: 1 date moved, 2 marked done, 1 newly overdue". It is absent on a first visit and when nothing changed. The new tests and the neighbouring suites pass. I did not run the whole suite or a type check: the repository has no tsconfig.json and no scripts/fast.ts.

• Last visit storage: a new migration adds a visit table under FORGE_APP_DATA, one row per signed-in user.
• Moves and done marks: src/since.ts counts the existing date.move and date.done audit rows on the viewer's own deals, so there is no second log. They are counted from visit.since, the moment of the last visit that was at least 30 minutes before the latest one.
• Newly overdue: this is not in the audit log. It counts open dates on open deals that fell due between the day of your last look and today.
• Rendering: the line is part of the server-rendered clock page, so nothing shifts, and its text is escaped. src/routes.ts records the visit and passes the line in, and src/pages/clock.ts includes it in its render cache key.
• Contract: no cell is changed.
• Docs: the README mentions the line in a paragraph outside the numbered tour, because a test pins the tour steps to src/tour.ts. docs/TECHNICAL.md has a row for the new module.
• Tests: src/since.test.ts covers the wording, the first visit, the reload rule, the counts (including other people's deals being left out) and the rendered page. I also added the new migration to the exclusion list in src/migrations.test.ts.

A reload within 30 minutes of your last view keeps the line instead of wiping it, which is why the baseline lags the latest view. The line reads "Since earlier today", "Since yesterday" or "Since Mon, Nov 9". I did not add the line to the terminal, JSON API or MCP, since the issue only asks for the clock page. To try it, open the clock, move or mark done a date, then come back after 30 minutes or more.

Closes #318

The clock now shows one quiet line above the book summary when something changed since your last visit, for example "Since yesterday: 1 date moved, 2 marked done, 1 newly overdue". It is absent on a first visit and when nothing changed. The new tests and the neighbouring suites pass. I did not run the whole suite or a type check: the repository has no tsconfig.json and no scripts/fast.ts.

• Last visit storage: a new migration adds a visit table under FORGE_APP_DATA, one row per signed-in user.
• Moves and done marks: src/since.ts counts the existing date.move and date.done audit rows on the viewer's own deals, so there is no second log. They are counted from visit.since, the moment of the last visit that was at least 30 minutes before the latest one.
• Newly overdue: this is not in the audit log. It counts open dates on open deals that fell due between the day of your last look and today.
• Rendering: the line is part of the server-rendered clock page, so nothing shifts, and its text is escaped. src/routes.ts records the visit and passes the line in, and src/pages/clock.ts includes it in its render cache key.
• Contract: no cell is changed.
• Docs: the README mentions the line in a paragraph outside the numbered tour, because a test pins the tour steps to src/tour.ts. docs/TECHNICAL.md has a row for the new module.
• Tests: src/since.test.ts covers the wording, the first visit, the reload rule, the counts (including other people's deals being left out) and the rendered page. I also added the new migration to the exclusion list in src/migrations.test.ts.

A reload within 30 minutes of your last view keeps the line instead of wiping it, which is why the baseline lags the latest view. The line reads "Since earlier today", "Since yesterday" or "Since Mon, Nov 9". I did not add the line to the terminal, JSON API or MCP, since the issue only asks for the clock page. To try it, open the clock, move or mark done a date, then come back after 30 minutes or more.

The clock now shows one quiet line above the book summary when something changed since your last visit, for example "Since yesterday: 1 date moved, 2 marked done, 1 newly overdue". It is absent on a first visit and when nothing changed. A second commit fixes the two preview failures, which came from tests and not from this feature. After that fix src/sample.test.ts and src/terminal.test.ts pass, and src/since.test.ts passed before it. I did not run the whole suite or a type check: the repository has no tsconfig.json and no scripts/fast.ts.

The feature

• A new migration adds a visit table under FORGE_APP_DATA, holding each person's last look at the clock.
• The line is built in the new src/since.ts, which counts date.move and date.done audit rows on the viewer's own deals, so there is no second log. Newly overdue is not in the audit log: it counts open dates that fell due between your last look and today.
• A reload within 30 minutes of the last view keeps the line, because the baseline only advances once a look is at least 30 minutes old.
• The line is server-rendered and escaped, so nothing shifts.
• No contract cell is changed. The terminal, JSON API and MCP do not show the line, since the issue only asks for the clock.
• The README mentions the line in a paragraph outside the numbered tour, because a test pins the tour steps to src/tour.ts. docs/TECHNICAL.md has a row for the new module, and src/since.test.ts covers the wording, counts, reload rule and page.

The two preview failures

• Both fail identically on main today, 2026-11-11, which is Veterans Day, so they were not caused by this pull.
• On a weekend or holiday boot the sample's first date rolls forward to the next business day. Its reminder is then already past, and a declined past reminder drops off the list.
• src/sample.test.ts now accepts the next business day as the latest the first date may fall on, on a non-business day.
• src/terminal.test.ts now reads the "not sent" and undo steps only on a business day.
• I changed these two tests and left the sample-rolling code alone, because changing it would shift the tour's dates on every non-business boot and risk the README tour. If you would rather the sample always land its first date on the boot day, that is a separate change.

To try it, open the clock, move or mark done a date, then come back after 30 minutes or more.

I've addressed all three review points and pushed them to the branch.

src/terminal.test.ts, src/since.test.ts, src/sample.test.ts and src/readme.test.ts pass. One run of the terminal suite failed a different test, "U puts a date back…", with a 6.4 s runtime, and the next full run of the file passed 62/62. I took it for load, since I did not look into why it failed. I did not run the whole suite or a type check: the repository has no tsconfig.json.

• Terminal line: the terminal's date list now shows the same "Since yesterday: …" line. A new sinceFor in src/since.ts is the one call that records the visit and builds the line, and both GET / and src/terminal.ts use it. The terminal asks once per session, so a key press redraws without counting as another visit. A guest gets none. The README and docs/TECHNICAL.md say so, and a new terminal test checks the line appears, survives a redraw, and is absent for a guest. It would fail without the feature.
• Zone tidy: src/routes.ts now computes agent.zone ?? DEFAULT_ZONE once, as zone.
• Decline test: I removed the isBusinessDay guard. The test now creates its own deal and a date due in 3 days, so its reminder is due today on any day. The undo steps always run.
• Not split out: I did not split the holiday fixes into a separate pull, because I cannot open pulls. The src/sample.test.ts change is an assertion that always runs, accepting the next business day as the latest the first date may fall on. If you want it separate, drop that commit.

I also noticed that the counts cover every deal the viewer can list, not only deals they authored. The deal list cell lets any user list every deal. That matches what the clock itself shows them, so I left it.