\n A fully-local, multi-backend camera.ui notifier\n plugin — delivers notifications to a service you control (ntfy,\n Gotify, Pushover, Telegram, Discord,\n Grafana, or a generic webhook).\n
\n\n---\n\n## Why this exists\n\n\nThere is intentionally no notifier in the open ecosystem: the closed, official NVR bundles a notifier that pushed to the camera.ui mobile app through camera.ui's proprietary FCM/APNs cloud relay. This plugin takes the only fully-local road to real background push instead: delivering to a push/webhook service *you* run or control.\n\nThis plugin is a pure **notifier**. It is decoupled from any single publisher — it delivers notifications from **any** publisher, including our NVR plugin's detection events and camera.ui's own system notifications, not just one plugin's output.\n\n## How it works\n\nOne plugin, contract `interfaces: [Notifier]`, built around a pluggable-backend (strategy) pattern:\n\n- A `Backend` interface abstracts one delivery service (id, label, config schema, target validation, and delivery).\n- A package-level registry maps each backend's stable id to its implementation; every backend self-registers from its own `init()`.\n- The plugin holds **one active target** in its own persisted config (`StorageSchema`): which service is selected, plus that service's validated fields. `getDevices` synthesizes a single `sdk.NotifierDevice` from this config on every call — there is no device registry.\n- `sendNotification` dispatches the synthesized device to its backend's `Send`. A backend failure is logged and returned to the host.\n\n### Why config, not device registration\n\nEarlier versions of this plugin modeled targets as registrable `NotifierDevice`s, the way camera.ui's own mobile-push notifier does. That model turned out to be unreachable from the stock UI: `registerDevice` is only ever called by the camera.ui mobile app's push-registration flow, which is hardcoded to the official NVR's plugin name. The generic notification settings panel renders `notificationSettings()` read-only — it has no \"add a device\" affordance for third-party plugins. The one part of the stock UI that **does** render an editable, savable form for a third-party plugin is its own settings page, which renders whatever `StorageSchema` the plugin declares. So Notify now models its target as plugin config instead of a device: you configure it once, in the plugin's own settings, and `getDevices` synthesizes the device the host's `Notifier` interface expects from that config.\n\nAdding a new backend later is **one new file** — `src/backend/