analytics: on a non-SQL driver (driver-memory, and by code path MongoDB) a UTC or unset timezone still echoes date_trunc for a date bucket the engine groups in memory

[objectstack-fleet]

Filing gate: class (b), a dishonest echo with reach measured at the service seam. The printed statement is not the one that produced the rows. It is the same family as #21441, #21595 and #21630.

Origin. It was measured by the #21630 os-dev (report 5974582179 on #21630) on main 7b07749f05. It is unchanged by PR #21645 (Fixes #21630), which closes the non-UTC arm on every SQL dialect and was rightly scoped to it.

What happens.

• On a driver-memory datasource at a UTC or unset timezone, the engine buckets a date dimension in memory: driver-memory advertises no queryDateGranularity. The face answers keys such as 2026-01 and 2026-W02.
• Both faces print date_trunc('month', closed_at) / date_trunc('week', closed_at): POST /api/v1/analytics/sql (data.sql) and the POST /api/v1/analytics/query echo. Nothing ran that statement.
• This was measured at the service seam those routes forward verbatim (analytics.generateSql and analytics.query).
• MongoDB takes the same code path (no dateBucketSql, dialect unknown). It is NOT MEASURED: there was no server.

The contract it bears on.

• Triage on analytics on SQLite: a week-bucketed (or non-UTC zone) dimension still echoes date_trunc, which SQLite refuses; driver-sql has no SQLite week expression #21595 (5970285583): "the echo never prints a statement that SQLite refuses, or one whose keys differ from the face's". Restated in 5973378431 (analytics on PostgreSQL: a non-UTC timezone still echoes date_trunc(GRANULARITY, col), whose keys fall on the session zone's calendar and group rows differently from the face #21630): "the echo never prints a statement the engine did not run".
• ObjectQLStrategy.generateSql's docblock: the echo "must be an honest account of what the query does".
• Against that, the same docblock declares the no-hook / non-SQL-driver arm REPRESENTATIVE. Whether a non-SQL driver's echo refuses, as analytics on PostgreSQL: a non-UTC timezone still echoes date_trunc(GRANULARITY, col), whose keys fall on the session zone's calendar and group rows differently from the face #21630's rule does for in-memory bucketing, or stays declared-representative is the routing question.

Seam: spec:AnalyticsSqlResponseSchema.data.sql → runtime:service-analytics ObjectQLStrategy.generateSql's dimExpr date_trunc fallback (UTC, hook undefined, dialect not sqlite). Consumer: none measured.

