[blike]

Summary

On a long Tesla history, going to an old date on the Drives page lagged badly, the Charging calendar offered months back to 2016, and long drives' routes stopped short. This makes going to any date one page read, starts the Charging calendar at the first session, and draws every position of a drive.

Changes

• Go to a date with one read. Picking a day the Drives or Charging list hasn't read yet used to read every page from today back to it. On a car with 9,365 drives, a day in 2022 took 47 pages and about 24 s of queries, with the list redrawing after each page, and every 5-minute refresh then re-read all 47. The list now opens at the picked record: one page, about 0.4 s.
• Newer pages above. A list opened part way back has a "Show newer drives / Back to latest" row at the top, and the mobile picker's newer arrow reads the page above too. The list keeps its place as newer records arrive above. Listings take a new after parameter (both sources) for this.
• Charging calendar starts at the first session. It had no start date, so it fell back to ten years back. The new GET /api/vehicles/:id/charging-coverage gives it one, as drive-coverage does for Drives.
• Long drives draw the whole way (A drive's detail route stops short when the drive has more than 10,000 positions #108). Drive detail read only the first 10,000 positions, about an hour of streamed driving. On one database that was 113 of 12,137 drives, the longest 29,922 positions. Tesla and Rivian detail now read every position, and so do Tesla trips, which still simplify routes before sending. The map draws every point; the speed/elevation chart draws an even 1,000 (evenly(), CHART_POINTS).
• Hovering the chart no longer redraws the page. The hovered point was held by the Drives page, so each new point redrew the drive card, calendar, every list row and the chart, and rebuilt the route. The map and chart now sit in their own RoutePanel; hovering moves only the map's marker, and the chart and route are built once per drive.
• DOM component tests (The web package has no DOM test environment, so component behaviour cannot be tested #103). Adds jsdom and Testing Library. A test opts in with // @vitest-environment jsdom, so existing static tests are unchanged.

Testing

• Unit tests added/updated: a jsdom test that goes to a date 900 days back and checks that two pages are read (not six), then Show newer and Back to latest; tests for evenly()
• Integration tests passed: DB tests for after paging and charging coverage on both sources, plus every position of a 25,000-position Tesla drive (704/704 with TEST_DATABASE_URL)
• Manually tested: against a real Tesla database (2 cars, 12,137 drives, 30M positions) in the browser, and by timing the server calls
• Existing tests passed

On a real Tesla database	Before	After
Go to Sep 2022 on Drives	47 pages, ~24 s	1 page, ~0.4 s
Charging calendar's first month	2016	Sep 2022
Drive with 29,922 positions	first 10,000 drawn	all, in ~160 ms

Deployment

• No special deployment requirements