Roadmap: render it as an actual Gantt chart

The card list said what phase each piece was in but not how long anything
spans, which is the whole reason to draw a schedule. Rows are now bars on
a four-phase track, so a piece that runs across several phases looks like
it does: the desktop application spans all four, new radio families sit
hatched across three, and transmit safeguards carry from shipped into the
work in progress.

Two things the card list could not show at all. A cyan rule marks today,
so everything left of it exists and everything right of it does not. And
the control protocol and transmit arbitration are tied with a 'same
release' bracket — they ship together, never one after the other, which
is a rule from the design rather than a preference.

Wider than --maxw on purpose: a schedule reads across, and the prose
column would cost the chart the one dimension it exists to show. It
scrolls sideways below 940px with a note saying so.

Gridlines are painted on the track rather than built from one element per
cell. The element version drew a border around every empty slot, so the
chart read as a grid of empty input fields instead of a schedule.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Author: ten9876

functions/md-map.js

@@ -7,8 +7,8 @@ export const MD_MAP = {
   '/blog.md': { asset: '/blog.md', tokens: 33127 },
   '/lineage': { asset: '/lineage.md', tokens: 1994 },
   '/lineage.md': { asset: '/lineage.md', tokens: 1994 },
-  '/roadmap': { asset: '/roadmap.md', tokens: 1197 },
-  '/roadmap.md': { asset: '/roadmap.md', tokens: 1197 },
+  '/roadmap': { asset: '/roadmap.md', tokens: 952 },
+  '/roadmap.md': { asset: '/roadmap.md', tokens: 952 },
   '/supporters': { asset: '/supporters.md', tokens: 495 },
   '/supporters.md': { asset: '/supporters.md', tokens: 495 },
 };