fix(plugin-calendar,plugin-gantt): show a stored date-only day on that day and write a date field as the calendar day (objectui#10866, sites 1 and 2)

[objectstack-fleet]

Part of #10866

Clause-②: no
Every read goes through the existing toDisplayDate, and a write to a date field sends the spec's own YYYY-MM-DD storage form. No declared key, export or accept set moves. @object-ui/types changes one description string.

What changed

This is slice 1 of the date-only zone family's successor card: sites 1 and 2, per triage 5861646819 item 1. It covers the calendar and the gantt, and in each plugin the reads and the writes change together. Sites 3 to 6 are later slices, listed under Acceptance notes.

Reads: every stored date-only value now goes through toDisplayDate from @object-ui/core. That function reads a date-only value at local midnight of the day it names. A value with a time keeps its instant.

• plugin-calendar ObjectCalendar: the event start and end.
• plugin-calendar calendar-view renderer: each event's start and end, and the authored currentDate (resolveAuthoredCurrentDate).
• plugin-gantt ObjectGantt: the task start and end, and baselineStart / baselineEnd (new helper readTaskDate).
• plugin-gantt GanttView: a marker's date, in both the zoned markers memo and resolvedMarkers, and the inline editor's committed start and end.

Writes: a date field is written as the calendar day. This covers the calendar drop (handleEventDropDefault), the calendar quick-create (submitQuickCreate) and the gantt drag (handleTaskUpdateDefault).

• A field declared date is written as the local calendar day yyyy-MM-dd, using core's toDateInputValue.
• Any other declared type (datetime) keeps toISOString().
• With no object schema to ask, the stored value's own shape decides (isRealCalendarDate). That is the same split the read makes, so the read and the write cannot disagree.
• A quick-create has no stored value, so on a field with no declared type it still writes the instant.
• New private helper toStoredDateValue, one in each plugin.

The gantt timeZone. The card asked for a decision on tzShift's treatment of a date-only value. The decision: a date-only day stands on that day of the chart's own calendar, for every viewer, and a drop writes the day of the chart's calendar it landed on.

• GanttView re-bases every Date it is handed into the business zone, and translates every emitted change back.
• ObjectGantt therefore hands it the instant that re-bases onto the named day's local midnight (readTaskDate). It reads a drop back through the same shim before taking the local day (toStoredDateValue).
• A date-only marker is placed on its day and is not re-based.
• With no timeZone both halves are the identity. That is the showcase's case and every chart's default.
• Two alternatives were not taken:
  • A per-task "this is a day" flag on GanttTask would widen an exported type (a public face, Clause-② yes).
  • Leaving days re-based like instants puts the bar on the previous day for any viewer east of the chart's zone.

The gantt working calendar (skipWeekends / holidays, scheduling.ts). The scheduler floored to UTC midnight and keyed days with getUTCDay / toISOString(). That only agreed with a date-only value while the value was read as UTC midnight.

• It now floors to local midnight and steps by calendar day. It keys days the way GanttView's own column fold (isWorkingColumn) already did.
• Left on UTC, a rescheduled successor landed a day early in every zone except UTC (see H1).

Also moved:

• makeTzShift moved unchanged out of GanttView.tsx into a new plugin-gantt/src/tzShift.ts, and GanttView re-exports it. The reason is that ObjectGantt now calls it, and the ObjectGantt suites replace ./GanttView with a probe (vi.mock('./GanttView', …)). Imported from there, it was undefined in each of those suites: the first full run went red with No "makeTzShift" export is defined on the "./GanttView" mock.
• Two ObjectGantt.test.tsx cases pinned the defect. They expected a drag to write 2024-02-01T00:00:00.000Z into a field declared date (on the api provider, a field stored as 2024-01-01). They now expect 2024-02-01. Both carry a comment saying so.
• @object-ui/types: the holidays JSDoc and its zod .describe() said the keys were UTC days. This change made that false, so both now say calendar days on the chart's own calendar. This is an in-place fix under the bounded exemption:
  • It is the same defect class, a one-phrase fix.
  • No open PR touches objectql.ts or objectql.zod.ts. I read the open-PR file lists at 2026-09-28T02:18Z and again at 03:11Z; the only file hit anywhere near this change is the release PR's CHANGELOGs.
  • It uses the same gate family.
  • The changeset names @object-ui/types as a patch for it.

Fix round 1, at 687890effa. CI on 8ac7b62270 went red in Test (shard 7/8) on the objectui#9909 locale census (machineLocaleCensus-9909.test.ts). The contract review on that commit asked for three more changes.

• The census entry follows the shim. Moving makeTzShift also moved a DECLARED site: tzOffsetMs's en-US formatToParts parser, which never renders text. The census reported GanttView.tsx · new Intl.DateTimeFormat('en-US', { — declared 1, found 0 and an undeclared [en-US] site in tzShift.ts. That DECLARED entry now names packages/plugin-gantt/src/tzShift.ts. Its expression, count (1), verdict and reason are unchanged. The root vitest.config.mts comment that cited tzOffsetMs by its file is re-pointed the same way.
• Literal-anchor sweep of the move. I grepped tests, scripts and ledgers for GanttView.tsx together with makeTzShift, tzOffsetMs or Intl.DateTimeFormat('en-US'. The census entry and that config comment were the only hits. The other GanttView.tsx ledgers (residue-namespaces-3546, gantt-count-interpolation-4157, check-i18n-call-site-keys.mjs) name i18n keys and union types, which did not move.
• GanttViewProps.workingCalendar (exported). Its JSDoc still said holidays were UTC keys. It now says they are calendar-day keys read on the chart's own calendar: the viewer's, or the business timeZone's when one is set.
• Other UTC working-day rule sites. I swept plugin-gantt, plugin-calendar, types, content/docs and skills for UTC wording about holidays, weekends or working days. Two more encoded the retired rule, and both now read the local day:
  • scheduling.test.ts's weekend count (getUTCDay). It is equivalent under the suite's pinned TZ=UTC.
  • packages/plugin-gantt/scripts/verify-phase6b.mjs's weekend-start check. This is a manual Playwright script, not run by CI; its browser context sets no timezoneId, so the page and the script share one zone.
• Changeset. The Writes bullet now ends: a calendar quick-create has no stored value, so there it still writes the instant. The frontmatter is byte-identical.
• Files this round: packages/i18n/src/__tests__/machineLocaleCensus-9909.test.ts, vitest.config.mts (comment), packages/plugin-gantt/src/GanttView.tsx (JSDoc), packages/plugin-gantt/src/scheduling.test.ts, packages/plugin-gantt/scripts/verify-phase6b.mjs and .changeset/10866-calendar-gantt-date-only-days.md.

H1 and H2

H1, measured on base. The new pins were added over the base source (b93e245f9, source unchanged) and run in the objectui#10183 driver's forks child. Controls, west = America/Los_Angeles, east = Asia/Shanghai:

• Calendar, west. 2026-10-05 sat in the October 4, 2026 cell. A two-day move wrote '2026-10-07T00:00:00.000Z'. A quick-create on the 12th wrote '2026-10-12T07:00:00.000Z'.
• Calendar, east. The read was already right. A move wrote '2026-10-07T00:00:00.000Z'. A quick-create on the 12th wrote '2026-10-11T16:00:00.000Z', which names the 11th.
• calendar-view, west. currentDate: '2026-11-01' opened on October, and 2026-11-05 sat on the 4th.
• Gantt reads. The task start read as year, month, day, hour [2026, 10, 4, 17] west and [2026, 10, 5, 8] east.
• Gantt writes. A drag wrote toISOString() instants into both date fields.
• Zoned charts. A west viewer of a chart zoned Asia/Shanghai got the bar at [2026, 10, 5, 8]. An east viewer of a chart zoned America/Los_Angeles got [2026, 10, 4, 17].
• Markers. A 2026-10-05 marker stood 32 px (west) and 37 px (east) off the edge of a bar starting that day.
• Inline editor. A typed 2026-10-07 was committed as [2026, 10, 6, 17] west and [2026, 10, 7, 8] east.
• Working calendar. A successor of a Friday task landed at [2026, 10, 11, 17] (a Sunday) west, and at [2026, 10, 9, 8] (the Friday itself) east.
• datetime controls, green on base and on head. The instant 2026-10-06T04:00:00.000Z sits on its local day in each zone. A two-day move writes 2026-10-08T04:00:00.000Z in both zones, and a gantt drag keeps the instant.

H2, the census. It covers the non-test sources of both plugins, searching for new Date(, toISOString( and Date.parse(. Neither plugin imports a date-fns parse. Each site is classified by the field it serves.

Date-only (a stored Field.date value, or an authored day). All are fixed here:

• ObjectCalendar: event start and end; drop patch; quick-create payload.
• calendar-view renderer: event start and end; currentDate.
• ObjectGantt: task start and end; baselines; drag patch.
• GanttView: marker date, 2 sites; inline editor start and end.
• scheduling.ts: the UTC day key and the UTC floor.

Datetime, or not a stored value, and so left as is:

• ObjectGantt: the tooltip's datetime sniff, which is a validity check on a datetime-shaped string. The new Date() placeholder for a date-less record. The lockedRange min/max copies.
• CalendarView: every new Date(x) copies a Date. Its props are typed Date, and the day math uses local getters and multi-argument constructors.
• GanttView: the tzShift shim, now(), copies and arithmetic. The startDate / endDate props are typed Date.
• calendar-view renderer: the registry's sample events (demo data built from new Date()).
• ResourceWorkload, shifts.ts, and the rest of scheduling.ts: copies and millisecond arithmetic.
• ObjectCalendar: the clock (useState(new Date()), handleCreate).

Pins and ablation

Five new pins, registered in the objectui#10183 driver's PINS.

• ObjectCalendar.dateOnlyZone-10866.test.tsx: the read cell, a two-day move and a quick-create, with datetime controls.
• calendarViewRenderer.dateOnlyZone-10866.test.tsx: events and currentDate.
• ObjectGantt.dateOnlyZone-10866.test.tsx: reads with baselines, the drag payload, and a zoned chart read and written, with datetime controls.
• GanttView.dateOnlyZone-10866.test.tsx: markers, unzoned and zoned, and the inline editor.
• scheduling.dateOnlyZone-10866.test.ts: the weekend and a holiday.

How the pins run:

• Each zone opens with a rig case.
• The suite-zone cases also run in the normal run. They assert the written shape, which UTC can tell apart.

Red on base, green on head. On base the driver gave Tests 6 failed | 8 passed (14): all 5 new pin rows plus the child-exit row, and the 8 existing pins stayed green. The failed cases were:

• every date-only read case, west, plus the east gantt read and markers;
• every date-only write case, both zones;
• both zoned-chart cases;
• both inline-editor cases;
• all 4 working-calendar cases.

The rigs and the datetime controls passed.

Ablation (read routing reverted), at f9ae4ebd7b. I committed first, then used ablation-replace.mjs --hold with 10 anchors, each asserted x1 → x0 with a changed blob. They set every read above back to new Date(…): 2 in ObjectCalendar, 3 in the calendar-view renderer, 1 in readTaskDate, and 4 in GanttView. No dist is involved: the vitest root config resolves @object-ui/* to src, and the plugin files are imported relatively. The driver went Tests 5 failed | 9 passed (14).

• Red: the calendar read (west), the calendar-view read (west), the gantt read in both zones, both zoned-chart cases, and all 4 marker cases and both inline-editor cases.
• Green: every pure write case, meaning the gantt drag onto the 7th in both zones, all quick-creates, and the calendar east move. All datetime controls and the working calendar also stayed green.
• One write row reddened, as a cascade: the west calendar move. It moves the event two days from the cell it was drawn in, so with the read reverted it wrote '2026-10-06'. That is still a day, not an instant, just one day early.
• Restore. Each file was restored with git checkout HEAD -- to its HEAD blob (68688411c93a, 26454aa22622, 266f62c9ecdb, 257811400efc), and git diff HEAD was empty.

Gates

Fix round 1, at 687890effa.

• Census red reproduced first, at 8ac7b62270 under the verify lock: Tests 2 failed | 5 passed (7), with exactly the two CI messages.
• The census, now green. Run under the lock with the zone-pin driver and the 12 script pins that read vitest.config.mts: Test Files 16 passed (16), Tests 566 passed (566). The census alone gives Tests 7 passed (7).
• plugin-calendar + plugin-gantt, under the lock: Test Files 137 passed (137), Tests 974 passed | 44 skipped (1018). That run does not include the driver, which ran in the census run above.
• Gates, each exit 0: check-changeset-presence / -no-major / -claims / -fixed / -overwrite, check-pending-changeset-literals, check-new-cross-file-line-citations (0 new citation(s)), check-control-bytes and check-unreferenced-sources. check-governed-queue-guard --test over the 20 changed paths answers NOT GOVERNED.
• ESLint, narrowed: the 5 files this round touched. 0 errors, and each file's warning count equals its count at 8ac7b62270.
• NOT MEASURED: type-check, this round. The re-created worktree has no built dependency closure. The round's type-level change is getUTCDay to getDay in one test; the rest is comments, one JSDoc and a string path. CI's Type Check covers it.

Round 0. The gates and ESLint ran at 8ac7b62270; the type-check and the two package-suite runs name their own commit.

Type-check, at 3587ab1a02. First the closure (pnpm --workspace-concurrency=2 --filter '@object-ui/plugin-calendar^...' --filter '@object-ui/plugin-gantt^...' run build: lock verdict command-exit 0). Then pnpm --workspace-concurrency=2 --filter @object-ui/plugin-calendar --filter @object-ui/plugin-gantt --filter @object-ui/types run type-check:

• each package echoes its type-check$ tsc --noEmit … && tsc -p tsconfig.test.json and prints Done;
• pnpm type-check:scripts exits 0;
• the gantt test project was re-run after the last commit, tsc -p tsconfig.test.json --noEmit, exit 0.

The test tsconfigs include src/**/*.test.ts(x).

Suites.

• At 3587ab1a02: pnpm exec vitest run packages/plugin-calendar/ packages/plugin-gantt/ scripts/__tests__/date-only-zone-pins-10183.test.ts gave Test Files 138 passed (138), Tests 988 passed | 44 skipped (1032). The 44 skipped are the new zone cases, which run in the driver's child.
• packages/types/ gave Test Files 257 passed (257), Tests 5482 passed (5482).
• The last commit only types the gantt pin. After it, the driver, the five pins, ObjectGantt.test.tsx and GanttView.tzshift.test.ts gave Test Files 8 passed (8), Tests 64 passed | 44 skipped (108).

Gates, each exit 0.

• check-changeset-presence, -no-major, -claims, -fixed and -overwrite.
• check-pending-changeset-literals.
• check-new-cross-file-line-citations, which prints VERDICT new-cross-file-line-citations: 0 new citation(s).
• check-control-bytes, check-test-path-roots, and check-vi-mock-specifiers / -inherit / -override-shape.
• check-phantom-dependencies, check-unused-dependencies and check-unreferenced-sources.
• check-governed-queue-guard --test over the 16 changed paths answers NOT GOVERNED.

ESLint, narrowed. The repo-wide run belongs to CI.

• What was run: the root eslint.config.js with --no-inline-config --format json over the 15 changed code files; the JSON holds 15 file results.
• Result: 0 errors. Each modified file's warning count equals its base count (via --stdin on the base blob): ObjectCalendar 31, the calendar-view renderer 1, GanttView 12, ObjectGantt 84, ObjectGantt.test.tsx 30, scheduling.ts 0, objectql.ts 34, objectql.zod.ts 1, the driver 0. The new files have 0 each.
• Why narrowing is safe: the config sets no parserOptions.project or projectService, so it is not type-aware and this diff cannot move a verdict on an untouched file.

Pending changesets. I read every pending changeset that names a file or symbol this change touches. check-changeset-claims lists 35 by file. None states the behaviour changed here: date reads, instant writes, UTC holiday keys, or the zone shim. No note is owed.

Serial

• Claim. The earliest live Claim: on the card is 5861874880 (seat 2, this PR). A later claim, 5861881966 (seat 4, site 1 only), names branch claude/issue-10866-calendar-date-only. That branch did not exist on the remote when this one was cut, and nothing here touches it.
• Open PRs. At 2026-09-28T02:18Z and again at 03:11Z, no open PR touched packages/plugin-calendar, packages/plugin-gantt, packages/types/src/objectql.ts, packages/types/src/zod/objectql.zod.ts or the zone-pin driver, apart from the release PR's CHANGELOG and package.json lines.
• Merge order. The next slices of finding(plugin-calendar,plugin-gantt,+): a stored date-only day shows as the day before west of UTC in six readers, and the calendar and gantt write it back as a UTC instant — the date-only zone successor closure card #10866 register in the same PINS list, so they are serial after this PR.

Acceptance notes

#10866 remains open; sites 3 to 6 are later slices.

• plugin-timeline: ObjectTimeline.dateBucket, the sort, the renderer's formatDate default face and the axis extent.
• plugin-charts: AdvancedChartImpl.formatTick and its toISOString() fallback.
• Core FormulaFunctions: DATEADD / DATEDIFF / DATEFORMAT against TODAY() / NOW(). Triage requires one zone decision, measured against the server formula engine.
• The i18n helpers: formatDate, formatDateTime, formatRelativeTime and formatDateSpec.

Observed, not filed. Each is a read-only inference, not measured.

• Calendar drop across a DST change. CalendarView's move adds the millisecond delta between two local midnights to the event's start. Suppose an event starts on the 25-hour day (the first Sunday of November, west), and is grabbed from a later cell of its span. The new start then lands at 23:00 of the day before the target, and a date field is written as that day. This is pre-existing arithmetic: a datetime event moves by an hour on the same path.
• Business-zone day placement near DST. It inherits makeTzShift's per-instant offsets, which the shim documents as close rather than exact near a DST transition in either zone.
• Date-only end is exclusive. A date-only gantt end reads as that day's start, so the bar ends where the end day begins. This is unchanged by this PR.

Written by the domain:ui#2 dispatch, session https://claude.ai/code/session_014mXUNuFomfj24w7s1pZzhN.

---

Generated by Claude Code

[github-actions]

changeset-claim-re-read

⚠️ 37 pending changeset(s) describe a file this change touches

Their bodies publish verbatim into the CHANGELOG at the next release, so this is a request to re-read them against your diff — addressed here because you are the one seat that can answer it without re-deriving anything.

⛔ Nothing here blocks, and nothing here is a verdict on your change. This gate exits 0, is not a required context, and judges name resolution, never meaning: it asked whether a pending body names a file you touched. "Is this sentence still true?" is the one question it will not answer, and the one you are being asked to answer.

.changeset/5903-objectgantt-declared-keys.md

• names packages/types/src/objectql.ts → packages/types/src/objectql.ts — edited by this change

  Both halves move together. The TS declaration (packages/types/src/objectql.ts) and its zod mirror (src/zod/objectql.zod.ts) gain the same ten keys at the same requiredness — all optional — and no KnownDrift entry is added. navigation is taken from @objectstack/spec's NavigationConfigSchema by reference rather than restated, matching ObjectGridSchema.navigation.

• names src/zod/objectql.zod.ts → packages/types/src/zod/objectql.zod.ts — edited by this change

  Both halves move together. The TS declaration (packages/types/src/objectql.ts) and its zod mirror (src/zod/objectql.zod.ts) gain the same ten keys at the same requiredness — all optional — and no KnownDrift entry is added. navigation is taken from @objectstack/spec's NavigationConfigSchema by reference rather than restated, matching ObjectGridSchema.navigation.

.changeset/6475-gantt-block-face-declared.md

• names plugin-gantt/src/ObjectGantt.tsx → packages/plugin-gantt/src/ObjectGantt.tsx — edited by this change

  The gantt nested-block spelling of a gantt config ({ type: 'object-gantt', gantt: { … } }) had no mirror entry at all: it rode through BaseSchema's .passthrough() entirely unvalidated, and the published TypeScript never taught the shape either — an author writing gantt: { … } got no completion, no type checking, no error on a misspelt member. It was the 28th and last of the keys getGanttConfig (plugin-gantt/src/ObjectGantt.tsx) reads off the schema that objectui#6051 (PR feat(types,plugin-gantt): declare the flattened GanttConfig face ObjectGantt reads (#6051) #6472) did not declare — severed into its own card because, unlike the other 27, declaring it changes what a published tool refuses.

.changeset/6939-objectql-record-source-refinement.md

• names plugin-gantt/src/ObjectGantt.tsx → packages/plugin-gantt/src/ObjectGantt.tsx — edited by this change

  Both renderers resolve their records from one of three keys, in this order — getDataConfig in plugin-map/src/ObjectMap.tsx and plugin-gantt/src/ObjectGantt.tsx: data, then staticData, then objectName. Both mirrors required objectName alone, so a document authored on staticData drew correctly and was refused by safeValidateSchema — six catalog entries, three per component.

.changeset/6940-rowactions-boolean-mirror.md

• names zod/objectql.zod.ts → packages/types/src/zod/objectql.zod.ts — edited by this change

  The list view's same-named rowActions in zod/objectql.zod.ts — z.array(z.string()), the legacy bare-name action list on ObjectGridSchema — is a different key that is correct as it stands, is in parity with its own TS twin (rowActions?: string[]), and is not touched.

.changeset/7113-chart-data-model.md

• names objectql.zod.ts → packages/types/src/zod/objectql.zod.ts — edited by this change

  .extend() with a NEW key still works and preserves the fold and the refinement; .optional(), z.discriminatedUnion, z.toJSONSchema and safeValidateSchema are all unaffected. Nothing in this repository calls the throwing combinators on either const, and the published surface already ships refined mirrors (objectql.zod.ts, complex.zod.ts, form.zod.ts, app.zod.ts), so the class is not new — but it is a real behaviour change on a published export and it belongs in the release note rather than in a reviewer's file.

.changeset/7200-object-form-section-style-keys-undeclared.md

• names zod/objectql.zod.ts → packages/types/src/zod/objectql.zod.ts — edited by this change

  The authored-metadata type now agrees with @objectstack/spec, whose FormSectionSchema is a strict object declaring neither key, and with the ruling's rationale (maintainer 2026-09-01, verbatim): "retire the reads … Declaring the keys was weighed and not adopted: it would formally invite free Tailwind strings into authored metadata, the exact class the boundary exists to keep out." A ?: never tombstone was not used: ObjectFormSection has no zod mirror (ObjectFormSchema in zod/objectql.zod.ts does not declare sections), so there is no parse door to refuse at, and a tombstone is still a declaration in completion and in the published .d.ts.

.changeset/7265-types-user-filter-field-derives.md

• names zod/objectql.zod.ts → packages/types/src/zod/objectql.zod.ts — edited by this change

  zod/objectql.zod.ts declared two schemas under names @objectstack/spec/ui already exports. They were triaged separately, by reading their sites, and went different ways.

.changeset/7313-object-calendar-record-source.md

• names plugin-calendar/src/ObjectCalendar.tsx → packages/plugin-calendar/src/ObjectCalendar.tsx — edited by this change

  ObjectCalendar resolves its records through the shared ladder (resolveRecordSourceConfig in @object-ui/core, called from plugin-calendar/src/ObjectCalendar.tsx): data first, then staticData, then objectName. The published TypeScript interface REQUIRED objectName and declared neither data nor staticData; the published Zod mirror did the same. So an object-calendar node authored on staticData — the route the plugin page documents twice — rendered correctly and was refused by safeValidateSchema, and could not be annotated with its own type (TS2741: Property 'objectName' is missing).

.changeset/7322-object-kanban-group-by-limit.md

• names objectql.ts → packages/types/src/objectql.ts — edited by this change

  Breaking for authored metadata: ObjectKanbanSchema.groupField is RETIRED (objectui#7322, ADR-0049 enforce-or-remove), and the two keys the object-kanban renderer actually reads — groupBy and limit — are now DECLARED and validated on both published faces: the TypeScript interface in objectql.ts and the Zod mirror in zod/objectql.zod.ts.

• names zod/objectql.zod.ts → packages/types/src/zod/objectql.zod.ts — edited by this change

  Breaking for authored metadata: ObjectKanbanSchema.groupField is RETIRED (objectui#7322, ADR-0049 enforce-or-remove), and the two keys the object-kanban renderer actually reads — groupBy and limit — are now DECLARED and validated on both published faces: the TypeScript interface in objectql.ts and the Zod mirror in zod/objectql.zod.ts.

.changeset/7352-drill-down-config-mirror.md

• names zod/objectql.zod.ts → packages/types/src/zod/objectql.zod.ts — edited by this change

  DrillDownConfigSchema is the zod mirror of DrillDownConfig, and both declarations that carry drillDown reference it — ChartSchema (zod/data-display.zod.ts) and ObjectDataTableSchema (zod/objectql.zod.ts) — so the published validator under @object-ui/types/zod reads the key for the first time (objectui#7352).

.changeset/7363-objectql-union-arms.md

• names objectql.ts → packages/types/src/objectql.ts — edited by this change

  ObjectGallerySchema and ObjectDataTableSchema are members of ObjectQLComponentSchema on both faces — the TS union in objectql.ts and the zod union in zod/objectql.zod.ts — so AnyComponentSchema, and with it validateSchema / safeValidateSchema / objectui validate, has an arm for object-gallery and object-data-table nodes (objectui#7363).

• names zod/objectql.zod.ts → packages/types/src/zod/objectql.zod.ts — edited by this change

  ObjectGallerySchema and ObjectDataTableSchema are members of ObjectQLComponentSchema on both faces — the TS union in objectql.ts and the zod union in zod/objectql.zod.ts — so AnyComponentSchema, and with it validateSchema / safeValidateSchema / objectui validate, has an arm for object-gallery and object-data-table nodes (objectui#7363).

.changeset/7632-shared-record-source-config.md

• names packages/types/src/objectql.ts → packages/types/src/objectql.ts — edited by this change

  That ladder is published contract on both faces — packages/types/src/objectql.ts and its zod mirror both ship .describe() strings naming getDataConfig's order (77cb489b4, maintainer ruling 2026-09-02), pinned by objectql-record-source-refinement-6939.test.ts — and it was hand-copied into five plugin components with no gate holding them together. A change to the ruled order had five edit sites and nothing that noticed a missed one; that is the AGENTS.md #0.1 drift class.

.changeset/7712-kanban-calendar-filter-input.md

• names ObjectCalendar.tsx → packages/plugin-calendar/src/ObjectCalendar.tsx — edited by this change

  ObjectKanban.tsx sends the authored key to the query as $filter: schema.filter and ObjectCalendar.tsx does the same, and @objectstack/spec's ComponentPropsMap declares filter on both blocks (measured: safeParse accepts it, and refuses an undeclared key by name on the same call). But none of the four registrations that publish those two renderers listed filter in inputs, and sdui-parser's validateTree reports unknown-prop for every key no inputs entry claims. So an author writing the one spelling that WORKS was told it was unknown — objectui#6678's shape, where a correct write draws the same diagnostic as a write that does nothing. That is worse than an inert key: it actively punishes the correct behaviour, and the honest response to it is to delete working metadata.

.changeset/7804-objectql-handler-key-arms.md

• names objectql.ts → packages/types/src/objectql.ts — edited by this change

  The four plain objectql.ts node faces declare the nine handler keys their registered renderers read (objectui#7804, the objectql.ts slice): ObjectFormSchema.onCancel / .onError / .onOpenChange / .onStepChange / .onSuccess, ObjectGallerySchema.onCardClick / .onRowClick, ObjectGridSchema.onNavigate and ObjectViewSchema.onNavigate.

.changeset/7804-tree-view-handler-slot.md

• names objectql.ts → packages/types/src/objectql.ts — edited by this change

  'runtime-slot' and not 'retired', measured at this key's own channel. 'retired' publishes "no renderer reads this key, so nothing could ever run it" — true of the two siblings already tombstoned on this arm (onSelectChange, onExpandChange) and flatly false here, since the read is live and INVOKED. ⚠️ No in-repo host builds a tree-view node carrying the key: the channel is wired end to end and only the supplier is absent, which is the same shape as ObjectFormSchema.onStepChange in this card's objectql.ts slice and is not evidence of a dead read. The TypeScript declaration is unchanged and still callable, so a programmatic host supplies it exactly as before.

.changeset/7917-export-breadcrumb-object-tree-zod-schemas.md

• names objectql.zod.ts → packages/types/src/zod/objectql.zod.ts — edited by this change

  AnyComponentSchema declares 107 node component types. 105 of them could be named on the ./zod barrel — ButtonSchema.safeParse(node), which is what a designer, a form builder or a targeted test needs. The arms declaring type: 'breadcrumb' (navigation.zod.ts) and type: 'object-tree' (objectql.zod.ts) could not: both were already export const in their own module, but index.zod.ts — the package's only zod entry point — did not re-export them, so the schemas existed, were maintained, and were applied by the union while no consumer could name them.

.changeset/7963-alert-dialog-footer-keys-retired.md

• names objectql.ts → packages/types/src/objectql.ts — edited by this change

  Nothing else moves. These spellings are overloaded across the tree and every other owner is a live key on a different declaration — FormSchema.cancelLabel, objectql.ts's confirmLabel, plugin-designer's ConfirmDialog React props, plugin-grid's def.confirmLabel, and plugin-form's ModalForm / DrawerForm, which build a local cancelLabel from schema.cancelText. None is an AlertDialogSchema; none is touched, and a pin asserts it. No fixture, catalog schema, example app or doc fence authored any of the three on an alert-dialog node, so no shipped document is stranded.

.changeset/8171-calendar-sort-input.md

• names ObjectCalendar.tsx → packages/plugin-calendar/src/ObjectCalendar.tsx — edited by this change

  objectui#7712's defect, one key over. ObjectCalendar.tsx lowers the authored key onto its own query as $orderby: convertSortToQueryParams(schema.sort), and @objectstack/spec's ComponentPropsMap['object-calendar'] declares sort (measured on 17.2.0: safeParse({ objectName, sort }) returns success: true, while the same strict schema on the same call refuses bogusProp by name — that control is what makes the acceptance a verdict). But neither of the two registrations that publish this renderer — plugin-calendar:object-calendar and view:calendar — listed sort in inputs, and sdui-parser's validateTree reports unknown-prop for every key no inputs entry claims. So an author writing the one spelling that WORKS was told it was unknown — objectui#6678's shape, where a correct write draws the same diagnostic as a write that does nothing.

.changeset/8174-kanban-calendar-filter-sort.md

• names ObjectCalendar.tsx → packages/plugin-calendar/src/ObjectCalendar.tsx — edited by this change

  filter had four declaration faces and only three of them named it: @objectstack/spec declares it (ComponentPropsMap['object-kanban'] and ['object-calendar']), both plugins' registration inputs publish it, and both renderers read it — ObjectKanban.tsx lowers schema.filter onto $filter, ObjectCalendar.tsx lowers schema.filter onto $filter and schema.sort onto $orderby through convertSortToQueryParams. This package's own published faces (the TypeScript interface and its zod mirror) named none of them, so an authored value reached the renderer only through BaseSchema's index signature and the mirror's .passthrough() — admitted, never examined. That is the same reasoning finding(types,plugin-kanban): ObjectKanbanSchema requires groupField (zero read sites) and declares neither groupBy nor limit — no working object-kanban node is assignable to any declared type #7322 used to move groupBy and limit into this same interface.

.changeset/8466-calendar-color-allday-fields.md

• names ObjectCalendar.tsx → packages/plugin-calendar/src/ObjectCalendar.tsx — edited by this change

  ObjectCalendar.tsx's getCalendarConfig reads FIVE flat keys off the node, and packages/plugin-calendar/README.md teaches all five in one sentence — "point titleField / startDateField / endDateField / allDayField / colorField at your own fields when they differ." Only three of the five were declared. The other two reached the renderer through BaseSchema's [key: string]: any on the TypeScript face and its .passthrough() on the zod mirror: admitted, never examined. A misspelling therefore left the calendar silently colourless while every published gate passed.

.changeset/8478-describe-line-addresses.md

• names zod/objectql.zod.ts → packages/types/src/zod/objectql.zod.ts — edited by this change

  Remove stale source-line citations (NAME.ext:NNN) from twelve published .describe() schema descriptions in packages/types/src/zod/overlay.zod.ts, zod/data-display.zod.ts and zod/objectql.zod.ts (finding(types): 27 published .describe() schema descriptions in packages/types/src/zod/** cite source line addresses — the authorable surface carries a citation nothing reads #8478).

.changeset/8735-objectql-mirror-docblocks-not-defaulted.md

• names zod/objectql.zod.ts → packages/types/src/zod/objectql.zod.ts — edited by this change

  Correct four zod/objectql.zod.ts docblocks that described the behaviour objectui#8317 removed. Since that change the zod mirrors strip imported @objectstack/spec defaults at this package's import boundary, but the docblocks on HttpRequestSchema, ListColumnSchema, SelectionConfigSchema and PaginationConfigSchema still said, in the present tense, that method, prefix.type, type and pageSize are defaulted on parse — the opposite of what each export does. Each now says the key is declared and accepted but NOT defaulted on parse.

.changeset/8767-object-grid-refuses-string-sort.md

• names packages/types/src/objectql.ts → packages/types/src/objectql.ts — edited by this change

  Migration. Write the array: sort: [{ field: 'name', order: 'desc' }]. Both keys are required. SortConfig.order carries no ? in @object-ui/types (packages/types/src/objectql.ts) and no .optional() in its zod mirror, and the protocol's own reusable SortItemSchema requires order as well — measured: that schema refuses [{ field: 'name' }] with invalid_value at 0.order. Do not omit it: this block's array arm interpolates whatever is present, so an omitted order lowers to $orderby: 'name undefined' today. That is pre-existing behaviour on the arm this change does not touch, and it is filed as a successor card rather than widened into here.

.changeset/8801-object-kanban-allow-collapse-retired.md

• names packages/types/src/objectql.ts → packages/types/src/objectql.ts — edited by this change

  • the declarations retired here — packages/types/src/objectql.ts and its mirror packages/types/src/zod/objectql.zod.ts; - the pins that assert the retirement — object-kanban-allow-collapse-retired-8801.test.ts and bare-kanban-node-key-retired-8802.test.ts; - a comment in packages/types/src/zod/complex.zod.ts, recording that the deleted retiredZeroReadKanbanKey helper once carried this spelling on the SIBLING arm; - one row of content/docs/api/schema-reference.md; - the .changeset/ release notes that discuss it — this one, the two historical entries covering the sibling arm's own spelling, and objectui#9629's note recording the correction to this paragraph.

• names packages/types/src/zod/objectql.zod.ts → packages/types/src/zod/objectql.zod.ts — edited by this change

  • the declarations retired here — packages/types/src/objectql.ts and its mirror packages/types/src/zod/objectql.zod.ts; - the pins that assert the retirement — object-kanban-allow-collapse-retired-8801.test.ts and bare-kanban-node-key-retired-8802.test.ts; - a comment in packages/types/src/zod/complex.zod.ts, recording that the deleted retiredZeroReadKanbanKey helper once carried this spelling on the SIBLING arm; - one row of content/docs/api/schema-reference.md; - the .changeset/ release notes that discuss it — this one, the two historical entries covering the sibling arm's own spelling, and objectui#9629's note recording the correction to this paragraph.

.changeset/8885-object-chart-drilldown-title-compareto.md

• names packages/types/src/objectql.ts → packages/types/src/objectql.ts — edited by this change

  ObjectChart.tsx reads all three off schema, and until now neither published copy declared any of them: not the TS interface (packages/types/src/objectql.ts) and not the zod mirror (packages/types/src/zod/objectql.zod.ts). They rode BaseSchema's index signature / .passthrough() and arrived unvalidated. drillDown was the sharpest case — this component's registry inputs advertise it to the designer palette, and @objectstack/spec publishes ChartDrillDownSchema for exactly this carrier, so an author was offered a key that neither published shape mentioned.

• names packages/types/src/zod/objectql.zod.ts → packages/types/src/zod/objectql.zod.ts — edited by this change

  ObjectChart.tsx reads all three off schema, and until now neither published copy declared any of them: not the TS interface (packages/types/src/objectql.ts) and not the zod mirror (packages/types/src/zod/objectql.zod.ts). They rode BaseSchema's index signature / .passthrough() and arrived unvalidated. drillDown was the sharpest case — this component's registry inputs advertise it to the designer palette, and @objectstack/spec publishes ChartDrillDownSchema for exactly this carrier, so an author was offered a key that neither published shape mentioned.

.changeset/8913-object-kanban-columns-declared.md

• names objectql.ts → packages/types/src/objectql.ts — edited by this change

  What moved. ObjectKanbanSchema gains columns on both halves that move together — the TypeScript interface (objectql.ts) and its Zod mirror (zod/objectql.zod.ts). Retiring the bare kanban node type key (objectui#8802) removed the only face that judged a lane, and object-kanban had never declared the key, so it rode BaseSchema's [key: string]: any / .passthrough(): read by the renderer at three sites, named by no published face.

• names zod/objectql.zod.ts → packages/types/src/zod/objectql.zod.ts — edited by this change

  What moved. ObjectKanbanSchema gains columns on both halves that move together — the TypeScript interface (objectql.ts) and its Zod mirror (zod/objectql.zod.ts). Retiring the bare kanban node type key (objectui#8802) removed the only face that judged a lane, and object-kanban had never declared the key, so it rode BaseSchema's [key: string]: any / .passthrough(): read by the renderer at three sites, named by no published face.

.changeset/8990-object-kanban-groupby-optional.md

• names packages/types/src/objectql.ts → packages/types/src/objectql.ts — edited by this change

  @objectstack/spec declares the key optional — groupBy: z.string().optional() on ObjectKanbanPropsSchema — while this package required it on the TypeScript declaration (packages/types/src/objectql.ts) and on the Zod mirror (packages/types/src/zod/objectql.zod.ts). objectui was therefore narrower than the protocol on a published key: ObjectKanbanSchema.safeParse and safeValidateSchema refused an object-kanban node the protocol accepts, and such a node could not be annotated with its own type.

• names packages/types/src/zod/objectql.zod.ts → packages/types/src/zod/objectql.zod.ts — edited by this change

  @objectstack/spec declares the key optional — groupBy: z.string().optional() on ObjectKanbanPropsSchema — while this package required it on the TypeScript declaration (packages/types/src/objectql.ts) and on the Zod mirror (packages/types/src/zod/objectql.zod.ts). objectui was therefore narrower than the protocol on a published key: ObjectKanbanSchema.safeParse and safeValidateSchema refused an object-kanban node the protocol accepts, and such a node could not be annotated with its own type.

.changeset/8992-user-actions-collapse-and-docblock.md

• names objectql.zod.ts → packages/types/src/zod/objectql.zod.ts — edited by this change

  objectql.zod.ts's UserActionsSchema read stripImportedDefaults(Spec).extend({ group, hideFields, rowColor }), an extension that existed only because @objectstack/spec did not declare those three keys while normalizeListViewSchema folded objectui's legacy showGroup / showHideFields / showColor onto them. The protocol adopted all three in 17.3.0 (objectui#5435's ruling), so the extension is now a second local copy of a protocol declaration — the shape two faces start drifting from — and it collapses into the plain by-reference re-export its own note always said it would become.

.changeset/9092-inline-locale-declared-face.md

• names objectql.ts → packages/types/src/objectql.ts — edited by this change

  • AppComponentSchema.label (app.ts) - ObjectGridSchema.label and .description (objectql.ts) - PageNodeSchema.aria.ariaLabel (layout.ts)

.changeset/9309-object-gallery-filter-destination-typed.md

• names objectql.ts → packages/types/src/objectql.ts — edited by this change

  ObjectGallerySchema.filter is typed as the destination its own docblock names — QueryParams['$filter'] — on both faces, the TS interface in objectql.ts and the zod mirror in zod/objectql.zod.ts (objectui#9309).

• names zod/objectql.zod.ts → packages/types/src/zod/objectql.zod.ts — edited by this change

  ObjectGallerySchema.filter is typed as the destination its own docblock names — QueryParams['$filter'] — on both faces, the TS interface in objectql.ts and the zod mirror in zod/objectql.zod.ts (objectui#9309).

.changeset/9511-record-id-is-a-string.md

• names objectql.ts → packages/types/src/objectql.ts — edited by this change

  The three authorable keys, each on BOTH faces. ObjectFormSchema.recordId (objectql.ts + zod/objectql.zod.ts), DetailViewSchema.resourceId (views.ts + zod/views.zod.ts) and DetailSchema.resourceId (crud.ts + zod/crud.zod.ts). ⚠️ The crud pair is DetailSchema, not DetailViewSchema, and it reaches the same renderer — not by symbol but by data flow: plugin-detail registers the 'detail' node type onto DetailView. A read that follows TypeScript symbols alone finds two keys and is incomplete.

• names zod/objectql.zod.ts → packages/types/src/zod/objectql.zod.ts — edited by this change

  The three authorable keys, each on BOTH faces. ObjectFormSchema.recordId (objectql.ts + zod/objectql.zod.ts), DetailViewSchema.resourceId (views.ts + zod/views.zod.ts) and DetailSchema.resourceId (crud.ts + zod/crud.zod.ts). ⚠️ The crud pair is DetailSchema, not DetailViewSchema, and it reaches the same renderer — not by symbol but by data flow: plugin-detail registers the 'detail' node type onto DetailView. A read that follows TypeScript symbols alone finds two keys and is incomplete.

.changeset/9549-tree-filter-declared.md

• names objectql.ts → packages/types/src/objectql.ts — edited by this change

  ObjectTreeSchema.filter is declared on both faces, in the shape objectui#9309 settled for ObjectGallerySchema.filter: QueryParams['$filter'] by indexed access on the TS interface in objectql.ts, and the same two-arm union (array first) on the zod mirror in zod/objectql.zod.ts (objectui#9549).

• names zod/objectql.zod.ts → packages/types/src/zod/objectql.zod.ts — edited by this change

  ObjectTreeSchema.filter is declared on both faces, in the shape objectui#9309 settled for ObjectGallerySchema.filter: QueryParams['$filter'] by indexed access on the TS interface in objectql.ts, and the same two-arm union (array first) on the zod mirror in zod/objectql.zod.ts (objectui#9549).

.changeset/9550-object-tree-root-barrel.md

• names objectql.ts → packages/types/src/objectql.ts — edited by this change

  ObjectQLComponentSchema declares the node types an ObjectQL block may be. Every one of its arms was a named export of this package's root barrel except ObjectTreeSchema, which was declared in objectql.ts, applied by the union, and re-exported by the ./zod barrel (objectui#7917) — while no TypeScript consumer could name it. There is no ./objectql subpath to reach around the barrel: the package's exports map is pinned by packages/types/src/__tests__/package-exports-manifest.test.ts, and the root barrel was the only route to this type.

.changeset/9606-object-kanban-card-title.md

• names zod/objectql.zod.ts → packages/types/src/zod/objectql.zod.ts — edited by this change

  Both published faces of the object-kanban arm now name the key: the zod mirror ObjectKanbanSchema in zod/objectql.zod.ts and its TypeScript twin, the ObjectKanbanSchema interface in objectql.ts. Both declare it OPTIONAL, at the same requiredness the other face uses, so the two faces accept and refuse the same documents. (Located and cited by SYMBOL: line addresses in zod/objectql.zod.ts have drifted before, and this change is itself about a drifted mirror.)

• names objectql.ts → packages/types/src/objectql.ts — edited by this change

  Both published faces of the object-kanban arm now name the key: the zod mirror ObjectKanbanSchema in zod/objectql.zod.ts and its TypeScript twin, the ObjectKanbanSchema interface in objectql.ts. Both declare it OPTIONAL, at the same requiredness the other face uses, so the two faces accept and refuse the same documents. (Located and cited by SYMBOL: line addresses in zod/objectql.zod.ts have drifted before, and this change is itself about a drifted mirror.)

.changeset/9628-kanban-column-collapsed-honoured.md

• names objectql.ts → packages/types/src/objectql.ts — edited by this change

  The key was declared on both published faces of the object-kanban arm — the lane element of ObjectKanbanSchema (objectql.ts and its Zod mirror) and the runtime lane KanbanColumn (complex.ts and its mirror) — and read by KanbanEnhanced alone, a module no production source imports. An authored { "id": "todo", "title": "To Do", "collapsed": true } therefore parsed green on both faces and reached a board that did nothing with it: KanbanImpl's only collapse is the SWIMLANE row's, held in viewer state under objectui:kanban-collapsed:ANGLE-BRACKETS(swimlaneField) and never keyed to a lane's declared value. That is the ADR-0049 declared-but-unhonoured shape.

.changeset/9786-detail-timestamps-display-locale.md

• names machineLocaleCensus-9909.test.ts → packages/i18n/src/__tests__/machineLocaleCensus-9909.test.ts — edited by this change

  Two instruments land with the repair, because the repair alone is what happened the last five times. detailTimestamps.displayLocale-9786.test.tsx renders every surface whose face reaches the DOM under a declared de-DE session and a declared en one and requires the two readings to differ — an assertion the runner's own locale cannot satisfy, since before this change both legs came from the machine and were byte-identical whatever the machine was. It also patches the Intl constructors and Date.prototype.toLocale* and inspects the argument each call actually receives, which is the only way to catch a variable that resolves to undefined, and the only way to reach RecordMetaFooter — whose absolute face is a TooltipContent child that Radix keeps out of the DOM until the tooltip opens. A census pin reddens when a new bare, undefined- or hard-coded-tag call site is written; it masks comments before it counts, and when it landed it declared InlineFieldInput's en-CA as an exemption with its reason — that call fed ANGLE-BRACKETS(input type="date"), whose value HTML defines as YYYY-MM-DD, so it was an ISO formatter and not a display locale. It landed scoped to this package and, under the ruling on this card, became the one repository-wide census in @object-ui/i18n (machineLocaleCensus-9909.test.ts, objectui#9909), which carried that exemption forward. objectui#10625 later removed the call: InlineFieldInput's date editor now renders @object-ui/fields' DateField, and the exemption went with it.

.changeset/9909-machine-locale-sweep.md

• names machineLocaleCensus-9909.test.ts → packages/i18n/src/__tests__/machineLocaleCensus-9909.test.ts — edited by this change

  One census, repository-wide. plugin-detail's machine-locale census pin (objectui#9786) is now a single test, machineLocaleCensus-9909.test.ts in @object-ui/i18n, covering every workspace package whose manifest depends on @object-ui/i18n. It refuses any call site that passes nothing, undefined, the 'default' pseudo-tag (a subtag no locale data answers, so Intl resolves it to the machine's locale) or a hard-coded tag, unless the site is declared with its reason — for example the catch fallback for a tag Intl itself rejected, or an ISO formatter feeding ANGLE-BRACKETS(input type="date"). Each declared site is counted exactly, so deleting one without its entry is refused too. The per-package pin it replaces is deleted. The runtime tripwire that observes the argument each locale-taking call (Intl constructors, Date and Number toLocale*) actually receives moved into the private @object-ui/test-support package, and every surface above is pinned with it: the same data under two declared locales must render differently, NO locale-taking call may receive the machine's locale (nothing, undefined or 'default'), and the surface's own calls must receive the declared tag. A call carrying another declared tag, such as the 'en' of the session's UI language, is tolerated by design: only the machine's locale is the defect.

Read the paragraph, not the line: both false halves of the objectui#8617 claim sat in one paragraph, and correcting either alone would have left it asserting the same wrong thing.

If a claim did go false, correct the body. That is precedented and prose-only, frontmatter untouched; check-changeset-overwrite.mjs will report the correction as its own case 2 ("correcting a declaration on purpose … legitimate"), which is the intended shape — one gate asks for the read, the other records the write.

Not covered, stated so nobody reads this as more: a born-false claim that spells no line address at all (objectui#9495 coordinated one by ORDINAL — "a grep finds that member first" — and deciding that means reading what the sentence means), a claim spelled as a symbol or a package rather than a backticked file name, and a file named ambiguously.

Angle-bracketed names in the quoted prose above are rewritten as ANGLE-BRACKETS(name): GitHub deletes tag-shaped fragments from a stored body, and a quote that silently loses the identifier it is about is worse than a visible repair.

Compared the checked-out tree with b2683a2c0 (merge-base with origin/main): 19 file(s) changed outside .changeset/, read against 1656 pending declaration(s) that publish a body (2248 pending in total). · run

[github-actions]

✅ Console Performance Budget

Metric	Value	Budget
Eager closure (gzip, 329 chunks)	3095.4 KB	3104.5 KB
Main entry chunk (gzip)	148.4 KB	350 KB
Entry file	index-DzWZo40G.js	—
Status	PASS	—

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

Package	Size	Gzipped
app-shell (consoleActionDispatch.js)	0.20KB	0.19KB
app-shell (index.js)	16.57KB	6.17KB
app-shell (runtime-config.js)	20.68KB	7.36KB
app-shell (types.js)	0.01KB	0.04KB
app-shell (urlParams.js)	10.06KB	3.86KB
auth (ActiveOrganizationStorage.js)	27.95KB	10.04KB
auth (AuthContext.js)	0.31KB	0.24KB
auth (AuthGuard.js)	2.07KB	1.00KB
auth (AuthProvider.js)	40.17KB	10.58KB
auth (AuthShell.js)	3.49KB	1.40KB
auth (ForgotPasswordForm.js)	12.21KB	3.45KB
auth (LoginForm.js)	18.15KB	5.39KB
auth (PreviewBanner.js)	0.90KB	0.50KB
auth (RegisterForm.js)	6.65KB	2.22KB
auth (SocialSignInButtons.js)	9.61KB	3.89KB
auth (UserMenu.js)	3.39KB	1.21KB
auth (auth-gate-events.js)	1.29KB	0.66KB
auth (authStyles.js)	5.04KB	1.72KB
auth (createAuthClient.js)	40.21KB	10.80KB
auth (createAuthenticatedFetch.js)	8.52KB	3.45KB
auth (index.js)	3.63KB	1.64KB
auth (invitation-status.js)	1.22KB	0.70KB
auth (org-roles.js)	6.66KB	2.78KB
auth (phone-identifier.js)	1.11KB	0.66KB
auth (types.js)	0.59KB	0.35KB
auth (useAuth.js)	5.30KB	1.02KB
auth (useWorkspaceAdminStatus.js)	11.08KB	4.58KB
collaboration (CommentThread.js)	27.13KB	7.95KB
collaboration (LiveCursors.js)	3.17KB	1.27KB
collaboration (PresenceAvatars.js)	6.49KB	2.64KB
collaboration (PresenceProvider.js)	2.79KB	1.13KB
collaboration (index.js)	1.68KB	0.73KB
collaboration (useCollaborationTranslation.js)	6.05KB	2.52KB
collaboration (useCommentSearch.js)	1.98KB	0.88KB
collaboration (useConflictResolution.js)	7.75KB	1.86KB
collaboration (useMentionNotifications.js)	1.81KB	0.68KB
collaboration (usePresence.js)	6.33KB	1.84KB
collaboration (useRealtimeSubscription.js)	7.91KB	2.01KB
components (index.js)	557.61KB	133.61KB
core (index.js)	9.93KB	3.94KB
create-plugin (index.js)	27.94KB	9.51KB
data-objectstack (index.js)	226.44KB	63.00KB
fields (index.js)	261.01KB	66.28KB
i18n (LocalizationContext.js)	1.76KB	0.96KB
i18n (builtinAggregateLabels.js)	0.86KB	0.49KB
i18n (currency.js)	2.59KB	1.22KB
i18n (fallbackInterpolation.js)	6.25KB	2.77KB
i18n (i18n.js)	8.87KB	3.64KB
i18n (index.js)	5.24KB	2.27KB
i18n (pickLocalized.js)	9.86KB	3.95KB
i18n (provider.js)	39.40KB	12.91KB
i18n (translateFn.js)	0.20KB	0.18KB
i18n (useDisplayLocale.js)	3.52KB	1.76KB
i18n (useObjectLabel.js)	34.34KB	9.17KB
i18n (useSafeTranslation.js)	5.60KB	2.33KB
layout (index.js)	39.28KB	11.09KB
mobile (MobileProvider.js)	0.92KB	0.49KB
mobile (ResponsiveContainer.js)	0.94KB	0.38KB
mobile (breakpoints.js)	1.51KB	0.70KB
mobile (createOfflineDataSource.js)	5.61KB	1.75KB
mobile (index.js)	1.99KB	0.87KB
mobile (offlineQueue.js)	3.91KB	1.35KB
mobile (pwa.js)	0.97KB	0.49KB
mobile (serviceWorker.js)	1.48KB	0.62KB
mobile (serviceWorkerSource.js)	3.41KB	1.48KB
mobile (useBreakpoint.js)	1.54KB	0.65KB
mobile (useGesture.js)	6.96KB	1.98KB
mobile (useOfflineSync.js)	1.99KB	0.72KB
mobile (usePullToRefresh.js)	6.62KB	2.45KB
mobile (useResponsive.js)	0.72KB	0.42KB
mobile (useSpecGesture.js)	5.52KB	2.10KB
mobile (useTouchTarget.js)	1.01KB	0.54KB
permissions (MePermissionsProvider.js)	13.52KB	4.88KB
permissions (PermissionContext.js)	0.31KB	0.25KB
permissions (PermissionGuard.js)	0.89KB	0.45KB
permissions (PermissionProvider.js)	6.24KB	2.16KB
permissions (discardProofCache.js)	1.04KB	0.55KB
permissions (evaluator.js)	8.33KB	3.07KB
permissions (index.js)	0.93KB	0.41KB
permissions (store.js)	0.91KB	0.42KB
permissions (useFieldPermissions.js)	1.28KB	0.53KB
permissions (usePermissions.js)	4.83KB	2.27KB
plugin-ai (index.js)	16.01KB	3.93KB
plugin-calendar (index.js)	51.96KB	14.83KB
plugin-charts (index.js)	83.99KB	22.86KB
plugin-chatbot (index.js)	197.67KB	46.90KB
plugin-dashboard (index.js)	136.82KB	36.44KB
plugin-designer (index.js)	216.42KB	44.47KB
plugin-detail (index.js)	233.48KB	61.79KB
plugin-editor (index.js)	2.23KB	1.05KB
plugin-form (index.js)	161.21KB	41.41KB
plugin-gantt (index.js)	170.35KB	42.19KB
plugin-grid (index.js)	228.11KB	62.72KB
plugin-kanban (index.js)	48.43KB	15.11KB
plugin-list (index.js)	115.01KB	28.49KB
plugin-map (index.js)	22.90KB	7.62KB
plugin-markdown (index.js)	13.88KB	4.80KB
plugin-report (index.js)	44.17KB	12.20KB
plugin-timeline (index.js)	31.00KB	9.09KB
plugin-tree (index.js)	11.21KB	3.89KB
plugin-view (index.js)	87.90KB	22.06KB
providers (DataSourceProvider.js)	0.75KB	0.39KB
providers (MetadataProvider.js)	1.37KB	0.59KB
providers (ThemeProvider.js)	1.90KB	0.85KB
providers (UploadProvider.js)	11.81KB	3.58KB
providers (index.js)	0.45KB	0.23KB
providers (types.js)	0.01KB	0.04KB
react-runtime (index.js)	5.62KB	2.34KB
react (LazyPluginLoader.js)	4.47KB	1.63KB
react (SchemaRenderer.js)	119.16KB	39.05KB
react (data-invalidation.js)	5.05KB	2.08KB
react (index.js)	4.03KB	1.86KB
react (schema-input.js)	4.25KB	2.04KB
react (spec-input.js)	0.20KB	0.18KB
sdui-parser (body-dialect.js)	4.78KB	2.09KB
sdui-parser (codegen.js)	7.50KB	3.05KB
sdui-parser (dashboard-widget-options.js)	3.08KB	1.30KB
sdui-parser (index.js)	6.16KB	2.71KB
sdui-parser (input-type.js)	2.84KB	1.40KB
sdui-parser (kanban-quick-add.js)	3.89KB	1.87KB
sdui-parser (parse.js)	25.28KB	7.80KB
sdui-parser (provenance.js)	3.84KB	1.90KB
sdui-parser (types.js)	0.28KB	0.23KB
sdui-parser (validate.js)	18.27KB	6.22KB
types (ai.js)	4.11KB	2.06KB
types (api-types.js)	0.20KB	0.18KB
types (app.js)	3.52KB	1.36KB
types (base.js)	0.20KB	0.18KB
types (blocks.js)	0.20KB	0.18KB
types (complex.js)	2.93KB	1.49KB
types (crud.js)	0.20KB	0.18KB
types (dashboard-filter-alias.js)	6.23KB	2.74KB
types (data-display.js)	3.75KB	1.85KB
types (data-protocol.js)	0.20KB	0.19KB
types (data.js)	0.20KB	0.18KB
types (designer.js)	1.85KB	0.85KB
types (disclosure.js)	0.20KB	0.18KB
types (error-code.js)	1.54KB	0.88KB
types (expression.js)	0.20KB	0.18KB
types (feedback.js)	0.20KB	0.18KB
types (field-types.js)	0.20KB	0.18KB
types (form.js)	0.20KB	0.18KB
types (http-inflight.js)	8.87KB	3.73KB
types (http-retry.js)	4.32KB	2.02KB
types (icon-key-migration.js)	4.26KB	1.63KB
types (index.js)	4.74KB	2.26KB
types (layout.js)	0.20KB	0.18KB
types (managed-by.js)	0.19KB	0.18KB
types (mobile.js)	5.00KB	2.39KB
types (navigation.js)	0.20KB	0.18KB
types (objectql.js)	0.20KB	0.18KB
types (overlay.js)	0.20KB	0.18KB
types (permissions.js)	2.52KB	1.31KB
types (plugin-scope.js)	0.20KB	0.18KB
types (record-components.js)	0.20KB	0.19KB
types (record-semantics.js)	1.28KB	0.67KB
types (registry.js)	0.20KB	0.18KB
types (reports.js)	0.20KB	0.18KB
types (select-option.js)	0.20KB	0.19KB
types (spec-report.js)	5.05KB	1.93KB
types (spec-ui-namespace.js)	0.20KB	0.19KB
types (strict-authoring-face.js)	17.15KB	6.32KB
types (system-fields.js)	3.33KB	1.54KB
types (theme.js)	6.27KB	2.87KB
types (ui-action.js)	8.11KB	3.32KB
types (views.js)	0.20KB	0.18KB
types (widget.js)	0.20KB	0.18KB

Size Limits

• ✅ Core packages should be < 50KB gzipped
• ✅ Component packages should be < 100KB gzipped
• ⚠️ Plugin packages should be < 150KB gzipped

[objectstack-fleet]

Contract review

Served-tier: CONTRACT_REVIEW_TIER
Head-sha: 8ac7b622702f66109ec28577de12fa2ecdaca142

① Derived judgments

Blocking

1. CI is red on the head, caused by the makeTzShift move. Test (shard 7/8) fails in machineLocaleCensus-9909.test.ts, which is keyed by file path:

   • "GanttView.tsx · new Intl.DateTimeFormat('en-US', { — declared 1, found 0";
   • "tzShift.ts:24 … [en-US]", an undeclared hard-coded tag.

   The dev's suites ran only calendar, gantt and types. Fix: in that DECLARED entry (verdict deliberate fallback), change file to packages/plugin-gantt/src/tzShift.ts, keeping the reason and the count of 1. This puts an i18n test path outside claim 5861874880's surface, so the seat amends the claim.

2. A published JSDoc this PR made false is left standing. GanttViewProps.workingCalendar (exported) still reads "any holidays (ISO yyyy-mm-dd UTC keys) are skipped", while scheduling.ts now keys holidays by the chart's local day. The dev fixed the same sentence in @object-ui/types but missed this sibling. Replacement: "any holidays (ISO yyyy-mm-dd calendar-day keys, read on the chart's own calendar: the viewer's, or the business timeZone's when one is set) are skipped rather than consumed".

Reads. A search of both plugins for new Date(, Date.parse, parseISO and date-fns shows every stored date-only read routed through toDisplayDate:

• ObjectCalendar start and end;
• the calendar-view events and currentDate;
• ObjectGantt start, end and baselines;
• GanttView markers and the inline editor.

The remaining sites are correct as they are: copies of Date-typed values, today placeholders, and the datetime-only tooltip regex. No date-only read is left raw.

Writes.

• The declared type is read from objectSchema.fields[field].type, and objectSchema is in the callbacks' dependencies.
• The isRealCalendarDate fallback is sound: it requires YYYY-MM-DD plus a day that exists, so a datetime stored at midnight UTC cannot be taken for a day.
• A datetime keeps its instant.
• Every gantt write shares handleTaskUpdateDefault.
• Gap: a no-schema quick-create still writes an instant. The PR body discloses it; the changeset does not (item 3).

tzShift decision: coherent.

• ObjectGantt hands from(L), GanttView draws to(from(L)) = L, and a drop at display day D writes toDateInputValue(to(from(D))) = D.
• Both sides build makeTzShift from the same ganttConfig.timeZone and the same identity rule. The mapping is exact for fixed offsets and within an hour near a DST change (disclosed).

scheduling.ts.

• It runs on display-space tasks, so "local day" is the chart's calendar, and the holidays docs are true.
• It does change datetime-only charts that author skipWeekends or holidays for viewers off UTC. That matches the column fold isWorkingColumn, which was already local, so it is a correction, and the changeset covers it. No datetime control row pins it.
• The existing getUTCDay assertions stay true under the root config's TZ=UTC.

The @object-ui/types holidays edit is true, and patch is right.

The two re-pointed ObjectGantt.test.tsx assertions pinned the defect (the drag case's schema declares type: 'date') and the real no-schema fallback.

Pins.

• All five are in PINS, and each zone opens with a rig case.
• They assert literal days and parts, so there is no tautology.
• The base reds match the reasons they name.
• Uncovered by any zone pin: the calendar no-schema fallback, the endDateField write, and the gantt no-schema path off UTC.

Changeset: the title, the defect paragraph, and the Reads, Writes, timeZone and working-calendar bullets are true.

Pending changesets spot-checked (10110, 10183, 10844, 5903, 6051, 6547, 7512, 10031, 10668): none becomes false.

Non-blocking (ride the same push)

3. The changeset's Writes bullet should say that a calendar quick-create with no schema still writes the instant.
4. plugin-gantt/scripts/verify-phase6b.mjs still checks weekends with getUTCDay(), the retired rule. It is a manual script, not CI.
5. The timeZone prose "persisted data stays real instants" (types JSDoc and spec describe) is loose now that a date field under a zoned chart persists a day. Record it on the card.
6. The dev-report finding that the DST-day calendar move writes the day before is a date-only write defect of this family. Record it on objectui#10866, the carrier.

② Semver level

patch for @object-ui/plugin-calendar, @object-ui/plugin-gantt and @object-ui/types is correct. No major, and Clause-②: no holds.

③ Boundary flags

• CI on head (final, 42 runs): 38 success, 3 skipped, 1 failure: Test (shard 7/8) (item 1).
• git merge-tree against main b2683a2c0: clean. The PR is behind.
• No other open PR touches these paths.
• NOT governed.
• Draft, assigned to os-elon-musk.
• Claim surface: packages/types and, after item 1, the i18n test lie outside claim 5861874880, so the seat amends it.

Implemented-by: claude/issue-10866-calendar-gantt-date-only-days
Reviewed-by: session_014mXUNuFomfj24w7s1pZzhN

VERDICT: FAIL

Items 1 and 2 stop the landing; items 3 to 6 ride the same push or the card.

[github-actions]

✅ Console Performance Budget

Metric	Value	Budget
Eager closure (gzip, 329 chunks)	3095.4 KB	3104.5 KB
Main entry chunk (gzip)	148.4 KB	350 KB
Entry file	index-DzWZo40G.js	—
Status	PASS	—

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

Package	Size	Gzipped
app-shell (consoleActionDispatch.js)	0.20KB	0.19KB
app-shell (index.js)	16.57KB	6.17KB
app-shell (runtime-config.js)	20.68KB	7.36KB
app-shell (types.js)	0.01KB	0.04KB
app-shell (urlParams.js)	10.06KB	3.86KB
auth (ActiveOrganizationStorage.js)	27.95KB	10.04KB
auth (AuthContext.js)	0.31KB	0.24KB
auth (AuthGuard.js)	2.07KB	1.00KB
auth (AuthProvider.js)	40.17KB	10.58KB
auth (AuthShell.js)	3.49KB	1.40KB
auth (ForgotPasswordForm.js)	12.21KB	3.45KB
auth (LoginForm.js)	18.15KB	5.39KB
auth (PreviewBanner.js)	0.90KB	0.50KB
auth (RegisterForm.js)	6.65KB	2.22KB
auth (SocialSignInButtons.js)	9.61KB	3.89KB
auth (UserMenu.js)	3.39KB	1.21KB
auth (auth-gate-events.js)	1.29KB	0.66KB
auth (authStyles.js)	5.04KB	1.72KB
auth (createAuthClient.js)	40.21KB	10.80KB
auth (createAuthenticatedFetch.js)	8.52KB	3.45KB
auth (index.js)	3.63KB	1.64KB
auth (invitation-status.js)	1.22KB	0.70KB
auth (org-roles.js)	6.66KB	2.78KB
auth (phone-identifier.js)	1.11KB	0.66KB
auth (types.js)	0.59KB	0.35KB
auth (useAuth.js)	5.30KB	1.02KB
auth (useWorkspaceAdminStatus.js)	11.08KB	4.58KB
collaboration (CommentThread.js)	27.13KB	7.95KB
collaboration (LiveCursors.js)	3.17KB	1.27KB
collaboration (PresenceAvatars.js)	6.49KB	2.64KB
collaboration (PresenceProvider.js)	2.79KB	1.13KB
collaboration (index.js)	1.68KB	0.73KB
collaboration (useCollaborationTranslation.js)	6.05KB	2.52KB
collaboration (useCommentSearch.js)	1.98KB	0.88KB
collaboration (useConflictResolution.js)	7.75KB	1.86KB
collaboration (useMentionNotifications.js)	1.81KB	0.68KB
collaboration (usePresence.js)	6.33KB	1.84KB
collaboration (useRealtimeSubscription.js)	7.91KB	2.01KB
components (index.js)	557.61KB	133.61KB
core (index.js)	9.93KB	3.94KB
create-plugin (index.js)	27.94KB	9.51KB
data-objectstack (index.js)	226.44KB	63.00KB
fields (index.js)	261.01KB	66.28KB
i18n (LocalizationContext.js)	1.76KB	0.96KB
i18n (builtinAggregateLabels.js)	0.86KB	0.49KB
i18n (currency.js)	2.59KB	1.22KB
i18n (fallbackInterpolation.js)	6.25KB	2.77KB
i18n (i18n.js)	8.87KB	3.64KB
i18n (index.js)	5.24KB	2.27KB
i18n (pickLocalized.js)	9.86KB	3.95KB
i18n (provider.js)	39.40KB	12.91KB
i18n (translateFn.js)	0.20KB	0.18KB
i18n (useDisplayLocale.js)	3.52KB	1.76KB
i18n (useObjectLabel.js)	34.34KB	9.17KB
i18n (useSafeTranslation.js)	5.60KB	2.33KB
layout (index.js)	39.28KB	11.09KB
mobile (MobileProvider.js)	0.92KB	0.49KB
mobile (ResponsiveContainer.js)	0.94KB	0.38KB
mobile (breakpoints.js)	1.51KB	0.70KB
mobile (createOfflineDataSource.js)	5.61KB	1.75KB
mobile (index.js)	1.99KB	0.87KB
mobile (offlineQueue.js)	3.91KB	1.35KB
mobile (pwa.js)	0.97KB	0.49KB
mobile (serviceWorker.js)	1.48KB	0.62KB
mobile (serviceWorkerSource.js)	3.41KB	1.48KB
mobile (useBreakpoint.js)	1.54KB	0.65KB
mobile (useGesture.js)	6.96KB	1.98KB
mobile (useOfflineSync.js)	1.99KB	0.72KB
mobile (usePullToRefresh.js)	6.62KB	2.45KB
mobile (useResponsive.js)	0.72KB	0.42KB
mobile (useSpecGesture.js)	5.52KB	2.10KB
mobile (useTouchTarget.js)	1.01KB	0.54KB
permissions (MePermissionsProvider.js)	13.52KB	4.88KB
permissions (PermissionContext.js)	0.31KB	0.25KB
permissions (PermissionGuard.js)	0.89KB	0.45KB
permissions (PermissionProvider.js)	6.24KB	2.16KB
permissions (discardProofCache.js)	1.04KB	0.55KB
permissions (evaluator.js)	8.33KB	3.07KB
permissions (index.js)	0.93KB	0.41KB
permissions (store.js)	0.91KB	0.42KB
permissions (useFieldPermissions.js)	1.28KB	0.53KB
permissions (usePermissions.js)	4.83KB	2.27KB
plugin-ai (index.js)	16.01KB	3.93KB
plugin-calendar (index.js)	51.96KB	14.83KB
plugin-charts (index.js)	83.99KB	22.86KB
plugin-chatbot (index.js)	197.67KB	46.90KB
plugin-dashboard (index.js)	136.82KB	36.44KB
plugin-designer (index.js)	216.42KB	44.47KB
plugin-detail (index.js)	233.48KB	61.79KB
plugin-editor (index.js)	2.23KB	1.05KB
plugin-form (index.js)	161.21KB	41.41KB
plugin-gantt (index.js)	170.35KB	42.19KB
plugin-grid (index.js)	228.11KB	62.72KB
plugin-kanban (index.js)	48.43KB	15.11KB
plugin-list (index.js)	115.01KB	28.49KB
plugin-map (index.js)	22.90KB	7.62KB
plugin-markdown (index.js)	13.88KB	4.80KB
plugin-report (index.js)	44.17KB	12.20KB
plugin-timeline (index.js)	31.00KB	9.09KB
plugin-tree (index.js)	11.21KB	3.89KB
plugin-view (index.js)	87.90KB	22.06KB
providers (DataSourceProvider.js)	0.75KB	0.39KB
providers (MetadataProvider.js)	1.37KB	0.59KB
providers (ThemeProvider.js)	1.90KB	0.85KB
providers (UploadProvider.js)	11.81KB	3.58KB
providers (index.js)	0.45KB	0.23KB
providers (types.js)	0.01KB	0.04KB
react-runtime (index.js)	5.62KB	2.34KB
react (LazyPluginLoader.js)	4.47KB	1.63KB
react (SchemaRenderer.js)	119.16KB	39.05KB
react (data-invalidation.js)	5.05KB	2.08KB
react (index.js)	4.03KB	1.86KB
react (schema-input.js)	4.25KB	2.04KB
react (spec-input.js)	0.20KB	0.18KB
sdui-parser (body-dialect.js)	4.78KB	2.09KB
sdui-parser (codegen.js)	7.50KB	3.05KB
sdui-parser (dashboard-widget-options.js)	3.08KB	1.30KB
sdui-parser (index.js)	6.16KB	2.71KB
sdui-parser (input-type.js)	2.84KB	1.40KB
sdui-parser (kanban-quick-add.js)	3.89KB	1.87KB
sdui-parser (parse.js)	25.28KB	7.80KB
sdui-parser (provenance.js)	3.84KB	1.90KB
sdui-parser (types.js)	0.28KB	0.23KB
sdui-parser (validate.js)	18.27KB	6.22KB
types (ai.js)	4.11KB	2.06KB
types (api-types.js)	0.20KB	0.18KB
types (app.js)	3.52KB	1.36KB
types (base.js)	0.20KB	0.18KB
types (blocks.js)	0.20KB	0.18KB
types (complex.js)	2.93KB	1.49KB
types (crud.js)	0.20KB	0.18KB
types (dashboard-filter-alias.js)	6.23KB	2.74KB
types (data-display.js)	3.75KB	1.85KB
types (data-protocol.js)	0.20KB	0.19KB
types (data.js)	0.20KB	0.18KB
types (designer.js)	1.85KB	0.85KB
types (disclosure.js)	0.20KB	0.18KB
types (error-code.js)	1.54KB	0.88KB
types (expression.js)	0.20KB	0.18KB
types (feedback.js)	0.20KB	0.18KB
types (field-types.js)	0.20KB	0.18KB
types (form.js)	0.20KB	0.18KB
types (http-inflight.js)	8.87KB	3.73KB
types (http-retry.js)	4.32KB	2.02KB
types (icon-key-migration.js)	4.26KB	1.63KB
types (index.js)	4.74KB	2.26KB
types (layout.js)	0.20KB	0.18KB
types (managed-by.js)	0.19KB	0.18KB
types (mobile.js)	5.00KB	2.39KB
types (navigation.js)	0.20KB	0.18KB
types (objectql.js)	0.20KB	0.18KB
types (overlay.js)	0.20KB	0.18KB
types (permissions.js)	2.52KB	1.31KB
types (plugin-scope.js)	0.20KB	0.18KB
types (record-components.js)	0.20KB	0.19KB
types (record-semantics.js)	1.28KB	0.67KB
types (registry.js)	0.20KB	0.18KB
types (reports.js)	0.20KB	0.18KB
types (select-option.js)	0.20KB	0.19KB
types (spec-report.js)	5.05KB	1.93KB
types (spec-ui-namespace.js)	0.20KB	0.19KB
types (strict-authoring-face.js)	17.15KB	6.32KB
types (system-fields.js)	3.33KB	1.54KB
types (theme.js)	6.27KB	2.87KB
types (ui-action.js)	8.11KB	3.32KB
types (views.js)	0.20KB	0.18KB
types (widget.js)	0.20KB	0.18KB

Size Limits

• ✅ Core packages should be < 50KB gzipped
• ✅ Component packages should be < 100KB gzipped
• ⚠️ Plugin packages should be < 150KB gzipped

[objectstack-fleet]

Contract review

Served-tier: CONTRACT_REVIEW_TIER
Head-sha: 687890effaf604d46b015589a9a74224eb98c155

This is an in-seat delta review of fix round 1 (8ac7b6227 to 687890eff, one commit), against record 5862881358 (FAIL).

① Derived judgments

• Item 1 (red shard 7): fixed. The machineLocaleCensus-9909 DECLARED entry for new Intl.DateTimeFormat('en-US', { now names packages/plugin-gantt/src/tzShift.ts, with the expression, count 1, verdict and reason unchanged. Its one other citation, the root vitest.config.mts comment naming GanttView.tsx's tzOffsetMs(...), follows the move; the scripts pins that read that file are green in the dev's quoted run.
• Item 2 (the stale published JSDoc): fixed. The GanttViewProps.workingCalendar wording matches the ordered text, and it is true of scheduling.ts, which counts the chart's display-space days.
• Item 3: fixed. The changeset Writes bullet's last sentence is the ordered text (quick-create with no stored value still writes the instant), and the frontmatter is untouched (the hunk starts at body line 9).
• Item 4: fixed. verify-phase6b.mjs reads getDay(), with a comment saying why (the browser context sets no timezoneId). It is a manual script: no workflow or package script references it.
• One extra site of the same class. The weekend count in scheduling.test.ts moves from getUTCDay to getDay. It is equivalent under the suite's pinned TZ=UTC, and now states the rule it tests.
• Items 5 and 6 are recorded on objectui#10866 (5862887370) for a later slice, not owed here.
• Nothing else moved. The delta is 6 files, all comment, prose, path or test-reader edits, plus one manual script. No runtime source changes beyond the JSDoc.

② Semver level

patch for @object-ui/plugin-calendar, @object-ui/plugin-gantt and @object-ui/types stands. The census test path is under packages/i18n/src, and check-changeset-presence accepts the one changeset (4 packages, 1 changeset). Clause-②: no holds.

③ Boundary flags

• CI: the landing waits for every check-run on this head to be final and green before pr_ready.
• git merge-tree against main b2683a2c0 is clean (dev's run, exit 0).
• The claim surface was amended at 5862887370 for packages/types, tzShift.ts, scheduling.ts, the census test and verify-phase6b.mjs. The vitest.config.mts comment edit is a citation this move falsified, the same rule.
• NOT GOVERNED.
• Draft, assigned to os-elon-musk.

Implemented-by: claude/issue-10866-calendar-gantt-date-only-days
Reviewed-by: session_014mXUNuFomfj24w7s1pZzhN

VERDICT: PASS