Add entities data layer (Base44-parity)

[HomemadeToast57]

What

bool.entities.<table> — a data API over the gateway that mirrors Base44's entity surface one-to-one, so generated apps read/write data without ever touching Supabase, SQL, or credentials (and without needing a raw-SQL escape hatch).

const todos = await bool.entities.todos.list("-created_at", 20, 0, ["id","title"]);
await bool.entities.todos.create({ title: "hi" });
await bool.entities.todos.filter({ status: "active", count: { $gte: 10 }, $or: [{a:1},{b:2}] });
await bool.entities.todos.updateMany({ done: false }, { $set: { done: true } });
await bool.entities.todos.deleteMany({ archived: true });
await bool.entities.todos.importEntities(csvFile);

Op parity with Base44: list / filter / get (with sort/limit/skip/fields), create / bulkCreate / update / bulkUpdate / updateMany / delete / deleteMany, importEntities, subscribe. Return types match Base44 (DeleteResult/DeleteManyResult/UpdateManyResult/ImportResult).

Filter DSL: MongoDB-style $eq $ne $gt $gte $lt $lte $in $nin $exists $regex $all $not per field + $and/$or/$nor at the root + array shorthand + null → IS NULL. Maps to PostgREST through supabase-js.

Design notes:

• Returns rows directly and throws on error (not {data,error}) — keeps app code plumbing-free, like Base44.
• Dynamic Proxy keyed by table name — no per-entity codegen/files.
• importEntities parses CSV client-side → bulkCreate — no new gateway endpoint / attack surface.
• Additive & backward-compatible: bool.db / supabase / auth unchanged.

Known gaps (documented): updateMany $inc/$mul/$push/$pull is read-modify-write (not atomic under concurrent writers — RPC follow-up); $size omitted (not expressible over PostgREST).

Tests

Drive the entities layer through the real supabase-js builder and assert the PostgREST request produced (path, filter/sort/pagination/fields query params, bulk/upsert method+headers, read-modify-write $inc round-trip, CSV parse). 39 tests pass; typecheck + build clean.

Version / channel

0.2.0 surface, published to the next (canary) dist-tag as 0.2.0-next.1 for testing (production latest stays 0.1.1). Promote to latest once verified in a canary app.

🤖 Generated with Claude Code