feat(audience): add transport, queue, and context collection to core

[nattb8]

What this adds

The transport, batched queue, and context collection modules that complete @imtbl/audience-core. These sit on top of the types/utils/config/storage/cookie from SDK-33 and give the web SDK (SDK-30) and pixel everything they need to send events.

• transport.ts — HTTP POST to the audience API with x-immutable-publishable-key header. Returns boolean success for v1 (the audience service returns { success, accepted, rejected } but rejected messages indicate SDK bugs, not transient errors — revisit if debugging needs arise).

• queue.ts — Batched message queue with localStorage durability. Flushes on a timer or when the queue reaches flushSize, whichever comes first. Failed flushes retry on the next cycle. Persisted messages survive page navigations and are restored on construction. Concurrent flush guard prevents races.

• context.ts — Collects device fingerprint signals that match the audience service EventContext schema: userAgent, locale, timezone, screen resolution, page URL/path/referrer/title. IP is collected server-side by the audience service, not by the SDK.

• Updated index.ts exports for all new modules.

Out of scope

• UTM parameter extraction (SDK-37, pixel/web SDK concern)
• keepalive fetch for page unload (SDK-38, web SDK concern)
• Device fingerprint hashing (SDK-39, server-side concern)

Linear: https://linear.app/imtbl/issue/SDK-34

🤖 Generated with Claude Code

[nx-cloud]

View your CI Pipeline Execution ↗ for commit 96b29ec

Command	Status	Duration	Result
nx affected -t build,lint,test	✅ Succeeded	8s	View ↗
nx run-many -p @imtbl/sdk,@imtbl/checkout-widge...	✅ Succeeded	2s	View ↗

---

☁️ Nx Cloud last updated this comment at 2026-04-02 01:13:23 UTC