Mini Object-relational Mapper II

Requirements

• Export MiniORM as named and default. new MiniORM(modelNames) accepts unique nonempty model-name strings. model(name) returns a stable delegate for a registered model; unknown models throw Error. Invalid/duplicate model names throw TypeError.
• Delegates expose synchronous create({ data }), findUnique({ where: { id } }), findMany({ where? } = {}), update({ where: { id }, data }), and delete({ where: { id } }). Records are flat own-enumerable string fields containing null, strings, booleans, or finite numbers. Data must be a plain object; reject unsupported record field values with TypeError. Extended query filters are defined below.
• create generates per-model positive integer IDs starting at 1 when data has no own id. Explicit positive safe-integer IDs are allowed, must be unique, and advance the next generated ID beyond them. Deleted IDs are not automatically reused. Invalid IDs throw TypeError; duplicate IDs throw Error.
• Keep create, findUnique, update, and delete behavior from the first version, including copied records, atomic invalid writes, immutable IDs, and independent models. Extend findMany({ where?, orderBy? } = {}).
• A field condition is a scalar or a nonempty operator object. Support equals (Object.is), in (scalar array), gt/gte/lt/lte (finite numeric operands; only numeric fields match), and contains (case-sensitive substring on string fields). Multiple operators on a field are ANDed; absent fields never match field conditions.
• Combine own fields with AND: Filter[], OR: Filter[], and NOT: Filter. Every own clause is ANDed. Empty AND is true, empty OR is false, and {} matches all records. These three uppercase names are reserved in filters. Reject malformed filters and unknown operators with TypeError, even when no records exist.
• orderBy is an array of { field, direction: asc | desc }. Compare fields in listed order; equal keys retain insertion order. Ascending type order is missing, null, boolean, number, string; within types use false before true, numeric order, and JavaScript string comparison. Descending reverses this order. Empty ordering preserves insertion order. Validate ordering before querying.
• Do not mutate query objects or records. Relations, pagination, asynchronous storage, SQL, and arbitrary nested record data remain out of scope.

Examples

Input: users.findMany({ where: { score: { gte: 2 }, name: { contains: "A" } }, orderBy: [{field:"name", direction:"asc"}] })
Output: Matching records ordered by name.

Input: users.findMany({ where: { OR: [{active:true}, {score:{lt:2}}] } })
Output: Records satisfying either condition, in insertion order.