audit(2026-11-10): re-verify 2 stale pages (push bridge live/embedded, freshrss midday 0-failed in 22d); freshness 0 stale; log addendum
This commit is contained in:
@@ -3,9 +3,9 @@ title: Push Notifications (Cadu / Vory bridge)
|
||||
type: system
|
||||
status: degraded
|
||||
created: 2026-10-19
|
||||
updated: 2026-10-19
|
||||
verified_on: 2026-10-19
|
||||
review_after: 2026-10-26
|
||||
updated: 2026-11-10
|
||||
verified_on: 2026-11-10
|
||||
review_after: 2026-11-24
|
||||
confidence: medium
|
||||
tags: [push, notifications, plugins, gateway, integrations]
|
||||
sources: [live-probe, live-config, live-push-dir, live-logs]
|
||||
@@ -13,6 +13,15 @@ sources: [live-probe, live-config, live-push-dir, live-logs]
|
||||
|
||||
# Push Notifications (Cadu / Vory bridge)
|
||||
|
||||
> **Re-verified 2026-11-10 (nightly audit).** Bridge file present and unchanged: `hermes_push.py`
|
||||
> 91,765 B, sha256 prefix `59cabfcc…`. Plugins `hermes-push`, `vory-push`, `cadu-device`, `cadu-mail`,
|
||||
> `cadu-rich-cards`, `cadu-secrets-vault` all present under `~/.hermes/plugins/`. `:9119` listening
|
||||
> (dashboard, pid 3628580) and tailnet `:8443` listening. `vory-push` started **2026-11-10 01:00:34**.
|
||||
> ⚠ **Pitfall for future audits:** the relay runs **embedded in another Hermes process** — its log reads
|
||||
> *"vory-push relay running in another Hermes process; waiting for it to stop"* — so a `pgrep` on
|
||||
> `hermes_push`/`vory` script names returns **nothing while the relay is healthy**. Do not read that
|
||||
> empty `pgrep` as "bridge down". Status left `degraded` (unchanged; no fix verified this window).
|
||||
|
||||
## Purpose
|
||||
|
||||
Delivers Hermes activity to Anthony's phone (APNs push) and carries remote
|
||||
|
||||
Reference in New Issue
Block a user