finding(test-infra): the date-face pin family asserts LOCAL-date faces while the repo pins no timezone anywhere — the suite is red for any contributor west of UTC-07:00

[os-justin]

Filed by the domain:ui PM seat (session_01YBWFb5YgMU5dw8p2VKj16S) on behalf of the objectui#8262 dev, who measured it while landing PR #8353 and could not file it: search_issues hard-failed twice with API rate limit already exceeded for user ID 323634890, and repo-scoped REST is gated 403 for that seat. ⛔ Not claimed.

Contributor-facing, not user-facing. No shipped behaviour is wrong. The cost is that a maintainer in the wrong timezone sees a wall of red that is not about the code.

What

A family of pins asserts literal local-date faces (Jul 4, 2024, 7/4/2026) derived from fixed UTC instants — 2026-07-04T07:00:00.000Z and friends. Every face is built from local date parts, so the literal reads Jul 4 in UTC and eastward of UTC-07:00, and Jul 3 west of it.

Nothing pins the timezone. Measured on main (this seat, independently, zero-quota):

vitest.config.mts   TZ=0   timeZone=0
turbo.json          TZ=0   timeZone=0
package.json        TZ=0   timeZone=0
6 × vitest.setup.*  TZ / timeZone = 0
.github/workflows   TZ: = 0 files
⚡ lit control — 'environment' in vitest.config.mts = 8   ⇒ the grep fires; the zeros are readings
T07:00:00.000Z in the affected files = 7 uses

The measurement that matters

From the reporting dev, at branch base 411a132c0, without PR #8353's new row:

TZ=Etc/GMT+8 pnpm exec vitest run packages/core/src/utils/__tests__/date-display.optionsStyle-7745.test.ts
  → Tests  10 failed | 4 passed (14)
  failures of the form:  expected 'Jul 3, 2024' to be 'Jul 4, 2024'

dataset-format.date.test.ts passes in the same run, so the exposure is not uniform across the family.

Population

Six files, reported by the dev:

• packages/components/src/__tests__/data-table-datetime-convention-7443.test.tsx
• packages/core/src/utils/__tests__/dataset-format.date.test.ts
• packages/core/src/utils/__tests__/date-display.optionsStyle-7745.test.ts
• packages/fields/src/__tests__/datetime-compact-style-7443.test.tsx
• packages/fields/src/__tests__/fields-date-widget-convention-8194.test.tsx
• packages/plugin-dashboard/src/__tests__/DatasetWidget.dateMeasure.test.tsx

⚠️ The dev counted 49 day-bearing assertions; this seat could not reproduce that number and says so rather than restating it. A date-shaped regex over the same six files returns 36 matching lines here, and 0 in DatasetWidget.dateMeasure.test.tsx — which means this seat's regex misses that file's spelling, not that the file is clean. The TZ=Etc/GMT+8 run above is the load-bearing evidence; treat both counts as approximations and re-enumerate before acting.

Fix shape

Reported as: set TZ=UTC once in vitest.config.mts, rather than editing dozens of assertions.

⚠️ Whoever takes it should check whether that hides a real locale/zone bug anywhere — pinning the zone makes the suite deterministic, which is the point, but it also means no test exercises a non-UTC session any more. If that coverage is wanted, it wants explicit per-case zones, not the runner's ambient one.

Related

objectui#8262 / PR #8353 (where it was measured) · objectui#8194 (its SCOPE FENCE block is in the population) · objectui#7443 · objectui#7620 · objectui#8209

Dedup

⚠️ Not run to completion, declared rather than hidden. The reporting dev could not search at all. This seat's one attempt (timezone / "TZ=UTC" / vitest.config / "local date") was itself refused by the rate limiter. No dedup claim is made. Suggested query for a triager: timezone TZ pin date test literal local date faces. Adjacent known cards: objectui#8194, objectui#8209.

---

Blocked-by: #8493

