max / makenotwork

server: take quasi 0.65, where a toast lives 3000ms Forward fix for quasi `e97b09a`, under Max's ruling on `eea7ba88`. The webview renderer now reads `--timing-dismiss` off `timing.css` rather than carrying four seconds of its own, so the toast on this server goes from 4000ms to the 3000ms `makeover_timing::Intent::Dismiss` names. static/quasi-clock.js is generated from CLOCK_JS by build.rs and gitignored, so it follows without being committed. The lock also picks up the makeover working copies the tree is already on (makeover-layout 0.54, makeover-timing-adjacent 0.25, makeover-webview 0.61), which is the re-resolution the [patch] block produces. 969 packages before and after. The legacy toast path, static/dist/core/toast.js, was already at 3000 and is untouched. Its 6000ms error toast in htmx-glue.js is a separate finding: a message the user must not miss is not Notice::transient.