Diagram tweaks

Author: tdroza-nhs

docs/collections/_diagrams/c4code-mesh-acknowledger.md

@@ -15,7 +15,7 @@ architecture-beta
     service meshAckLambda(logos:aws-lambda)[MeshAcknowledger] in meshAcknowledger
     service mesh(server)[MESH]
 
-    meshDownloaded:R -- L:meshAckQueue
+    meshDownloaded:R --> L:meshAckQueue
     meshAckQueue:R --> L:meshAckLambda
     meshAckLambda:B --> T:mesh
     meshAckLambda:R --> L:meshAcknowledged

docs/collections/_diagrams/c4code-mesh-poller.md

@@ -13,7 +13,7 @@ architecture-beta
     service clientConfig(aws:res-aws-systems-manager-parameter-store)[Client Configuration] in meshPoller
     service mesh(server)[MESH]
 
-    meshDownloaded:R -- L:meshPollLambda
+    meshDownloaded:R --> L:meshPollLambda
     clientConfig:B --> T:meshPollLambda
     meshPollLambda:B --> T:mesh
     meshPollLambda:R --> L:pdmSaved

docs/collections/_diagrams/c4code-mesh-retriever.md

@@ -17,7 +17,7 @@ architecture-beta
     service mesh(server)[MESH]
     service s3(logos:aws-s3)[DocumentReference] in meshRetriever
 
-    meshReceived:R -- L:meshDownloadQueue
+    meshReceived:R --> L:meshDownloadQueue
     meshDownloadQueue:R --> L:meshDownloadLambda
     meshDownloadLambda:T --> B:mesh
     meshDownloadLambda:B --> T:s3

docs/collections/_diagrams/c4code-mesh-statusreporter-scheduler.md

@@ -24,7 +24,7 @@ architecture-beta
     junction j2
     junction j3
 
-    scheduledEvent:R -- L:reportSchedulerLambda
+    scheduledEvent:R --> L:reportSchedulerLambda
     clientConfig:B --> T:reportSchedulerLambda
     reportSchedulerLambda:R -- L:j1
     j1:T -- B:j2

docs/collections/_diagrams/c4code-printer-removefromqueue.md

@@ -15,9 +15,9 @@ architecture-beta
    service manageTtlExpiry(logos:aws-lambda)[HandleTTLExpiry] in manageTTL
    service printTTLExpired(aws:res-amazon-eventbridge-event)[ItemDequeued Event]
 
-   pollEvent:R -- L:manageLambda
-   manageLambda:R -- L:manageDb
-   manageDb:R -- L:ttlStream
-   ttlStream:B -- T:manageTtlExpiry
-   manageTtlExpiry:R -- L:printTTLExpired
+   pollEvent:R --> L:manageLambda
+   manageLambda:R --> L:manageDb
+   manageDb:R --> L:ttlStream
+   ttlStream:B --> T:manageTtlExpiry
+   manageTtlExpiry:R --> L:printTTLExpired
 ```

docs/collections/_diagrams/c4code-printer-sendtoprint.md

@@ -17,7 +17,7 @@ architecture-beta
     junction j1
 
 
-    itemDequeued:R -- L:printQueue
+    itemDequeued:R --> L:printQueue
     printQueue:R --> L:printLambda
     printLambda:B <-- T:docRefBucket
     printLambda:T --> B:digLtrsBucket

docs/collections/_events/mesh-inbox-message-acknowledged.md

@@ -0,0 +1,10 @@
+---
+title: mesh-inbox-message-acknowledged
+type: uk.nhs.notify.digital.letters.mesh.inbox.message.acknowledged.v1
+nice_name: MESHInboxMessageAcknowledged
+service: MESH Services
+schema_envelope:  https://notify.nhs.uk/cloudevents/schemas/digital-letters/2025-10-draft/events/uk.nhs.notify.digital.letters.mesh.inbox.message.acknowledged.v1.schema.json
+schema_data: https://notify.nhs.uk/cloudevents/schemas/digital-letters/2025-10-draft/data/digital-letters-mesh-inbox-message-acknowledged-data.schema.json
+---
+
+This event is published when an acknowledgement has been successfully sent to the sender via MESH to indicate that a message request has been accepted.