effect-orm 0.6.0 and fix the failing electric-proxy e2e

CLAUDE.md

@@ -197,7 +197,7 @@ yield* db.transaction(Effect.gen(function* () { /* every statement in here joins
 ```
 
 - `db.transaction(effect)` pins every statement inside `effect` (repositories included) to one connection through fiber context; there is no transaction handle to pass around.
-- Schema changes: edit `src/tables`, then `bun run db:generate --name <name>`. effect-orm does not model enums or unique constraints: write those in a `--custom` migration.
+- Schema changes: edit `src/tables`, then `bun run db:generate --name <name>`. Enums are `PG.enumType`, unique constraints `PG.unique` in `uniqueConstraints`; `generate` migrates both. What effect-orm does not model (check constraints, removing or reordering enum labels) goes in a `--custom` migration.
 
 ## Architecture Notes
 

apps/electric-proxy/src/e2e/electric-proxy-filters.e2e.test.ts

@@ -1094,7 +1094,7 @@ const assertVisibilitySpec = (rows: Array<Record<string, unknown>>, spec: Visibi
 describe("electric-proxy filter E2E (real Electric)", () => {
 	beforeAll(async () => {
 		runShell("docker compose up -d postgres electric cache_redis")
-		runShell("bun run --cwd packages/db db:push", REPO_ROOT, { DATABASE_URL: DB_URL })
+		runShell("bun run --cwd packages/db db:migrate", REPO_ROOT, { DATABASE_URL: DB_URL })
 
 		fixture = createFixture()
 		seedFixture(fixture)