Design pillar: TypeScript strictness — no any, generic track(), strict option types

[productdevbook]

TypeScript gaps are the #2 complaint class in every wrapper. We ship strict types day one.

Evidence

• `Incompatible with typescript tawk/tawk-messenger-react#13` — "Incompatible with typescript" (open since 2022) Incompatible with typescript tawk/tawk-messenger-react#13
• `Add typescript type definition file tawk/tawk-messenger-react#7` — "Add TypeScript type definition file" Add typescript type definition file tawk/tawk-messenger-react#7
• `Hope to support typescript tawk/tawk-messenger-vue-3#7` — "Hope to support TypeScript" Hope to support typescript tawk/tawk-messenger-vue-3#7
• `Callback for Crisp.message.onMessageSent missing TypeScript definition crisp-im/crisp-sdk-web#27` — "Callback for onMessageSent missing TypeScript definition" Callback for Crisp.message.onMessageSent missing TypeScript definition crisp-im/crisp-sdk-web#27
• `Carousel message type mismatch between docs & typings crisp-im/crisp-sdk-web#16` — "Carousel message type mismatch between docs & typings" Carousel message type mismatch between docs & typings crisp-im/crisp-sdk-web#16
• `The operand of a 'delete' operator must be optional. crisp-im/crisp-sdk-web#22` — `isolatedModules` / `export {}` failure The operand of a 'delete' operator must be optional. crisp-im/crisp-sdk-web#22
• `Types for IntercomAPI nhagen/react-intercom#83` — "Types for IntercomAPI" Types for IntercomAPI nhagen/react-intercom#83
• `Instructions result in type error nhagen/react-intercom#91` — "Instructions result in type error" Instructions result in type error nhagen/react-intercom#91
• `Typescript Generics devrnt/react-use-intercom#456` — "Typescript Generics" (asks for `trackEvent(event, metaData?: T)`) Typescript Generics devrnt/react-use-intercom#456
• `Provider complains about custom attributes devrnt/react-use-intercom#478` — "Provider complains about custom attributes" Provider complains about custom attributes devrnt/react-use-intercom#478
• `Cannot find namespace 'JSX'. aaronhayes/react-use-hubspot-form#49` — "Cannot find namespace 'JSX'" Cannot find namespace 'JSX'. aaronhayes/react-use-hubspot-form#49
• `Failed prop type: Zendesk: prop type defer is invalid B3nnyL/react-zendesk#22` — "Failed prop type: defer is invalid" Failed prop type: Zendesk: prop type defer is invalid B3nnyL/react-zendesk#22
• `Incorrectly using PropTypes (boolean instead of bool) B3nnyL/react-zendesk#31` — "Incorrectly using PropTypes" Incorrectly using PropTypes (boolean instead of bool) B3nnyL/react-zendesk#31

Contract

1. `strict: true`, `noImplicitAny`, `verbatimModuleSyntax`, `isolatedModules`, `noUncheckedIndexedAccess` all on.
2. `track<T extends Record<string, JsonValue>>(event: string, metadata?: T)` — generic metadata.
3. Per-provider `LoadOptions` extends base with discriminated union — required fields (`appId`, `websiteToken`, `key`, `portalId`, `propertyId`) are required at the type level.
4. `declare global` extensions only inside provider files, never polluting global consumers — use ambient `ahize/globals` optional import for users who want `window.Intercom` typed.
5. No `any`, no `Function`, no `{}`. Callback payloads defined as typed unions per provider.
6. Publish with `provenance` + `attw` checks in release pipeline to guarantee types don't regress under modern resolution modes.

[productdevbook]

Implemented in c532a7c