sqlite "ConstraintViolation" reported as a "PROXY_ERROR"

As mentioned in the title, following are 2 traces coming from turso's UI, it's very easy to reproduce:

Violating NOT NULL constraint

Error: PROXY_ERROR: error executing a request on the primary: NOT NULL constraint failed: User.id
    at window.drizzle (https://turso.tech/_next/static/chunks/7061-c994b6446462fd0a.js:1:28549)
    at async https://turso.tech/_next/static/chunks/74f8cf84.b675ca02858c4173.js:400:3481
    at async https://turso.tech/_next/static/chunks/74f8cf84.b675ca02858c4173.js:25:22415
    at async Promise.all (index 0)
    at async saveChanges (https://turso.tech/_next/static/chunks/74f8cf84.b675ca02858c4173.js:25:22362)
    at async https://turso.tech/_next/static/chunks/74f8cf84.b675ca02858c4173.js:144:7618

Violating UNIQUE constraint

PROXY_ERROR: error executing a request on the primary: UNIQUE constraint failed: User.email

This is a problem as it hurts error handling in apps.

Start by reproducing the NOT NULL and UNIQUE constraint failures in the Turso UI, following the primary-request path shown in the traces and the window.drizzle/saveChanges calls. Trace where SQLite constraint errors become PROXY_ERROR; done means these violations are exposed distinctly enough for application error handling.