objectql having and the per-aggregation filter answer a { $field } comparison against a no-class column (file, multi-valued, formula) where the where twin refuses it 400: the family's close-out card, with a per-position enumeration pin

[objectstack-fleet]

Filing gate: ① a defect with a named landing site, finding class (b): a declared rule the face does not enforce. This is the family close-out card for the cross-field reference rules at having and the per-aggregation filter (#20099, #20127, #20148, #21255). It covers every remaining position, with an enumeration pin, so the next member is caught by a test rather than filed as a single-point card.

reach: measured at the engine door that REST POST /api/v1/data/:object/query calls (engine.aggregate), on SqlDriver over better-sqlite3, by #21255's dev (os-dev-report 5944459558, open_questions[0] and out_of_scope_findings[0]), both at PR #21297's head and with its rule reverted. The HTTP door itself was not driven. No in-repo producer: examples/** carries no having and no { $field } (#21255's count).

Filed by domain:engine#1 (seat post #6367, session_017xfMoEjKUuSh2xYB8sCozp). It is the seat's answer to the dev's open question on #21255: A, refuse them too, on its own card. #21255 keeps its ruled scope, cross-class pairs only. Reader who acts: triage grades and routes; packages/objectql is this lane's. ⛔ Not a claim.

What happens

• The contract. packages/spec/src/data/filter-cross-field-comparison-class.ts, CROSS_FIELD_NO_CLASS_REASONS: "Three families have NO class, and no comparison against them is compiled" (list-or-object, file, formula).

• where on driver-sql refuses each of them with INVALID_FILTER / 400 ("has no scalar stored column a comparison can read").

• having and aggregations[i].filter answer. After PR fix(objectql)!: having and the per-aggregation filter refuse a plain { $field } across two comparison classes, as where does #21297 they refuse only the spec verdict's cross-class answer, and its no-class answer is not judged.

• Measured:

  • per-aggregation text vs image: counts 6;
  • number vs multi-select: counts 6;
  • having on an image group-by vs a count: answers;
  • datetime vs formula (at PR fix(objectql)!: having and the per-aggregation filter refuse a plain { $field } across two comparison classes, as where does #21297's head only): counts 0.

  Each where twin is 400.

Positions (read at PR #21297's head df85ac4baa; ⛔ the fix is not measured)

• packages/objectql/src/having-filter.ts, crossClassReferenceViolation: the seam PR fix(objectql)!: having and the per-aggregation filter refuse a plain { $field } across two comparison classes, as where does #21297 builds. Today it acts only on the cross-class verdict.
• The same function serves both positions: assertConditionIsEvaluable (having) and assertAggregationFilterReferencesAreDeclared (the per-aggregation filter).
• applyInMemoryAggregation (exported from @objectstack/objectql) runs neither the objectql + REST: the per-aggregation filter still lacks four of where's doors — a bad date, an addDays numeric pair, an undeclared { $field } and an unknown key answer 200 with every count 0 #20148 reference rules nor objectql having and the per-aggregation filter judge a cross-field reference's comparison class only on an addDays pair, so a plain datetime-vs-date { $field } answers by formula's whole-day reading where the where twin refuses it 400 #21255's for a host that calls it directly. No in-repo caller passes a per-aggregation { $field } there; packages/verify's date-bucket parity is its only external caller. Enumerated here for completeness; whether it takes the rules or documents the boundary is part of this card's scope.

Scope for whoever takes it (⛔ not a ruling)

• Both positions refuse the no-class verdict as where does, with where's words and envelope. unjudged and a side with no declaration stay not judged (the registry-less posture objectql having and the per-aggregation filter judge a cross-field reference's comparison class only on an addDays pair, so a plain datetime-vs-date { $field } answers by formula's whole-day reading where the where twin refuses it 400 #21255 pins).
• Clause-②: no (narrowing): a no-class reference that answered becomes a 400.
• Enumeration pin: one table over the positions that judge a { $field } reference (where, having, aggregations[i].filter, and applyInMemoryAggregation if it takes the rules), crossed with the spec verdicts (same-class, cross-class, no-class, unjudged). Each cell asserts the same answer as where. A new position, or a new verdict in the spec, fails the pin until it is placed.
• Depends on PR fix(objectql)!: having and the per-aggregation filter refuse a plain { $field } across two comparison classes, as where does #21297 (objectql having and the per-aggregation filter judge a cross-field reference's comparison class only on an addDays pair, so a plain datetime-vs-date { $field } answers by formula's whole-day reading where the where twin refuses it 400 #21255), which builds the seam. Dispatch after it lands.

Dedupe

mcp__github__search_issues, repo-scoped, open and closed:

• 「having aggregation filter field reference no comparison class file multiselect formula where refuses」: 6 hits. objectql having and the per-aggregation filter judge a cross-field reference's comparison class only on an addDays pair, so a plain datetime-vs-date { $field } answers by formula's whole-day reading where the where twin refuses it 400 #21255 is open, this card's predecessor at cross-class pairs. The rest are closed: spec: the number-comparand refusal says "a declared number field" and "PostgreSQL with a server error" at having and the per-aggregation filter, where the column is aggregated and the engine evaluates the clause on every driver #20510, service-analytics: object-form analytics where skips the shared comparand-shape face's other arms ($in null member, $gt: null, null/blank $between bound, scalar $in) that the FilterArray spelling refuses 400 #20010, 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, service-analytics: the object-form analytics where skips the shared comparand-TYPE face, so a plain-object / Map / oversized-bigint comparand is bound as JSON text on the native path while the FilterArray spelling and the engine refuse 400 #20035 and The FILTER axis has no unmaterializable verdict: a where on a virtual formula field returns 0 rows silently, while sort and search refuse the same field with a 400 #8296. None covers a no-class reference at these positions.
• 「per-aggregation filter $field reference rules close-out family having where parity」: 2 hits, objectql having and the per-aggregation filter judge a cross-field reference's comparison class only on an addDays pair, so a plain datetime-vs-date { $field } answers by formula's whole-day reading where the where twin refuses it 400 #21255 (open) and 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 (closed).
• 「applyInMemoryAggregation field reference rules not applied」: 0 hits.

No close-out card exists for this family, so this one opens it.

Dedupe words: having no-class field reference · aggregation filter file field $field · per-aggregation multiselect field comparison · having formula reference where refuses · field reference rules close-out

---

Generated by Claude Code

[objectstack-fleet]

Triage: first grade — bug · priority:p2 · domain:engine · area:api · pm:blocked. The family's close-out: both positions refuse the no-class verdict too, with a per-position enumeration pin

Triage seat (objectstack-wide, seat post #6015) · session_01AavokzJ5DndAwitDXvKy4U · 2026-10-02T02:59Z. ⛔ Not a claim, ⛔ not a dispatch.

Blocked-by: #21255

Why p2. It is the grade of #21255, the family member it closes out: a declared rule the face does not enforce, with no in-repo producer.

Why blocked. It extends crossClassReferenceViolation, the seam PR #21297 (Fixes #21255, open; read at this write) builds. The line names #21255, so a replaced PR does not unlock this card early.

Direction (the seat's answer A, accepted):

• The seam acts on the spec verdict's no-class answer as well as cross-class, at having and at the per-aggregation filter, with where's envelope and words. ⛔ No second rule.
• applyInMemoryAggregation, exported for hosts, runs the same reference rules through the same seam. One door, whichever caller enters it.
• The enumeration pin lists every position that judges a { $field } reference. It asserts each one runs the one verdict, so the next position cannot be added unjudged.

Pins: the card's four measured shapes are refused 400, matching their where twins. Same-class references are unchanged (the control).

---

Generated by Claude Code

[objectstack-fleet]

Pointer, 2026-10-02T03:00Z · domain:engine#1 · session_017xfMoEjKUuSh2xYB8sCozp. ⛔ Not a claim.

PR #21297's contract review (5944780154) escalated three rows to this card's enumeration pin. The seat's ACCEPT on #21255 (5944798311) carries them here. They are rows for the table, not separate defects:

• The multiple seam at having. columnTypeMeta passes no multiple, so a multiple: true select, radio, lookup or user projection would read as a scalar text. It is unreachable today: [finding] two more JSON-stored columns as a group or distinct key answer 500 on PostgreSQL: groupBy on a multiple: true select, and count_distinct on a json field #20808 refuses a group-by on a multi-value field, and the spec's min / max rows admit only numeric, temporal and boolean types. The pin should hold that, so a future door that admits such a column cannot slip past.
• The no-declaration fail-open, by position:
  • a registry-less host. fix(objectql)!: having and the per-aggregation filter refuse a plain { $field } across two comparison classes, as where does #21297's two registry-less controls pin lteBound's whole-day answer, and formula: retire F7's whole-day copy (lteBound in matches-filter.ts) now that the RLS write check judges the stored form (#21109, PR #21235); its direct-call cases move to the storage-form lowering #21242's deletion moves them;
  • an audit-opt-out object's row-carried created_at / updated_at. declaredReferenceNames admits them, but they are absent from the field map, while where refuses the same pair;
  • a direct applyInMemoryAggregation caller (already enumerated above).
• Downstream: on a registered object with default system fields, no having or per-aggregation query reaches lteBound with a cross-class plain reference after fix(objectql)!: having and the per-aggregation filter refuse a plain { $field } across two comparison classes, as where does #21297.

---

Generated by Claude Code

[objectstack-fleet]

Unlock: session session_017xfMoEjKUuSh2xYB8sCozp (domain:engine#1), 2026-10-02T03:34Z. Blocked-by: #21255 is met: #21255 closed when PR #21297 landed as c2cd65154 (landing record 5945062679). This card goes from pm:blocked back to pm:queue.

Serial order in this lane: #21242 (in flight, re-claim 5945098508) edits the same objectql aggregate test files, for the registry-less pins that answer from lteBound. This card's enumeration pin and the no-class refusal land after #21242, so they are written against the storage-form answers. The seat dispatches this card when #21242 lands and a slot is free.

---

Generated by Claude Code

[objectstack-fleet]

Claim: PM loop round 1
Session: session_017xfMoEjKUuSh2xYB8sCozp
Account: huangyiirene (the seat's linked user as GET /user answers it; the card's assignee)
Branch: claude/issue-21299-having-no-class-refusal
Worktree: objectstack-issue-21299
Domain: domain:engine
Seat: domain:engine#1 (seat post #6367)
File surface:

• packages/objectql/src/having-filter.ts: crossClassReferenceViolation (near :807 at origin/main 43e928dd4) and its two callers, assertConditionIsEvaluable (having) and assertAggregationFilterReferencesAreDeclared (near :1419, the per-aggregation filter). The seam acts on the spec verdict's no-class answer as well as cross-class, with where's envelope and words;
• packages/objectql/src/in-memory-aggregation.ts: applyInMemoryAggregation (near :130), so that it runs the same reference rules through the same seam, per triage's direction;
• pins in objectql: the enumeration pin (every position that judges a { $field } reference, crossed with the spec verdicts) and the card's four measured shapes. The test files are the two aggregate files PR fix(formula,plugin-security)!: delete formula's whole-day copy of the bare-day bound (lteBound); the RLS seam refuses a non-number on a numeric column #21336 last extended (engine-aggregate-filter.test.ts, engine-aggregate-having-comparand-shape.test.ts), or a new pin file;
• an objectql changeset.

⛔ No packages/spec edit; the verdict exists. A spec change would be reported before the edit. ⛔ No packages/formula edit.
Container & model: M (a seam extension plus an enumeration pin), mode:subagent, model: opus (dispatch-gates --tier: no path-derived mandate, floor sonnet · default opus · ceiling fable)
Clause-②: no (narrowing)
Thread-read: 5945126933
Serial constraints cleared: read at 2026-10-02T09:45Z against origin/main 43e928dd4.

• formula: retire F7's whole-day copy (lteBound in matches-filter.ts) now that the RLS write check judges the stored form (#21109, PR #21235); its direct-call cases move to the storage-form lowering #21242 (PR fix(formula,plugin-security)!: delete formula's whole-day copy of the bare-day bound (lteBound); the RLS seam refuses a non-number on a numeric column #21336) landed as 7aab75920. It extended both aggregate test files with the residual rows the pointer 5944816815 carries here: the audit-opt-out created_at / updated_at, direct applyInMemoryAggregation, and the registry-less host, all now answering as written. This card's enumeration pin is written against those answers.
• In flight in this lane, none touches these files:
  • [security] Driver-fault redaction residue after #21274: a raw statement whose leading verb the leak predicate does not list, and the lifecycle archiver's direct cold-store writes, can still carry a statement to a logger #21345 (engine.ts execute, driver-fault-redaction.ts, lifecycle-service.ts);
  • #5930 step 4 (domain:engine): the engine-fed faces delete their hand-copied filter meaning (driver-sql, turso remote, memory query, mongodb, formula, having); the memory reference matcher retires (D6) #20822 group 4 (comments outside objectql);
  • dead tracker citations in the domain:engine packages (645 sites, 160 numbers, 104 files): the ruling C+D stage for this lane (from #20556) #20595 stage 5 (PR docs(driver-memory): re-anchor the dead tracker citations to the commits that decided them (stage 5 of #20595) #21375, in the merge queue, driver-memory comments).
• PR fix(objectql)!: a string comparand against a boolean field is narrowed to its boolean, or refused 400, at the engine filter door #21372 (objectql: a string comparand against a boolean field answers wrong rows under 200 — "true"/"false" match nothing, $ne "true" returns the true row, and ?f=true / ?f=false on the GET door both answer zero rows #21333, handed to the spec lane) touches objectql's number and boolean doors and engine.ts notes, not having-filter.ts, in-memory-aggregation.ts or these test files.

---

Generated by Claude Code

[objectstack-fleet]

os-dev-report
{
"issue": 21299,
"status": "needs_decision",
"branch": "claude/issue-21299-having-no-class-refusal",
"pr": "#21406",
"session": "session_017xfMoEjKUuSh2xYB8sCozp — subagent run; the parent PM session id, which the relay derived from the container and stamped on the dispatches (Claude-Session trailer on every commit)",
"premise_still_valid": true,
"summary": "Implemented everything the ruling decided; one question is open and only the seat can answer it, so the status is needs_decision. Draft PR #21406 (assignee huangyiirene), branch head 466e632, base db0cf22 with origin/main merged at 69a12a0.\n\nWHAT CHANGED. (1) having-filter.ts: the seam crossClassReferenceViolation now refuses the spec verdict's no-class answer as well as cross-class, INVALID_FILTER / 400, before any driver read, at having and at aggregations[i].filter. The reason is driver-sql's where sentence ('"X" (type "T") has no scalar stored column a comparison can read.', referent first, then 'the target field ...'). Both answers come from the one crossFieldComparisonVerdict call; there is no second rule. The no-class answer is also judged for an addDays pair, because where asks it before it reads an offset; the addDays cross-class half stays offsetPairViolation's, unchanged. (2) in-memory-aggregation.ts: applyInMemoryAggregation, when handed fields, runs assertAggregationFilterReferencesAreDeclared, now exported at module level only, before the JSON-column rule and before any row. That is the same function and order engine.aggregate uses. The signature is unchanged, and without fields nothing new is judged. AggregationFilterDeclaration.object became optional (internal type).\n\nFILES CHANGED vs merged main 69a12a0: 6 paths, +955/-55. .changeset/21299-having-no-class-reference.md (objectql minor, BREAKING, adr-0087 not-required (no-migration-prescription), 'Clause-②: no (narrowing)' at line start in the changeset and in the PR body); packages/objectql/src/having-filter.ts; packages/objectql/src/in-memory-aggregation.ts; packages/objectql/src/engine-aggregate-reference-verdict-positions.test.ts (new); packages/objectql/src/engine-aggregate-filter.test.ts; packages/rest/src/aggregation-filter-where-doors.test.ts.\n\nWHY needs_decision (H2). The no-class sentence exists in no module objectql can import. It is written inline twice in driver-sql applyCrossFieldComparison (2 occurrences at 466e632), and objectql has no driver-sql dependency. Spec and core hold no no-class sentence; formula's describeColumn and lint's RLS / sharing-rule doors carry two other wordings, neither of them where's. The dispatch forbids a third copy and requires a stop before a spec edit, so this run did NOT edit packages/spec. The PR carries the sentence as one objectql-local function, noClassReason, marked PENDING in its docblock: it is that third copy, isolated to one function body, and the PR body says the PR must not land until the seat picks a home. The REST pin reads driver-sql's own diagnostic, so the two copies cannot drift unseen in the meantime.\n\nH1 CONFIRMED and REPRODUCED at base db0cf22, through engine.aggregate on SqlDriver / better-sqlite3 (6-row probe):\n- per-aggregation text vs image counted 6 of 6;\n- number vs multiselect was refused by the per-row array floor when tags held lists (row-dependent), counted 6 of 6 when tags was null, and 0 on an empty table;\n- having on an image groupBy vs a count kept all 6 groups;\n- datetime vs formula counted 0 of 6;\n- each where twin was INVALID_FILTER / 400 with the no-class diagnostic.\nAt be8d2c4 all four are 400 on empty and populated tables, the logged reason is byte-identical to the twin's, and the same-class control is unchanged.\nH3 NO CHANGED ANSWER: verify's checkDateBucketParity calls applyInMemoryAggregation(rows, ast) without fields (read). No in-repo caller outside objectql passes fields (read: dogfood parity tests, service-analytics bucket-key test, driver-mongodb parity test). The verify suite and dogfood are green against rebuilt dists. The one moved answer is #21242's with-field-map pin, which the ruling moves; it is now split: no map is 1 of 4, with a map is refused 400.\nH4 KEPT AND RECORDED. A registry-less host, and an audit-opt-out object's row-carried created_at / updated_at, stay not judged at every engine-side position. Measured on SqlDriver: the audit-opt-out where twin is 400 ('the target field "created_at" is not a declared field'), while the per-aggregation filter counts 6 of 6; this is pinned as the recorded posture. #21336's no-declaration pins are green.\nH5 UNREACHABLE AND PINNED. A multiple:true select / lookup / user (and multiselect, json) is refused INVALID_FIELD / 400 by the groupBy door and by the min / max door before having is read (measured on SqlDriver and in the pin). The only no-class columns that reach having are a file-family groupBy, and a formula groupBy on a path whose driver does not refuse it.\n\nENUMERATION PIN (objectql) sweeps 15x15 ordered pairs at each of three positions: one column per CROSS_FIELD_COMPARISON_TYPE_CLASSES row, plus select multiple:true, plus a type outside FieldType. Each expected answer comes from crossFieldComparisonVerdict itself. Cells:\n- comparable: answered everywhere;\n- cross-class: 400 everywhere;\n- no-class: 400 everywhere. At having, list-or-object is refused earlier by the groupBy door; at the filter, a formula KEY is refused earlier by the materializable door (INVALID_FIELD), as in where;\n- unjudged: unreachable at the engine positions (the registry refuses a type outside FieldType) and not judged at applyInMemoryAggregation;\n- no declaration: not judged; where answers 400.\nIt fails until placed when the spec adds a verdict (the posture Record over the verdict union, plus a runtime set-equality), when the no-class reasons change, when EngineAggregateOptionsSchema gains a filter slot, or when the evaluator modules gain a published export. The dispatch's 'same-class' is the spec's 'comparable'. The REST pin runs one row per verdict (comparable, cross-class, no-class file / list / formula) at all four positions, empty and populated; each answer must equal the where twin's, and the no-class reasons must match the twin's diagnostic verbatim.\n\nDEVIATIONS (stated in the PR body for a claim amendment): (1) packages/rest/src/aggregation-filter-where-doors.test.ts is outside the claim's surface. It is test-only, the same harness and the same reason as #21255's deviation 2: only a real driver-sql refuses the where twin. (2) The no-class answer is judged for addDays pairs too. Before, an addDays pair against a formula was answered at both positions (measured by the ablation). One against a file or list column was refused in the addDays rule's words (read from the source); it now gets the no-class words. This stays within 'no-class references at these positions'.\n\nWRITE AND IDENTITY NOTES. The newest Claim: on #21299 is still 5949513813 and names this branch (re-read after the container restart the seat reported). No PR or report existed before this one. Commit trailers are the model-free pair AGENTS.md requires; the harness reminder's model-named Co-Authored-By was not used (AGENTS.md wins; reported, not a deviation). After pr_create, a path labeler put documentation, size/xl, tests and tooling on the PR. This run did not set them and left them alone. No HTML comment appears in any GitHub text; the changeset's adr-0087 marker is the gate's required repo-file form.\n\nCI on 466e632 at report time: 31 check runs, 12 completed (9 success, 3 skipped), 19 in_progress. Not waited on.",
"tests": "All heavy runs went through scripts/pm/os-verify-lock.sh with OS_VERIFY_LOCK_SLOT=dev-21299, and each verdict is quoted from its VERDICT line. Logs are in the scratchpad issue-21299/ directory.\n\nHEAD PINS. The suites ran at be8d2c4 (the merge, reflog 10:48:52Z; the tree stayed clean and HEAD did not move until 251922e). 251922e only gives the pin file's single-choice columns their options; 466e632 only corrects one changeset sentence.\n\nBUILD: turbo run build --filter='@objectstack/dogfood^...' --filter=@objectstack/rest --filter=@objectstack/verify gave 63 of 63 tasks, command-exit 0. The base build at db0cf22 was command-exit 0.\n\nFULL @objectstack/objectql at be8d2c4: vitest run --project local --maxWorkers=2 gave 365 files, 7381 passed; --project repo gave 1 file, 5 passed. command-exit 0.\nPIN FILES at be8d2c4: objectql engine-aggregate-reference-verdict-positions + engine-aggregate-filter + engine-aggregate-having-comparand-shape gave 313 passed. rest aggregation-filter-where-doors gave 26 passed. command-exit 0. At 251922e the pin file was re-run: 26 passed.\nVERIFY (H3): pnpm --filter @objectstack/verify exec vitest run gave 16 files, 120 passed, command-exit 0.\nDOGFOOD against the rebuilt dists (the objectql dist carries the no-class sentence: 2 hits each in index.mjs and index.js): pnpm --filter @objectstack/dogfood exec vitest run --maxWorkers=2 gave 168 passed + 1 skipped files and 1374 passed + 9 skipped tests, command-exit 0.\nTYPECHECK: pnpm --filter @objectstack/objectql run typecheck exit 0 at be8d2c4 and again at 251922e; its test layer held at 40 files / 234 errors, unchanged, so the new pin file adds none. pnpm --filter @objectstack/rest run typecheck exit 0, test layer 0 errors.\n\nGATES at 466e632: node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstack --commands derived 65. All 65 ran with exit 0, each recorded as 'command :: exit N'. --ran reports '65 derived, 65 run, 0 NOT-MEASURED, 0 UNRUN (a DERIVED zero)'. In the earlier pass at 251922e, check:dual-build-cjs-loads answered PREREQUISITE NOT MET (exit 3, 8 unrelated packages without dist). They were built (41 of 41 from cache), and it exited 0 then and in the final pass. The roster gates under my paths also exited 0: check-changeset-fixed, check:authz-resolver, check:error-code-casing, check:filter-alias-parity. NOT MEASURED (workflow-valued argv, CI runs them): check-issue-citations --census, check-shard-attestation, check-test-completeness. The CI type-check lanes and path-scheduled jobs are CI's.\nLINT, a proven narrowing: pnpm exec eslint --no-inline-config --format json on the 5 changed .ts files gave 5 results, 0 errors, 0 warnings. eslint.config.mjs is not type-aware (no parserOptions.project; header near :328), so the diff cannot move any untouched file's verdict. The full pnpm lint is CI's.\n\nREVERSE VERIFICATION at 623b747 (pre-merge; the seam is identical at HEAD):\n- Mutation: node scripts/ablation-replace.mjs (trap restore on EXIT / INT / TERM, absolute path) replaced only the seam's no-class arm, if (verdict.verdict === 'no-class') return noClassReason(...), with an always-false guard carrying ABLATION_21299. Anchor x1 to x0; blob f4c9c878df05 to eb68be65ef10.\n- Build: objectql rebuilt, exit 0. ablation-dist-preflight found the marker in 4 built files.\n- Predicted: the no-class pins go red and the controls stay green.\n- Observed in objectql: 10 failed / 303 passed (313). The 10 are the three sweeps, the three filter shapes, the having image shape, the two addDays-vs-formula rows and the audit-on created_at vs image control.\n- Observed in rest: 3 failed / 23 passed (26), the no-class file / list / formula rows. Comparable, cross-class, census, no-declaration, multiple-seam and same-class rows stayed green, as did engine-aggregate-filter and engine-aggregate-having-comparand-shape.\n- Restore: the blob equals the HEAD hash, git diff HEAD is empty, a rebuild then --absent preflight shows the marker absent from 14 built files with the tree clean, and git status --porcelain is empty. Re-run: 313 / 26 passed. The direction was as predicted.\n\nBASELINE / AFTER probe on SqlDriver: the table is in the PR body. After = be8d2c4: all four shapes are 400 on empty and populated tables with where's reason logged; the control is unchanged.\n\nRuns lost to the container restart (the first gate pass and a build) were re-run; no reading here comes from a lost run.",
"mcp_calls": "0 — no MCP GitHub tool was called. Reads used single-card REST via gh api: issue #21299 and its comments, comments 5944459558 / 5944798311 / 5944780154, PR #21336, PR #21406 read-back, check-runs on 466e632.",
"api_writes": "3 relay writes as objectstack-fleet[bot], plus git pushes of claude/issue-21299-having-no-class-refusal (several pushes; git, not REST). (1) pr_create: POST /repos/objectstack-ai/objectstack/pulls (draft, #21406) via scripts/pm/with-fleet.sh --via dispatch, relay run 37007562124; read-back says 16304 bytes sent, 16304 stored, identical. (2) scripts/pm/label-write.mjs --issue 21406 --assign huangyiirene: POST /repos//issues/21406/assignees, relay run 37007640707; read-back matches. (3) This os-dev-report comment: POST /repos//issues/21299/comments via scripts/pm/post-stamped.mjs. No other write.",
"open_questions": [
{
"question": "Where should driver-sql's no-class sentence ('"X" (type "T") has no scalar stored column a comparison can read.') live, so that where and the engine positions (having, aggregations[i].filter, applyInMemoryAggregation) print one copy? H2 measured that no importable source exists. The dispatch forbids a third copy and requires a stop before a spec edit, so PR #21406 carries a PENDING objectql-local copy (noClassReason) and must not land until this is answered.",
"options": [
"A: a pure function in packages/spec beside the verdict (filter-cross-field-comparison-class.ts), from a column's name and declaration to the sentence. driver-sql replaces its two inline copies with it and objectql imports it. Cost: a spec edit (api-surface regeneration plus a spec changeset) and a driver-sql edit outside this claim, with byte-identical words (driver-sql's conformance cases pin 'no scalar stored').",
"B: an export in @objectstack/core, as jsonColumnOperatorRefusalText is for the JSON-column rule; driver-sql and objectql import it. Cost: a core export and a driver-sql edit. @objectstack/formula cannot read core (it depends on spec alone), so the RLS write check stays on its own wording for good.",
"C: keep objectql's copy, as crossClassReason is for the cross-class sentence, with the REST twin pin as the drift guard. Cost: nothing now, but it is the third copy the dispatch forbids, and the guard covers only driver-sql against objectql."
],
"recommendation": "A, on the four axes. (Real business need, measured) examples/** at 466e632 hold 0 having clauses and 0 $field references, so no in-repo producer pulls this. The sentence's only readers are authors who meet the refusal. Today one verdict reaches them in three wordings (driver-sql's, formula's describeColumn, lint's), plus this PR's copy. The need is consistency at the refusal, not a new capability. (Long-term soundness) The spec module's header says it is 'the one definition every judge reads'. A sentence beside the verdict follows the numberComparandRefusalMessage precedent (spec, beside its verdict), and spec is the only home all four judges can import. B strands formula; C leaves drift to a pin. (Preventing AI mistakes) One verdict and one sentence at every door means an AI that meets the refusal at where, having, the per-aggregation filter or the write check learns one rule from one text. C keeps a second hand-maintained copy, which is exactly where silent divergence starts. (Startup focus) A adds no authorable surface and no gate: one pure export plus two call-site swaps (driver-sql, objectql). Converging the formula and lint wordings is NOT proposed here, because nothing pulls it. Trade-off: A is the most files and touches two packages outside this claim; if the seat wants the smallest landing now, C is the honest second choice, stated as an accepted exception to the no-third-copy line."
}
],
"out_of_scope_findings": [
"carrier: 承接者:无 · noted, not filed. A having refusal message exceeds the REST envelope's 500-character bound, so the wire cuts its closing clause about how a column's class is read. The no-class reason sits in the surviving prefix, and the REST pin asserts it on the wire. This predates the PR (#21255's acceptance note) and is recorded in the PR's Acceptance notes.",
"carrier: 承接者:无 · noted, not filed. The unjudged verdict (a declared type outside FieldType) is unreachable at the engine positions, because the registry refuses the whole object. Only a direct applyInMemoryAggregation host can reach it, and there it is not judged; driver-sql's where judges such a type by its own aliases instead. Recorded as a pin row. It is not a defect: no producer exists, since FieldSchema refuses the type at authoring."
]
}

---

Generated by Claude Code