CCM-15256: invalid attachment received diagram (#280)

* Add InvalidAttachmentReceived to PrintAnalyser diagram
* Added schema for InvalidAttachmentReceived event

Author: tdroza-nhs

.tool-versions

@@ -4,6 +4,7 @@ jq 1.6
 nodejs 24.10.0
 pre-commit 3.6.0
 python 3.14.0
+ruby 3.2.0
 terraform 1.10.1
 terraform-docs 0.19.0
 vale 3.6.0

README.md

@@ -11,12 +11,17 @@ architecture-beta
     service analyseLambda(logos:aws-lambda)[PrintAnalyser] in printAnalyser
     service safeBucket(logos:aws-s3)[SafeFiles] in printAnalyser
     service pdfAnalysed(aws:res-amazon-eventbridge-event)[PDFAnalysed Event]
+    service invalidAttachment(aws:res-amazon-eventbridge-event)[InvalidAttachmentReceived Event]
     group printAnalyser(cloud)[PrintAnalyser]
 
+    junction j1
+
     fileSafe:R --> L:analyseQueue
     analyseQueue:R --> L:analyseLambda
     safeBucket:B --> T:analyseLambda
-    analyseLambda:R --> L:pdfAnalysed
+    analyseLambda:R -- L:j1
+    j1:T --> B:pdfAnalysed
+    j1:B --> T:invalidAttachment
 
 
 ```

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

@@ -0,0 +1,10 @@
+---
+title: invalid-attachment-received
+type: uk.nhs.notify.digital.letters.print.invalid.attachment.received.v1
+nice_name: InvalidAttachmentReceived
+service: Print Supplier Services
+schema_envelope:  https://notify.nhs.uk/cloudevents/schemas/digital-letters/2025-10-draft/events/uk.nhs.notify.digital.letters.print.invalid.attachment.received.v1.schema.json
+schema_data: https://notify.nhs.uk/cloudevents/schemas/digital-letters/2025-10-draft/data/digital-letters-print-invalid-attachment-received-data.schema.json
+---
+
+This event is published when a digital letter attachment is not in the expected (PDF) format. It indicates that the attachment cannot be processed for printing and requires attention to resolve the issue.

…/collections/_events/file-quarantined.md …ctions/_events/print-file-quarantined.mddocs/collections/_events/file-quarantined.md renamed to docs/collections/_events/print-file-quarantined.md docs/collections/_events/file-quarantined.md renamed to docs/collections/_events/print-file-quarantined.md

@@ -0,0 +1,16 @@
+$schema: https://json-schema.org/draft/2020-12/schema
+title: InvalidAttachmentReceived Data
+description: Data payload of the InvalidAttachmentReceived event
+type: object
+additionalProperties: false
+properties:
+  messageReference:
+    $ref: ../defs/requests.schema.yaml#/properties/messageReference
+  senderId:
+    $ref: ../defs/requests.schema.yaml#/properties/senderId
+  failureCode:
+    $ref: ../defs/requests.schema.yaml#/properties/failureCode
+required:
+  - messageReference
+  - senderId
+  - failureCode

docs/collections/_events/file-safe.md …s/collections/_events/print-file-safe.mddocs/collections/_events/file-safe.md renamed to docs/collections/_events/print-file-safe.md docs/collections/_events/file-safe.md renamed to docs/collections/_events/print-file-safe.md

@@ -62,7 +62,7 @@ properties:
     type: string
     description: A codified reason for the status of the message
     examples:
-      - "FAILURE001"
+      - "DL_CLIV_002"
   reasonText:
     type: string
     description: Human-readable explanation for the reasonCode

docs/collections/_events/print-invalid-attachment-received.md

@@ -36,4 +36,4 @@ properties:
     type: string
     description: The failure code indicating the reason for the message being invalid
     examples:
-      - "LOCALID_HEADER_MISSING"
+      - "DL_CLIV_001"

src/cloudevents/domains/digital-letters/2025-10-draft/data/digital-letters-print-invalid-attachment-received-data.schema.yaml

@@ -0,0 +1,22 @@
+$schema: https://json-schema.org/draft/2020-12/schema
+title: InvalidAttachmentReceived
+type: object
+allOf:
+  - $ref: ../digital-letters-print-profile.schema.yaml
+properties:
+  type:
+    type: string
+    const: uk.nhs.notify.digital.letters.print.invalid.attachment.received.v1
+    description: Concrete versioned event type string for this event (.vN suffix).
+  source:
+    type: string
+    pattern: ^/nhs/england/notify/(production|staging|development|uat)/(primary|secondary|dev-[0-9]+)/data-plane/digitalletters/print
+    description: Event source for digital letters.
+  dataschema:
+    type: string
+    const: ../data/digital-letters-print-invalid-attachment-received-data.schema.yaml
+    description: Canonical URI of the event's data schema.
+    examples:
+      - digital-letters-print-invalid-attachment-received-data.schema.yaml
+  data:
+    $ref: ../data/digital-letters-print-invalid-attachment-received-data.schema.yaml