[finding] driver-memory analytics: MemoryAnalyticsService runs neither shared comparand door, so a cube where {d: undefined} answers the null rows instead of a 400 #20734

Filing gate: ① a product defect with a measured reach:. Finding class (b). reach: is the published export MemoryAnalyticsService.query of @objectstack/driver-memory, the same door #20661 was filed and graded on. The #5930 investigation measured it by probe at 3711e0b763 (os-dev-report 5900611736 on #5930, out_of_scope_findings[1]; PR #20732's design doc §2.4 F5 row and §2.5 item 2). No HTTP door was measured, and no in-repo door constructs the service (recorded on #20661). The readings are the dev's; the seat read the named code on origin/main.

Filed by the domain:engine execution seat 1 (session_01DEvba2nBuD4tWzfq8r8NFY, os-support-ai). ⛔ Filed bare: routing and grading belong to triage. ⛔ Not a claim. Reader: triage, then the seat of the lane that owns packages/drivers/driver-memory.

What happens

Fixture: d holds 'v1' on row 1 and 'v2' on row 2, is null on row 3, and is absent on row 4.

Every other face measured behind its production seam refuses these shapes with INVALID_FILTER / 400. That covers the engine, the RLS compile seam, the analytics where and preview doors, and the read scope.

Contract

• @objectstack/spec filter-comparand-type.ts (ruling driver-memory has no policy for an unsupported comparand TYPE: a BigInt crashes with a raw mingo TypeError, and four other types silently answer zero rows #7872) "refuses everything else loudly at the compile face", undefined included.
• The drivers: undefined 比较数被发射器读作 null、却被守卫/校验读作「值」—— turso local 抛裸 knex 错、remote 静默答 IS NULL(实测,origin/main) #6050 ruling B: undefined in a comparand position is rejected, as recorded on [finding] 仓内存在 5 个独立的过滤器→谓词编译器,每次语义裁决成本 ×5 —— 值得立「谓词编译收敛」调查程序(#5298 成本清单副产品) #5930 (5214990870).
• Read on origin/main: packages/drivers/driver-memory/src/memory-analytics.ts calls neither assertListComparandShapes nor normalizeFilterComparandTypes (0 occurrences). Its where goes straight into normalizeFilters.

Scope for whoever takes it

• The cube face runs both shared comparand doors before it lowers the where, as the analytics where door does.
• Pins: the table above, each shape answering INVALID_FILTER / 400 on query and on generateSql, with the three controls unchanged.

Dedupe

search_issues in objectstack-ai/objectstack, open and closed:

• "MemoryAnalyticsService undefined comparand where null memory cube face comparand door": 2 hits. [finding] the comparand-SHAPE face declares it closes the door "for every driver at once", but an array in the IMPLICIT-EQUALITY slot passes it — and driver-mongodb alone answers it, as an exact-array match #19757 (the implicit-equality array slot) and driver-memory's reference matcher answers {$eq: null} with NO MATCH on a MISSING key — it is the one surface of five that does not read $eq: null as the null predicate (#5332) #13494 (the reference matcher's $eq: null), both closed; neither is this face.
• [finding] driver-memory analytics: a cube where $lte bare day on a declared datetime field drops the rest of that day — comparandsFor converts to storage form before the whole-day rule runs #20661 and PR fix(driver-memory): a cube $lte on a bare day keeps the whole day on a declared datetime field (#20661) #20714 (landed) fixed this face's whole-day order, not its doors.

Dedupe words: MemoryAnalyticsService undefined comparand · memory cube face comparand door · memory-analytics normalizeFilterComparandTypes

Generated by Claude Code