max / quasi

Move the Tauri delivery adapter to quasi-notifs, behind a tauri feature Settled in quasicoherent c231ff13 (Max): option (a), a feature on quasi-notifs rather than a crate of its own. quasi-tauri depends on quasi-router and quasi-http unconditionally -- the protocol handler is most of what it is -- so its `notifs` feature could not be taken without the whole description stack coming with it. Eight lines over tauri-plugin-notification cost an app the router, which is why goingson wrote its own copy instead of adopting the framework's. quasi-notifs is where it belongs on its own terms rather than by elimination. deliver.rs already holds Occurrence, the Deliver trait and Outbox, so the crate defines the delivery abstraction and an impl of it is not foreign; "apart from how it reaches a person" is about the kinds, not the crate. And the dep-free argument needed no rewriting: synckit and describe already make synckit-config and quasi-router itself optional on the ground that an app which only declares kinds should not link one to do it. `tauri` is the third instance of a pattern the crate already runs. quasi-tauri's `notifs` feature goes away rather than re-exporting, so there is one place to find the adapter. Nothing else in the tree named it. (b), making quasi-router optional in quasi-tauri, was declined for the reason the task gave: it is a feature that turns off the crate's purpose. (c), leaving it, was declined because the adapter then gets rewritten by whoever adopts first in each app, and goingson was already that.