docs: say how far in the ladder goes, and why

F1 described the scale only by how far out it goes — three months on a
screen — which left the close end reading as decoration rather than the
answer to two events ending a day apart. The suite count moves with the
test the previous commit added.

Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>

AGENTS.md

@@ -116,7 +116,7 @@ src/client/       React app, service worker, manifest
                   lanes.ts — how the timeline stacks: a lane per game, or one deadline queue; pure
 scripts/          build-feed.ts, build-static.ts, parse-fixture.ts (offline), refresh-sources.ts (fetches)
 serve.ts          static server + /api/health
-test/             606 tests
+test/             607 tests
 fixtures/<game>/  raw HTML + .expected.json per source — pinned, kept forever
 snapshots/        current page per source, rewritten by refresh — see its README
 ```

docs/PRD.md

@@ -105,6 +105,12 @@ three-month board throws away whatever the reader had scrolled to. And the dated
 the scale shrinks, since a week is 42px at the widest setting and the dates would sit on top of one
 another; the gridlines stay weekly either way, because they carry the rhythm rather than the reading.
 
+The close end of the ladder goes to a day being wider than a fingertip (108px). That is not a
+flourish: events routinely end within a day of each other, and at a scale where their bar ends are a
+few pixels apart the board is being asked the one question it exists to answer and telling the
+reader to squint. It also gives a one-day event a bar to read and to tap rather than the 34px
+minimum every short bar collapses to.
+
 **The board draws at most two months of past.** A standing login campaign can have been running for
 half a year, and drawing from the earliest start bought months of empty calendar that nobody scrolls
 back through and that pushed every other bar off to the right. An event older than the board keeps