Skip to content

History / Codebase Rules

Revisions

  • docs(rules): state the pointer-driven hover rule for hairline handles

    @rajebdev rajebdev committed Nov 17, 2026
  • docs: record the DOM-globals pair, the voided in-flight read, and platform-named tests The Release gate of 2026-11-13 failed 20 cases on two legs, none of them in the file that caused it. Three rules keep the next reader from re-breaking it: a suite restores the window it installs through `pristine-globals` and that list carries `EventTarget` beside `Event`; a module-level client cache is voided together with its in-flight read; and a test that takes a platform argument builds its expectation with that platform's rules.

    @rajebdev rajebdev committed Nov 13, 2026
  • 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.

    @rajebdev rajebdev committed Nov 10, 2026
  • docs(layout): record the chat column's width modes One variable (`--chat-column-max`), one class (`chat-column`), one attribute (`data-chat-width` on `<html>`): the fact that used to be an `max-w-[970px]` literal at eight call sites. The page states the three widths, why `full` widens the composer too, why the default is removed from the attribute rather than written, why the overrides are `:root[data-chat-width=…]`, and why the choice is global instead of per-session. Codebase-Rules gets the one rule a future reader would otherwise re-break: a width that belongs to the chat column is a READING width, not one of the remembered panel widths — the chat is the layout's filler column, so it has no px and no fraction to remember.

    @rajebdev rajebdev committed Oct 29, 2026
  • docs: split the manual into a wiki

    @rajebdev rajebdev committed Oct 28, 2026