feat: fetch events-config from config registry in AnalyticsController

README.md

@@ -271,6 +271,7 @@ linkStyle default opacity:0.5
   ai_controllers --> base_controller;
   ai_controllers --> messenger;
   analytics_controller --> base_controller;
+  analytics_controller --> config_registry_controller;
   analytics_controller --> geolocation_controller;
   analytics_controller --> messenger;
   analytics_controller --> utils;

oxlint-suppressions.json

@@ -2452,16 +2452,6 @@
       "count": 1
     }
   },
-  "packages/config-registry-controller/src/config-registry-api-service/config-registry-api-service.test.ts": {
-    "typescript/no-unsafe-assignment": {
-      "count": 6
-    }
-  },
-  "packages/config-registry-controller/src/config-registry-api-service/config-registry-api-service.ts": {
-    "typescript/no-unsafe-assignment": {
-      "count": 1
-    }
-  },
   "packages/connectivity-controller/jest.config.cjs": {
     "import/unambiguous": {
       "count": 1

packages/analytics-controller/CHANGELOG.md

@@ -9,6 +9,9 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ### Changed
 
+- **BREAKING:** `AnalyticsControllerMessenger` requires `ConfigRegistryController:getState` in its allowed actions and `ConfigRegistryController:stateChanged` in its allowed events ([#10448](https://github.com/MetaMask/core/pull/10448))
+- Update `AnalyticsController.init` to listen for ConfigRegistryController state changes and update in-memory event-purpose classification when the version differs ([#10448](https://github.com/MetaMask/core/pull/10448))
+- Add `@metamask/config-registry-controller` `^4.0.0` as a dependency ([#10448](https://github.com/MetaMask/core/pull/10448))
 - Bump `lodash-es` from `^4.17.21` to `^4.18.1` ([#10447](https://github.com/MetaMask/core/pull/10447))
 
 ## [3.2.0]

packages/analytics-controller/README.md

@@ -34,7 +34,7 @@ The AnalyticsController provides a unified interface for tracking analytics even
 3. **Subscribe to state changes**: Persist changes to isolated storage
 4. **Persist to isolated storage**: Keep analytics settings separate from main state (protects against state corruption)
 
-`eventsConfig.events` maps event names to one or both `AnalyticsPurpose` values (`product` and `marketing`). Unlisted names default to product-only. Phase 1 uses the config already persisted in state. Loading it from config registry will be added later.
+`eventsConfig.events` maps event names to one or both `AnalyticsPurpose` values (`product` and `marketing`). Unlisted names default to product-only. The config is loaded from `ConfigRegistryController` state during `init` and refreshed automatically when `ConfigRegistryController` state changes.
 
 Each `track` and `view` payload is emitted once when at least one eligible purpose is opted in. A dual-purpose event is still emitted once when both consents are enabled. Its allowed purposes are stamped using Segment's consent context:
 

packages/analytics-controller/package.json

@@ -51,6 +51,7 @@
   },
   "dependencies": {
     "@metamask/base-controller": "^10.0.0",
+    "@metamask/config-registry-controller": "^4.0.0",
     "@metamask/geolocation-controller": "^2.0.0",
     "@metamask/messenger": "^3.0.0",
     "@metamask/utils": "^12.0.0",