v1.2.0 — Tero ACID store, GA4-style events, crash reporting

v1.2.0 replaces the monolithic JSON file with Tero, an embedded ACID store. Writes are now transactional and per-document, so concurrent events can no longer corrupt the database, and the cost of an event stops growing with your dataset size.

The SDK gains GA4-style event helpers across the board: pageView, login, purchase, addToCart, and the rest of the standard surface, all passing structured eventParams. Server-side users get the same helpers from the createClient() API.

Crash reporting lands as captureException(). Unhandled errors route to POST /analytics as exception events with description, stack, and fatal flags — so a failed purchase shows up next to the session that caused it. The dashboard groups them into an error feed for triage.

Also included: the browser SDK now ships a passive fingerprint, per-project session keys are namespaced, and the served tracker resolves its own endpoint from the script URL. Full SDK documentation is in the Docs section.