feat: Support arbitrary boolean expressions with subqueries (OR, NOT)

.changeset/arbitrary-boolean-expressions-with-subqueries.md

@@ -0,0 +1,19 @@
+---
+"@core/sync-service": minor
+"@core/elixir-client": minor
+---
+
+Add support for arbitrary boolean expressions with subqueries.
+
+Previously, WHERE clauses with OR or NOT combined with subqueries would cause shape invalidation. This update implements RFC "Arbitrary Boolean Expressions with Subqueries" which enables:
+
+- OR with multiple subqueries: `WHERE project_id IN (SELECT ...) OR assigned_to IN (SELECT ...)`
+- NOT with subqueries: `WHERE project_id NOT IN (SELECT ...)`
+- Complex expressions: `WHERE (a IN sq1 AND b='x') OR c NOT IN sq2`
+
+Key features:
+- DNF (Disjunctive Normal Form) decomposition for WHERE clause analysis
+- `active_conditions` array in row messages indicating which atomic conditions are satisfied
+- Position-based move-in/move-out handling that correctly inverts behavior for negated positions
+- Deduplication logic to prevent duplicate inserts when rows match multiple disjuncts
+- Updated elixir-client to parse `active_conditions` field in message headers

.changeset/fix-move-in-coverage-check.md

@@ -0,0 +1,5 @@
+---
+"@electric-sql/sync-service": patch
+---
+
+Fixed a bug where changes were incorrectly skipped when a record's subquery reference value was in a pending move-in, but the record didn't match other non-subquery conditions in the WHERE clause. For example, with a shape `parent_id IN (SELECT ...) AND status = 'published'`, if the parent became active (triggering a move-in) but the child had `status = 'draft'`, the change would incorrectly be skipped instead of being processed as a delete.