max / quasi

0.65.0: a toast's lifetime is named once, and it is 3000ms `84a99fe6`, under Max's ruling on `eea7ba88`: (b), "3000 for now". The three renderers held the same four seconds written out three times, against `makeover_timing::Intent::Dismiss`'s 3000. The value the crate publishes wins and the literals go. quasi-tui and quasi-immediate take `makeover-timing` and derive `LINGER` from `notice_lifetime(true)`; both `expires_at` sites now resolve one call rather than checking transience and reading a constant, which is the same branch said once. The public `LINGER` name stays in both, since both re-export it. quasi-webview reads `--timing-dismiss` off the computed style instead. That is the property makeover-build has written into every consumer's `timing.css` since 0.52.0, and it had no consumer until now. The script keeps a fallback for a page that ships it without the stylesheet, pinned to `Intent::Dismiss.ms()` by a test, on the same footing as the two elapsed-time format implementations that already agree across two languages by test. Not done here and filed as quasicoherent `43bdbff7`: the done condition's "waiting Motion::Fade before removing the node". No renderer has a leaving, the webview has nowhere to put the rule (the stylesheet is makeover-webview's, which carries no toast styling), and adding the wait without the fade is only a longer message. Consumers forward-fixed in the same pass: MNW server, audiofiles, goingson. MNW's static/quasi-clock.js is generated from CLOCK_JS by build.rs, so it follows on its next build.