fix(plugin-timeline,plugin-charts,i18n): a stored date-only day reads as that day in every zone on the timeline, a chart's date axis and the i18n date helpers (objectui#10866, slice 2) - #10901
Merged
objectstack-fleet[bot] merged 5 commits intoSep 28, 2026
Conversation
…as that day in every zone (objectui#10866, slice 2) The timeline's date bucket, sort and item date, the chart's date-only x-axis tick, and @object-ui/i18n's formatDate / formatDateTime / formatRelativeTime / formatDateSpec parsed a YYYY-MM-DD value with the engine's own Date parse (UTC midnight), so every viewer west of UTC read the day before. Each now reads it through core's toDisplayDate; a value with a time part keeps its instant. The ISO faces (timeline iso, chart locale fallback) print a date-only value's day from local getters, since toISOString of the local midnight names the day before east of UTC. formatDateSpec applies its timeZone to an instant only. Four zone pins registered in the date-only zone-pin driver, each under America/Los_Angeles and Asia/Shanghai with an instant control. Claude-Session: https://claude.ai/code/session_01DuWo5bdP9SdVebamn99GGk Co-authored-by: Claude <noreply@anthropic.com>
…ate-only zone pins (objectui#10866) The pins set process.env.TZ in the forked child and read the driver's flag off process.env; TypeScript 6 includes no @types by default, so the test program named neither. packages/plugin-calendar/tsconfig.test.json names node for the same pins. Claude-Session: https://claude.ai/code/session_01DuWo5bdP9SdVebamn99GGk Co-authored-by: Claude <noreply@anthropic.com>
…e pin (objectui#10866) Claude-Session: https://claude.ai/code/session_01DuWo5bdP9SdVebamn99GGk Co-authored-by: Claude <noreply@anthropic.com>
github-actions
Bot
added
documentation
Contributor
|
changeset-claim-re-read
|
Contributor
❌ Console Performance Budget
The eager closure is every chunk the entry reaches through static imports — what the browser fetches and parses before the app renders. The entry chunk on its own is a small fraction of it. Which half objected:
📦 Bundle Size Report
Size Limits
|
Contributor
Author
Contract reviewServed-tier: Read: card objectui#10866 (body, triage ① Derived judgmentsBlocking
Per site, re-measured on head: 50 of 50 cases pass in both zones, every rig case among them.
The behaviour beyond a parse swap. All three are right, pinned and named in the changeset: the
The chart span keeps the engine parse: sound. It is a duration between two categories of one axis. Two date-only values are UTC midnights a whole number of days apart in every zone; two local midnights differ by an hour across a DST change, so a span near the 62-day bound would flip faces. An instant pair is the same under either parse. Site-3 census: four reads, as the dev says. Bucket, sort, Pins. Four Site 5. No
② Semver level
③ Boundary flags
Implemented-by: VERDICT: FAIL Item 1 stops the landing; ③'s same-push items ride the fix; the rest is the card's. Generated by Claude Code |
…bjectui#10866) packages/i18n now imports @object-ui/core at runtime (the date helpers read through toDisplayDate), and i18n-runtime outranks framework, so rolldown's default recursive capture wrote 54 of core's 81 modules and 2 of types/src into i18n-runtime; Bundle Analysis's membership half went red. includeDependenciesRecursively: false is the objectui#9345 repair the data-adapter paragraph documents; the circular-chunk caveat is re-checked in the group's comment. The eager-closure pin now names i18n-runtime beside data-adapter. Claude-Session: https://claude.ai/code/session_01DuWo5bdP9SdVebamn99GGk Co-authored-by: Claude <noreply@anthropic.com>
…he stored day while its axis does not (objectui#10866) Claude-Session: https://claude.ai/code/session_01DuWo5bdP9SdVebamn99GGk Co-authored-by: Claude <noreply@anthropic.com>
Contributor
✅ Console Performance Budget
The eager closure is every chunk the entry reaches through static imports — what the browser fetches and parses before the app renders. The entry chunk on its own is a small fraction of it. 📦 Bundle Size Report
Size Limits
|
This was referenced Sep 28, 2026
Contributor
Author
Contract reviewServed-tier: Delta review of fix round 2 against record ① Derived judgmentsItem 1 (the red
Item 2 (the changeset's gantt sentence): repaired. The Timeline bullet now says the variant's axis headers, extent and bar positions are unchanged, so west of UTC its bar tooltip, printed through the same item-date function, names the stored day while the axis above it still reads the day before, until a later slice. Every clause is true against the measurements in Item 3: No regression from round 1. The five source files are byte-identical to Every sentence checked is true. The changeset (above). The config's new comment: the 54 / 81 / 2 readings, the red-then-green membership half, "the flag adds no cycle", the function-body read — each reproduced here; its two
② Semver level
③ Boundary flags
Implemented-by: VERDICT: PASS Generated by Claude Code |
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Sep 28, 2026
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Sep 28, 2026
This was referenced Sep 28, 2026
objectstack-fleet
Bot
deleted the
claude/issue-10866-timeline-charts-i18n-date-only
branch
September 28, 2026 09:03
akarma-synetal
pushed a commit
to akarma-synetal/objectui
that referenced
this pull request
Sep 28, 2026
…ts name 23 objectui issues that answer 404, and re-qualify 19 bare objectstack numbers (objectui#10803, batch 6) (objectstack-ai#10914) Part of objectstack-ai#10803 Clause-②: no Dispatched implementation of the `domain:ui` seat objectstack-ai#1 claim (comment `5864334310`) on objectui#10803, batch 6, session `https://claude.ai/code/session_01DuWo5bdP9SdVebamn99GGk`. Citations only: no sentence's claim moves, and every edited pending changeset's frontmatter is byte-identical. The one runtime string that moves is `InputSchema.wrapperClass`'s zod `.describe()` text in `@object-ui/types`, which loses its dead pointer and nothing else (amendment `5860244997`, Q1 = A; `patch` changeset). No test pins any changed text: the literal-anchor sweep below finds no specific anchor, so no test file is edited. This batch carries the release note `5863776648`'s three lists: - the last **23 family numbers**; - the **18 bare objectstack numbers above 10900** from PR objectui#10892's C0 census, plus **#13086**, a 404 the C0 instrument cannot see because it shares a token with #13337 (**Premise**); - the live-but-wrong bare `objectstack-ai#3391` at the two `rowCrudAffordances.ts` sites beside `objectstack#3720`. ## Why `Part of`, not a closing line The order says `Part of`. With this PR the family list (all 115 numbers of amendment `5860244997` Q2) and the C0 above-10900 list both read 0. Whether the card now closes, or carries the dead `objectstack#N` class measured in **Acceptance notes** 1, is the seat's call. ## Premise, re-measured on `origin/main` `9f0c84a44` (the branch point) - **The 23 family numbers.** REST `GET /repos/objectstack-ai/objectui/issues/N`: 23 of 23 answer 404, and a second read of each answers 404 again. `GET .../pulls/N` answers 404 for all 23. Lit controls: objectui#10533 and objectui#7714 answer 200. - **No new family member.** The distinct `objectui#N` citations in the two in-scope classes at the branch point, less those at batch 1's head `6c3ad7c80`, are 24 numbers. Each was read once: 24 of 24 answer 200. So the family list is still batch 5's 23. - **#14026 was a sister-repo card written as objectui's.** objectui#14026 answers 404 as an issue and as a pull. objectstack#14026 answers 301 to objectui#10102, the card it was transferred to. That card's measurement-round claim (branch `claude/issue-14026-import-mapping-selector-probe`) is the session of `ecf14190e`, the commit that added `14026-list-import-mappings-pin.md`, and six sibling in-scope lines already write `objectstack#14026` for the same card. - **C0, the bare-number census** (the instrument of PRs objectui#10875 and objectstack-ai#10892, at the branch point): ``` git grep -hoP '(?:^|(?<=[^\w#&/.\-]))#\d+(?![0-9A-Za-z_])' 9f0c84a -- '.changeset/*.md' 'packages/*/src/**' ':!**/__tests__/**' ':!**/*.test.*' ':!**/*.spec.*' ':!**/test/**' ':!**/tests/**' | sort -u | wc -l ``` - 984 distinct at `9f0c84a44`, against 998 at batch 5's `b2683a2c0`. The 14 that batch 5 re-pointed are gone, and none is new. - Above 10900 there are 23: the same 5 CSS colours and the same 18 numbers. Each of the 18 answers 404 as an objectui issue and as an objectui pull on two reads. - In objectstack, 16 of the 18 answer 200 with the sentence's own subject (the **C0 mapping** below). #13033 and #13413 answer 404 there too, as issues and as pulls. Their squash commits exist in objectstack's history (a full, not shallow, clone): `c459da6bc` "narrow the per-option `default` key out of the form-view options vocabulary … (#13033)" and `89448a52b` "remove the inert AUTH_SSO_PROVIDER_SCHEMA export (#13413)". Both are ancestors of objectstack `main` (`git merge-base --is-ancestor`, exit 0). - **The C0 instrument's blind spot.** Its lookbehind refuses a `#` preceded by `/`, `-`, `.` or `&`. That form (`#A/#B`, `-#N`) carries 109 distinct numbers at the branch point. The 17 that no earlier batch read were each read once. 16 answer 200. **#13086 answers 404**, as an issue and as a pull, in objectui and in objectstack. It sits in `6985-wizard-card-r-alignment.md` as "the #13337/#13086 fence", in the same token as #13337, so it rides here. objectstack's `check-yaml-examples.ts` header, at its landing `2ebfe7e9f` (PR objectstack#13267, which answers 200), reads "Check YAML Examples (anti-drift for the AUTHORING format, #13086)" and "Ruled 2026-08-29 (#13086)". - **objectstack-ai#3391.** objectui#3391 answers 200 with an unrelated subject (a record-header api action placeholder). objectstack#3391 answers 200 as the apiMethods whitelist contract card ("跟踪:UI 操作按钮与 apiMethods 白名单一致性契约落地"), and objectstack#3720's own title calls itself "objectstack-ai#3391 遗漏的第四个面". - Every edited changeset is pending: it is present in `.changeset/` on `main`. The checkout is not shallow. ## Census (the enumeration pin for this batch) The instrument PR objectui#10854 printed and PRs objectui#10869 / objectstack-ai#10875 / objectstack-ai#10892 reused, with this batch's 23 numbers substituted (REF = a commit or tree): ``` git grep -nE '(objectui#|#|issues/)(8072|8127|8137|8204|8229|8248|8307|8408|9231|9241|9244|9365|9373|9375|9542|9553|9585|10117|10119|10120|10129|10132|14026)([^0-9]|$)' REF -- '.changeset/*.md' 'packages/*/src/**' ':!**/__tests__/**' ':!**/*.test.*' ':!**/*.spec.*' ':!**/test/**' ':!**/tests/**' | grep -v 'objectstack#' | wc -l ``` - REF = `9f0c84a44` (branch point): **104** lines. - One more line is hidden by the `grep -v 'objectstack#'` filter: `9943-viewtype-totals-page-row-retired.md` names objectui#8127 beside an `objectstack#` citation. - So the true population is **105** lines: 28 changeset lines in 26 files, and 77 src lines in 42 files. - Unfiltered, REF reads 111. The other 6 lines are live `objectstack#14026` lines. - REF = `2b3d2061a` (this head): **0**. Unfiltered it reads 7, all live: the six `objectstack#14026` lines and the re-qualified one. - This head merged with a fresh `main` (`8522396c0`, `git merge-tree --write-tree`, clean, tree `f19d17884`): **0**. REF = `8522396c0` alone: 104. - **C0**, the 19 numbers, bare and not `objectstack#`-qualified: 28 lines in 23 files at the branch point; 0 at this head. At this head C0 reads 966 distinct numbers, and above 10900 only the five CSS colours are left. - Lit control, the printed instrument over live objectui#7714 at this head: 17 lines. Hex-colour false positives (a number followed by a hex letter) at the branch point: 0. - **Out of scope, as it stands** (the 23 numbers, filtered, whole tree at this head): - 94 test lines in 36 files; - 5 `.github` lines in 1 file (`ci.yml`, objectui#9241); - 2 `apps/console` lines in 1 file (`FormPage.tsx`, objectui#8408); - 1 line of the root `vitest.config.mts`; - 0 scripts, 0 governed, 0 `CHANGELOG.md`. - For the 19 C0 numbers: 13 test lines in 10 files, and 1 line of `packages/plugin-tree/README.md`. ## Citation form - **Landing shas.** The 9-character backticked sha of the commit on `main` that landed the change the sentence rests on, as in the earlier batches. All 15 distinct objectui shas below are ancestors of `main`: `git merge-base --is-ancestor`, exit 0 each. Control legs in the same checkout: the head of PR objectui#10902 (`496c63c06`) answers exit 1, and the known ancestor `5f789538d` answers exit 0. `git rev-parse --short=9` returns the same 9 characters for each. - **Own-card pointers** in a changeset are dropped, not replaced. The configured changelog generator (`@changesets/cli/changelog`, per `.changeset/config.json`) prefixes each released entry with the hash of the commit that added the file, which is that landing. - **The claim lived only on the card.** Where the sentence rests on something that lived only on the dead card, the sha only locates it: "the card behind SHA". - **Nothing answers.** The pointer is dropped and the sentence names the card by role (objectstack-ai#9553 only). - **Sister-repo numbers.** - A bare sister-repo number becomes `objectstack#N` after reading it there. - "objectstack PR #N" becomes "PR objectstack#N", since the qualifier now carries the repository. "framework #N", "upstream #N" and "spec #N" keep their word, as batch 4 kept "framework PR objectstack#6942". - Where the objectstack pull request itself answers 404, the sentence cites its commit in that repository as objectstack `SHA`, the spelling the tree already uses for an objectstack commit ("Measured on objectstack `9bd4344e4`"). - **Runtime text** carries no sha: see **Special cases** 6. ## Mapping, the 23 family numbers Lines / files are the branch-point census for that number. "Method" is how the landing was found; for every source site, `git log -S 'objectui#N' -- FILE` names the commit that wrote the citation, and it is the landing below unless the row says otherwise. | dead number | resolution | method | lines / files | why the commit carries it | |:--|:--|:--|:--|:--| | objectstack-ai#8072 | `c974edf14`; own-card pointer dropped; runtime pointer dropped | changeset's adding commit, subject "(objectui#8072)" | 5 / 3 | it mirrors `wrapperClass` on `InputSchema`, which is what both comments and the `7722` changeset say happened | | objectstack-ai#8127 | `ca3942729`; "the card behind `ca3942729`" twice (**Special cases** 2) | `git log -S` names `ca3942729` for the first citation in all 10 source files; `05a49f2ee` (objectui#9880) and `8a7e09fa1` (the `9943` changeset's landing) wrote three later sentences that cite the same fix | 17 / 11 | it derives `ViewType` from `@objectstack/spec` instead of re-declaring it, and its message records the `page`-degrades-like-a-typo measurement the sentences cite | | objectstack-ai#8137 | own-card pointer dropped (landing `0fa7a9c83`) | changeset's adding commit | 1 / 1 | the only site is its own changeset's pointer | | objectstack-ai#8204 | own-card pointer dropped (landing `580b0fdf4`) | changeset's adding commit | 1 / 1 | the pointer opened a paragraph as its own sentence | | objectstack-ai#8229 | "a separate finding" (changeset); "the finding `8b7ea3945` reconciled" (`flex.tsx`) | `8b7ea3945`'s message: "Reconciles the third face objectui#8229 found" | 2 / 2 | the finding lived on the dead card; `8b7ea3945` is the commit that reconciled it, and it is the `7735` changeset's own landing | | objectstack-ai#8248 | own-card label dropped from the second list item (landing `d02942b0e`) | changeset's adding commit; its message covers objectui#8458 and objectui#8248 | 1 / 1 | the changeset lists the two cards its one landing closed | | objectstack-ai#8307 | `5591f03bd`; own-card pointer dropped | changeset's adding commit | 11 / 4 | it makes a lane header over a windowed fetch say `77+`, and it wrote every comment that cites the card | | objectstack-ai#8408 | own-card pointer dropped; "seam 2 of the card behind `8241a4400`" | changeset's adding commit; `8241a4400`'s message names no seams | 2 / 2 | the seam list lived on the dead card | | objectstack-ai#9231 | `383502b23`; own-card pointer dropped | changeset's adding commit | 3 / 2 | it gives the create dialog's confirm control its own accessible name, the rule both `i18n.ts` comments state | | objectstack-ai#9241 | own-card pointer dropped (landing `250429c8f`) | changeset's adding commit | 1 / 1 | the only site is its own changeset's heading | | objectstack-ai#9244 | `bd0995738` | `git log --grep`: its message names the card; it wrote all three comments | 3 / 2 | it emits one col-span class per breakpoint tier, not one for the widest | | objectstack-ai#9365 | own-card pointer dropped (landing `0970a0e00`) | changeset's adding commit | 1 / 1 | the only site is its own changeset's pointer | | objectstack-ai#9373 | `c1006ed8e`; own-card pointer dropped | changeset's adding commit | 2 / 2 | it resolves the inline locale map before the interpolation options, the `ListView` comment's subject | | objectstack-ai#9375 | own-card pointer dropped (landing `e427e9c00`) | changeset's adding commit | 1 / 1 | the only site is its own changeset's pointer | | objectstack-ai#9542 | `43c0d1710`; own-card pointer dropped; "filed as a separate card" (**Special cases** 3) | changeset's adding commit; `git log -S` names it for the `action-button` / `action-icon` comments too | 9 / 6 | it accepts and resolves an inline `I18nLabel` on `resultDialog` and makes `ResultDialogSpec` derive its label members | | objectstack-ai#9553 | nothing answers: "a separate card carried that census" | `git log --grep` finds only `40f34b4ba`, which points at the card; no commit lands it | 1 / 1 | see **Special cases** 4 | | objectstack-ai#9585 | "`ee70287e4`'s pin measures it NOT GATED"; in its own changeset, "a pin in this change measures it" | no commit names it; `ee70287e4` adds the test "NOT GATED: the renderer paints the very node the mirror refuses, without parsing it" | 2 / 2 | see **Special cases** 5 | | objectstack-ai#10117 | `4c6f549ef`; own-card pointer dropped | changeset's adding commit | 3 / 2 | it resolves a lookup title candidate in `page:header` and adds the record-key safety net both comments describe | | objectstack-ai#10119 | `73a3c89af`; own-card pointer dropped | changeset's adding commit | 4 / 2 | it makes a nav ancestor's gates reach its subtree and stops a group outliving its children | | objectstack-ai#10120 | `80c54122e`; own-card pointer dropped | changeset's adding commit; for each file `git log -S` names it, or a later commit that cites its gate: `e0f820246` (objectui#10563) or `b809375ac` (objectui#10163) | 16 / 13 | it makes a form neither submit nor offer a field the caller may read but not edit, the FLS half every site names | | objectstack-ai#10129 | `6cc910b6d`; own-card pointer dropped | changeset's adding commit | 10 / 5 | it routes a field-backed action param to its record picker and refuses an unreadable one | | objectstack-ai#10132 | `061f5e829`; own-card pointer dropped | changeset's adding commit | 8 / 4 | it makes the two declared-translatable dashboard surfaces resolve, including the axis `title` forward | | #14026 | re-qualified `objectstack#14026` | see **Premise** | 1 / 1 | it is the card the pin's measurement answered | ## Mapping, the 19 bare sister-repo numbers | number | resolution | what objectstack says | lines / files | |:--|:--|:--|:--| | objectstack-ai#11289 | `objectstack#11289` ("upstream") | "record:details sections cannot survive an empty record: `hideEmpty` / `collapsible` / `showBorder` are honoured by the renderer but undeclared" | 2 / 2 | | #11662 | PR `objectstack#11662` | "feat(spec): declare hideEmpty / collapsible / showBorder on record:details sections" | 1 / 1 | | #12616 | PR `objectstack#12616` | "feat(spec): declare record:details section headerColor as a closed six-token enum" | 1 / 1 | | #12718 | PR `objectstack#12718` | "feat(spec): retire preview mode — the RuntimeMode 'preview' value and the whole PreviewModeConfig block" | 1 / 1 | | #13033 | objectstack `c459da6bc` | the pull request answers 404; its squash commit narrows the per-option `default` key out of the form-view options vocabulary, the ruling `form-spec.ts` says was executed upstream | 1 / 1 | | #13337 | `objectstack#13337` | "docs(objectui): layout-dsl teaches only shapes the live schemas accept" | 1 / 1 | | #13086 | `objectstack#13267` | the card answers 404; PR objectstack#13267 landed its ruled YAML-examples gate (see **Premise**) | the same line | | #13413 | objectstack `89448a52b` | the pull request answers 404; its squash commit removes an inert schema export and leaves a note recording the absence as a choice, the shape the `base.zod.ts` note cites as precedent | 1 / 1 | | #13632 | `objectstack#13632` | "[spec] `FieldSchema` accepts a `lookup`/`master_detail` with no `reference` target …", the card 17.3.0's refinement answered | 3 / 3 | | #13733 | PR `objectstack#13733` | "feat(spec): wizard view v1 — declaration-and-refusal tightening of FormViewSchema type:'wizard' (Card S)" | 1 / 1 | | #13855 | `objectstack#13855` | the field-grouping decision card whose option B is a section `group` reference, landed by `39404f3d9` (#13897) "a layout section can reference a declared field group" | 1 / 1 | | #13906 | `objectstack#13906` ("framework") | "two more `computeExecCtx` seams read "failed" and "not wired" as one value …" | 6 / 3 | | #14274 | PR `objectstack#14274` | "fix(sdui-parser): refuse an authored `type` attribute on the html tier …" | 1 / 1 | | #14945 | `objectstack#14945` | "A flow cannot REFUSE with per-record text …", honoured by `cca699149` "the flow `end` node honours `outcome: 'refused'`" | 1 / 1 | | #15469 | `objectstack#15469` ("spec") | "`GanttConfigSchema` is `strictObject(...).passthrough()` …", landed as `9c270bba0` "close the gantt/tree config .passthrough() windows … (#15469)" | 2 / 2 | | #15948 | `objectstack#15948` | "fix(plugin-auth)!: session payload `positions[]` is the security axis, not the better-auth role scalar" | 1 / 1 | | #17493 | `objectstack#17493` | "three residues of #17322's node-door refusal …", landed as `2c1011b01` "refuse a blank string in a flow node's predicate slot" | 1 / 1 | | #20051 | `objectstack#20051` | "judge a flattened view overlay's top-level `options.KIND` …", whose door half is `6a4aec71d` | 1 / 1 | | #20160 | PR `objectstack#20160` | "fix(spec): a joined report refuses a top-level dataset / rows / columns / values, pointing each onto blocks[]" | 2 / 2 | The live-but-wrong number: "(`/me/permissions` `apiOperations`, objectstack-ai#3391)" becomes "… `apiOperations`, objectstack#3391)" at the two `rowCrudAffordances.ts` sites. ## Special cases (the judgement calls) 1. **#14026 is re-qualified, not dropped as an own-card pointer.** The card behind `14026-list-import-mappings-pin.md` was never an objectui card: it was objectstack#14026, now objectui#10102. Dropping the pointer would lose which hypothesis the pin refuted. Re-qualifying it matches the six sibling lines. 2. **objectstack-ai#8127, the card by role twice.** - `CreateViewDialog.tsx`: "one of the sites the card records as "drifted, …"" becomes "one of the sites the card behind `ca3942729` records as …". That record lived on the card. - `plugin-list` `ViewSwitcher.tsx`: "objectui#8127 was filed against the two in `@object-ui/types`, and the maps below were described there as total …" becomes "the card behind `ca3942729` was filed against …". - `normalize-list-view.ts`: "The bug objectui#8127 records" becomes "The bug `ca3942729` records". That commit's message carries the measurement: `page` resolved "to exactly what it resolved a typo to". 3. **objectstack-ai#9542 in `8648-ui-action-four-undeclared-keys.md`.** - The superseded paragraph keeps its pre-landing voice: "so it is filed as a separate card and ⛔ not guessed at here". - The superseding paragraph reads "`43c0d1710` landed the derivation". - "(Noted here by the objectui#9542 seat, …)" becomes "(Noted here by the seat that landed `43c0d1710`, …)". 4. **objectstack-ai#9553, nothing answers.** `base.zod.ts` said "No count of authored `events` keys is stated here — objectui#9553 carries that census." No commit landed that card. `40f34b4ba` only points at it, and the `AGENTS.md` fix `7550728a6` names a different card. So the sentence now reads "— a separate card carried that census". The census is not restated, per AGENTS.md objectstack-ai#9. 5. **objectstack-ai#9585, the measurement's instrument.** The card measured the render path NOT GATED, and no commit names it. But the commit that wrote both citing sentences, `ee70287e4`, adds a pin that re-measures exactly that: "NOT GATED: the renderer paints the very node the mirror refuses, without parsing it". - `disclosure.ts` now reads "(`ee70287e4`'s pin measures it NOT GATED)". - Its own changeset, `8236-collapsible-open-intercept-retire.md`, whose landing is `ee70287e4`, reads "(a pin in this change measures it NOT GATED)". 6. **The runtime string.** Only the listed text moves. | file | member | before | after | |:--|:--|:--|:--| | `types/src/zod/form.zod.ts` | `InputSchema.wrapperClass` `.describe()` | "Classes on the wrapper div around the input and its label (objectui#8072)" | "Classes on the wrapper div around the input and its label" | No test, doc or changeset quotes it: a whole-tree search for the old string returns only the source line. 7. **objectstack-ai#8229 in `flex.tsx`.** "(objectui#8229, folded into objectui#7735's ruling)" becomes "(the finding `8b7ea3945` reconciled, folded into objectui#7735's ruling)". objectui#7735 answers 200 and stays. 8. **#13413's sentence.** "Precedent of the same shape: objectstack#12009 / PR #13413." becomes "… objectstack#12009 / objectstack `89448a52b`." objectstack#12009 answers 404 too, but it is a qualified sister-repo number outside this batch's lists, so it is left and listed (**Acceptance notes** 1). 9. **#20160 across a line break.** In `10746-joined-report-clears-binding.md`, "(objectstack PR" ends one line and "#20160: …" opens the next. They become "(PR" and "objectstack#20160: …". ## The literal-anchor sweep (both test-pin classes, ruling `5861900779`) - **Instrument.** Every string, template, numeric and regex literal in all 4068 tracked test and script files (119016 distinct literals), parsed with TypeScript. - **Candidate filter.** A literal is a candidate only if it matches the diff's removed lines with two lines of context, raw or comment-flattened. That leaves 2839. - **Test applied to each candidate.** Does its occurrence count DROP between `9f0c84a44` and `2b3d2061a` in any of the 92 files this PR changes, in raw text or in a comment-flattened form? 229 distinct literals drop. - **Every one is a generic token.** Digits and short numbers, punctuation, single letters, `objectui#`, `objectui#1`, and whole-tree scanners such as `/#\d+/` and `/objectui#\d+/`. The three `objectui#\d+` matchers (`ActionRunner.disabledGate`, `registry-inputs-spec-parity`, `catalog-gallery-render`) assert over their own test data and read no changed file. - **No specific anchor.** None is a batch number, a changed phrase, or the changed `.describe()` string. So no test pins changed runtime text (class one), and no source-reading test pins a changed comment or docblock citation (class two). - Test titles and comments that name these numbers are out of the card's classes and stay (**Census**, out of scope). ## Held **By the serial rule: nothing.** Re-mapped before the push, on 9 open PRs: objectui#10910, objectstack-ai#10908, objectstack-ai#10907, objectstack-ai#10906, objectstack-ai#10901, objectstack-ai#10891, objectstack-ai#10777, objectstack-ai#10278 and the release PR objectstack-ai#5400 (objectstack-ai#10902 and objectstack-ai#10904 had merged since the claim). Two of them share files with this PR. Their hunks were read against their merge-bases; each file is identical at its merge-base and at `9f0c84a44`, so the lines map directly. - **objectui#10907, `types/src/zod/form.zod.ts`.** It inserts a refusal constant before `InputSchema`, two tombstone members further down `InputSchema`, and a comment in the `InputShorthandSchema` arm. This PR's three edited lines (the `wrapperClass` comment and description, and the arm's "shrank that row" comment) sit outside every one of its hunks and their 3-line context. - **objectui#10906, `metadata-admin/i18n.ts` and `previews/ViewPreview.tsx`.** Its `i18n.ts` insertions are far from the two `createDraft` comments, and its `ViewPreview.tsx` hunks are far from the `options` fold docblock. Trial merges with this head (`git merge-tree --write-tree`): - clean for objectstack-ai#10910, objectstack-ai#10908, objectstack-ai#10907, objectstack-ai#10906, objectstack-ai#10901, objectstack-ai#10891 and objectstack-ai#10777; - objectstack-ai#10278 (`eab4c8e52`) conflicts in `ObjectGrid.tsx`, `plugin-grid/README.md` and `content/docs/plugins/plugin-grid.mdx`, and conflicts identically against `9f0c84a44` alone; - objectstack-ai#5400 (Version Packages) regenerates and is not a hold. objectui#10891 shares no file with this PR. ## Changesets - `.changeset/10803-dead-citation-sweep-sixth-batch.md`, EMPTY frontmatter. It covers the comment-only edits in 15 released packages; no published behaviour changes through them. It points at the second file for `@object-ui/types`' runtime text. - `.changeset/10803-sixth-batch-runtime-strings.md`, `'@object-ui/types': patch`: the `wrapperClass` description loses its pointer. No key, path, issue code, accept set, refusal or severity moves. ## Proof of prose-only (C4), against `9f0c84a44`, on this head `2b3d2061a` - **Source.** Each of the 53 touched `.ts` / `.tsx` files was parsed at `9f0c84a44` and at this head with TypeScript 6.0.3's `createSourceFile`, and re-printed by `createPrinter({ removeComments: true })`. - 52 of 53 prints are identical. - `form.zod.ts` is equal once the one listed substitution (**Special cases** 6) is applied to the base print, matched once. - 0 parse diagnostics. - Lit controls on the same instrument: editing a string literal moves the print; re-spacing a comment does not. - **Changesets.** The frontmatter block of every one of the 37 edited changesets is byte-identical at `9f0c84a44` and this head (37 of 37, by md5). The overwrite gate below agrees. - **Scope of the diff:** 92 files, +175 / −140. That is 37 edited and 2 new changesets, and 53 non-test source files in 15 released packages. No test file. ## Gates, on this head `2b3d2061a` Each line is the gate's own verdict and exit code, captured by redirect-then-`$?`. - `node scripts/check-changeset-presence.mjs`, exit 0: "53 source file(s) of 15 released package(s) changed, and this change declares 2 changeset(s): .changeset/10803-dead-citation-sweep-sixth-batch.md, .changeset/10803-sixth-batch-runtime-strings.md." - `pnpm changeset:check`, exit 0: "All workspace packages are in the changeset fixed group." / "No changeset declares a `major` bump." - `node scripts/check-changeset-overwrite.mjs` (report-only), exit 0: "2 changeset(s) added, 37 modified, 0 deleted". `declared at base` equals `declares now` for 37 of 37. - `pnpm check:changeset-claims` (report-only), exit 0: - "Every one of those 1 address(es) either names the tree it was read from, or points at a line this change does not move"; - "Every package declared across those 31 body(ies) is either not negated …"; - the standing notice "75 pending changeset(s) describe a file this change touches". - Read against the diff: a pending changeset quoting a replaced pointer would itself carry the dead number and sit in the census, which reads 0. No pending changeset quotes the changed description. - `pnpm check:control-bytes`, exit 0: "check-control-bytes: OK (scanned 9178 tracked text file(s); skipped 85 binary)." - `pnpm check:new-line-citations`, exit 0: "VERDICT new-cross-file-line-citations: 0 new citation(s), enforcement report-only -> exit 0". - `pnpm check:pending-changeset-literals`, exit 0: "No test source names a pending changeset." - Also run over the touched comments: - `pnpm check:installed-pin-claims`, exit 0 ("OK"); - `pnpm check:comment-mask-corpus`, exit 0 (1 disagreeing file, within the ceiling objectui#7882 holds open); - `pnpm check:handler-key-reads`, exit 0 ("every judged read is a declared member of it"). - The governed-surface predicate over the 92 paths, exit 0: "NOT GOVERNED — 92 path(s) checked against 5 governed surface(s); none matched." Lit control `AGENTS.md`: exit 3. **Tests**, through the shared verify lock, on `2b3d2061a`. Each is `VERDICT command-exit 0`. - `scripts/__tests__/`, the whole directory, whose whole-tree scanners read the touched files: `Test Files 177 passed | 2 skipped (179)`, `Tests 5322 passed | 2 skipped (5324)`. The two skipped files are the network-escape fixtures that run only as a child. - `packages/types/`, the whole package, whose runtime text moved: `Test Files 264 passed (264)`, `Tests 5854 passed (5854)`. `pnpm --filter @object-ui/types type-check`, exit 0. - **The pins nearest the re-pointed text:** - in `types`: `input-wrapper-class-mirrored-8072`, `zod-mirror-parity`, `wrapper-class-declared-7722`, `zod-mirror-authors-no-defaults-7735`, `collapsible-open-refusal-8236`, `tree-view-config-readers-8253` and `layout-default-jsdoc-7361`; - in `components`: `collapsible-open-intercept-8236`, `registration-defaults-match-renderer-8229` and `action-undeclared-keys-8648`; - in `plugin-view`: `ViewSwitcher` and `ViewSwitcher.viewTypeTotalsBothLegs-9943`; - in `plugin-kanban`: `laneCountHonesty-8307`; - in `plugin-grid`: `rowCrudAffordances` and `rowCrudEffectiveOps`. - Result: `Test Files 15 passed (15)`, `Tests 381 passed (381)`. - No red leg: the sweep found no anchor to move, so there is no pin whose old copy should fail. **Declared narrowing.** NOT MEASURED locally: - the full suites and type-check of the 14 other touched packages, and eslint. - Reason: the comment-stripped syntax tree of 52 of 53 touched source files is identical to `main`, and the 53rd differs only by the listed literal. - CI runs the full farm. ## Acceptance notes 1. **A sister-repo class of the same defect: 30 `objectstack#N` citations answer 404 in objectstack.** - **Measurement.** Every distinct `objectstack#N` in the two in-scope classes at the branch point is 359 numbers. Each was read once: 328 answer 200, 1 answers 301 (objectstack#14026 to objectui#10102), and 30 answer 404, each confirmed by a second read. - **The 30:** objectstack-ai#5970 objectstack-ai#5976 objectstack-ai#6038 objectstack-ai#6124 objectstack-ai#6281 objectstack-ai#6331 objectstack-ai#6450 objectstack-ai#6483 objectstack-ai#6515 objectstack-ai#9933 objectstack-ai#9934 objectstack-ai#10354 objectstack-ai#10485 objectstack-ai#10695 objectstack-ai#11330 #11507 #11513 #11658 #11703 #11753 #11846 #12009 #12868 #13117 #13670 #16126 #17147 #17762 #17987 #18012. - **Sites at this head:** 82 lines in 63 files, 26 of them changeset lines. - **Three of them sit in sentences this PR edits, and are left as they are:** - objectstack#11846, "(objectstack#11846, landed as PR objectstack#12718)" in `6748-preview-mode-provenance-ratchet.md`; - objectstack#12009, in `base.zod.ts`'s precedent line; - objectstack#12868, in `form-spec.ts`'s "RULED 2026-08-28 (objectui#6263 / objectstack#12868, …)". - **Why left.** They were not in this batch's lists, and the class is the seat's to scope. objectstack's own card for dead tracker citations in its tree is objectstack#19123, whose landing `66e266c93` counts #12868 among the dead numbers it measured. Triage item 3 would put a dead number in these classes on this card. The fix shape measured here for such a number is the objectstack commit, as with `c459da6bc`. 2. **The rest of the bare `objectstack-ai#3391` population.** Only the two sites the claim names were re-qualified. 28 more in-scope lines in 10 files write the apiMethods whitelist card as a bare `objectstack-ai#3391`, which resolves to the unrelated objectui#3391: - `ObjectDataPage.tsx`, `ObjectView.tsx` (app-shell); - `managedBy.ts`; - `MePermissionsProvider.tsx`, `PermissionContext.ts`, `PermissionProvider.tsx`; - `fieldWriteGate.ts`; - `ImportWizard.tsx`, `ObjectGrid.tsx`; - `ListView.tsx`. It is live, not a 404, so it is outside the family pin. Two of those lines pair it with a bare 3546 that means objectstack#3546 ("detail/form 面的 edit/delete 按钮接入服务端 effective 操作集"), while objectui#3546 is an unrelated i18n card. Carrier: none. 3. **A stale claim beside a re-pointed sentence.** The same `base.zod.ts` paragraph says "AGENTS.md's abridged protocol sketch shows `events?: Record…` and its action-system commandment authors one". `7550728a6` removed both from `AGENTS.md`, so that sentence is now false. It is not a citation, and this PR does not touch it. Carrier: none. 4. **The C0 blind spot, for any later census.** The bare-number instrument's lookbehind hides a number written after `/`, `-`, `.` or `&` (`#13337/#13086`, `-objectstack-ai#2231`). This batch read the 17 such numbers no batch had read, and #13086 was the only 404. A later census can narrow the lookbehind to refuse only a word character, `#` or `&` before the `#`, and drop URL fragments by hand. 5. **Filenames are not citations.** Pending changeset and test FILENAMES carry several of these numbers. They stay, as in PRs objectui#10707, objectstack-ai#10797, objectstack-ai#10854, objectstack-ai#10869, objectstack-ai#10875 and objectstack-ai#10892. --- _Generated by [Claude Code](https://claude.ai/code/session_01DuWo5bdP9SdVebamn99GGk)_ Co-authored-by: Claude <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part of #10866
Clause-②: no
Slice 2 of the date-only zone family's carrier card: site 3 (
plugin-timeline), site 4 (plugin-charts) and site 6 (the@object-ui/i18ndate helpers), per triage5861646819, seat 2's release note5863305580and claim5863746430. Site 5 (coreFormulaFunctions) is measured, not edited: the measurement and a recommendation are below. The card stays open.Why
Clause-②: no: display reads of stored date-only values stop shifting a day west of UTC. No authored key, accepted document or public type moves.What changed
Every read below now takes the shared step,
toDisplayDatefrom@object-ui/core(the objectui#10183 convention). It tells the two shapes apart by the VALUE, never by a declared field type: a date-onlyYYYY-MM-DDstring is rebuilt at local midnight of the day it names, and a value with a time part keeps its instant (the engine parse).plugin-timeline.ObjectTimeline: the date bucket (startOfDay(toDisplayDate(raw))) and the sort (asortKeyovertoDisplayDate) now read alike. The vertical renderer groups ADJACENT items, so a sort that disagreed with the buckets ordered "Today" above "Overdue" for a mix of shapes. A value the shared step refuses (unparsable, or a day its month does not have) sorts with the dateless items, where it already bucketed ("No date").formatDate: theshortandlongfaces read the local-midnight value. Theisoface prints a date-only value from local getters (coretoDateInputValue), becausetoISOString()of a local midnight names the day before east of UTC; an instant keeps its UTC day. A refused value prints as written oniso, wheretoISOString()threwRangeError: Invalid time valueduring render.plugin-charts.AdvancedChartImpl'sformatTickreads the category throughtoDisplayDate. Its fallback for a localeIntlrefuses prints a date-only category from local getters and keeps an instant's UTC day (isRealCalendarDateon the category is the split). The span that picksMMM DorMMM YYYYkeeps the engine parse on purpose: it is a duration between two categories, a whole number of days for two UTC midnights, where two local midnights are an hour off across a DST change and a 62-day span would flip faces. A refused category falls through to the raw category.formatDate,formatDateTime,formatRelativeTime(utils/formatting.ts) andformatDateSpec(utils/spec-formatters.ts) parse throughtoDisplayDate.formatDateSpecappliestimeZoneto an instant only (isRealCalendarDateon the string is the split, the same test the shared step makes). A date-only value is formatted in the local zone, the only zone where the shared step's local midnight reads back as its day;toDisplayDate's own contract says to read its result with local getters or local-zoneIntlonly.formatRelativeTimereturns an unparsable value as its string, the face the other three already give, instead of throwing. It is needed here: the shared step refuses2026-02-30, which the engine used to roll.@object-ui/i18nalready depends on@object-ui/core(it re-exportsnumber-displayfrom there) andcoreimports nothing fromi18n. No cycle, and no copy of the helper.PINSofscripts/__tests__/date-only-zone-pins-10183.test.ts(plus one header sentence):ObjectTimeline.dateOnlyZone-10866,TimelineRenderer.dateOnlyZone-10866,AdvancedChartImpl.dateOnlyZone-10866andformatting.dateOnlyZone-10866. Each runs underAmerica/Los_AngelesandAsia/Shanghai, each zone opens with a rig case and a fixture-validity case, and each carries an instant control. Suite-zone cases run in the normal run too.packages/plugin-timeline/tsconfig.test.jsonnamesnodetypes for the pins'process.env(TypeScript 6 includes no@typesby default;packages/plugin-calendar/tsconfig.test.jsonnames it for the same pins).5864479592item 1; claim amended at5864501516).apps/console/vite.config.ts: thei18n-runtimemanual-chunk group takesincludeDependenciesRecursively: false. This slice givespackages/i18nits first runtime import of@object-ui/core,i18n-runtimeoutranksframework(83 over 80), and rolldown's default recursive capture followed the import and wroteframework's declared members intoi18n-runtime, which turnedBundle Analysis's membership half red. The flag is the objectui#9345 repair the config'sdata-adapterparagraph documents; the group's new comment records the circular-chunk re-check that paragraph asks for (readings below).scripts/__tests__/check-eager-closure-budget.test.tspins it: thedata-adapteroptions case is now one case per group,data-adapterandi18n-runtime, each asserting it outranksframeworkand declares the flag.toDisplayDatekeeps its one home in core; nothing is copied into i18n.content/docs/plugins/plugin-timeline.mdx("Date Formatting") and one inpackages/i18n/README.md("Formatting Utilities")..changeset/10866-timeline-charts-i18n-date-only.md:patchfor@object-ui/plugin-timeline,@object-ui/plugin-chartsand@object-ui/i18n. Fix round 2 extends its gantt sentence (review item ③a): the variant's axis headers, extent and bar positions are unchanged, so west of UTC its bar tooltip now names the stored day while the axis above it still reads the day before, until a later slice. The console chunking change moves no published file, so it needs no declaration (check-changeset-presencecounts the same 9 source files of 3 released packages).Readings, base
b8e09415cagainst head, in both zonesMeasured by a throwaway harness on the forks pool with the pins' own fixtures, once over the base sources and once over head (the harness file was deleted; the pins hold the same values).
Timeline, clock
2026-10-06T12:00Z("today" is October 6th in both zones),en-US:2026-10-06and2026-10-072026-10-06and instant2026-10-06T04:00Zshort/long,2026-10-06iso,2026-10-06iso,2026-02-30Chart x-axis ticks,
en-US:2026-09-01,2026-09-022026-09-01,2026-12-012026-09-02T03:00Z,2026-09-03T03:00Z2026-02-28,2026-02-30The two fallback rows are green on base by construction: the old parse was UTC, so its
toISOString()was right. They are the half a parse-only repair breaks east of UTC; see the second ablation below.i18n helpers, clock 10:00 on August 30th local in each zone,
en-US:formatDate('2026-09-01')formatDateTime('2026-09-01')formatRelativeTime('2026-09-01')formatDateSpec('2026-09-01', medium)timeZone: 'America/New_York'formatDate('2026-09-02T03:00:00.000Z')(instant)formatDate('2026-02-30')formatRelativeTime('not a date')The Shanghai
formatDateTimerow moves on the time only (8:00 AM to 12:00 AM): the day was already right there, and a date-only value is now midnight of its day in every zone.Tests and gates
Fix round 2, at head
52f4d10d052f4d10d0: all 43 check-runs completed, 40 success, 3 skipped, 0 failed.Bundle Analysissuccess (run36386759427); its budget comment5864690342reads PASS, eager closure 3095.7 KB of 3104.5 KB.Bundle Analysisreproduced locally first. Console build under os-verify-lock (cd apps/console && pnpm exec vite build; the gate reads only that step's reports, so the packagetscandbuild:pluginsteps were not run), thennode scripts/check-eager-closure-budget.mjs:8559187c4, before the flag: exit 1, byte halves green (3096.3 KB of 3104.5 KB), membership red: "packages/coreis declared inframeworkbut 54 ini18n-runtime(27 of its 81 modules landed inframework)" and "packages/types...packages/types/src2 ini18n-runtime". The reviewer's mechanism holds; the capture is 54 modules of core's barrel slice, not two.52f4d10d0: exit 0, every half green: "Console eager closure is 3095.5 KB gzipped across 329 of 2445 chunks (budget: 3104.5 KB, headroom: 9.0 KB)"; membershippackages/core81 modules inframework,packages/types13 inframeworkand itssrc/zodsubtree 9 intypes-zod.main9f0c84a44in a separate worktree: exit 0, 3095.6 KB across 329 of 2445 chunks.data-adapterparagraph asks a new taker of the flag to): on both builds of this branchframeworkandi18n-runtimeimport each other, flag or no flag; onmaini18n-runtimeimports noframeworkchunk, anddata-adapterandframeworkimport each other there already. So the cycle comes with this slice's i18n-to-core import, not with the flag, and it has the shapedata-adapteralready has. The flagged build's JS chunk names matchmain's one for one (2445 each, empty diff). The builti18n-runtimechunk imports oneframeworkbinding and reads it only inside theformatRelativeTimefunction body, never at module evaluation. Browser smoke:vite previewof the flagged build and of themainbuild, each loaded in Chromium (Playwright): the sign-in page rendered with 0 page errors, and each logged 12 console errors; the eight the probe printed for each build are the same failed resource loads with no backend running (502, one 404). Both preview servers were stopped by their recorded PIDs.scripts/ablation-replace.mjs, wrap mode, thei18n-runtimeanchorpriority: 83, includeDependenciesRecursively: false },replaced bypriority: 83 },, counted 1 to 0, blob3e9a3b88d4c6todf2d1a47a29f): exactly the newi18n-runtimerow red,Tests 1 failed | 177 passed (178); restored, blob equal to HEAD,git diff HEADempty.scripts/__tests__suites whose corpus holdsapps/console/vite.config.ts, run by name (check-changeset-presence,check-eager-closure-budget,console-vite-alias-closure-4925,cross-file-line-citation-census,scripts-type-check,side-effects-declaration-consistency,turbo-build-inputs,turbo-lint-inputs,turbo-task-guard-coverage,turbo-test-inputs,vite-declared-lazy-views,vite-ineffective-dynamic-imports,vite-objectstack-client-dist,vite-objectstack-spec-dist,vite-types-zod-lazy,vitest-config-alias-targets-3944,vitest-config-type-check):Test Files 17 passed (17),Tests 945 passed (945). Everyscripts/__tests__suite:Test Files 177 passed | 2 skipped (179),Tests 5327 passed | 2 skipped (5329).pnpm exec vitest run packages/plugin-timeline/ packages/plugin-charts/ packages/i18n/ scripts/__tests__/date-only-zone-pins-10183.test.ts:Test Files 193 passed (193),Tests 2576 passed | 40 skipped (2616). Each VERDICT command-exit 0.type-checkechotsc --noEmit && tsc -p tsconfig.test.jsonandDone;pnpm type-check:scriptsandpnpm type-check:vitest-configexit 0 (VERDICT command-exit 0).check-changeset-presence(the same 9 source files of 3 released packages, 1 changeset),-no-major,-fixed,-overwrite,check-pending-changeset-literals,check-control-bytes,check-new-cross-file-line-citations(0 new citations),check-governed-queue-guard --testover 16 paths (NOT GOVERNED).check-changeset-claims(report-only) adds6681-declared-lazy-marketplace-routes, which namesapps/console/vite.config.tsfor its marketplace co-tenant groups; this change does not touch them, and it stays true. On the local console build,check-eager-locale-catalogues(NOT MEASURED in round 1) andcheck-sdui-registration-pinsexit 0.apps/console/vite.config.tsandcheck-eager-closure-budget.test.ts, 0 errors and 0 warnings each, as at8559187c4.Round 1, at
8559187c4pnpm exec vitest run scripts/__tests__/date-only-zone-pins-10183.test.ts):Tests 5 failed | 13 passed (18), VERDICT command-exit 1. The 5 are the four new pin rows and the child-exit row; the 13 existing pins stayed green.Test Files 5 passed (5),Tests 28 passed | 40 skipped (68), VERDICT command-exit 0 (the 40 skipped are the zone cases, which run inside the driver's forks child).git checkout HEAD --on absolute paths): the base blobs proven on disk before the run,Tests 5 failed | 13 passed (18), then each restored blob equal to its HEAD blob andgit diff HEADempty.scripts/ablation-replace.mjs, wrap mode, both anchors counted 1 to 0 with changed blobs): the timelineisolocal-getter line deleted and the chart fallback reduced totoISOString(). Measured direction: exactly the two Shanghai rows went red (expected '2026-10-05' to be '2026-10-06';expected [ '2026-08-31', '2026-09-01' ] to deeply equal [ '2026-09-01', '2026-09-02' ]),Tests 3 failed | 15 passed (18); every LA row stayed green. Both files restored, blob equal to HEAD,git diff HEADempty.pnpm exec vitest run packages/plugin-timeline/ packages/plugin-charts/ packages/i18n/ scripts/__tests__/date-only-zone-pins-10183.test.ts,Test Files 193 passed (193),Tests 2576 passed | 40 skipped (2616), VERDICT command-exit 0. The i18n suite includes the objectui#9909 machine-locale census.scripts/__tests__gate (os-verify-lock,pnpm exec vitest run scripts/__tests__/ --maxWorkers=2, at head8559187c4):Test Files 177 passed | 2 skipped (179),Tests 5326 passed | 2 skipped (5328), VERDICT command-exit 0.--filter 'PKG^...'for each of the three packages, VERDICT command-exit 0);pnpm --workspace-concurrency=2 --filter @object-ui/plugin-timeline --filter @object-ui/plugin-charts --filter @object-ui/i18n run type-checkechoestsc --noEmit && tsc -p tsconfig.test.jsonandDonefor each;pnpm type-check:scriptsexit 0.--listFileson each test program lists the new pins (2, 1, 1).check-changeset-presence(9 source files of 3 released packages, 1 changeset),-no-major,-fixed,-overwrite,check-pending-changeset-literals,check-new-cross-file-line-citations(VERDICT new-cross-file-line-citations: 0 new citation(s)),check-control-bytes,check-unreferenced-sources,check-test-path-roots,check-vi-mock-specifiers/-inherit/-override-shape,check-phantom-dependencies,check-unused-dependencies,check-i18n-call-site-keys,check-i18n-en-drift,check-i18n-dead-keys,check-doc-fence-languages,check-doc-links,check-package-self-import,check-governed-queue-guard --testover the 14 paths (NOT GOVERNED). A control-byte self-scan over the changed files: no hits.check-changeset-claims(report-only) names three pending changesets that cite a touched file:7546-chart-series-keys-declared(series keys inAdvancedChartImpl.tsx),8632-malformed-picklist-option-loudand9615-locale-count-ten(both citepackages/i18n/README.mdsections this change does not touch). Each read; none becomes false.eslint.config.jswith--no-inline-config --format jsonover the 10 changed code files (10 results in the JSON): 0 errors; the three modified sources keep their base warning counts, measured with--stdinon the base blobs (AdvancedChartImpl.tsx44,ObjectTimeline.tsx28,renderer.tsx14); the new files and the driver 0. The config sets noparserOptions.projectorprojectService, so the rules are not type-aware and this diff cannot move any untouched file's verdict.check-readme-exportsandcheck-doc-snippet-types(prerequisite: every package built; this change adds prose only, no fenced block, to the README and the doc);check-eager-locale-catalogues(prerequisite: a console build; measured in fix round 2, above). CI builds and runs them.Site 5,
FormulaFunctions: measurement only, no editMeasured with
@objectstack/formula17.4.0, the version installed here, and read against objectstackpackages/formula/src/stdlib.tsand ADR-0053 D1; process zoneAmerica/Los_AngelesandAsia/Shanghai,nowpinned at2026-09-28T05:30Zand2026-09-28T20:00Z.TODAY()orDATEADDby those names; the equivalents aretoday(),daysFromNow(n),addDays(d, n),addMonths(d, n)anddaysBetween(a, b). A calendar day is aDateat UTC midnight of that day (ADR-0053 D1), a date-only string hydrates to UTC midnight, arithmetic runs in UTC,addMonthsclamps to the month's last day, andtoday()is the calendar day inEvalContext.timezone(default UTC) as UTC midnight. No result depends on the process zone. For a CEL default on adatefield the engine stores such a result as its UTC day (objectqlnormalizeExpressionDefaultthroughresolveNowDefault).today()at 05:30Z:2026-09-28T00:00Zwith the zone unset or Shanghai,2026-09-27T00:00Zwith Los Angeles; at 20:00Z,2026-09-29T00:00Zwith Shanghai.addDays('2026-09-01', 1):2026-09-02T00:00Zeverywhere;addDays('2026-11-01', 1):2026-11-02T00:00Z;addMonths('2026-01-31', 1):2026-02-28T00:00Z.FormulaFunctions.TODAY()is the UTC day asYYYY-MM-DD(2026-09-28in both zones at both clocks), so it agrees with the server only while the reference zone is UTC.DATEADDparses the UTC midnight, moves it with LOCAL setters and returns an instant string:DATEADD('2026-09-01', 1, 'day')gives2026-09-02T00:00:00.000Zin both zones (agrees);DATEADD('2026-11-01', 1, 'day')in LA gives2026-11-02T01:00:00.000Z, andDATEADD('2026-03-08', 1, 'day')in LA gives2026-03-08T23:00:00.000Z(the server:2026-11-02and2026-03-09at midnight UTC);DATEADD('2026-09-01', 1, 'month')in LA gives2026-10-02T00:00:00.000Z(Shanghai and the server: October 1st);DATEADD('2026-01-31', 1, 'month')gives2026-03-03T00:00:00.000Zin every zone, UTC included (the server clamps to February 28th);DATEFORMAT('2026-09-01', 'YYYY-MM-DD')gives2026-08-31in LA;DATEDIFF('2025-12-31', '2026-01-01', 'year')gives 0 in LA and 1 in Shanghai and UTC.toDisplayDate) then reads as an instant, a day early west of UTC.addMonthsdoes), format with UTC getters, and hand a date-only argument back asYYYY-MM-DD(the spec's calendar-day stored form) and an instant as an instant. ONE thing needs a statement, because the server takes it from a context the client does not have: the zoneTODAY()uses in the browser. Proposed wording for the seat: "ADR-0053's compute-tz axis covers client-evaluated formulas:TODAY()in@object-ui/corenames the calendar day in the same reference timezone the server'sEvalContext.timezoneresolves for that user, and UTC when none is available to the client." Recommended because ADR-0053 putstoday()on the compute-tz axis (execution context), not the render-tz axis (the viewer), and a client formula that disagrees with the server's saved answer is the worse split; the cost is thatTODAY()keeps disagreeing with the viewer's own "today" (the timeline's buckets) until that timezone reaches the client.Acceptance notes
toISOString()").generateTimeScaleHeaders,calculateDateRange,calculateBarDimensions, thefindUnusableGanttDatevalidity gate and the min-over-max inversion guard still use the engine parse, andemptyGanttDateRange(the empty plan's axis) still takes today as the UTC day (new Date().toISOString().split('T')[0]), not the viewer's. Measured on head:generateTimeScaleHeaders('day', '2026-10-05', '2026-10-07', 'en-US')reads Oct 4, Oct 5, Oct 6 in LA (Oct 5, Oct 6, Oct 7 in Shanghai);'month'over2026-10-01to2026-12-31reads Sep 2026, Oct 2026, Nov 2026 in LA. The composed timeline refusesvariant: 'gantt'(objectui#6655), so only authored rows reach it;examples/schema-catalog/src/schemas/plugin-timeline/gantt-style-timeline.jsonauthors date-only rows. Left for a later slice of this card: routing it means the validity gate refuses a day its month does not have and the datetime axis labels move to the viewer's day, two decisions of their own. The bar tooltip on that variant usesformatDate, so it now reads the stored day while the headers and bar positions do not: west of UTC a header can read Oct 4 over a bar whose tooltip says 10/5/2026. The changeset says so (fix round 2).packages/app-shell/src/utils/relativeTime.ts(timeAgo, for notification and activity rows) callsformatRelativeTimewith epoch milliseconds from an instant, which never takes the date-only arm. Its behaviour does not move.formatRelativeTimestill counts from now to an instant, now local midnight for a date-only value: at 01:00 on August 31st,2026-09-01reads "in 23 hours" (derived, not measured), which is what a UTC viewer always read at 01:00 UTC. Calendar-day phrasing is a separate decision.formatDateSpecwith atimeStyleand a date-only value prints midnight in the viewer's zone (and, forlongorfull, that zone's name).Serial
b8e09415cat 04:59:24Z, two minutes after the claim. This branch was fast-forwarded onto it before any edit, andplugin-charts/src/ChartRenderer.tsxandplugin-timeline/src/useTimelineTranslation.tsare not touched, so nothing near its hunks had to be left.packages/i18n/src/locales/*; this PR touches no locale file.git merge-tree --write-treeof head52f4d10d0againstmain8522396c0: clean (exit 0); nothingmaingained since the branch base touches these 16 paths.Implemented by the dev agent for
domain:uiseat #1, sessionhttps://claude.ai/code/session_01DuWo5bdP9SdVebamn99GGk.Generated by Claude Code