os-adr: ADR-0024 addendum — apprise-api gem + CLI done, apprise-client retired

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BuTaxjCa543Sf77Ti7zYkh
This commit is contained in:
jared 2026-07-13 16:13:43 -04:00
parent bd7615d962
commit 58f330fdf3
1 changed files with 2 additions and 0 deletions

View File

@ -25,6 +25,8 @@ The `planka-api` gem's tick/digest delivery was specified as Pushover-direct (`P
Apprise replaces the originally planned Pushover-direct integration as the single notification transport, deployed as an Apprise API server so any service (Discord, Telegram, Bark, Home Assistant, etc.) can be targeted via configuration rather than new code, with Planka's native Apprise support converging on the same server. This iteration's scope stays minimal (server + a minimal Apprise client swapped in for the planned Pushover gem code), with a fuller client gem, CLI wrapper, and an os-notify plugin captured as later backlog work; the underlying notification-blindness policy is unchanged. Apprise replaces the originally planned Pushover-direct integration as the single notification transport, deployed as an Apprise API server so any service (Discord, Telegram, Bark, Home Assistant, etc.) can be targeted via configuration rather than new code, with Planka's native Apprise support converging on the same server. This iteration's scope stays minimal (server + a minimal Apprise client swapped in for the planned Pushover gem code), with a fuller client gem, CLI wrapper, and an os-notify plugin captured as later backlog work; the underlying notification-blindness policy is unchanged.
_Addendum 2026-07-13:_ the fuller client gem and CLI wrapper backlog items are done — `~/dev/ruby-gems/apprise-api` (gem `apprise-api`, module `Apprise`, v0.2.0) is the sole Apprise client, now including the `apprise-notify` CLI executable. The interim minimal client (`~/dev/ruby-gems/apprise`, gem `apprise-client`) was retired and deleted after live verification and a no-dependents check. Remaining backlog: the `os-notify` plugin and multi-service routing/Planka-native wiring.
## Alternatives rejected ## Alternatives rejected
**Pushover gem as planned** — single-service dead end; every future service would be a new integration. **Deferring Apprise entirely** — the server + minimal client is comparable effort to the Pushover path, so there is no cheaper interim. **Pushover gem as planned** — single-service dead end; every future service would be a new integration. **Deferring Apprise entirely** — the server + minimal client is comparable effort to the Pushover path, so there is no cheaper interim.