Zone.js not loaded runtime error after Clarity v4 upgrade

Error context

Upgrading a project from Clarity v3 to v4 on Angular 15 triggers a runtime error: Zone.js not loaded. The failure occurs during application bootstrap when a custom zone.js build is used.

Goal

Determine the exact zone.js configuration changes required for Clarity v4 so that the application starts without the Zone.js not loaded error.

Constraints and uncertainty

• Clarity v4 drops IE11 polyfills and expects a standard zone.js setup.
• The project uses a custom zone.js bundle (e.g., zone.js/dist/zone-evergreen) rather than the default Angular CLI configuration.
• Documentation mentions “zone.js configuration changes required” but does not enumerate the specific imports or polyfill flags needed for a custom build.

Open questions

1. Which zone.js entry point and polyfill flags must be included for Clarity v4 compatibility?
2. Are there any required Angular CLI builder options (e.g., zone.js in polyfills) that differ from the v3 setup?
3. Does Clarity v4 rely on any zone.js features (such as ZoneAwarePromise) that must be explicitly enabled?