[thedogwiththedataonit]

Applications need an authenticated way to submit product events and bind consented browser activity to an existing Brew contact. Add typed analytics tracking and short-lived identity-token methods, with canonical OpenAPI types and documentation. Identity-token requests deliberately omit automatic and caller-supplied idempotency headers so expired proofs cannot be replayed.

Validation: 791 tests across 128 files, typecheck, lint, formatting, ESM/CJS/declaration builds and generated-type freshness all passed. Paired platform implementation: https://github.com/GetBrew/brew-v2/pull/2514. Hold for coordinated merge; this PR does not publish a package.

Reviewed with sol-loop: 3 rounds with GPT-6.1 Sol. Sol verdict: approved.
Created with GPT-6 in Codex.

---

^{Need help on this PR? Tag @codesmith-bot with what you need.}

Confidence Score: 5/5

The reviewed changes appear safe to merge as part of the coordinated platform rollout.

Summary

Adds trusted event tracking and short-lived browser identity tokens to brew.analytics.

• Servers can submit trusted product events through analytics.
• Servers can issue short-lived proofs linking browser activity to a contact.
• Email test deliveries are described as not using plan sends.
• Public API descriptions and generated types cover more current endpoint details.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart LR
  Backend[Application backend] --> Analytics[brew.analytics]
  Analytics --> Track[track]
  Analytics --> Identity[createIdentityToken]
  Track --> Events[Accepted IDs and rejected events]
  Identity --> Token[Short-lived token]
  Token --> Browser[Browser SDK]

Loading

_{Reviews (7) · Last reviewed commit: "Sync plan and notification API contracts" · Reviewed by Greptile}