Files
pulse/docs/release-control
rcourtman fa1cf95dcf feat(relay): make Relay discoverable where users configure alerts and say what it does
Production telemetry shows 17 weekly-active installs with Relay enabled out
of 6,225 — the weakest adoption of any feature flag. A funnel walk from a
fresh session showed why: the only Relay surface was the last item of the
last Settings section, hidden entirely from unlicensed installs, described
in transport jargon, and never mentioned on the alert Notifications page
where "get alerts on my phone" actually lives.

- Alerts → Notifications: new "Mobile push notifications" destinations
  section (AlertPushDestinationsSection) presenting push via Pulse Mobile
  alongside email/Apprise/webhooks. Licensed installs get a pointer to the
  canonical /settings/system-relay panel; unlicensed installs get the shared
  FeatureGateSection with the relay upgrade destination, suppressed when
  upgrade prompts are hidden. Page description now names mobile push.
- Settings nav: system-relay no longer sets hideWhenUnavailable — the
  Remote Access entry stays visible to free installs and the panel-owned
  upgrade gate communicates the paid boundary. relayRead capability hiding
  is unchanged.
- Remote Access copy rewritten around user value: push notifications and
  remote monitoring through Pulse Mobile with no port forwarding or VPN;
  pairing help drops "provisions a dedicated relay access credential"
  jargon, names iOS + Android early access, and states that download-page
  install links appear after activation-key entry. EN/ES/DE headers updated.
- Contracts updated in-commit: alerts.md (destinations catalog extension
  point), frontend-primitives.md (system-relay is not a deep-link-only
  flow), cloud-paid.md (value-first relay presentation obligation).

Contract-Neutral: i18n messages edit changes settings-header/alerts-destinations copy only; no security-privacy delta; alerts/cloud-paid/frontend-primitives contracts updated in-commit
2026-07-17 23:38:36 +01:00
..