feat(braze): sync V6 recommended eCommerce events

[rmi22186]

Summary

• port the canonical Braze master-v6 opt-in recommended eCommerce forwarding from 1b8a4ca3, superseding the stale draft in feat: sync Braze 6 kit from upstream #1310
• update the bundled Braze dependency floor to ^6.9.0 and add the upstream browser coverage
• preserve V3 monorepo package identity, core SDK dependency, repository docs, and package-manifest runtime version injection from fix(braze): derive runtime versions from package manifests #1399
• exclude generated dist/** files and changes to every other kit

Comparison notes

• src/BrazeKit-dev.js matches feat: sync Braze 6 kit from upstream #1310/canonical master-v6 except that runtime version is injected from this package manifest
• test/tests.js matches feat: sync Braze 6 kit from upstream #1310/canonical behavior plus the manifest-version assertion from fix(braze): derive runtime versions from package manifests #1399
• the current monorepo README is newer than upstream and already documents the recommended-event setting; legacy upstream changelog numbering is intentionally not copied into the V3 lockstep release track

Test plan

• cd kits/braze/braze-6 && npm run build && npm test (Chrome Headless + Firefox Headless, 206 successful assertions)
• Prettier 1.18.2 check on changed source, test, config, and manifest files
• npm run lint
• Confirm generated CJS/IIFE/ESM bundles replace the runtime version token during build

[cursor]

PR Summary

Medium Risk
Opt-in commerce forwarding changes event shape and Braze APIs for customers who enable it; incorrect mapping or session/cart ID logic could affect analytics correlation, though legacy paths remain the default.

Overview
Adds an opt-in useEcommerceRecommendedEvents path on the Braze v6 web kit so supported mParticle commerce actions map to Braze’s recommended schema (ecommerce.cart_updated, checkout_started, product_viewed, order_placed) via braze.logEcommerceEvent, with refunds sent as ecommerce.order_refunded custom events. Connection settings can remap cart/checkout/subtotal and product URL attributes (including HTML-escaped config JSON); cart/checkout IDs prefer event attributes, then SessionId / sessionManager, so carts can correlate across the funnel.

When the toggle is off, the host SDK lacks logEcommerceEvent, or the action isn’t supported, behavior unchanged—legacy purchase/custom commerce forwarding still runs. @braze/web-sdk is raised to ^6.9.0; kit version comes from package.json at build time via @rollup/plugin-replace. Tests cover mapping, fallbacks, and version exposure.

^{Reviewed by Cursor Bugbot for commit 875cc6c. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 9dc3dc9. Configure here.}

[sonarqubecloud]

Quality Gate failed

Failed conditions
C Security Rating on New Code (required ≥ A)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE