v0.4.0

Added

• notify_switchboard.explain, a new read-only action. For a target — and
  optionally an importance and a person — it answers, per person, whether a
  message would be routed, set aside or dropped and why: which silence is on,
  when the snooze lifts, which presence rule decided, and which services it
  would reach. Nothing is sent and no counter moves.
• A fresh install works after one form. Adding the first person also creates a
  default target pointing at them, so notify.switchboard reaches a real
  phone straight away. That target picks up each new person automatically until
  you edit it, after which it is yours.
• Phones are picked from a list instead of typed. The person editor offers the
  instance's notify services, marks the ones registered to that person's own
  Home Assistant user and pre-selects them. A service that does not exist yet
  can still be typed in.
• iOS Focus sensors are proposed as silence entities for a new person. Android's
  Do Not Disturb is not; docs/quickstart.md carries the one-line template
  sensor that bridges it.
• Send somebody a test message and Send a test message through a target
  in the options menu. Each sends one real message through the ordinary path —
  counted, deferred or dropped like any other — and then shows the explanation
  for it.
• The alert: block to paste is generated for you on a confirmation step after
  saving a target, keyed on that target's own alert. Nothing is written until
  you submit that step.
• Two new warnings when the configuration cannot work: a person in an audience
  with no notify service at all, and a target tied to an alert.* that does not
  exist.

Changed

• The person editor is two steps: pick the person, then choose their devices,
  silences and wake time. Change somebody's devices opens the second step on
  what is stored, so the list of discovered phones never silently re-adds an
  output you removed.