fix(plugins): reject a storage range filter with no defined bound

[vedanshujain]

What does this PR do?

Targets feat/plugin-storage-updateif (emdash-cms#2169) rather than main, because it was found while reviewing that branch.

buildCondition pushes only the bounds that are defined, so a range filter whose every bound is undefined returned an empty SQL string. buildWhereClause then joined that empty string into the clause, dropping the predicate entirely.

The reachable shape is a bound built from an optional value:

const since = options.since;   // string | undefined
await ctx.storage.events.query({ where: { timestamp: { gte: since } } });

That type-checks, because every bound on RangeFilter is optional. Verified against the pre-fix code — three rows seeded, filter { stock: { gte: undefined } }:

query() returned 3 of 3 rows

So query() and count() returned the whole collection, and updateIf() applied its write with no guard at all:

updateIf("p1", { where: { stock: { gte: undefined } }, delta: { stock: { dec: 1 } } })
→ { applied: true }   row seeded at stock: 0 is now stock: -1

That last one is the oversell updateIf exists to prevent. A second field alongside the empty one emits a dangling AND and fails to parse.

buildCondition now throws StorageQueryError naming the field, and buildWhereClause skips any condition contributing no SQL. Callers that mean "match unconditionally" omit the field.

Note this changes behavior of the already-released query() and count(): a filter that previously matched everything now throws. That is the point of the fix — the old behavior was silent and failed open — but it is a behavior change on a shipped API, so it is called out in the changeset.

Type of change

• Bug fix
• Feature (requires maintainer-approved Discussion)
• Refactor (no behavior change)
• Translation
• Documentation
• Performance improvement
• Tests
• Chore (dependencies, CI, tooling)

Checklist

• I have read CONTRIBUTING.md
• pnpm typecheck passes
• pnpm lint passes
• pnpm test passes (or targeted tests for my change) — full packages/core suite, 6554 passed / 10 skipped / 0 failed
• pnpm format has been run
• I have added/updated tests for my changes (if applicable)
• User-visible strings in the admin UI are wrapped for translation (if applicable) — n/a, no admin UI change
• I have added and reviewed the user-facing changeset (if this PR changes a published package)
• New features link to an approved Discussion — n/a, bug fix
• I have included screenshots below if this PR changes the UI — n/a, no UI change

AI-generated code disclosure

• This PR includes AI-generated code — model/tool: Claude Opus 5 (Claude Code)

Screenshots / test output

Not applicable — no UI change.

Three regression tests, each confirmed to fail before the fix:

• storage-query.test.ts — buildCondition throws for an all-undefined range filter; buildWhereClause never emits a dangling AND.
• storage.test.ts — query() rejects the filter instead of returning every row (the shipped path).
• storage-updateif.test.ts — updateIf() throws instead of writing unguarded, and the row is unchanged.

Test Files  543 passed | 2 skipped (545)
     Tests  6554 passed | 10 skipped (6564)