feat: include data connections and SMTP in artifact deployment

Component-NotificationService.md

@@ -6,7 +6,7 @@ The Notification Service provides email notification capabilities to scripts run
 
 ## Location
 
-Central cluster (definition management). Site clusters (email delivery).
+Central cluster (definition management, stores in config DB). Site clusters (email delivery, reads definitions from local SQLite).
 
 ## Responsibilities
 
@@ -17,8 +17,8 @@ Central cluster (definition management). Site clusters (email delivery).
 - Managed by users with the Design role.
 
 ### Delivery (Site)
-- Resolve notification list names to recipient lists.
-- Compose and send emails via SMTP.
+- Resolve notification list names to recipient lists from **local SQLite** (populated by artifact deployment). Sites do not access the central config DB.
+- Compose and send emails via SMTP using locally stored SMTP configuration.
 - On delivery failure, submit the notification to the Store-and-Forward Engine for buffered retry.
 
 ## Notification List Definition
@@ -72,7 +72,8 @@ Consistent with the External System Gateway pattern:
 
 ## Dependencies
 
-- **Configuration Database (MS SQL)**: Stores notification list definitions and SMTP config.
+- **Configuration Database (MS SQL)**: Stores notification list definitions and SMTP config (central only).
+- **Local SQLite**: At sites, notification lists, recipients, and SMTP configuration are read from local SQLite (populated by artifact deployment). Sites do not access the central config DB.
 - **Store-and-Forward Engine**: Handles buffering for failed email deliveries.
 - **Security & Auth**: Design role manages notification lists.
 - **Configuration Database (via IAuditService)**: Notification list changes are audit logged.