feat: event type filtering, batch notifications, audit logging

AGENTS.md

@@ -0,0 +1,67 @@
+Description
+
+Expand automated tests around payload validation logic.
+
+Acceptance Criteria
+Invalid payloads are tested.
+Edge cases are covered.
+Coverage percentage increases.
+
+
+##Description##
+
+The notification contract currently emits events for every action, but off-chain consumers cannot selectively subscribe to specific notification categories. Introduce support for filtering events by notification type to reduce unnecessary processing.
+
+##Tasks##
+Add notification type metadata to emitted events.
+Update the event structure where necessary.
+Ensure backward compatibility for existing listeners.
+Add tests covering different notification categories.
+
+##Acceptance Criteria##
+Consumers can identify notification types directly from emitted events.
+Existing functionality remains unaffected.
+Unit tests validate the new event format.
+
+
+Description
+
+Organizations may need to send notifications to large recipient groups. Creating notifications individually increases gas costs and operational overhead.
+
+Introduce a batch notification creation mechanism to improve efficiency.
+
+Tasks
+Design batch creation function.
+Validate recipient arrays.
+Emit events for each created notification.
+Benchmark gas consumption.
+Add unit and integration tests.
+Document expected limitations.
+
+Acceptance Criteria
+Multiple notifications can be created in a single transaction.
+Invalid recipients are handled appropriately.
+Gas costs are lower than individual transactions.
+Tests cover large batch scenarios.
+
+
+Description
+
+Organizations require visibility into delivery attempts and outcomes for compliance and operational monitoring.
+
+Create an audit logging system that records notification lifecycle events.
+
+Tasks
+Define audit event schema.
+Log notification creation events.
+Log delivery attempts.
+Log delivery failures.
+Log notification acknowledgments.
+Create query endpoints.
+
+Acceptance Criteria
+All lifecycle events are recorded.
+Audit records are searchable.
+Logs remain immutable after creation.
+
+