A dataset measure over a date field renders its raw ISO string — formatMeasure short-circuits before format is read

Found by opening a dashboard in a real ObjectStack application (objectstack-ai/duly) against published @objectstack/* 17.2.0. Source-confirmed afterwards in this repo.

The claim

A min / max measure over a date or datetime field cannot be rendered as a date on any dataset-bound widget, and the format escape hatch the spec offers for exactly this is unreachable for those values.

The KPI tile renders 2026-07-04T07:00:00.000Z where a date belongs — a 24-character ISO string in text-2xl font-semibold, which wraps to two lines inside the card.

Where it comes from

packages/plugin-dashboard/src/DatasetWidget.tsx:768 renders the dataset-bound metric value:

<span className={cn('text-2xl font-semibold tabular-nums', accentClass)}>
  {formatMeasure(value, f?.format, f?.currency, f?.percentScale, displayLocale)}
</span>

and formatMeasure in packages/core/src/utils/dataset-format.ts opens with:

if (v == null) return '—';
if (typeof v !== 'number') return String(v);

That second line is before format is touched. So for any non-numeric measure value the function is String(v) and nothing else — the format argument the call site carefully threads through is dead on this path. tabular-nums on the span is the same assumption stated in CSS.

Everything downstream of that guard is a numeral-pattern formatter (decimals from format.split('.')[1], %, $, currency), which no date pattern can enter.

Why the escape hatch does not close it

DatasetMeasureSchema in @objectstack/spec carries format: z.ZodOptional<z.ZodString> — an open string, so authoring format: 'YYYY-MM-DD' (or anything else) passes validate and build cleanly. It then has no effect, because the value never reaches the branch that reads it. An author gets a green toolchain and an unchanged raw timestamp, with nothing anywhere saying why.

Reproduce

Declare a measure aggregating a date field and bind it to a type: 'metric' widget:

// dataset
{ name: 'oldest_touch', label: 'Oldest touch', aggregate: 'min', field: 'last_update_at' }

// dashboard widget
{ id: 'oldest', title: 'Oldest untouched task', type: 'metric',
  dataset: '<ds>', values: ['oldest_touch'] }

Open the dashboard. The tile shows the raw ISO string. Adding format: 'YYYY-MM-DD' to the measure changes nothing.

Scope beyond the metric tile

The same formatMeasure call is on three other surfaces, all with the same guard in front of them, so a date measure is raw in each: DatasetWidget.tsx:876 (chart value formatting), DatasetWidget.tsx:1083 (dataset table cells), and views/metadata-admin/previews/DatasetPreview.tsx:235. PivotTable.tsx:46 takes value: number outright.

Suggested direction

The narrow fix is to let formatMeasure recognise a date-shaped string (or a measure whose format names a date pattern) before the numeric short-circuit, and route it through the same date display path list cells already use — the argument for reusing that path rather than adding a second one is the same one the file's own header makes about percent, where two conventions drifted between a list cell and a dashboard measure (objectui#4576).

Whatever the resolution, the silence is the worse half: a format that the schema accepts and the renderer can never read is declared ≠ enforced. If dates are out of scope for measure formatting, the spec's format should say so and a date-typed aggregate should be refused at author time rather than rendered raw.

Application impact

Low severity — the number is correct and legible, just ugly. Reported because the silence is the reusable finding, not the wrapped timestamp.

Triage — `finding` · `needs-user-decision` · `domain:ui` · `priority:p3`. Recommendation attached so it is a yes/no.

domain:ui seat (session session_012wwHa4aaFybxXrfmfHioDM). Found in a no:label sweep — this card was carrying no labels at all since filing, so nothing surfaced it (#7211).

Why not dispatched: the two directions are different products

The card's own framing:

The narrow fix is to let formatMeasure recognise a date-shaped string … If dates are out of scope for measure formatting, the spec's format should say so and a date-typed aggregate should be refused at author time rather than rendered raw.

⇒ Implementing date rendering and refusing date aggregates are not two routes to one outcome. If dates are out of scope, implementing rendering blesses a shape meant to be refused. ⛔ A dev must not pick by which is cheaper.

⚠️ I am being deliberate about this because I got the identical call wrong earlier today: on #6318 I wrote a dispatch fence as a binary (renderer honours the key ⇒ fork; does not ⇒ fix the fixture) and it had no true branch for the case in front of it. The lane flagged it instead of forcing it. Same shape here.

⭐ Recommended: implement the narrow fix.

Three reasons, and the third is the one that decides it:

min/max over a date is a legitimate aggregate. "Oldest untouched task" is a real KPI, and the card found this in a real application. Refusing it removes a capability someone is already using correctly.
The asymmetry is in the tier. Implementing is renderer-side — formatMeasure is in packages/core, no declared surface moves, Clause ② not engaged, landable today. Refusing means narrowing DatasetMeasureSchema.format or the aggregate's field type in @objectstack/spec — Clause ②, and the CONTRACT_REVIEW_TIER quota is exhausted. ⇒ One branch can ship; the other cannot, for reasons unrelated to its merit.
⭐ Reuse the list-cell date path, do not add a second one. The card makes this argument and cites the precedent: [core][fields] A percent renders as 1.234,5 % in a list cell and 1.234,5% as a dashboard measure — two percent conventions for one number #4576, where two percent conventions drifted between a list cell and a dashboard measure. That is the same file's own header warning, and it is why "implement" should mean route through the existing path, not write a date formatter here.

Answer: "implement" or "refuse".

⚠️ The finding is the silence, and it survives either answer

a format that the schema accepts and the renderer can never read is declared ≠ enforced

The format argument is threaded carefully through the call site and is dead on this path — formatMeasure returns String(v) for any non-numeric value before format is touched. An author writes format: 'YYYY-MM-DD', gets a green validate and build, and an unchanged raw timestamp with nothing saying why.

⇒ Whichever direction is ruled, that silence must close. If "refuse", the spec says so and the author is told at build time. If "implement", format becomes reachable. ⛔ What is not acceptable is leaving an open-string format that parses and cannot be read.

Scope, for whoever takes it

The same formatMeasure call sits on four surfaces, all behind the same guard: DatasetWidget.tsx:768 (metric tile), :876 (chart values), :1083 (dataset table cells), and views/metadata-admin/previews/DatasetPreview.tsx:235. PivotTable.tsx:46 takes value: number outright and is a different question.

⇒ A fix at formatMeasure serves all four at once, which is a further argument for fixing it there rather than at the tile.

Grading

p3, and the card grades itself the same way — "the number is correct and legible, just ugly." ⛔ Not p2: nothing is wrong, nothing is lost, and no decision is made on bad data. The reusable half is the declared ≠ enforced silence, which is a p3 correctness-of-contract issue rather than a user-facing defect.

Generated by Claude Code

Maintainer ruling recorded — A: implement date rendering in `formatMeasure` through the list-cell date path; date aggregates stay legal

Director seat (objectstack #12708), summon #8, session session_01ShyhexkB2d1AeRZ85tgAAe, 2026-09-02.

Provenance (who / verbatim / where): maintainer, live PM chat with the director seat, 2026-09-02, replying to decision batch #7 in which this card was item 3 with the recommendation A (fallback B, refuse date aggregates at author time). Verbatim reply: 「7189 A 其他同意」 — "其他同意" covers this card, so A is adopted as recommended.

Ruled: A. min / max over a date or datetime field is a legitimate measure and stays legal. formatMeasure in packages/core/src/utils/dataset-format.ts recognises a date-shaped value before the numeric short-circuit and routes it through the date display path list cells already use. No second date formatter is written in this file (the file's own header records why, from objectui#4576). Because the fix lands in formatMeasure, all four call sites are served at once: the metric tile, chart values, dataset table cells, and the metadata-admin dataset preview. PivotTable.tsx takes a number and is a different question, not touched here.

Option B (narrow DatasetMeasureSchema.format or the aggregate's field type in @objectstack/spec and refuse date aggregates at build time) is not taken: it removes a KPI a real application is already using correctly.

The silence must close either way. The finding's reusable half is that format is accepted by the schema and never read on this path. Under A, format becomes reachable for date values if the shared date path accepts a pattern. If it does not, the implementer states that in the PR and the spec seat adds one sentence to the format describe() on DatasetMeasureSchema ("applies to numeric measures; date measures render by locale"), so the remaining gap is documented rather than silent. That sentence is a spec-lane follow-up of one line, filed by the domain:ui seat when the measurement is in hand, not a rider on this PR.

Execution: domain:ui lane, S. Clause-② no (renderer side, no declared surface moves). @object-ui/core changeset, patch. Pin: a min measure over a datetime renders through the same path a list cell uses for that field, on the metric tile and in the dataset table, and a numeric measure is byte-identical before and after.

State transition, same stroke: needs-user-decision → pm:queue; priority:p3 retained. Ledger: objectstack director seat post #12708, summon #8.

Generated by Claude Code

Claim — `domain:ui` execution seat

Session session_01EMrWaQw3XS5DxTHxp4yRyC. Branch claude/issue-7178-formatmeasure-date. Dispatching now.

Authority for the round is the director-seat ruling in comment 5509025252 (summon #8, 2026-09-02, maintainer verbatim 「7189 A 其他同意」) — option A, implement. Date aggregates stay legal; formatMeasure recognises a date-shaped value before the numeric short-circuit and routes it through the date display path list cells already use. ⛔ Option B (narrow DatasetMeasureSchema.format or refuse date aggregates at author time) is not taken, and @objectstack/spec is not touched.

File surface declared for cross-lane serialization: packages/core/src/utils/dataset-format.ts and its tests. No ListView.tsx, no data-table.tsx — no overlap with the two open holds in this lane.

State transition, same stroke: pm:queue → pm:dispatched, assignee set.

Generated by Claude Code

os-dev-report

{
  "issue": 7178,
  "status": "done",
  "branch": "claude/issue-7178-formatmeasure-date",
  "pr": "https://github.com/objectstack-ai/objectui/pull/7442",
  "premise_still_valid": true,
  "summary": "Ruling A implemented. `formatMeasure` now recognises a date-shaped value ahead of the `String(v)` short-circuit and routes it through the list-cell date path; all four call sites are served unchanged, `@objectstack/spec` untouched, `PivotTable` untouched. Reusing the shared path REQUIRED LIFTING IT: `formatDate` / `formatDateTime` / `formatRelativeDate` / `DateDisplayOptions` moved from `packages/fields/src/index.tsx` (React) down into `packages/core/src/utils/date-display.ts`, exactly as objectui#4576 moved `formatDisplayNumber`, because core is the React-free engine and could not import from fields. `@object-ui/fields` re-exports all four names, so no consumer changes, and a reference-identity test pins that the cell renderer and the measure formatter are the same function object. THREE THINGS THE PM MUST WEIGH. (1) The `framework` chunk budget goes RED: 523,823 -> 524,402 B (+579), 402 B over the 524,000 ceiling; ui-components falls 510 B and the aggregate eager closure moves +16 B, so this is a relocation, not payload growth. No ceiling or budget file touched. (2) The ruling's pin says a datetime measure renders through the path a list cell uses; for `date` that is exact, for `datetime` it CANNOT be, because `DateTimeCellRenderer` inlines its own format and never calls `formatDateTime` — filed as #7443, and I followed ObjectGantt's sniffed-ISO dispatch instead. (3) The changeset carries `@object-ui/fields: patch` alongside the ruled `@object-ui/core: patch`, because the lift changes that package's source.",
  "tests": "All runs from the REPO ROOT — this repo refuses a package-directory vitest run (its own guard, objectui#3378, which silently runs the console suite and reports 22 files passed). Final commit 5ad78fde. NEW: packages/core/src/utils/__tests__/dataset-format.date.test.ts 13 passed; packages/plugin-dashboard/src/__tests__/DatasetWidget.dateMeasure.test.tsx 5 passed (the ruling's pin: metric tile + dataset table, expectations DERIVED by calling formatDateTime from @object-ui/fields rather than hardcoded); packages/fields/src/__tests__/date-display.reexport-identity.test.ts 2 passed. type-check + lint exit 0 on @object-ui/core, @object-ui/fields, @object-ui/plugin-dashboard after building each dependency closure. BYTE-IDENTITY SWEEP: a verbatim `git show BASE:` copy of the pre-fix function compared against the new one across value x format x currency x percentScale x locale — 'compared=33696 forms; distinct values that moved=4 (2026-02-30, 2026-07-04, 2026-07-04T07:00:00.000Z, 2026-07-04 07:00:00); moved forms=3240; expected movers that did NOT move=0'. Every number, numeric string ('1751612400000', '2026', '1e21'), the nullish em dash, arbitrary prose and every non-string is byte-identical. ABLATION, two legs, directions written before the run and all four matched: vitest aliases every workspace package to `src` (vitest.config.mts), so these legs read source directly and NO REBUILD LEG APPLIES — none is claimed. Leg 1 restored the pre-fix `return String(v)`: blob 4c176afe -> 65a1a202, injected-text count 1, deleted-text count 0; core 8 failed / 5 passed, dashboard 3 failed / 2 passed — every date and format case red, EVERY numeric must-not-change case green. Leg 2 replaced the re-export with a behaviour-identical local wrapper: blob 7799271d -> 1121f05d, injected-text count 1; identity 1 failed / 1 passed — identity red, behaviour green, which is the drift the pin exists to catch. Both restores under `trap ... EXIT INT TERM` with absolute paths, restored with `git checkout HEAD -- PATH` and proven BY STATE: `git diff HEAD --stat` empty AND blob hash equal to the HEAD blob, for both files; final `git diff HEAD --stat` empty. BUNDLE BUDGET, two full builds with CI's own recipe (turbo build packages -> console build -> node scripts/check-eager-closure-budget.mjs), branch 5ad78fde vs branch point 6411def25: framework 523,823 -> 524,402 B (+579, ceiling 524,000, OVER by 402); ui-components 396,598 -> 396,088 (-510); vendor-objectstack unchanged; aggregate eager closure 3,254,604 -> 3,254,620 (+16 B). Baseline checker exit 0, branch checker exit 1.",
  "mcp_calls": "8",
  "open_questions": [
    {
      "question": "The ruling's pin reads 'a min measure over a datetime renders through the same path a list cell uses for that field'. Measured, that is satisfiable for `date` but NOT for `datetime`: `DateCellRenderer` calls the shared `formatDate`, but `DateTimeCellRenderer` inlines its own `toLocaleDateString` + `toLocaleTimeString` pair and never calls `formatDateTime`. For 2024-07-04T07:00:00.000Z in en-US the cell renders '7/4/2024 7:00 am' and `formatDateTime` renders 'Jul 4, 2024, 07:00 AM'. Which target should a datetime measure take?",
      "options": [
        "A — `formatDateTime`, the module's declared datetime function, dispatched date-vs-datetime exactly as ObjectGantt.tsx already does for a sniffed ISO string with no field type attached. This is what the PR does.",
        "B — replicate `DateTimeCellRenderer`'s compact face in the measure path, matching the cell byte for byte.",
        "C — first reconcile the two datetime conventions (filed as #7443), then point the measure at the survivor."
      ],
      "recommendation": "A, as shipped — but the PM should know the pin's wording is not literally met for `datetime`, which is why I am raising it rather than reporting a clean pass. Long-term soundness decides it: a measure reaches `formatMeasure` with a column, not a field definition, so it is ObjectGantt's 'no field type attached' case by construction, and that site is the repo's existing answer to it — B would author a THIRD datetime convention inside `dataset-format.ts`, which is precisely what the ruling and objectui#4576 forbid, and it would do so to imitate a compact grid-cell face that is a dense-row design decision, not a platform convention. Real business need favours A too: the KPI tile is a `text-2xl` card, and the card's own complaint was that a 24-character string wrapped there, so the fuller 'Jul 4, 2024, 07:00 AM' is the fitting face and no application is asking for the grid face on a tile. C is correct in the long run but is a different card with its own decision, and blocking a ruled p3 fix behind it strands the defect. Startup scope discipline: A costs nothing new, B and C both expand the surface."
    },
    {
      "question": "The `framework` chunk lands 402 B over its 524,000 B ceiling, so Bundle Analysis will be red on #7442. The bytes are a RELOCATION (ui-components -510 B, aggregate +16 B), not payload growth. How should this be routed?",
      "options": [
        "A — park #7442 behind the open ceiling decision in #7399, alongside #7391 and #7400.",
        "B — raise PER_CHUNK_GZIP_CEILINGS.framework to fit this PR.",
        "C — shrink the change to fit — i.e. keep the date convention inside dataset-format.ts instead of lifting the shared one."
      ],
      "recommendation": "A. B is explicitly forbidden to me and is the maintainer's call in #7399, and C is forbidden by the ruling — it is the second-convention failure objectui#4576 already paid for. Worth putting in front of the maintainer for #7399: this PR is evidence that the framework ceiling now reds on a change whose true payload cost is +16 bytes across a 3.25 MB closure, because the group is defined by PATH (`/packages/(core|react|types)/`) and any code moving INTO core scores against it even when an equal amount leaves another eager chunk. That is a property of the attribution, not of the change."
    }
  ],
  "out_of_scope_findings": [
    "filed as #7443: `datetime` has two display conventions — `DateTimeCellRenderer` inlines its own `toLocaleDateString` + `toLocaleTimeString` and never calls `formatDateTime`, which also leaves `field.format` unreadable for datetime cells; `data-table.tsx`'s `formatCellValue` is a third, independently authored spelling. Labelled `finding` + `domain:ui`, unassigned, no `pm:queue`."
  ]
}

Declared file surface, extending the claim comment above for cross-lane serialization: packages/core/src/utils/dataset-format.ts, packages/core/src/utils/date-display.ts (new), packages/core/src/index.ts, packages/fields/src/index.tsx (the lift plus a re-export), and the three new test files. ⛔ No ListView.tsx, no data-table.tsx — no overlap with the two open holds in this lane. packages/fields/src/index.tsx was not named as held.

Generated by Claude Code

ACCEPT on the code — but PR #7442 is HELD, not enqueued: `framework` reds by 402 B

domain:ui execution seat, session session_01EMrWaQw3XS5DxTHxp4yRyC. Ruling A (5509025252) is implemented. Card stays pm:dispatched; ⛔ auto-merge not enabled, PR stays draft.

The shared path was reused by LIFTING it — verified independently, not taken on report

The ruling's ⭐ constraint was route through the date display path list cells already use, no second date formatter. There was no way to do that in place: formatDate / formatDateTime / formatRelativeDate lived in packages/fields (React), and packages/core is the React-free engine and cannot import from it. So they moved down into packages/core/src/utils/date-display.ts, and @object-ui/fields re-exports all four names — the same move objectui#4576 made for formatDisplayNumber.

⭐ The identity pin is what makes this a lift rather than a copy, and it is the right instrument: expect(fromEntry).toBe(fromCore) ×3 — reference identity. A behaviour-identical copy passes every value assertion and fails this one. The dev's ablation leg 2 proves it fires: replacing the re-export with a behaviour-identical local wrapper gave identity red, behaviour green, which is exactly the drift the pin exists to catch.

The byte-identity sweep is the other half and is the strongest evidence here: 33,696 forms compared against a verbatim git show BASE: copy of the pre-fix function, across value × format × currency × percentScale × locale. 4 distinct values moved, 3,240 forms moved, 0 expected movers failed to move. Every number, numeric string ('1751612400000', '2026', '1e21'), the nullish em dash and arbitrary prose are byte-identical. That is the ruling's "a numeric measure is byte-identical before and after" pin, measured rather than asserted.

@object-ui/fields: patch alongside the ruled @object-ui/core: patch is correct — the lift changes that package's source, so declaring only core would have been the dishonest half.

⚠️ The ruling's pin is NOT literally met for `datetime` — recorded, not papered over

The pin reads "a min measure over a datetime renders through the same path a list cell uses for that field." The dev reported this is unsatisfiable for datetime, and I re-measured it on origin/main rather than accepting it:

	reading
`DateCellRenderer` (`packages/fields/src/index.tsx:929`)	calls the shared `formatDate` at `:951` ✅ the pin holds for `date`
`DateTimeCellRenderer` (`:973`)	inlines `toLocaleDateString` + `toLocaleTimeString`; never calls `formatDateTime`
`formatDateTime` (`:688`)	defined, exported — and zero call sites in the file

⇒ There is no shared datetime path to route through. formatDateTime is itself a declared ≠ enforced instance, which is the same class as this very card. For 2024-07-04T07:00:00.000Z in en-US the cell renders 7/4/2024 7:00 am and formatDateTime renders Jul 4, 2024, 07:00 AM.

Decision: option A, as shipped — dispatch to formatDateTime, the module's own declared datetime function, sniffing date-vs-datetime the way ObjectGantt.tsx already does for an ISO string with no field type attached. Reasoning:

B is forbidden by the ruling. Replicating DateTimeCellRenderer's inline face inside dataset-format.ts would author a third datetime convention — precisely the second-spelling failure the ruling and objectui#4576 forbid, and it would do so to imitate a compact grid-cell face that is a dense-row design decision, not a platform convention.
C strands a ruled p3 behind a larger undecided card. The reconciliation is real and is now filed as datetime has two display conventions: DateTimeCellRenderer inlines its own and never calls formatDateTime #7443; it should not gate this fix.
A measure reaches formatMeasure with a column, not a field definition, so it is ObjectGantt's "no field type attached" case by construction — and that site is this repo's existing answer to it.
A also gives formatDateTime its first reader, which narrows a declared ≠ enforced gap rather than widening one.

⛔ I am flagging rather than silently redefining the pin. If the director seat or the maintainer reads the pin's wording as binding on datetime specifically, this is the place to object — the code is right by the ruling's intent, and its letter is unsatisfiable as written.

⛔ Why it is not enqueued: `framework` is 402 B over, and the bytes are a RELOCATION

CI's own verdict on 5ad78fde, corroborating the dev's two full builds:

❌ Console Performance Budget                     Status: FAIL
  Aggregate closure ceiling        ✅ pass    3178.3 KB / 3191.4 KB
  Per-chunk ceilings               ❌ over its ceiling
  Ceiling sensitivity (headroom)   ✅ pass
  Ceiling freshness                ✅ pass

chunk	before	after	ceiling
`framework`	523,823	524,402 (+579)	524,000 — over by 402
`ui-components`	396,598	396,088 (−510)	399,000
aggregate eager closure	3,254,604	3,254,620 (+16)	—

CI's own per-package table shows the same movement independently: fields 61.71 → 61.26 KB gz (code left), core 2.32 → 2.42 KB gz (code arrived).

⇒ The true payload cost of this change is +16 bytes across a 3.25 MB closure, and the aggregate ceiling passes. Only the per-chunk ceiling objects, because the framework group is defined by path — /packages/(core\|react\|types)/ — so code moving into core scores against it even when an equal amount leaves another eager chunk.

Routing: option A — PR #7442 parks behind #7399, alongside #7391 and #7400. ⛔ Not B (raising PER_CHUNK_GZIP_CEILINGS.framework is a gate ceiling and is the maintainer's call, never this seat's). ⛔ Not C (keeping a date convention inside dataset-format.ts is the second-convention failure the ruling forbids — it would trade a governance blocker for the exact defect the card exists to prevent).

Nothing in the budget script, the ceilings or any baseline was touched. No test skipped, disabled or quarantined.

Generated by Claude Code

fix(core,fields): refuse an impossible calendar day in date-times and…

Navigation Menu

Repository navigation

A dataset measure over a date field renders its raw ISO string — `formatMeasure` short-circuits before `format` is read #7178

The claim

Where it comes from

Why the escape hatch does not close it

Reproduce

Scope beyond the metric tile

Suggested direction

Application impact

Triage — `finding` · `needs-user-decision` · `domain:ui` · `priority:p3`. Recommendation attached so it is a yes/no.

Why not dispatched: the two directions are different products

⭐ Recommended: implement the narrow fix.

⚠️ The finding is the silence, and it survives either answer

Scope, for whoever takes it

Grading

Maintainer ruling recorded — A: implement date rendering in `formatMeasure` through the list-cell date path; date aggregates stay legal

Claim — `domain:ui` execution seat

ACCEPT on the code — but PR #7442 is HELD, not enqueued: `framework` reds by 402 B

The shared path was reused by LIFTING it — verified independently, not taken on report

⚠️ The ruling's pin is NOT literally met for `datetime` — recorded, not papered over

⛔ Why it is not enqueued: `framework` is 402 B over, and the bytes are a RELOCATION

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

A dataset measure over a date field renders its raw ISO string — formatMeasure short-circuits before format is read #7178

Description

The claim

Where it comes from

Why the escape hatch does not close it

Reproduce

Scope beyond the metric tile

Suggested direction

Application impact

Activity

os-warren commented on Sep 1, 2026

Triage — finding · needs-user-decision · domain:ui · priority:p3. Recommendation attached so it is a yes/no.

Why not dispatched: the two directions are different products

⭐ Recommended: implement the narrow fix.

⚠️ The finding is the silence, and it survives either answer

Scope, for whoever takes it

Grading

os-project-manager commented on Sep 2, 2026

Maintainer ruling recorded — A: implement date rendering in formatMeasure through the list-cell date path; date aggregates stay legal

os-project-manager commented on Sep 3, 2026

Claim — domain:ui execution seat

os-project-manager commented on Sep 3, 2026

os-project-manager commented on Sep 3, 2026

ACCEPT on the code — but PR #7442 is HELD, not enqueued: framework reds by 402 B

The shared path was reused by LIFTING it — verified independently, not taken on report

⚠️ The ruling's pin is NOT literally met for datetime — recorded, not papered over

⛔ Why it is not enqueued: framework is 402 B over, and the bytes are a RELOCATION

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

A dataset measure over a date field renders its raw ISO string — `formatMeasure` short-circuits before `format` is read #7178

Triage — `finding` · `needs-user-decision` · `domain:ui` · `priority:p3`. Recommendation attached so it is a yes/no.

Maintainer ruling recorded — A: implement date rendering in `formatMeasure` through the list-cell date path; date aggregates stay legal

Claim — `domain:ui` execution seat

ACCEPT on the code — but PR #7442 is HELD, not enqueued: `framework` reds by 402 B

⚠️ The ruling's pin is NOT literally met for `datetime` — recorded, not papered over

⛔ Why it is not enqueued: `framework` is 402 B over, and the bytes are a RELOCATION