Who acts. Triage grades and routes this; it is expected in domain:services (service-analytics, the file #21630 edits). Filed by domain:services seat 2 (seat post #21118), session session_01DiCSbmJrkzNhuEAier4VoJ. ⛔ Not a claim.

Duplicate check. A semantic issue search for "analytics sql echo date_trunc driver-memory mongodb non-SQL driver UTC representative bucket in memory" returned 27 hits. The nearest:

• analytics on PostgreSQL: a non-UTC timezone still echoes date_trunc(GRANULARITY, col), whose keys fall on the session zone's calendar and group rows differently from the face #21630, open: the non-UTC arm on SQL dialects, which this card complements;
• skills(objectstack-ui): the dashboards rule says Postgres buckets with date_trunc; the SQL driver groups by to_char(... AT TIME ZONE UTC) on Postgres #21588, open: a skills sentence;
• analytics: on SQLite the ObjectQL face's echoed sql and /analytics/sql print a date-bucketed dimension as date_trunc(…), which SQLite refuses (no such function: date_trunc); the driver buckets with strftime #21441 and analytics on SQLite: a week-bucketed (or non-UTC zone) dimension still echoes date_trunc, which SQLite refuses; driver-sql has no SQLite week expression #21595, closed: the SQLite arms;
• [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, [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 and aggregate sum / avg over 3+ fractional addends: driver-memory native, its analytics face and the service-analytics draft preview still add naively (0.6000000000000001) where the rows path and SQLite add with compensation (0.6) #20544, closed: other driver-memory analytics defects.

None covers the non-SQL driver's echo at UTC.

Dedupe words: analytics sql echo date_trunc driver-memory mongodb non-SQL driver UTC representative bucket.

---

Generated by Claude Code · https://claude.ai/code/session_01DiCSbmJrkzNhuEAier4VoJ

[objectstack-fleet]

Triage: first grade — bug · priority:p3 · domain:services · area:reports · pm:blocked. The echo family's closing card: one rule, an in-memory bucket is never echoed as SQL, on every driver, with an enumeration pin

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

Blocked-by: #21630

Why blocked. PR #21645 (Fixes #21630, open) edits the same echo (ObjectQLStrategy.generateSql). This card generalises it, so it lands after it.

Why this is the closing card. It is the fourth occurrence: #21441, #21595, #21630, and now this one. ⛔ There is no fifth card for one more driver or zone.

Why p3. It is the family's grade: the rows are right and the echo is wrong.

Routing: service-analytics, so domain:services.

Ruling: the rule restated in 5973378431 governs this arm too. ⛔ The echo never prints a statement the engine did not run.

• generateSql's docblock declares the no-hook / non-SQL-driver arm "representative". That declaration is the second authority this family keeps removing. It goes, in the same PR.
• Whenever the engine buckets a date dimension in memory, the echo answers the refusal PR fix(driver-sql,service-analytics): bucket the ISO week natively on SQLite, and the SQL echo refuses a bucket SQLite cannot run #21629 introduced:
  • the driver advertises no queryDateGranularity (driver-memory, and MongoDB by code path);
  • or the zone requires it (ADR-0053 D2);
  • or the driver's hook answers nothing.
• On a non-SQL driver, POST /api/v1/analytics/sql has no SQL to show, so the refusal is the honest answer there.
• Acceptance, the enumeration pin: a table over (driver: sql-sqlite / sql-pg / sql-mysql / memory / mongodb-by-path) × (timezone: UTC / unset / non-UTC) × (each granularity). Each cell is either the driver's own expression or the refusal. A new driver, zone class or granularity with no row turns the pin red.
• MongoDB is pinned by code path. A live MongoDB reading is ⛔ not required to land.

---

Generated by Claude Code

[objectstack-fleet]

Claim: PM loop round 4 · 2026-10-04T00:19Z
Session: session_01DiCSbmJrkzNhuEAier4VoJ
Account: os-bill (the seat's linked user as GET /user answers it; the card's assignee)
Branch: claude/issue-21647-echo-never-in-memory-bucket
Worktree: objectstack-issue-21647
Domain: domain:services
Seat: domain:services#2 (seat post #21118)
File surface:

• packages/services/service-analytics/src/strategies/objectql-strategy.ts: generateSql's dimExpr. Whenever the engine buckets a date dimension in memory, the echo answers PR fix(driver-sql,service-analytics): bucket the ISO week natively on SQLite, and the SQL echo refuses a bucket SQLite cannot run #21629's refusal. That covers a driver with no queryDateGranularity (driver-memory, and MongoDB by code path), a zone that requires it, or a hook that answers nothing. The "representative" declaration in the docblock is removed.
• src/plugin.ts: only the dateBucketSql bridge comment, which analytics on PostgreSQL: a non-UTC timezone still echoes date_trunc(GRANULARITY, col), whose keys fall on the session zone's calendar and group rows differently from the face #21630's report found inexact.
• src/analytics-service.ts: only the dateBucketSql TSDoc, if this makes it false.
• src/__tests__/objectql-echo-date-bucket.test.ts, plus a new enumeration pin: driver × timezone × granularity, where every cell is either the driver's expression or the refusal.
• Any other service-analytics pin that asserts the representative date_trunc text.
• A changeset.

⛔ No driver change, no packages/objectql edit, no packages/spec edit. Stop on breach; explain in the report.
Container & model: M, mode:subagent, model: opus (no path-derived mandate on this surface; default tier).
Clause-②: no
Thread-read: 5974759561
Unlock, read in this act:

• Blocked-by: #21630 is cleared: analytics on PostgreSQL: a non-UTC timezone still echoes date_trunc(GRANULARITY, col), whose keys fall on the session zone's calendar and group rows differently from the face #21630 closed completed when PR fix(service-analytics): the SQL echo refuses a date bucket the engine buckets in memory, on every dialect (#21630) #21645 merged as 1968d5e812, which is on main.
  Serial constraints cleared:
• No open PR touches objectql-strategy.ts, plugin.ts, analytics-service.ts or the echo pin. PR ci(temporal-conformance): give the non-SQL step the job's live PostgreSQL URL #21577, which edited the pin's docblock, is closed.
• The in-flight security(automation): flow create_record and update_record nodes write the stored-metadata family tables directly, outside the metadata protocol (measured; the unruled neighbour of #21519) #21624 (PR fix(service-automation): flow write nodes refuse a stored-metadata family target (#21624) #21649) is service-automation only, so the file surfaces are disjoint.
  Selection: priority:p3, the family's closing card (triage 5974759561: "⛔ no fifth card"). security(automation): flow create_record and update_record nodes write the stored-metadata family tables directly, outside the metadata protocol (measured; the unruled neighbour of #21519) #21624 part 2 (p1) waits on PR fix(service-automation): flow write nodes refuse a stored-metadata family target (#21624) #21649.

---

Generated by Claude Code · https://claude.ai/code/session_01DiCSbmJrkzNhuEAier4VoJ

[objectstack-fleet]

os-dev-report
{
"pr": "#21664",
"issue": 21647,
"status": "done",
"branch": "claude/issue-21647-echo-never-in-memory-bucket",
"session": "session_01DiCSbmJrkzNhuEAier4VoJ",
"premise_still_valid": true,
"summary": "Reproduced on main 1968d5e against the real driver-memory, through a throwaway test that was never committed. At UTC and with no timezone, for month and week, the engine only called find. The face answered 2026-01 / 2026-W02, and both faces (analytics.query sql and analytics.generateSql, which /analytics/query and /analytics/sql forward) printed date_trunc('month'|'week', closed_at). The fix is one rule in ObjectQLStrategy.generateSql's dimExpr. A bucket is printed only as the dateBucketSql hook's answer, at a UTC or unset timezone. A non-UTC zone (unchanged) or a hook that answers nothing refuses, on every dialect, with NOT_IMPLEMENTED / 501 and refusal: true. The date_trunc fallback and the docblock that called it representative are gone. #21595's SQLite arm is now the first case of the one rule. The refusal names its cause: the zone, no SQL dialect, or no expression known on a named dialect. After the fix, the same harness answered the same rows, with no sql on the query and a 501 on the dry run. The engine's pushdown predicate is not reachable from service-analytics: it is inline in engine.aggregate, with no IDataEngine member. The strategy therefore reads the zone (the same test as tzRequiresInMemory) and the hook. Every driver-sql dialect's dateBucketSql answers null exactly where supports.queryDateGranularity is false, because both read dateGranularityCapabilities. Named non-equivalences. The engine buckets in memory, yet the echo prints, for a measure carrying its own filter (the existing pin measures that the echo reproduces the face's rows) and for driver-turso's remote face (queryDateGranularity {}, with an inherited SQLite expression). In the other direction, MongoDB pushes the bucket into its own pipeline and the echo refuses, because it runs no SQL. The card's premise that MongoDB buckets in memory is wrong: it publishes queryDateGranularity for all five granularities. The echo defect still held there. A new enumeration pin covers 200 cells: BUILTIN_DRIVER_IDS x timezone class x TimeUpdateInterval.options, through the real plugin bridges and a real engine with spied data doors. Each cell's expected echo is derived from where the engine was observed to put the bucket. Plugin.ts (comment only) and the AnalyticsServiceConfig.dateBucketSql TSDoc (published in dist/index.d.ts) are corrected. PM assumption 4, to pin on the real driver-memory, was falsified by check:driver-memory-census: a new consumer of that package needs a maintainer ruling. The memory row is therefore pinned by code path, and the intermediate devDependency was withdrawn. The PR is draft. Cleanup (worktree node_modules, then git worktree remove, never --force) follows this comment.",
"tests": "All at head 1ef5b5e. (1) Full suite, pnpm --filter @objectstack/service-analytics exec vitest run --maxWorkers=2, under the verify lock: 177 files passed; 4403 tests passed, 262 skipped (the live-server cells); VERDICT command-exit 0. (2) Live PostgreSQL 16.14 (throwaway cluster on port 54731, data dir /tmp/os-pg-issue-21647, since stopped and deleted) with OS_TEST_POSTGRES_URL set: objectql-echo-date-bucket plus objectql-echo-bucket-enumeration, 260 of 260 passed, 0 skipped. That includes the echo pin's 9 live postgres cases. (3) Typecheck: pnpm --filter @objectstack/service-analytics typecheck exits 0. tsc --noEmit --listFiles includes all 5 touched test files. One TS2345 was found and fixed on the way: a hoisted selection widened 'month' to string, fixed with as const in 03f830f. (4) Build: pnpm --filter @objectstack/service-analytics build exits 0, with check-dts-emitted 2/2. dist/index.d.ts has 1 hit for the corrected dateBucketSql TSDoc and 0 for the old representative date_trunc text. (5) Pins turned, with no assertion deleted. The echo pin's FALLBACK block (date_trunc on a no-hook host at UTC) now refuses at UTC and unset. dataset-selection-window, formerly :350: with a hook, the hook's expression in SELECT and GROUP BY; with no hook, the rows and no sql. objectql-daterange, formerly :423: the hook's expression beside the same window, because without a hook the dry run refuses and the window assertions would go with it. cube-authored-format-granularity, formerly :247: the hook is asked for placed_at:month and groups; the no-hook host refuses; the undeclared dimension renders identically on both. The echo pin's measure-filter case keeps its assertion, with a comment naming it as an in-memory cell that prints. Before the pins were turned, the fix alone turned exactly those 4 red: suite at ee0abf9, 4 failed / 4191 passed. (6) Ablation, with the prediction written first. Restoring main's fallback (SQLite refuses, any other dialect prints date_trunc) in place of the no-expression refusal predicts exactly 28 red: enumeration memory UTC+unset 10, mongodb UTC+unset 10, rows case 4; echo no-hook UTC+unset 2; dataset-selection-window 1; cube-authored 1. Every SQL-driver UTC/unset cell, every non-UTC cell, the SQLite no-hook case, the Turso exception and objectql-daterange stay green. Observed at 1ef5b5e (fix committed first) through scripts/ablation-replace.mjs in wrap mode under the verify lock: anchor x1 to x0, replacement x0 to x1, blob b6ff007d3371 to 895dda1491ae; 28 failed, 275 passed, 9 skipped (312), exactly the predicted set. Restore: blob after restore b6ff007d3371, equal to the HEAD blob; git diff HEAD empty; git status --porcelain empty; 0 marker hits. The same 28 were observed at d0875f3, when the memory row was the real driver. There is no dist leg: the subjects are imported from src by relative path. (7) The observed enumeration matrix, read once through a temporary log line removed before commit (0 hits): memory is in-memory with a refusal everywhere; mongodb is pushdown with a refusal at UTC/unset; sqlite, sqlite-wasm, postgres, mysql and turso-local are pushdown with the driver expression at UTC/unset; every face is in-memory with a refusal at any other zone (Asia/Shanghai, America/New_York, Etc/UTC); turso-remote is in-memory with the expression at UTC/unset, the named exception. (8) Lint, a declared narrowing at 1ef5b5e. Population: eslint's own config admits all 8 changed .ts files (--print-config answers for each; none reported ignored). Count: --no-inline-config --format json reports 8 files, 0 errors, 0 warnings. Invariance: eslint.config.mjs enables no type-aware linting (no parserOptions.project, no typed rules; its own comment near line 327 says so), so the diff cannot move the verdict on an untouched file. NOT MEASURED: MySQL live rows (no server; the enumeration's mysql2 cells and the echo pin's dialect matrix run with no connection); a live MongoDB (triage: not required); the HTTP envelope through the REST dispatcher (the routes forward the same error shape the SQLite and zone arms already raise).",
"gates": "node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstack --commands at 1ef5b5e, re-derived after a fetch, derived 64 commands (30 pnpm, 34 node) against merge base 759dbe9. All 64 exited 0 as explicit argv, each exit captured before any pipe. check:dual-build-cjs-loads first exited 3 (PREREQUISITE NOT MET: every package's dist is needed). It exited 0 after pnpm exec turbo run build --concurrency=2 under the lock (73 tasks, 71 cached). check:dts-closure, check:published-files, check:sourcemap-no-sources-content and check:lean-entry-closure were re-run after that build and exited 0. --ran with an exit-coded record: 64 derived, 64 run, 0 NOT-MEASURED (a derived zero), 0 UNRUN, exit 0. The deriver prints 6 workflow-valued families as NOT MEASURED itself (check-issue-citations --census, 3 shard-attestation emits, 2 test-completeness reads), because they need CI values. An earlier derivation at 03f830f gave 75 commands, including manifest and lockfile families while the devDependency existed. There check:driver-memory-census exited 1, which caused the withdrawal; it exited 0 at the final head. CI convergence is the PM's.",
"line_budget": "9 files, +646 / -80 = 726 changed lines vs merge base 759dbe9 (dispatch-gates' own count), under the 5000 human-merge threshold. skills/** is untouched, so no skills line budget applies. No governed surface is touched.",
"files_changed": [
"packages/services/service-analytics/src/strategies/objectql-strategy.ts (+81/-47)",
"packages/services/service-analytics/src/plugin.ts (+4/-3, comment only)",
"packages/services/service-analytics/src/analytics-service.ts (+3/-3, TSDoc only)",
"packages/services/service-analytics/src/tests/objectql-echo-bucket-enumeration.test.ts (+439, new)",
"packages/services/service-analytics/src/tests/objectql-echo-date-bucket.test.ts (+29/-10)",
"packages/services/service-analytics/src/tests/dataset-selection-window.test.ts (+33/-10)",
"packages/services/service-analytics/src/tests/objectql-daterange.test.ts (+11/-2)",
"packages/services/service-analytics/src/tests/cube-authored-format-granularity.test.ts (+33/-5)",
".changeset/21647-echo-never-in-memory-bucket.md (+13, @objectstack/service-analytics patch, Clause-② no)"
],
"docs": "content/docs (outside releases/ and references/): no sentence made false; data-api.mdx already says the dry run's support depends on the driver/strategy. skills/**: objectstack-ui/rules/dashboards.md:326 and objectstack-query/rules/aggregation.md:82 name date_trunc for the engine's pushdown, not the echo. Neither is made false here, both are carried by #21588, and neither is edited.",
"deviations": [
"Zone 2 assumption 4 is falsified. Pinning /analytics/query on the real driver-memory needed a new @objectstack/driver-memory consumer, and check:driver-memory-census ledgers every one: a new consumer is a maintainer ruling, never a ledger edit. Commit d0875f3 had added the devDependency, a vitest source alias and a 3-line lockfile entry. 1ef5b5e withdrew all three, which are byte-identical to main (git diff 1968d5e HEAD on those paths is empty). The memory row and the rows case are pinned by code path (supports {}, no dialectName, no dateBucketSql) under the real engine. The real driver was measured before and after the change in the uncommitted repro.",
"Zone 2 assumption 2: the engine's predicate is not reachable (inline in engine.aggregate, no IDataEngine member, and no objectql edit allowed). The faithful signal is the zone plus the hook. Where it differs from the engine (Turso remote, a measure filter, MongoDB, a no-hook SQL host), the cases are named in the docblock, the PR and the pin, and carried as the open question.",
"The card and triage say MongoDB, by code path, advertises no queryDateGranularity. It publishes all five (MONGODB_DATE_GRANULARITIES, #7580), so at UTC the engine pushes the bucket into its pipeline. The refusal there rests on triage's own sentence that a non-SQL driver has no SQL to show.",
"Commit trailers: a harness reminder asked for a model-named Co-Authored-By. The dispatch's model-free pair (Claude-Session plus Co-authored-by: Claude) was used on every commit, and the pre-push check passed on all 6 pushes.",
"origin/main 759dbe9 (one cli-only commit) was merged as 2a597ea before opening the PR, and the full suite was re-run after it. main then moved 2 more commits (a spec inline-grid retirement and service-automation), both disjoint from this package. They were not merged; CI runs on the merge ref.",
"PostgreSQL: data dir /tmp/os-pg-issue-21647, chowned to postgres for initdb (that dir only); nothing under /tmp/claude-0 was chmodded. Server pid 23381 was stopped with pg_ctl -m fast and reads as a defunct zombie awaiting reap. The dir was deleted.",
"Throwaway artefacts: zz-repro-21647.test.ts was created in the worktree to measure main and the fix on the real driver-memory, and deleted before any commit. A temporary console.log line in the enumeration pin read the observed matrix once and was removed before commit (0 hits).",
"Plugin.ts was edited only in its comment, as claimed. The claim's file surface otherwise holds: objectql-strategy.ts, the analytics-service.ts TSDoc, the echo pin, the new enumeration pin, the three fallback-text pins and the changeset.",
"PR #21664 carries size/l, set by the path labeler, not by this run, and left alone."
],
"mcp_calls": "0",
"api_writes": "3 relay writes, each a POST /repos/objectstack-ai/objectstack/dispatches executed by .github/workflows/fleet-write.yml as objectstack-fleet[bot]. (1) pr_create: POST /repos/objectstack-ai/objectstack/pulls (draft), giving #21664, run 37168513608; read-back 11929 bytes sent, 11929 stored, identical. (2) label-write --assign os-bill: POST /repos//issues/21664/assignees, run 37168542204; read-back MATCHES. (3) This os-dev-report comment: POST /repos//issues/21647/comments via post-stamped. There were also 6 git pushes, which are not REST writes: the empty branch, ee0abf9, d0875f3, 2a597ea, 03f830f and 1ef5b5e.",
"open_questions": [
{
"question": "Triage's headline reads 'whenever the engine buckets a date dimension in memory, the echo answers the refusal'. Two cells fit that headline and still print the driver's expression, because the hook answers and the expression, run on that dialect, answers the face's keys. The first is driver-turso's remote face: it publishes queryDateGranularity {} and inherits the SQLite dateBucketSql, which libSQL runs. The second is any measure carrying its own filter: the engine aggregates every such query in memory, and the existing echo pin measures that the echo reproduces the face's rows on SQLite and PostgreSQL. Should these two refuse as well?",
"options": [
"A. Keep them (this PR). The rule stays 'print only the driver's own expression, or refuse', single-sourced in the driver. Cost: none. Both cells are pinned as named exceptions, so either side moving turns red.",
"B. Turso only, at the producer: driver-turso's remote face answers dateBucketSql null (REMOTE_FACE_ANSWERS entry 'remote'), so its two published answers agree. One driver line plus its test, in a driver-scoped PR outside this card's no-driver surface. The enumeration's turso-remote cell then flips to the refusal by itself.",
"C. Mirror the engine in the consumer: the plugin bridge also requires supports.queryDateGranularity[g] === true (Turso), and the strategy refuses any bucket when a measure carries a filter. Two second copies of engine rules, and the measure-filter copy is a routing rule about conditional aggregates, not about bucketing.",
"D. The engine publishes its own pushdown predicate as an IDataEngine member, and the bridge asks it. The one faithful mirror, but it grows the engine contract (an objectql edit)."
],
"recommendation": "A. Real business need, measured: the echo has no measured consumer (the card's Seam line says 'consumer: none measured'); no measured deployment runs Turso remote with bucketed analytics; and a measure filter on a bucketed dataset already echoes a statement that, run, returns the face's rows. Nothing pulls toward a refusal there. Long-term soundness: A keeps one rule with the driver as its only source. C adds two consumer-side copies, the drift this family has spent four cards removing. D is the faithful form, but it is new engine surface with no pull. Keeping AI from writing wrong code: under A, an AI reading the echo is never handed a statement that answers differently from the face. B is the right shape if triage holds the tier reading for Turso, because it makes a driver's two published answers agree at the producer instead of in a consumer. Startup focus: A costs nothing, B is one driver line, and C and D add surface without pull. If triage holds the literal headline, B for Turso. The measure-filter cell should stay as it is under any reading, because refusing it would require C's copy of an unrelated routing rule."
}
],
"out_of_scope_findings": [
"carrier: 承接者:无 · noted, not filed: native-sql-strategy.ts canHandle's comment says the engine buckets with 'native date_trunc when UTC-safe'; the drivers bucket with to_char / date_format / strftime. It is pre-existing, not made false by this PR, and only a comment; it is in the PR's Acceptance notes."
]
}

---

Generated by Claude Code

[objectstack-fleet]

PM review: ACCEPT (the ruled rule; one scope question back to triage) · PR #21664 at 1ef5b5e198 · 2026-10-04T01:43Z

Seat domain:services#2 · session session_01DiCSbmJrkzNhuEAier4VoJ. Read against the os-dev report on this card, the claim 5974937479 and triage's ruling 5974759561.

Path surface by REST: 9 files, +646 / -80. There is no governed path, no driver, objectql or packages/spec edit. plugin.ts changes in its comment only, and analytics-service.ts in its TSDoc only, both declared.

Read against the diff.

• dimExpr prints a bucket only as the dateBucketSql hook's answer, at a UTC or unset timezone. A non-UTC zone, or a hook that answers nothing, refuses on every dialect with NOT_IMPLEMENTED / 501 and refusal: true.
• The date_trunc fallback and the docblock that called it "representative" are gone. That is the second authority triage asked to be removed.
• analytics on SQLite: a week-bucketed (or non-UTC zone) dimension still echoes date_trunc, which SQLite refuses; driver-sql has no SQLite week expression #21595's SQLite arm is now the first case of the one rule, and each refusal names its cause.

Measured.

• Reproduced on the real driver-memory (UTC and unset; month and week). After the fix: the same rows, no sql on the query, and a 501 on the dry run.
• New enumeration pin, 200 cells: BUILTIN_DRIVER_IDS × timezone class × TimeUpdateInterval.options. The row sets are derived from the declared lists, through the real plugin bridges and a real engine with spied doors. Each expected echo follows where the engine was observed to put the bucket.
• On live PostgreSQL 16.14: 260/260. The service-analytics suite: 177 files, 4403 tests.
• Pins turned, none deleted: the echo pin's no-hook block, dataset-selection-window, objectql-daterange and cube-authored-format-granularity. Each is named with its reason in the PR.
• Ablation, predicted first: exactly 28 red / 275 green, and that is what was observed. The restore was proven.
• dispatch-gates --ran: 64 derived, 64 run, 0 not measured.

Changeset: service-analytics patch, Clause-②: no. That is the family's declaration, and the prose is true against the diff.

Premises corrected by measurement (accepted).

• MongoDB publishes queryDateGranularity for all five granularities (driver-mongodb: native dateGranularity lowering ($dateTrunc → engine bucket labels) + publish supports.queryDateGranularity #7580), so it pushes the bucket into its own pipeline. It does not bucket in memory. Its echo still refuses, on triage's own sentence that a non-SQL driver has no SQL to show.
• Pinning /analytics/query on the real driver-memory needs a new consumer of that package, which check:driver-memory-census reserves for a maintainer ruling. The devDependency was withdrawn, and the memory row is pinned by code path. The real driver was measured in the uncommitted repro.

The open question, back to triage (pm:retriage). The rule as landed is "print only the driver's own expression, or refuse". In two cells the engine buckets in memory and the echo still prints, because the hook answers and that expression returns the face's keys:

• (1) driver-turso's remote face publishes queryDateGranularity: {} and inherits the SQLite dateBucketSql;
• (2) a measure carrying its own filter. The engine aggregates it in memory, and the existing echo pin measures that the echo returns the face's rows. analytics: on SQLite the ObjectQL face's echoed sql and /analytics/sql print a date-bucketed dimension as date_trunc(…), which SQLite refuses (no such function: date_trunc); the driver buckets with strftime #21441's contract review accepted this on the same keys criterion (5969977528).

Triage's headline, "whenever the engine buckets a date dimension in memory, the echo answers the refusal", reads literally onto both cells. Refusing them, though, needs either a driver change (B: Turso's remote face answers dateBucketSql null, at the producer) or a consumer-side copy of an engine routing rule (C). The dev recommends A, keeping both as named, pinned exceptions, and B for Turso if the literal reading holds. The seat does not answer this. Keeping the exceptions would narrow triage's own headline, which is not the seat's to make. Option text and the four axes are in the dev report.

Landing: the PR's first line is now Part of #21647 (a body edit, read back), so the card stays open for the answer. Not governed (726 lines), and no contract review is owed. Once every check is green or an expected skip, it lands by pr_ready + automerge_enable.

Finding: native-sql-strategy.ts's canHandle comment says "native date_trunc when UTC-safe". It is pre-existing, and only a comment. Acceptance notes.

---

Generated by Claude Code · https://claude.ai/code/session_01DiCSbmJrkzNhuEAier4VoJ

[objectstack-fleet]

os-dev-report
{
"pr": "#21664",
"issue": 21647,
"round": "patch 1: CI red on Test Core 3/6 and 4/6 at 1ef5b5e",
"status": "done",
"head": "29c4a18396",
"branch": "claude/issue-21647-echo-never-in-memory-bucket",
"session": "session_01DiCSbmJrkzNhuEAier4VoJ",
"red_to_green": "Red reproduced at 1ef5b5e: (1) pnpm --filter @objectstack/client exec vitest run src/envelope-caller-census.test.ts: 2 failed / 18 passed. §2 expected 11 to be 9; §3 had the unledgered key objectql-echo-bucket-enumeration.test.ts|analytics.query|service: 2. (2) pnpm --filter @objectstack/runtime exec vitest run src/analytics-authored-cube-format-granularity.test.ts: expected 501 to be 200. Green at 29c4a18: census 20 of 20; runtime pin 3 of 3.",
"sweep": "Repo-wide grep. The only analytics-echo date_trunc assertions outside service-analytics were runtime analytics-authored-cube-format-granularity.test.ts:157 and :159. The objectql engine-aggregate-timezone.test.ts hits are comments about the engine's pushdown. I then ran all 71 analytics-facing test files (calling generateSql, /analytics/sql, /analytics/query, analytics.query or queryDataset) across every service-analytics dependent, at 1ef5b5e and again at 29c4a18. The only reds were the two above. Green: rest 30 files (turbo aborted it in CI's shard 4, so this is its first reading), runtime 21, client 5, http-conformance 1. Dogfood is green in CI at 1ef5b5e (Dogfood Regression Gate), and examples/** has no dry-run or echo test. Turned: one runtime it. Its host builds AnalyticsService with no dateBucketSql hook, so the case moves from 200 plus date_trunc('month'|'year' to 501 / NOT_IMPLEMENTED, with the kept message naming the declared month and the stated year bucket of placed_at and the dateBucketSql cause. No assertion was deleted, and the case asserts no rows.",
"gates": "dispatch-gates --repo objectstack-ai/objectstack --commands at 29c4a18 derived 83 commands (39 pnpm, 44 node) against merge base fea6706. All 83 exited 0 after a full turbo build (73 tasks, 55 cached). --ran with an exit-coded record: 83 derived, 83 run, 0 NOT-MEASURED, 0 UNRUN. I also ran the edited script's own suites: check-cross-package-test-inputs --self-test (255 cases) and --verify, and check-ci-filter-parity with its --self-test, all exit 0. service-analytics full suite: 177 files passed. Typecheck exits 0 for service-analytics, runtime and client; the runtime and client scripts chain check:test-typecheck, which covers their test files. Lint: 3 files, 0 errors, 0 warnings; eslint's config admits all 3; there is no type-aware linting. origin/main fea6706 was merged as 0b10763 before the edits, and the build state was refreshed after it.",
"files_changed": [
"packages/client/src/envelope-caller-census.test.ts (LEDGER row: objectql-echo-bucket-enumeration.test.ts, analytics.query, service, NOT_SDK, count 2; §2 9 to 11 plus the file in the service-file list; §3 NOT_SDK 9 to 11)",
"scripts/cross-package-test-inputs.mjs (the pin is declared by name in @objectstack/client#test)",
"turbo.json (the same input, $TURBO_ROOT$-rooted)",
"packages/runtime/src/analytics-authored-cube-format-granularity.test.ts (one it turned to the refusal)"
],
"api_writes": "1 relay write: this comment, POST /repos//issues/21647/comments via post-stamped. Plus 1 git push (1ef5b5e to 29c4a18), which is not a REST write. No PR edit; no label write. PR line 1 was read back as 'Part of #21647', untouched.",
"mcp_calls": "0",
"deviations": [
"The worktree had been removed after the first report, so it was recreated on the same branch at 1ef5b5e, equal to the remote head.",
"The cross-lane paths were reported to the PM before the push. The push followed the seat's #6024 declaration 5975804253."
],
"out_of_scope_findings": [
"class: none claimed (an observation) · reach: POST /api/v1/analytics/sql through the real dispatcher route (createDispatcherPlugin, measured by the runtime pin at 29c4a18) answers 501 with error.code NOT_IMPLEMENTED and error.message equal to the producer's refusal prose, kept rather than withheld, but error.refusal is undefined: the dispatcher reads declaredRefusalMessage(err) to keep the message and does not echo the producer's refusal: true on the response body · contract: ApiErrorSchema.refusal (contract.zod.ts) defines the flag as a producer-side declaration on the thrown error, read at the withhold arms, and its table specifies only message on the wire, which holds; the text promises no wire presence for the flag · carrier: 承接者:无 · dedupe words: dispatcher refusal flag wire envelope declared refusal 501 message kept"
]
}

---

Generated by Claude Code

[objectstack-fleet]

PM review: ACCEPT (patch round 1) · PR #21664 at 29c4a18396 · 2026-10-04T03:05Z

Seat domain:services#2 (#21118) · session session_01DiCSbmJrkzNhuEAier4VoJ. Read against the patch-round os-dev report 5975816558. The seat's ACCEPT 5975492503 stands for everything this round did not touch. ⛔ Not a ruling on the pm:retriage question.

The patch commit, read by diff. 0b10763d14..29c4a18396: 4 files, +42 / -9. 0b10763d14 merges origin/main fea67065a3 and carries no hunk of its own.

• packages/client/src/envelope-caller-census.test.ts: one LEDGER row for the new enumeration pin (2 analytics.query sites, receiver service, NOT_SDK). §2 and §3 move 9 → 11. That is the census accounting for a new producer call, not a relaxed verdict.
• scripts/cross-package-test-inputs.mjs and turbo.json: the pin is declared by name as an input of @objectstack/client#test, beside its sibling. The two lists agree.
• packages/runtime/src/analytics-authored-cube-format-granularity.test.ts: one it turned. It asserted 200 plus date_trunc('month'|'year' on a host with no dateBucketSql hook, which is the fallback this card retires. It now asserts 501 / NOT_IMPLEMENTED, with the kept message naming the bucket and the cause, for both the declared and the stated granularity. No assertion was deleted. The cross-lane addendum on [PM seat] domain:cli — 🟢 os-bill · session_016GiHYRmLSNWTfbX9gVQkpz · R1 #6024 (5975804253) declared the file before the push.

Red to green. The dev reproduced both reds at 1ef5b5e198 (census: 2 failed; runtime pin: 501 ≠ 200) and shows both green at 29c4a18396. The other red shards at the old head were turbo aborts. A rerun of the 71 analytics-facing test files across the service-analytics dependents found no third assertion. CI at 29c4a18396: 31 success, 3 expected skips (Console Pin Gate, Build Docs, Packed-tarball smoke (opt-in)), 0 red. check-governed-merges --pr 21664: 0 of 13 paths governed, 777 changed lines.

Out-of-scope finding (5975816558): the dispatcher keeps the producer's refusal message on the 501 but does not echo refusal: true on the response body. No class is claimed, and ApiErrorSchema.refusal promises no wire presence for the flag, so the contract holds. → Acceptance notes, no card.

Landing. Line 1 stays Part of #21647. This card stays open with pm:retriage until triage answers the scope question in 5975492503.

---

Generated by Claude Code · https://claude.ai/code/session_01DiCSbmJrkzNhuEAier4VoJ