max / quasi

0.99.0: say code as classified runs, and a diff line as a change quasicoherent 19d7602d, option (d), and the last certain gap in the vocabulary. `Node::Code { runs, language, inline }` carries `Lexeme`s and never a bare string. That is the whole ruling: an app that browses source already has a lexer, a renderer does not and should not grow one, and three renderers each growing their own would disagree about the same file. The alternatives were a highlighter inside quasi-webview that goingson and audiofiles would pay for although neither browses source, or a `Node::Diff` putting git's data model in a vocabulary shared by a task manager and a sample browser. `inline` is a flag rather than a second member because the distinction is containment: a clone URL in a sentence and a file in a source browser are the same claim about the same text, and `Node::containment` reads the flag, so an inline literal is a leaf that may sit in a Row or a Cell and a block is not. `Lexeme` carries its own text rather than a range into a source string. A range would allocate less and would hand every renderer a byte offset that may not land on a character boundary; two of the three would get it wrong on the first file with a multi-byte character in it. The run carrying its text cannot express that bug. `Cells::change` is the diff half, so file, blame and a diff are all `Node::Table` and nothing here learns what a hunk is. `None` is not `Change::Context`: one says this table is not a diff, the other says this line did not change, and without the distinction every ordinary table in the tree would read as a diff whose lines are all context. All three renderers have an arm, and none took a dependency: - quasi-webview writes a span per classified run, `lex-<class>` off `Syntax::name`, and nothing at all for a plain run, which is most of a file. A diff row gets `data-change` beside `data-tone`, so a host that has never heard of a diff still gets the success and danger it already styles. - quasi-tui maps the classes onto the theme's status colours, following base16 Tomorrow, and puts the diff's sign in front of the row rather than a tint behind it: the sign survives a monochrome terminal and a colour does not. - quasi-immediate does the same in egui, monospaced. The two terminal-shaped choices are documented where they are made rather than here: a terminal spending status colours on syntax is deliberate, because the palette has no syntax colours and is not going to grow any.