the notify hook is wired and silent: this home has no config/notify channel

[atqamz]

#80 landed the notification hook at d1359010. It fires on blocked, failed,
needs-decision and done, reads /home/atqa/secondhand/config/notify, and that file does not exist -
this home has only harness, model and stale-threshold.

With it absent the hook stays quiet by design. So the mechanism is wired and reaches nobody, which is the exact
scenario #80 was filed for: work continuing while nobody is watching, and nobody being told.

What is needed

A channel. ntfy topic or otherwise - one line is enough and I will wire it.

I am not choosing it myself. The template decides where a message physically goes, that is outward-facing, and
which of Atqa's four profiles it should reach is not derivable from the code.

What is already verified, so this is only the channel

The review raised an exit-1-on-unconfigured contract, and I checked whether an unconfigured home costs the
watcher itself. It does not:

• NotifyFilter() reads no config field, and cfg.EventFilter gates only the stdout write, with notifyEvent
  running unconditionally after it. So hand watch --event done cannot silence a failed, blocked or
  needs-decision notification, and there is a test pinning that.
• Both functions are void with no return path into the poll loop, so a failing notify cannot stop the watcher
  ticking or printing.
• ErrNotConfigured is the one branch that prints nothing, so an unconfigured home does not spew a warning per
  event per poll.

Why this is an issue rather than a note in a file

It was carried in data/inbox.md, which #64 deleted on the grounds that every section of it
had a real home already. "Open threads" map to issues, so this is that.

Related: #80
Related: #64

[atqamz]

Checked this host for a local channel that would let the hook reach somebody without an outward-facing decision. There is not one, so the refusal to choose recorded above stands and I am not working around it.

• notify-send, ntfy and dunstify are all absent, and dunst is not running. A desktop channel would mean installing a notifier, which is not something to do globally for this.
• curl is present, so an ntfy or Telegram template works the moment there is a topic - that is the one-liner this issue is asking for.
• The remaining local option is a shell template that appends to a file in the fleet home. That is worse than leaving the hook silent: a file the fleet writes and nobody reads is exactly what delete data/inbox.md; each of its sections has a real home already #64 deleted data/inbox.md for, and recreating it under another name repeats a mistake this home already paid for.

So the mechanism cannot be usefully unblocked from inside the repo. It needs a channel that leaves this host, which is the outward-facing call, plus which of the four profiles it belongs to.

Everything else is verified and unchanged: the hook fires on blocked, failed, needs-decision and done, an unconfigured home costs the watcher nothing, and ErrNotConfigured prints nothing rather than warning per event per poll. One line in /home/atqa/secondhand/config/notify closes this.

[atqamz]

Deferred to 0.3.0, same treatment as #36: 0.2.0 ships with the hook wired and unconfigured, which is its current documented behavior and costs the watcher nothing.

The choice when this is picked up is a channel that leaves this host - an ntfy topic is the cheapest, one curl line with no token and nothing secret in the config file, at the cost of anyone knowing the topic name being able to read it. A Telegram bot is the private alternative and needs a token kept out of the file. Either way it is one channel for everything the fleet says rather than one per profile, so the profile question does not need answering first.

Nothing in the code is waiting on this. ErrNotConfigured is the quiet branch by design and there is a test pinning that an unconfigured home neither warns per poll nor stops the watcher ticking.