max / quasi

Node::Rich carries richness and trust as two axes docengine's presets are named points on a diagonal: strict turns tables, footnotes and task lists off at the same time as it turns nofollow, raw-HTML stripping and scheme filtering on. quasi read one name off that diagonal for every source, so the only way to have prose with a followed link in it was to ask for the permissive treatment of raw HTML as well. MNW hit the consequence: nine internal links across four described pages were telling crawlers not to follow the site's own documents. Richness is what the format may express, Trust is who wrote it. They correlate without being the same question - a creator's forum post is rich and untrusted, a button's own hint is plain and trusted - and the four cells all mean something, including Document + Untrusted, which no docengine preset spelled. quasi-webview composes docengine::Renderer from the two rather than picking a preset. Prose + Untrusted is Renderer::strict() field for field, so every call site written before the axes existed keeps exactly what it had, and Trust::Untrusted is the Default, written out rather than derived because the unsafe direction has to be the one somebody types. The scripting fence on the rich div earns its place now: an untrusted source never reached it with an attribute, a trusted one can, so the guarantee stops depending on which way the axis is set. The inline path inside a row still takes neither axis. That is containment rather than trust: a run in a cell is one line in something usually already clickable, so blocks and links go whatever the node declares. quasi-tui ignores both, and says so: Trust protects a document from an author and a terminal has no document to protect. 0.93.0 -> 0.94.0 across the suite.