v0.7.0

piggery now tells you, by itself, when a team's mail flow needs you, and piggery check tests your
files before a restart.

After upgrading, run piggery setup --outdated: the pi and omp integrations are now 3 and dsh 4
(Paseo, Claude and Codex are unchanged). Then restart the pi, omp and dsh sessions that were open.

Breaking: only piggery writes to notify now. An agent's send to notify is refused, and a
to: notify routing line or a notify: notify timer in a template is ignored with a warning
(piggery check lists them). Notify hooks run from ~/.piggery/hooks/notify.d/; a single
~/.piggery/hooks/notify is no longer run, so move it into that directory.

• Notices, decided by the engine at the end of a gate's turn, from the team's mail alone: reply
  (a turn on team mail ended and the gate sent nothing), settled (the gate sent its last message
  and nobody works or has mail waiting), failed (a turn on team mail failed, so that mail waits)
  and gate_lost. Your chat with the gate, a gate that is still dispatching work, a headless gate
  and a member that is not the gate never notify. The hook's JSON line adds gate and dir,
  and kind is the notice's kind. The respawn-limit notice goes to the worker's lead only.
• piggery setup notify add desktop|herdr|ntfy:<topic> writes a ready hook into notify.d/
  (remove takes it out; alone, it lists the hooks and what each needs). Every file there runs in
  parallel, each with its own 10-second limit.
• piggery check: reads config.yaml, the harness profiles, every template and your prompts with
  the daemon's own loaders and prints what they would refuse or ignore; it changes nothing.
• The daemon checks once a day for a newer release; top, setup and update --check say vX available: piggery update. Nothing is installed on its own; update.check: false turns it off.
• top shows the latest notices at the bottom left, beside the events; n opens or closes them,
  like e for the events. ps --view carries them as notices, and the update notice as
  daemon.update.
• The template list an agent reads now also shows a template that team up would refuse.
• Fix: a build stamped dev-<sha> is treated as a build from source: piggery update no longer
  replaces it with an older release unless --force.