[ejsmith]

Summary

• Include the current intercom_user_jwt with every identified Intercom SPA update.
• Cover both route-impression updates and later identity/company-data updates with regression tests.

Why

Messenger Security rejects identified user updates that omit both user_hash and intercom_user_jwt. The initial boot contained the JWT, but our update helper only resent the JWT when its value changed. Route updates therefore always sent user_id without authentication, producing 403 Forbidden responses while users navigated the Svelte SPA.

Intercom documents intercom_user_jwt as the field used to identify and update secured Messenger users: https://www.intercom.com/help/en/articles/10589769-authenticating-users-in-the-messenger-with-json-web-tokens-jwts

Impact

Secured Intercom updates remain authenticated while navigating or refreshing user/company data. No API contract or legacy Angular behavior changes.

Verification

• npm run test:unit -- --run src/lib/features/intercom/updates.test.ts src/lib/features/intercom/intercom-shell.svelte.test.ts
• npm run validate
• npm run build

Breaking changes

None.

[github-actions]

Package	Line Rate	Branch Rate	Complexity	Health
Exceptionless.Insulation	37%	35%	286	❌
Exceptionless.Core	75%	67%	9992	➖
Exceptionless.Web	85%	69%	7024	✔
Exceptionless.AppHost	38%	40%	139	❌
Summary	78% (23476 / 30282)	67% (11011 / 16516)	17441	✔