docs: listed M24 in the milestone index Also synced the rows the index never gained (19, 20, 22, 23), corrected M13 to partial and the numbering note to name the milestones that actually are planned.
docs(terminal): match the wiki to the ghostty-web renderer The terminal page still described xterm: `XTERM_GLYPH_FALLBACKS` (renamed to `TERMINAL_GLYPH_FALLBACKS`), an atlas refresh that no longer exists (`refreshAtlasWhenNerdFaceLoads` / `clearTextureAtlas`), `onBinary`, and a Cmd key that xterm discards. It now states what ships, with the measurements each rule came from: - both faces are awaited and a late one re-measures the grid, because the renderer measures its cell box at `open()`; - the cell box is Kabmo's `Mg` ink plus 4 px above / 1 px below (16 px), not the vendor's 13 px that ends on the descender and clips every SGR background block; - the terminal paints no surface and the fit drops the addon's 15 px scrollbar reservation, so the grid uses the whole panel; - a grid is announced only from a fit that measured the container, is at least 10x5, and held still for 120 ms — `resize 5x37` and the 80x24 default both reached a shell, whose wrapped prompt redraws then lived in the scrollback and replayed on every reload; - PTY frames must leave as binary frames; the JSON byte-map spelling was the ceiling (4.58 MB/s against 34.8 MB/s). The neighbouring pages that named `.xterm`, a WebGL canvas, an xterm buffer and an xterm-owned scrollbar follow, and M21 joins the index.
docs: add the Milestones page Kabmo's plan pages had no index and no order, and several of them still said "nothing implemented" after the feature shipped. The main repository now keeps them as `docs/milestones/M<NN>-<slug>.md`, numbered by when the work started, with one status line each and a contract test pinning the naming and the links. This page is the index a reader lands on: the eighteen milestones with what each delivered and where it stands, the five still owed and why (a browser leg that will not launch, a desktop sidecar never built, a device run emulation cannot do, and two research-only pages), and the two items declined on the record instead of left open. It also states the two rules a future reader would otherwise re-break: a number means when the work started, so a `planned` page keeps an early one; and a status line is a claim with a date and a commit behind it, which is what makes it worth reading. `Harnesses` is the one existing page that cited the old paths, so its two links move here too.