v0.6.0

Added

• docs/migration-guide.md: where to start when you already have a pile of
  inline notify.mobile_app_* calls and alert: blocks — one target per alert,
  observer mode so nothing in your YAML has to change, and a rollback that is
  one menu action. README.md gains a Glossary defining target, person, output,
  audience, presence rule, silence, snooze, wake time, deferral, summary,
  episode and observer mode.
• Two options-menu entries, Advanced settings of a target and Set up
  somebody's night, and a checkbox on the step that shows the alert:
  snippet.
• A five-line recipe for turning a speaker into an output, using core's own
  platform: tts notify platform, in README.md and docs/quickstart.md.

Changed

• Adding a target asks five questions — Short identifier, Name, Alert
  watched, Who to tell, Watch the alert directly. The other nine moved
  to an Advanced settings step with the same choices and the same defaults.
  A target created from the basic step alone routes exactly as it would have
  before.
• The person editor is split the same way: devices and silences on the first
  step, Wake time and Sum it all up in one message on a second one. Each
  half writes only its own fields, so changing a phone can never erase somebody's
  night.
• A routing-table row is called a target everywhere — interface, errors,
  warnings and documentation, in all three languages. "Rule" survives only in
  presence rule.
• A silenced person with no wake time is now held until their silence ends,
  when that silence publishes its own end (a core schedule). A silence that
  publishes no end — an input_boolean, a Focus sensor, a temporary
  notify_switchboard.silence — still drops the message exactly as before.
• The expiry defaults (not very important 120 min, normal 720 min, important
  never) are documented defaults, not frozen values: a future version may pick
  other numbers. Set your own on How long a message set aside stays useful.

Fixed

• notify_switchboard.silence and notify_switchboard.unsilence now release or
  re-arm the queue they affect. Lifting a silence by hand used to leave a held
  message waiting for the following night.
• A message held with no wake time no longer loses its timer when a temporary
  silence outlives the night — it used to wait for the next night, which for a
  message with an expiry usually meant it never arrived.
• Renaming or deleting a silence entity now counts as that silence lifting,
  instead of leaving the queue waiting for an "off" that never comes.
• The alert: block shown after saving a target in observer mode no longer
  carries a notifiers: list. Pasting it as instructed wired the alert both
  ways at once and produced duplicate notifications.

Removed

• The Class field of a target, which nothing ever read. A value already
  stored is ignored — not migrated, not deleted — and there is nothing to do by
  hand.