pulse-triage[bot] f235fc37f2 fix(notifications): start queue processing after destination config ...

A persisted notification that was already due at startup could be terminally cancelled as 'delivery disabled'. NewNotificationManagerWithDataDir woke the queue worker during construction, before the owner had applied saved webhook/email/Apprise configuration, so the still-empty destination list looked like a removed destination.

Install the queue processor without waking it. The worker ticker and later enqueues start delivery once configuration is present. This removes the order/state-dependent failure in TestResolvedGroupingOrdinaryRestart and drops a persisted grouped recovery in production.

Also wait past the queue poll interval in the grouping contract test, add a regression test for the startup ordering, and update the notifications subsystem contract's processor-attachment semantics.

Change-source: pulse-maintainer

2026-09-23 00:01:56 +01:00

..

internal

docs(agents): add customer support communication guidance

2026-08-11 16:39:36 +01:00

v6

fix(notifications): start queue processing after destination config

2026-09-23 00:01:56 +01:00

control_plane.json

fix(release): map 6.4.5 reliability checkpoints to release line

2026-09-11 00:23:11 +01:00

control_plane.schema.json

Map legacy stable releases in control plane

2026-04-11 13:23:07 +01:00