⚠️ Added by the domain:devx @ objectui execution seat, 2026-09-08T03:12Z. The work is complete and PR #8486 is green on every check except one: Test (shard 2/4), which fails on plugin-kanban's ObjectKanban.contractEnvelope-6839.test.tsx — a defect external to this diff, measured three ways (shard 2's membership is byte-identical on base and branch; the CI runner is already UTC so the pin is a semantic no-op there; the kanban file is not zone-sensitive under any of four zones). ⇒ This is the state-model's work finished, PR held by an external gate case, ⛔ not unfinished work.

---

Generated by Claude Code

[claude]

Claim: PM loop round R46 — domain:devx @ objectui execution seat.
Session: session_01FhBNJcLRZLe8M87VcUgpKr
Branch: claude/issue-8366-date-face-timezone
Worktree: /home/user/objectui-issue-8366
Domain: domain:devx
Dispatch: one os-dev subagent of this session (mode:subagent, model: opus); the dispatch note with the brief follows. Labels pm:queue → pm:dispatched and assignee set in one write, read back and diffed against the union at 2026-09-08T01:55Z.

⚠️⚠️ This seat put FOUR false premises into dispatch briefs today — 660 judged (tree: 663), 1309 fences (read in the shared checkout; origin/main reads 1310), UNGATED_DOCS = {} (it holds 4), and "objectui#8045 is open" (closed 2026-09-07T19:09:04Z). ⭐ The last brief instructed the dev to re-read every referenced card on GitHub while this seat took that card's status from the card's own record table. ⇒ Every fence, number and card status below is a PREDICTION. Re-derive before you act on it, and a corrected brief with zero implementation is a good outcome.

⚠️ SIX cards this shift carried a false premise in the card face itself — #8006 #8029 #8113 #8117 #8122 #7925, three of them repeated verbatim in the triage comment.

⛔ A zero-hit reading means nothing without a control term you know is present, in the same run. ⛔ origin/main is verified on a clean extract or a detached worktree, ⛔ NEVER on /home/user/objectui's working tree. ⛔ A grep over a whole file cannot answer a question about one region of it — three probes did exactly that today and hit a docblock, a different schema, and a deliberately dated historical sentence.

---

Generated by Claude Code

[claude]

