max / quasi

0.39.0: a readout can say it is derived from now, and each renderer ticks it `ba4dcfae`, implementing the ruling on `f00244a6` (Max, 2026-08-18, jointly with `4453bf82`): the renderer owns the clock, and what a description carries is a kind rather than a format string. `Node::Since`, `Node::Until` and `Node::Age` each hold a `SystemTime` and say which way the readout runs against it. Nothing here names a cadence or a spelling. Why a kind and not an instant plus a format: a format string is presentation living in a description, and it would bind three renderers with different width budgets to one spelling. Why not a bare instant: a stopwatch and a last-modified stamp become indistinguishable, so a renderer cannot pick a cadence and would tick a static date once a second. The kind answers many-readouts-one-tick for free, since every `Since` on a screen refreshes together by sharing one, and `Screen::clocks` is how a renderer asks which kinds it is holding. All three are leaves, so a readout sits in a row's run or a table cell, which is where the measured one is. Each renderer picks two cadences off the granularity it chose to draw at: a second for the stopwatch and the countdown, which read `h:mm:ss`, and thirty seconds for the stamp, which reads "3h ago" and changes on the minute at its finest. The three picked the same numbers, so a screen described once and drawn three times does not go stale at three rates. quasi-tui answers `Runtime::tick_in` for a host to use as its input timeout; quasi-immediate asks the context for the frame, since egui sleeps between them and a stopwatch nobody woke is a stopwatch that stops; quasi-webview emits the instant and the kind as attributes with the first words beside them and ships `CLOCK_JS`, which writes every set after that. `Shell::clock_src` serves it, `without_clock` drops it, and dropping it leaves the server's words on the page rather than a hole -- the failure mode the selection script already has, and not idiomorph's silent one. The webview states the format twice, once in Rust and once in JS, and both sides carry a note plus tests at the boundaries the script's branches turn on. That is the cost of a renderer that emits once and is then held by a browser. Forward-fixed: goingson, audiofiles and the MNW server take 0.39. goingson's task row was the site waiting on this ruling by name -- its time cell held a "Timer running" badge and a comment saying the elapsed value was undecided; it now carries `Node::since` of the session's start.