Maurice 712a33626a refactor(server): give the notification vocabulary its own module ...

The event names, the channel ids and the ExternalChannel contract move to
nest/notifications/notification-events.ts, which imports nothing.

The cluster only looked acyclic: notifications.ts and channelRegistry.ts both
reached back into notificationPreferencesService for NotifEventType, and both
edges were `import type`, so they compiled away. Putting any of those names in a
value position - an enum, a const array, an injected class - would have made the
cycle real, with builtins.ts as a third ring. Nothing can fold while that is
true.

The drift guard against the shared NotificationEventKey moves with the union it
guards; it sat three files away from it.

2026-08-08 12:09:56 +02:00

..

discovery.ts

v3.4.0 (#1540)

2026-07-18 22:13:52 +02:00

host-compat.ts

refactor(server): remaining nest domains read env via app-config

2026-07-25 15:29:13 +02:00

manifest.ts

refactor(server): give the notification vocabulary its own module

2026-08-08 12:09:56 +02:00

native-scan.ts

3.2.0 (#1426)

2026-07-05 01:13:04 +02:00

safe-extract.ts

3.2.0 (#1426)

2026-07-05 01:13:04 +02:00

safe-fetch.ts

3.2.0 (#1426)

2026-07-05 01:13:04 +02:00

verify-signature.ts

3.2.0 (#1426)

2026-07-05 01:13:04 +02:00