v0.3.0

UX Struggle Detector v0.3.0

Guided live lab

A responsive, local checkout exercise runs the actual SDK collector, the production struggle detector and targeted interventions. Inspect real event and rule evidence, enable clear feedback, try field validation, stop/resume/reset collection and export JSON. No model call, order, address submission or database connection is involved. The demonstration does not measure conversion lift.

Complete tours and collection lifecycle

Five-step guided product tour; SDK tours support Back, Next, Finish, Escape, focus trapping/restoration, missing targets and replay. Persisted intervention completion is reported only on Finish. Text stays inert. SDK destruction aborts transport, collectors, timers and owned interventions, restores owned history wrappers and permits reinitialization. Runtime IDs now bind to their DOM targets and refresh across route/organization changes.

Installable SDK

The attached csnyder256-ux-struggle-sdk-0.3.0.tgz includes dependency-free ESM/CommonJS, declarations and script builds. Verify checksums.txt before installing the local package. sdk-provenance.json records the exact build source and package hash. npm registry publication is gated on a configured publisher; this release distributes the package directly on GitHub Releases.

Strict NodeNext consumers, inert SSR imports, the full existing suite and a real desktop/mobile browser journey are checked in CI. Script auto-initialization remains available; package imports are inert until initialized. One SDK instance is supported per page. Destroy intentionally discards pending data; flush first when delivery is required. Input values are excluded, but labels/routes/custom metadata still require your privacy policy and consent handling.

Upgrade

Server and SDK versions should match. Back up PostgreSQL, review schema changes and preserve private runtime settings. This release adds no schema migration; existing intervention rows remain intact. Keep the prior server/SDK release for rollback.

Deployment instructions.

v0.2.0

ux-struggle-detector v0.2.0 — Clarus Heal self-hosting release

What changed

• Docker Compose deployment with PostgreSQL, persistent data and an explicit schema setup step.
• Standalone production server and versioned browser SDK downloads.
• Audited tenant authorization, ingestion and detector boundary fixes.

Install and upgrade

Back up PostgreSQL before upgrading. Existing installations must review schema changes rather than run the fresh-install setup command. Container defaults require authentication and ingestion keys. Existing legacy intervention rows remain intact; newly created rows carry tenant scope.

See deployment instructions and the attached checksums.

v0.1.0

First public snapshot. UI mapping, drop-in browser SDK, 40 server-side struggle detection rules, and same-response interventions.