max / quasi

Generate a kind's configuration, and deliver one quasi-notifs, second and third halves. The declaration landed with nothing to read it; these are the two pieces that make declaring a kind worth anything. CONFIGURATION. A kind produces its own `enabled` key plus one per knob, each with a posture and a default, and a described settings pane made of those. The keys are dotted -- `event-reminder.lead`, never `event_reminder_lead` -- which is what `is_key` was refusing a dot for, and it settles the collision this was filed in front of: goingson's `event_lead_minutes` is the Events tab dot rather than a delivery setting, and a generated key cannot be mistaken for a hand-written one. The default lives in the declaration and nowhere else, which is the failure goingson's own config header records: `event_lead_minutes` came to have its default written in three places because nothing produced it. `Registry::spec` is a real `synckit_config::ConfigSpec` rather than a parallel table, so a new kind cannot arrive with its keys unclassified and therefore silently Local. It leaks its keys once, on purpose and documented: a spec holds `&'static str` because an app's spec is a const, and the registry is a static whose key set is fixed at compile time. The pane is nodes, so the terminal and egui hosts get it for free, and every control carries the write route rather than a submit button -- the case `Field::changes` exists for, and what goingson reached through 109 lines of its own dispatcher. DELIVERY. `Deliver` is one method and `Outbox` is everything a host would otherwise re-answer: the enabled key consulted before anything is sent, a duplicate suppressed by identity rather than by timing, a restart that does not spam, and bounded memory whose clearing resets the bootstrap it would otherwise defeat. All four are goingson's watcher, and all four are tested against no host at all. `CatchUp` is on the declaration because goingson answers it twice and differently: a snooze that expired overnight still fires, an event reminder for a meeting that started an hour ago does not. That is a fact about what the kind means, not about the renderer, so it is declared once rather than answered per host. `quasi_tauri::Notifier` is what is left for the host, and it is one call. Server-mediated push stays declined (`ce3be80a`); a push adapter would be a `Deliver` like any other. Both features are optional: synckit-config carries a bundled SQLite and the description suite is a suite, and an app that only declares kinds should link neither.