Dispatched — domain:devx @ objectui execution seat, PM session session_01FhBNJcLRZLe8M87VcUgpKr, R46, 2026-09-08T01:57Z. One of three slots (with #8115 and #8125).

Dev. One os-dev subagent of this session on branch claude/issue-8366-date-face-timezone, worktree /home/user/objectui-issue-8366, from origin/main at ed17be480 or later. Race re-read at 01:55Z: the newest Claim: is 5577907971, naming that branch — and it is the only one. ⛔ No second claim, ⛔ never writes the assignee.

⚠️ This card has NO triage comment, and the brief says so rather than papering over it. Every other card this lane dispatches carries an English triage audit comment with a ruling; #8366 has zero comments and reached pm:queue + domain:devx + priority:p3 by labels alone. ⇒ There is no ruling for the brief to carry. Where the brief states a preference it is labelled this seat's reading and ⛔ explicitly not an adjudication. ⚠️ Recorded here for the triage seat: this card's grading has no audit comment. ⛔ This seat does not write one.

⭐ The card's own measurement is the reason it is dispatchable at all. The reproduction is concrete — TZ=Etc/GMT+8 turns date-display.optionsStyle-7745.test.ts into 10 failed | 4 passed, expected 'Jul 3, 2024' to be 'Jul 4, 2024' — and every zero carries a control: TZ/timeZone = 0 across vitest.config.mts, turbo.json, package.json, six setup files and every workflow, against a lit control of 'environment' in vitest.config.mts = 8. ⚠️ And it names its own asymmetry: dataset-format.date.test.ts passes in the same run. The brief makes that asymmetry a thing to explain, ⛔ not to smooth over.

⭐ The design fork is the deliverable, and the dev must argue it rather than pick it. Pin the timezone (cheap, but makes every future date pin depend on a global nobody looks at, and hides the class); make the pins timezone-independent (removes the class, costs a rewrite and risks a pin that no longer asserts what it was written for); or both, scoped. Answer under the four axes, implement the argued option, and state the cost of the rejected one. ⚠️ And the brief says plainly that "this needs a ruling rather than a dev's judgement" is an admissible answer — pinning a global test timezone is arguably a repo-wide convention, not a fix. This seat routes it if so.

⛔ Fences. ⚠️ vitest.config.mts became a ledger row twenty minutes ago: objectui#8337 landed as ed17be480 with UNREACHED_GROUPS carrying the exact path 'vitest.config.mts'. Editing its contents does not disturb the row; ⛔ do not touch UNREACHED_GROUPS, ⛔ do not rename or re-extension the file. ⛔ No shipped behaviour changes — if the fix would reach packages/core's date formatting, stop and report: different card, different lane. ⚠️ The population reaches other lanes' test files, inherent to a test-infra fix on a domain:devx card; every file touched outside scripts/ gets listed in the PR body so its owners can see it.

⚠️ Non-vacuity is the whole risk: a green suite under one TZ proves nothing. Red under a west-of-UTC-07:00 TZ before, green after, and green under TZ=UTC on both sides.

⚠️⚠️ The brief warns the dev about this seat before it warns it about anything else. Four false premises reached dispatch briefs today — 660 judged (tree: 663), 1309 fences (read in the shared checkout; origin/main reads 1310), UNGATED_DOCS = {} (it holds 4), and "objectui#8045 is open" (closed 2026-09-07). ⭐ That last brief instructed its dev to re-read every referenced card on GitHub while this seat took the status from the card's own record table. ⇒ Every fence, number and card status in the brief is labelled a prediction, and a corrected brief with zero implementation is stated as a good outcome.

---

Generated by Claude Code

[baozhoutao]

os-dev-report

{
  "issue": 8366,
  "status": "done",
  "branch": "claude/issue-8366-date-face-timezone",
  "pr": "https://github.com/objectstack-ai/objectui/pull/8486",
  "pr_number": 8486,
  "head_sha": "e1641f8e621dc88af2f00987fb1d45d376d80170",
  "base": "76573a1843d46bb9f070a9f97ef45219e23b5a30",
  "premise_still_valid": true,
  "premise_notes": "Defect reproduces on origin/main 76573a184; every zero in the card re-derived against a lit control. TWO CORRECTIONS. (1) The card's 'red for any contributor west of UTC-07:00' is too narrow: the six files, run together, give UTC 184 passed / Europe-Paris (+02:00) 7 failed / Asia-Shanghai (+08:00) 7 failed / America-New_York (-04:00) 31 failed / Etc-GMT+8 (-08:00) 33 failed. The suite is green at EXACTLY ONE offset, red east of UTC as well as west, because a face like 'Jul 4, 2024, 07:00 AM' pinned off an 07:00Z instant is true only at UTC+00:00. (2) The single-file reading moved: card says 10 failed | 4 passed (14) at base 411a132c0; on 76573a184 the same file is 11 failed | 4 passed (15) (PR #8353 added a row). Card zeros confirmed: TZ/timeZone = 0 in vitest.config.mts, turbo.json, package.json and all six vitest.setup.* ; 'TZ:' = 0 workflows. Controls: 'environment' in vitest.config.mts = 8, 'runs-on' = 34 workflows. Population confirmed: all six named files exist. Fence confirmed by measurement, not by reading: vitest.config.mts appears 0 times in lint:root's 276-file ESLint population, which is what objectui#8337's UNREACHED_GROUPS row asserts; the row itself is untouched and check:lint-rule-coverage exits 0. No triage comment exists on the card - the only comment is this seat's own Claim (5577907971) - so no ruling was carried, and the fork below is argued rather than assumed.",
  "summary": "Chose option A and argued it: vitest.config.mts now sets process.env.TZ = 'UTC' in module scope, so every legitimate run is deterministic (apps/console/vitest.config.ts imports the root config; the 11 packages/*/vite.config.ts reach assertCanonicalVitestInvocation, which refuses the package-cwd invocations that could bypass it). No test file was edited, so the card's warning about reaching other lanes' test files does not apply to this diff. THE ASYMMETRY IS EXPLAINED, not smoothed over: dataset-format.date.test.ts and DatasetWidget.dateMeasure.test.tsx pass in every zone because they DERIVE the expected face by calling the same formatter under test (expect(out).toBe(formatDateTime(ISO, {locale}))), and the latter says so in a docblock headed 'Why the expectations are DERIVED and not literal'. Option B was rejected on measurement: the four failing files pin literals deliberately, and date-display.optionsStyle-7745.test.ts states the reason in prose - its faces are 'anchored by the two literals the card measured, so a redesign that moved both sides together could not pass silently'. Those literals sit beside equivalence assertions that are already zone-independent, so deriving them would turn the anchor into formatDate(v) === formatDate(v) and delete what the file was written for. The pin is unconditional and not ??=, because a contributor's zone comes from /etc/localtime rather than TZ, so a conditional assignment would leave the reported population unfixed while looking like a fix; the guard forbids the ??= / ||= spelling. Coverage loss is measured at zero: no test in the repo reads the ambient zone (process.env.TZ, getTimezoneOffset, resolvedOptions() = 0 hits across all *.test.ts(x); live control - the same resolvedOptions() pattern hits 5 times elsewhere), and the one zone-aware production surface, GanttView's makeTzShift/tzOffsetMs, takes its zone from metadata (schema.timeZone) and is already tested with explicit per-case zones. A guard test spawns a real vitest under TZ=Etc/GMT+8 and asserts the run still sees UTC, because CI is UTC and an in-process assertion would be green there whether or not the pin survived - the original defect one level up. MY READING ON ROUTING: this does NOT need a maintainer or triage ruling. It is test infrastructure with no shipped-behaviour reach; the pinned value equals the value CI and this container already run at, so the change is behaviourally inert everywhere it is currently exercised and only adds determinism elsewhere; and the one coverage question the card raises has a measured answer. I state that as my reading rather than an adjudication - if the PM seat disagrees it can route it, and the diff is one line plus one guard file, so reverting costs nothing.",
  "files_changed": [
    "vitest.config.mts (the pin plus its comment; contents only, path and extension unchanged, UNREACHED_GROUPS untouched)",
    "scripts/__tests__/vitest-timezone-pin-8366.test.ts (new; the spawn-based guard)",
    ".changeset/8366-vitest-timezone-pin.md (new; empty frontmatter, declares no release)"
  ],
  "tests": "NON-VACUITY, the six files run together, all through scripts/pm/os-verify-lock.sh, reading its own VERDICT line. BEFORE: TZ=UTC 'Test Files 6 passed (6) / Tests 184 passed (184)' VERDICT command-exit 0; TZ=Etc/GMT+8 '4 failed | 2 passed (6) / 33 failed | 151 passed (184)' VERDICT command-exit 1, failures of the form \"expected 'Jul 3, 2024' to be 'Jul 4, 2024'\" and \"expected '7/3/2024 11:00 pm' to be '7/4/2024 7:00 am'\"; TZ=America/New_York 31 failed; TZ=Europe/Paris 7 failed; TZ=Asia/Shanghai 7 failed. AFTER: TZ=Etc/GMT+8, TZ=America/New_York, TZ=Asia/Shanghai and TZ=UTC each 'Test Files 6 passed (6) / Tests 184 passed (184)', VERDICT command-exit 0 on all four. GUARD TEST: pnpm exec vitest run scripts/__tests__/vitest-timezone-pin-8366.test.ts -> '1 passed (1) / 4 passed (4)', VERDICT command-exit 0 (4 ran, 0 skipped, so the spawn case really executed). ABLATION, direction predicted in writing BEFORE the run (spawn case and static case RED; ambient case GREEN because this box is UTC - which is the point; control GREEN). Mutation proven on disk before any result was read: HEAD blob 89896da7cd4777abfb6bab7f66c04b1691600ed1, marker \"^process.env.TZ = 'UTC';$\" count 1 -> 0, injected marker count 1, on-disk hash 04beeb3449fc516137e3c824f98728b6647df7f8 (differs from HEAD blob), 'MUTATION PROVEN ON DISK'. Observed, matching the prediction: 'Test Files 1 failed (1) / Tests 2 failed | 2 passed (4)' with '× a real vitest spawned under a non-UTC TZ still runs in UTC' and '× the pin is where the spawn says it is'; the nested child's own output appears in the failure - '× the suite runs in UTC, whatever zone the contributor is in / AssertionError: expected 480 to be +0' - the direct reading that the pin is what forces UTC. Restore under trap 'EXIT INT TERM' with absolute paths via 'git checkout HEAD -- $REPO_ROOT/vitest.config.mts', proven BY STATE: 'git diff HEAD --stat' printed nothing, and 'git status --short' is clean. NO BUILD/DIST STEP APPLIES: the subject is vitest.config.mts itself, read from source by the spawned vitest, and the guard resolves through vitest's source aliases - nothing goes through a package exports map, so there is no dist/ leg to preflight. SCOPE: pnpm exec vitest run scripts/ -> 'Test Files 122 passed (122) / Tests 3634 passed (3634)', VERDICT command-exit 0 - this is the population that reads vitest.config.mts (vitest-invocation-guard.test.ts, dist-pins-guard-message-8274.test.ts, check-lint-rule-coverage.test.ts, unit-registry-absence-collision.test.ts, package-scripts-vitest-projects.test.ts, vitest-config-alias-targets-3944.test.ts and the rest). GATES, exit codes captured before any pipe: node scripts/check-changeset-presence.mjs = 0 ('No source or published contract of a released package changed in this range, so no changeset is owed' - one was added anyway, empty frontmatter, the repo's documented no-release declaration, matching .changeset/14026-list-import-mappings-pin.md); node scripts/check-lint-rule-coverage.mjs = 0; node scripts/check-governed-queue-guard.mjs --test (the three changed paths) = 0, 'NOT GOVERNED - 3 path(s) checked against 5 governed surface(s); none matched' (so no maintainer-speed-read section is owed); check:control-bytes = 0 (6716 tracked text files scanned); check:vi-mock-inherit = 0; check:vi-mock-specifiers = 0; check:unreferenced-sources = 0; type-check:scripts = 0; type-check:coverage = 0; type-check:vitest-config = 0. Control bytes additionally self-scanned outside the gate: grep -naP over the three changed files returned no match (exit 1). TYPE-CHECK IS MEASURED, NOT ASSUMED: tsc -p tsconfig.scripts.json --listFiles returns the new test file (count 1), so type-check:scripts really compiled it. LINT, DELIVERED AS A PROVEN NARROWING at the final commit e1641f8e6, three legs: (1) receiving population read from ESLint's own config via the repo's own root-lane invocation 'lint:root' rather than a guess; (2) 276 files judged, 0 errors, 32 warnings, exit 0, counted from --format json, with the new test file present at 0/0 and vitest.config.mts absent (0 occurrences), independently confirming the UNREACHED_GROUPS row; (3) invariance for the packages/* and apps/* turbo lint lanes this narrows away - eslint.config.js contains 0 occurrences of projectService / parserOptions / project: (live control: 10 occurrences of 'rules' in the same run), so no type-aware linting is enabled and this diff cannot move the verdict on any untouched file, and it touches no file in those lanes. HONEST LIMIT, stated rather than hidden: this container's ambient zone is UTC (offset 0, resolvedOptions().timeZone = 'UTC'), the same as CI, so the pin is behaviourally INERT for every locally-runnable suite other than the new guard - a full-suite run here cannot detect a regression from this change, and its greenness would not be evidence. The evidence that matters is the cross-timezone matrix above, which is why it was run in five zones rather than once.",
  "four_axis_analysis": {
    "options": [
      "A - pin the runner's timezone to UTC in vitest.config.mts (CHOSEN)",
      "B - rewrite the pins to be timezone-independent (derive the expected face, or assert UTC parts)",
      "C - both, scoped: pin the zone and record the pins that would still be zone-dependent"
    ],
    "shi_ji_ye_wu_xu_qiu": "MEASURED, not read as plausible. Who writes these pins: contributors adding date-face regressions. Who reads them: CI, under UTC, where the defect is invisible, and contributors elsewhere, who pay all of it. Measured exposure: green at exactly one offset (UTC 0 failures; +02:00 7; +08:00 7; -04:00 31; -08:00 33). So the served need is real and has a named population - the objectui#8262 dev who measured it, reproduced here. A serves it with one line and no assertion touched. B serves the same population but pays by rewriting four files' assertions, and the measurement says those assertions are not incidental: the two files that ALREADY pass do so by derivation and say in their docblocks that derivation was deliberate, while the four that fail pin literals and say in prose that the literals are the anchor that stops a both-sides redesign passing silently. So B trades a contributor-facing annoyance for a real loss of regression coverage. C's incremental half over A is an inventory document with no consumer. Verdict on this axis: A.",
    "xiang_mu_chang_yuan_he_li_xing": "A puts the decision in the one place that already owns how this repo runs tests - the root vitest.config.mts, whose governing ruling (objectui#3240, maintainer 2026-08-06) is literally 'one config, one conclusion'. apps/console/vitest.config.ts imports it, and assertCanonicalVitestInvocation already refuses the invocations that would bypass it, so one line genuinely covers every legitimate run. The card's long-run worry - that pinning hides a locale/zone bug - is answered by measurement rather than argument: zero tests read the ambient zone, and the single zone-aware production surface (GanttView.makeTzShift) is already tested with explicit per-case zones, which is the shape the card itself says non-UTC coverage should have. So A removes an uncontrolled input rather than masking one. B is the workaround shape here, not A: it leaves the runner's zone uncontrolled forever and makes every future date pin re-derive the discipline privately. A's honest long-term cost, stated: the suite now depends on a global nobody looks at - which is why this is A-plus-a-guard, not A alone, and why the guard fails on CI rather than only on a contributor's laptop. Verdict: A.",
    "fang_ai_xie_dai_ma_fan_cuo": "This is where A and B separate most sharply. B's shape is 'make the assertion tolerant of an input it cannot control' - the pin stops asserting the face and starts asserting f(x) === f(x). That is the ??-fallback / lenient-consumer pattern one level up, and it is exactly the form an AI writing the fiftieth date pin would copy, producing a pin that can never fail. A tightens instead: the environment is declared once, loudly, at the contract point, and the declaration is ENFORCED - a spawn under a non-UTC TZ proves the runtime honours it, so nothing can declare 'this suite runs in UTC' without it being true (declaration equals enforcement). The static half additionally forbids the ??= / ||= spelling, which is precisely the plausible-looking but inert variant an AI would reach for while believing it had added an escape hatch. Verdict: A.",
    "chuang_ye_jie_duan_bu_kuo_san": "A adds one configuration line and one guard file: no new env var, no new opt-out, no new convention for authors to learn. I deliberately REJECTED an OBJECTUI_TEST_TZ escape hatch that I had designed: nobody has asked for non-UTC runs, and the card itself says non-UTC coverage wants explicit per-case zones - so an ambient escape hatch would be an unpulled declaration surface that also reopens the class for anyone with TZ exported. On the no-gradualism half (maintainer 2026-08-27): the pin is unconditional and immediate, no ??=, no staged window, no dual spelling; ??= would look like a transition and would in fact leave the reported population unfixed. C is rejected on this axis - its extra half is a document with no consumer and no gate, and the useful part of it (which pins were already zone-independent, and why) ships as the config comment and the PR body instead. Verdict: A.",
    "recommendation": "A, implemented as one config line plus one spawn-based guard test. Rejected costs, stated: B would convert four files' deliberate anti-tautology anchors into self-comparisons - date-display.optionsStyle-7745.test.ts loses the two literals it names in prose, and fields-date-widget-convention-8194.test.tsx alone carries 16 failing cases whose expected faces would become tautologies - for a class A removes anyway at roughly 1/50 the diff. C costs an unconsumed inventory charged against the startup-focus axis with no offsetting pull. No axis conflict arose: all four point the same way.",
    "conflict": "none - the four axes agree on A"
  },
  "open_questions": [],
  "out_of_scope_findings": []
}

---

Generated by Claude Code