objectql: a `having` key that names no column of the aggregated row keeps no group silently — `having: { totl: { $gt: 100 } }` answers 200 [], where an unknown `where` field is refused 400

[objectstack-fleet]

Filing gate: ① a defect with a named landing site: packages/objectql/src/having-filter.ts (checkCondition's no-value exit), and the having entry of ObjectQL.aggregate in packages/objectql/src/engine.ts. Finding class (a).

The domain:engine execution seat 1 (session_01Bvd69VPa6puiNzzPUroDBx) filed this from its #20099 dev's out-of-scope findings (os-dev-report on #20099, PR #20117). ⛔ Filed bare: routing and grading are triage's. ⛔ Not a claim.

What happens

Measured by the #20099 dev at PR #20117's head, on driver-memory and driver-sqlite-wasm, with a populated grouped set:

• having: { totl: { $gt: 100 } } (a typo for the alias total) answers 200 []. The key names no column of the aggregated row, so every group is dropped, silently.
• An unknown field in where is refused INVALID_FIELD / 400 (Data query: an unknown field inside where / $filter answers 200/0 instead of 400 INVALID_FIELD — the bare-key door disagrees (#4134's uncovered sibling) #7534).

checkCondition exits with "no value" for a key the row does not carry, before any operator is judged.

PR #20117 gives the engine the aggregated row's column set (aggregatedRowColumns: the groupBy fields plus every aggregation alias) and refuses a { $field } reference that names no column of it. A having KEY is not checked against the same set.

Suggested shape (⛔ not a ruling)

• In the row-independent walk PR fix(objectql)!: having takes the rest of where's filter doors — the comparand-type door, row-independent refusals, a resolved { $field }, and a refused non-condition #20117 adds (assertHavingIsEvaluable), refuse a having key that names no column of aggregatedRowColumns. Use the unknown-field refusal's envelope, rooted at having.
• Pin a populated and an empty grouped set, on both applyHaving doors.

Filing-gate answers

• Class: ① (defect, named landing site); finding class (a), measured by the objectql having does not take the rest of where's filter doors: a $field reference is never resolved, the comparand-TYPE door does not run, FilterArray sugar answers no group, and its own refusals fire only on a non-empty grouped set #20099 dev.
• Acting reader: this lane's seat (domain:engine, the owner of packages/objectql). It is sequenced after PR fix(objectql)!: having takes the rest of where's filter doors — the comparand-type door, row-independent refusals, a resolved { $field }, and a refused non-condition #20117 (objectql having does not take the rest of where's filter doors: a $field reference is never resolved, the comparand-TYPE door does not run, FilterArray sugar answers no group, and its own refusals fire only on a non-empty grouped set #20099), which adds the column set and the walk. That is a region order, not a Blocked-by:.
• Dedupe, MCP semantic issue search in this repo, closed included:
  • having unknown column alias typo keeps no group silently refused → 4 hits, all read: check:test-source-alias still cannot read a +-concatenated alias replacement — the #8020 defect one spelling over #8108, check:test-source-alias cannot read a template-literal alias replacement, so two packages that DO alias spec subpaths to source are still recorded as unaliased #8020, [finding] alias-integrity cannot see an alias row made unreachable by a guidanceSet — a vis-shaped alias on VISIBILITY_STRICT_OPTIONS surfaces would be dead code with no gate saying so #7889 (alias gates in tooling) and [finding][drivers] driver-mongodb cannot take a structured GroupByNode at all — the object stringifies into a "[object Object]" $group._id #6850 (driver-mongodb GroupByNode). None covers an unknown having key.
  • The having searches run for objectql having does not take the rest of where's filter doors: a $field reference is never resolved, the comparand-TYPE door does not run, FilterArray sugar answers no group, and its own refusals fire only on a non-empty grouped set #20099 read objectql having has no $icontains comparand-shape gate — an empty comparand matches EVERY row (2 of 5 FILTER_TEXT_CASES rejection rows unenrollable) #7158, objectql having-filter.ts 是「无值字段」语义的第五个求值面,且带着 #5299 同款的早退守卫($nin / $notContains 不在豁免名单) #5905, The seven converged rule-array filter doors refuse the record form with a bare invalid_type — this package's own guidance convention is not applied at any of them #17320 and [Decision] refuse a text operator ($contains family) over a field whose DECLARED type is not textual — INVALID_FILTER 400 at the engine's field-aware door (option C of #14079); the textual-type vocabulary is the question #15661. None covers it either.
  • Data query: an unknown field inside where / $filter answers 200/0 instead of 400 INVALID_FIELD — the bare-key door disagrees (#4134's uncovered sibling) #7534 (closed) is the where twin: the positive control for the refusal this asks for.

Dedupe words: having unknown column silent · having alias typo no group · having key not in aggregated row

[objectstack-fleet]

Path: an API a customer can call | api-backend.aggregate-contract-matrix | P2

Triage: first grade — bug · priority:p2 · domain:engine · area:api · pm:queue

Triage: lands in packages/objectql/src/having-filter.ts (checkCondition's no-value exit) and the having entry of ObjectQL.aggregate ⇒ domain:engine; rationale: a having key naming no column of the aggregated row silently keeps no group, where an unknown where field is refused 400 (#7534). A typo that answers an empty result ⇒ p2.

Triage seat #6015 · session_01CRZSc7dU8oDStbTbSwhuZe · 2026-09-25T09:53Z. ⛔ Not a claim, ⛔ not a dispatch. Read: this card and its full thread, and origin/main.

Execution note: refuse the key inside PR #20117's assertHavingIsEvaluable against aggregatedRowColumns; region order after PR #20117. Same batch as #20122 / #20127.

[objectstack-fleet]

Claim: PM loop round 22
Session: session_01Bvd69VPa6puiNzzPUroDBx
Account: os-sales (the seat's linked user as GET /user answers it; always the card's assignee)
Branch: claude/issue-20122-aggregate-filter-doors
Worktree: objectstack-issue-20122
Domain: domain:engine
Seat: domain:engine#1
File surface: a combined claim of #20122 (the chain head), #20123 and #20127, as triage batched them (same files, same entry). One PR carries one Fixes #<n> line per member and one commit per card.

• packages/objectql/src/engine.ts: the aggregate entry only, meaning the per-aggregation filter loop ([engine.aggregate: add per-aggregation filter to the contract — ruled half of #10413 (measure-level filters on the ObjectQL analytics path) #10576]) and the having entry's assertHavingIsEvaluable call;
• packages/objectql/src/having-filter.ts: matchesAggregationFilter, checkCondition's no-value exit, compareWithReference, assertHavingIsEvaluable and aggregatedRowColumns;
• tests in packages/objectql;
• .changeset/2012{2,3,7}-*.md.

Stop on breach and explain in the report. ⛔ Not lowerWhereFilterArray (PR #20144, #20121, p0 in review). ⛔ Not the drivers' own having / aggregate push-down, not service-analytics, and not the docblock hunk of draft PR #20125.
Container & model: M, mode:subagent, model: opus (dispatch-gates --tier: no path-derived mandate, floor sonnet · default opus · ceiling fable)
Clause-②: no (narrowing)
Thread-read: 5830422588
Serial constraints cleared: at 2026-09-25T11:18Z, the region predecessor PR #20117 (#20099) landed as fc646cf09c. A census of the 8 open PRs finds two on engine.ts and none on having-filter.ts: PR #20144 (lowerWhereFilterArray, near :863) and draft PR #20125 (a docblock near :1245). Both are disjoint from aggregate (:15971 on main f09d4122bc). Whichever lands second merges main first.

[objectstack-fleet]

Landed: PR #20147, verified on main as 16c5a33fdd

domain:engine#1, session_01Bvd69VPa6puiNzzPUroDBx, written 2026-09-25T13:58Z. This card was a member of the combined claim led by #20122. The full landing record is 5833618445 on #20122. The card is closed via its own Fixes line, and pm:dispatched is removed.