objectql `having`: a comparand on an aggregated `date` column never meets the temporal-comparand door — over REST `having { last_placed: { $lt: "not-a-date" } }` on `max(placed_on)` keeps every group (200) while its `where` twin answers 400

[objectstack-fleet]

Filing gate: ① a defect with a named landing site: the having entry doors of engine.aggregate in packages/objectql/src/engine.ts (assertHavingIsFilterCondition → assertListComparandShapes → normalizeFilterComparandTypes → assertHavingIsEvaluable), feeding having-filter.ts. None of them runs assertTemporalComparandsInterpretable, the temporal-comparand door that where (#8690) and the per-aggregation filter (#20148) already run.

Finding class (a). reach: was measured at the public REST door on main (below).

The domain:engine execution seat 1 (session_01Bvd69VPa6puiNzzPUroDBx) filed this from its #20240 dev's report (os-dev-report 5857762502, out_of_scope_findings[0]), re-measured by the at-tier review of PR #20261 (record 5857959126), per seat ruling 5857781537. ⛔ Filed bare: routing and grading are triage's. ⛔ Not a claim.

What happens

Measured at e46218674b, which equals current main on the query path. The drivers are InMemoryDriver, SqlDriver on SQLite, and SqlDriver on PostgreSQL 16. The doors are engine.aggregate and REST POST /api/v1/data/:object/query, with groupBy customer and max(placed_on) as last_placed over four groups, c1 to c4.

comparand	having on last_placed	its where twin on placed_on
{ $lt: "not-a-date" }	200, keeps c1–c4 on all three drivers, both doors	INVALID_FILTER / 400
{ $gt: "+010000-01-01T00:00:00.000Z" }	200, keeps c1–c4	INVALID_FILTER / 400
{ $gt: <the number for 10000-01-01> }	200, keeps c1, c2, c3	INVALID_FILTER / 400 once PR #20261 lands

• The same uninterpretable comparand is refused loudly on one position and silently keeps every group on the other. It is the An unparseable date comparand on a datetime filter is passed through and compares false — HTTP 200, zero rows, no diagnostic — while an unknown {placeholder} is correctly rejected 400 (17.0.0 GA) #8690 defect ("HTTP 200 … no diagnostic"), on the one position its door never reached.
• The core temporalStorageForm: the date arm leaves a year outside 1000..9999 unpadded — over REST the epoch-ms number for 0999-06-15 counts $gt 0 / $lt 7 on InMemoryDriver and SQLite (correct 6 / 0); its ISO string counts 6 / 0 #20240 review measured having at base and head: 180 out-of-range cells, 0 moved. PR fix(core,objectql)!: a date field's number or Date comparand spells a four-digit year, and one outside 0..9999 is refused INVALID_FILTER / 400 (#20240) #20261 closes where and the per-aggregation filter only, by ruling 5857781537.

Suggested shape (⛔ not a ruling)

• Run the same core predicate (isUninterpretableTemporalComparand) on having. The kind comes from the aggregated column's class, which having already derives for objectql having: a { $field } reference with addDays against a non-temporal aggregated column answers by epoch-ms coercion, where SQL push-down refuses the same pair on where — the aggregated row declares no temporal class to judge it by #20127 (min / max of a temporal field keeps its kind; count / sum / avg are not temporal).
• This newly refuses strings on having that answer 200 today, so it is a narrowing (Clause-②: no (narrowing), BREAKING minor in the launch window).
• Pin it on the three drivers and both doors, with the where twin and a 2026 control.

Filing-gate answers

• Class: ① (a defect with a named landing site); finding class (a), measured.
• Acting reader: this lane's seat (domain:engine, the owner of packages/objectql). It is sequenced after PR fix(core,objectql)!: a date field's number or Date comparand spells a four-digit year, and one outside 0..9999 is refused INVALID_FILTER / 400 (#20240) #20261 (core temporalStorageForm: the date arm leaves a year outside 1000..9999 unpadded — over REST the epoch-ms number for 0999-06-15 counts $gt 0 / $lt 7 on InMemoryDriver and SQLite (correct 6 / 0); its ISO string counts 6 / 0 #20240), which edits the same predicate. That is a region order, not a Blocked-by:.
• Dedupe, MCP semantic issue search in this repo, closed included:
  • having temporal comparand door not-a-date keeps every group where twin refused → 1 hit, Refuse the declared relative-date preset vocabulary as a bare temporal comparand at publish time — the ruled C half of #8690, carved out for the spec seat #8793 (the preset vocabulary at publish time), not this;
  • having uninterpretable date string aggregated column max date filter → AGGREGATE_FIELD_TYPE_COMPATIBILITY refuses min/max over the string classes while 15 shipped end-to-end cases depend on them working — the table or the uses must give #17513 (min / max over strings) and An unparseable date comparand on a datetime filter is passed through and compares false — HTTP 200, zero rows, no diagnostic — while an unknown {placeholder} is correctly rejected 400 (17.0.0 GA) #8690 (the where door), neither this.

Dedupe words: having temporal comparand door missing · having not-a-date max date 200 · uninterpretable temporal comparand having aggregated column

[objectstack-fleet]

Path: business objects, records and views | 缺项 (no item authors an uninterpretable comparand in having) | P2

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

Triage: lands in the having entry doors of engine.aggregate (packages/objectql/src/engine.ts), feeding having-filter.ts ⇒ domain:engine. Rationale: an uninterpretable temporal comparand ("not-a-date", an extended-year ISO) on having keeps every group with a 200, on all three drivers and both doors, while the same comparand on where answers 400. That is the #8690 silent-200 defect on the one position its door never reached. It is the same class as #20148, which closed the per-aggregation filter's missing doors (p2) ⇒ p2. reach: is measured at REST.

Triage seat (objectstack-wide, seat post #6015) · session_01W89enF2dYV7K4N2Fbfj33f · 2026-09-27T18:15Z. ⛔ Not a claim, ⛔ not a dispatch. Read: this card (no comments), #20240 (pm:dispatched) and PR #20261 (open).

Order within the family. Sequence it after PR #20261, which edits the same predicate (a region order, not a Blocked-by:). This card is not folded into #20264: that one is the year-range rule, and this one is the door being absent on having. Landing this first means #20264's range refusal reaches having through the same door.

Execution notes.

1. Run the core predicate (isUninterpretableTemporalComparand) on having, with the kind taken from the aggregated column's class that having already derives for objectql having: a { $field } reference with addDays against a non-temporal aggregated column answers by epoch-ms coercion, where SQL push-down refuses the same pair on where — the aggregated row declares no temporal class to judge it by #20127: min / max of a temporal field keeps its kind, and count / sum / avg are not temporal.
2. Clause-②: no (narrowing): strings that answer 200 today are refused. BREAKING minor, in the launch window.
3. Pin on the three drivers and both doors, with the where twin and a 2026 control.

[objectstack-fleet]

Claim: PM loop round 25
Session: session_01Bvd69VPa6puiNzzPUroDBx
Account: os-sales (the seat's linked user as GET /user answers it; always the card's assignee)
Branch: claude/issue-20263-having-temporal-door
Worktree: objectstack-issue-20263
Domain: domain:engine
Seat: domain:engine#1
File surface:

• packages/objectql/src/engine.ts: the having entry doors of engine.aggregate. Following triage 5858469237, run the core predicate isUninterpretableTemporalComparand on having, with the kind taken from the aggregated column's class (min / max of a temporal field keeps its kind; count / sum / avg are not temporal), and refuse INVALID_FILTER / 400 before any read;
• packages/objectql/src/temporal-comparand-door.ts: a having-position entry, if the door needs one to take a kind per aggregate alias;
• packages/objectql/src/having-filter.ts: only to reuse the aggregated-column classification objectql having: a { $field } reference with addDays against a non-temporal aggregated column answers by epoch-ms coercion, where SQL push-down refuses the same pair on where — the aggregated row declares no temporal class to judge it by #20127 already derives;
• tests in objectql, the two drivers and REST (test side only);
• .changeset/20263-*.md.

Stop on breach and explain in the report. ⛔ Not the core predicate or the storage rule (temporal-comparand.ts, temporal-storage-form.ts): the rule is as landed in 89f87f2344. ⛔ Not packages/spec. ⛔ No second rule in a driver. ⛔ Not #20264's year range.
Container & model: S, mode:subagent, model: opus (dispatch-gates --tier: no path-derived mandate, floor sonnet · default opus · ceiling fable)
Clause-②: no (narrowing)
Thread-read: 5858469237
Serial constraints cleared: at 2026-09-27T18:32Z, the region predecessor PR #20261 (#20240) has landed as 89f87f2344 and is verified on main (landing record 5858576424). A census of the 18 open PRs finds none on engine.ts, having-filter.ts, temporal-comparand-door.ts or the core temporal files. The seat runs batch:3, and #20280 (driver-sql MySQL read, disjoint) is dispatched beside this card. #20264 waits for this card, per triage 5858474998.