@modainteract/moda-interact-shared 2.5.0 → 2.6.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -31,6 +31,8 @@ necessarily a supported package subpath. Type-only exports require `import type`
31
31
  | `/billing` | Billing plan/usage contracts, provider-status normalization, subscription-reconciliation jobs, purchased-credit counters and deterministic billing identifiers. |
32
32
  | `/recovery-policy` | Recovery offer modes and validation of an already-resolved effective recovery policy. Does not retrieve or decide merchant entitlements. |
33
33
  | `/whatsapp` | Normalized inbound WhatsApp content/message schemas and parsers. Provider delivery statuses are in `/billing`. |
34
+ | `/whatsapp-template-events` | ARCH-047 v2 Meta template-status observations: strict nine-field schema and pure occurrence UUID v4 event/job ID formatters. |
35
+ | `/whatsapp-template-events/fixtures` | Portable JSON golden vectors for v2 status observations and expected BullMQ job IDs. |
34
36
  | `/merchant-communications` | Merchant communication and translation job contracts, constants and validation. |
35
37
  | `/merchant-communications/node` | Node-only deterministic translation queue-job identifiers. |
36
38
  | `/shopify` | Shopify commerce/recovery event schemas, parsers, event versions and shared queue contracts. |
@@ -1659,6 +1661,40 @@ Type-only exports:
1659
1661
 
1660
1662
  </details>
1661
1663
 
1664
+ <details>
1665
+ <summary>/whatsapp-template-events — 6 runtime exports, 1 type</summary>
1666
+
1667
+ Import: `@modainteract/moda-interact-shared/whatsapp-template-events`.
1668
+
1669
+ From [src/whatsapp-template-events.ts](src/whatsapp-template-events.ts):
1670
+
1671
+ Runtime exports:
1672
+
1673
+ - `META_TEMPLATE_STATUS_QUEUE`
1674
+ - `META_TEMPLATE_STATUS_JOB`
1675
+ - `META_TEMPLATE_STATUS_SCHEMA_VERSION`
1676
+ - `MetaTemplateStatusObservationV2Schema`
1677
+ - `formatMetaTemplateStatusEventIdentity`
1678
+ - `formatMetaTemplateStatusJobId`
1679
+
1680
+ Type-only export:
1681
+
1682
+ - `MetaTemplateStatusObservationV2`
1683
+
1684
+ Messaging must verify the complete webhook batch **before** generating a fresh
1685
+ cryptographically random UUID v4 for every matching observation. Shared formats
1686
+ that UUID without generating randomness. Both ingress and Background must parse
1687
+ events with `MetaTemplateStatusObservationV2Schema`; it checks the exact nine own
1688
+ fields and the 4096-byte UTF-8 JSON limit. Neither event UUID nor `receivedAt`
1689
+ orders provider statuses, which remain Background-owned policy. Repeated Meta
1690
+ status values can correspond to separate event occurrences.
1691
+
1692
+ Compatibility vectors: [fixtures/meta-template-status-v2.json](fixtures/meta-template-status-v2.json),
1693
+ published at `/whatsapp-template-events/fixtures`. The fixture is test data,
1694
+ not a provider webhook payload.
1695
+
1696
+ </details>
1697
+
1662
1698
  <details>
1663
1699
  <summary>/merchant-communications — 40 exports</summary>
1664
1700