CCM-13294 Update reporting component event references (#136)

- Fix typo in diagrams reference for reportgenerator
- Standardize event names for reporting components:
  - reportscheduler/generator: events-raised/consume updated to remove "daily"
  - reportsender: new component documentation added

Author: tdroza-nhs

docs/architecture/c4/notifhir/reporting/recorder/index.md

@@ -8,7 +8,7 @@ is_not_draft: false
 last_modified_date: 2025-10-24
 owner: Tom D'Roza
 author: Tom D'Roza
-diagrams: [c4code-tracker-listener, c4component-nhsapp-callback, sequence-nhsapp-callback]
+diagrams: [c4code-mesh-statusreporter-recorder, sequence-nhsapp-callback]
 events-raised: []
 events-consumed: [
     mesh-inbox-message-downloaded,

docs/architecture/c4/notifhir/reporting/reportgenerator/index.md

@@ -8,8 +8,8 @@ is_not_draft: false
 last_modified_date: 2025-10-28
 owner: Ross Buggins
 author: Tom D'Roza
-diagrams: [c c4code-mesh-statusreporter-generator]
-events-raised: [reporting-daily-report-generated]
-events-consumed: [reporting-daily-report-timer-expired]
+diagrams: [c4code-mesh-statusreporter-generator]
+events-raised: [reporting-report-generated]
+events-consumed: [reporting-generate-report]
 c4type: code
 ---

docs/architecture/c4/notifhir/reporting/reportscheduler/index.md

@@ -9,7 +9,7 @@ last_modified_date: 2025-10-28
 owner: Ross Buggins
 author: Tom D'Roza
 diagrams: [c4code-mesh-statusreporter-scheduler]
-events-raised: [reporting-daily-report-timer-expired]
+events-raised: [reporting-generate-report]
 events-consumed: []
 c4type: code
 ---

docs/architecture/c4/notifhir/reporting/reportsender/index.md

@@ -0,0 +1,15 @@
+---
+
+title: Report Sender
+parent: Reporting
+nav_order: 4
+has_children: true
+is_not_draft: false
+last_modified_date: 2025-11-26
+owner: Ross Buggins
+author: Tom D'Roza
+diagrams: [c4code-mesh-statusreporter-sender]
+events-raised: [reporting-report-sent]
+events-consumed: [reporting-report-generated]
+c4type: code
+---

docs/assets/aws-icons-mermaid.json

@@ -6,8 +6,8 @@ title: c4code-mesh-statusreporter-generator
 
 ## Decisions
 
-1. ReportScheulder lambda publishes a `GenerateReport` event for each trust that has new report data in the previous 24 hours.
-2. The event metadata contains the trust ID so the ReportGenerator lambda knows which trust to generate a report for.
+1. ReportSchedulder lambda publishes a `GenerateReport` event for every known client
+2. The event data payload contains the `senderId` so the ReportGenerator lambda knows which trust to generate a report for.
 
 ```mermaid
 architecture-beta
@@ -16,7 +16,7 @@ architecture-beta
     service sqs(logos:aws-sqs)[ReportGenerator Queue] in reportGenerator
     service reportGeneratorLambda(logos:aws-lambda)[Report Generator] in reportGenerator
     service s3(logos:aws-s3)[Reports] in reportGenerator
-    service reportsdb(aws:arch-amazon-dynamodb)[Reports] in reportGenerator
+    service reportsdb(aws:arch-amazon-athena)[Reports] in reportGenerator
     service reportGeneratedEvent(aws:res-amazon-eventbridge-event)[ReportGenerated Event]
 
     generateReportEvent:R --> L:sqs

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

@@ -3,7 +3,7 @@
 # To regenerate, run: make update-readme
 # To customize labels and purposes, edit: readme-metadata.yaml
 
-generated: '2025-11-26T12:32:47.898Z'
+generated: '2025-11-27T17:20:53.023Z'
 common: null
 domains:
   - name: digital-letters