feat: add events

specification.json

@@ -682,7 +682,7 @@
         {
             "id": "Requirement 5.2.4",
             "machine_id": "requirement_5_2_4",
-            "content": "The `event handler` function MUST accept a `event details` or `error event metadata` parameter.",
+            "content": "The `event handler` function MUST accept a `event details` parameter.",
             "RFC 2119 keyword": "MUST",
             "children": []
         },

specification/sections/05-events.md

@@ -71,9 +71,9 @@ This is particularly relevant for `event handler functions` which are attached t
 
 #### Requirement 5.2.4
 
-> The `event handler` function **MUST** accept a `event details` or `error event metadata` parameter.
+> The `event handler` function **MUST** accept a `event details` parameter.
 
-see: [`event details`](../types.md#event-details), [`error event metadata`](../types.md#error-event-details)
+see: [`event details`](../types.md#event-details)
 
 #### Requirement 5.2.5
 

specification/types.md

@@ -109,29 +109,16 @@ An enumeration of possible provider states.
 A structure defining a provider event payload, including:
 
 - flags changed (string[], optional)
+- message (string, optional)
 - event metadata ([event metadata](#event-metadata))
 
-### Provider Error Event Details
-
-A structure defining a provider error event payload, including:
-
-- error message (string, required)
-- event metadata ([flag metadata](#event-metadata))
-
 ### Event Details
 
 A structure defining an event payload, including:
 
 - client name (string, required)
 - flags changed (string[], optional)
-- event metadata ([event metadata](#event-metadata))
-
-### Error Event Details
-
-A structure defining an error event payload, including:
-
-- client name (string, required)
-- error message (string, required)
+- message (string, optional)
 - event metadata ([event metadata](#event-metadata))
 
 ### Event Metadata