fix(plugin-calendar): a month-grid move keeps the wall-clock time across a DST change (objectui#11005)

[objectstack-fleet]

Fixes #11005
Clause-②: no

Ruling 5881826705 (letter B), PM claim 5882077455, branch claude/issue-11005-month-grid-calendar-days, dispatched from session https://claude.ai/code/session_011p7ikEivgXefNDaE5S5Uec. The month grid now moves a value by calendar days and keeps its wall-clock time. This holds for every value, for a move and for a drag of the span's end.

What changes

1. CalendarView, MonthView.handleDrop. The move used to count deltaMs, the milliseconds between the grab cell's local midnight and the drop cell's, and add it to the start and the end. It now counts the calendar days between the two cells from their local year, month and day (calendarDaysBetween). The difference is taken on the UTC calendar, so it is a whole number with no rounding. It then moves a local copy of the start and of the end with setDate (moveByCalendarDays), leaving hours, minutes, seconds and milliseconds untouched. The drag of a span's end (resize-end) moves the end the same way, and its guards still compare day cells.
2. ObjectCalendar: the objectui#10866 slice-4 day repair is removed (toMovedDateValue, isStoredDay, DAY_MS). It was measured redundant (see below). The default drop handler writes each field through toStoredDateValue again, as it did before that slice: a date field as the local day of the value the grid hands back, and a datetime field as its instant.
3. Pins. A new zone pin, CalendarView.monthMoveCalendarDays-11005, sits at the grid. It covers Los Angeles and Shanghai, plus two suite-zone cases, and is registered in the driver's PINS (scripts/__tests__/date-only-zone-pins-10183.test.ts). In ObjectCalendar.dstDayMove-10866:
   • The four datetime controls are renamed from "keeps the grid's instants" to "keeps its wall-clock time".
   • The first Los Angeles control's end moves from 2026-11-02T17:00:00.000Z (09:00 PST) to 2026-11-02T18:00:00.000Z (10:00 PST). This is the ruled instant change.
   • Its header prose says what changed. Its ten date day moves are untouched.
4. Docs. The plugin README's month-view drag table and the two month-view bullets in content/docs/plugins/plugin-calendar.mdx now say that a move and an end drag keep the time of day (AGENTS.md commandment Add automated testing infrastructure and CI/CD workflows #2).
5. Changesets. .changeset/11005-month-grid-calendar-days.md declares @object-ui/plugin-calendar: patch. The pending slice-4 changeset is reconciled in the dated-note form (see mechanism assumption 4).

The ruled zone pins

These run under TZ=America/Los_Angeles, where the clocks fall back on November 1st and spring forward on March 8th, 2026, and under TZ=Asia/Shanghai. Base is a33cf7e.

Ruled pin	Where	On base	On head
A datetime moved across a DST change keeps its wall-clock time	New pin, four Los Angeles moves	A 10:00 event on Nov 1 moved two days wrote 11:00. One moved back onto Nov 1 wrote 09:00. A 10:00 event on Mar 8 moved two days wrote 09:00. A span whose end crosses Nov 1 wrote its end at 09:00.	10:00 each
A local-midnight instant lands on the dropped day	New pin, two Los Angeles spans	The card's case: a start of 2026-11-01T07:00:00.000Z, grabbed on Nov 2 and dropped on Nov 3, wrote 2026-11-02T07:00:00.000Z (Nov 1, 23:00). A span ending at midnight on Mar 9, moved back one day, started at 2026-03-06T09:00:00.000Z (01:00).	Midnight of the dropped day
A date-only value is unchanged	Slice 4's ten day moves through ObjectCalendar, Los Angeles and Shanghai	Written by the repair	The same ten days, with the repair removed
A zone without DST behaves as before	New pin, four Shanghai drags	Exactly N times 24 hours	The same instants
resize-end follows the same rule	New pin, two Los Angeles end drags	Hours, minutes and seconds already kept; milliseconds dropped (19:30:15.000Z for 19:30:15.250Z)	The whole time of day

Mechanism assumptions (Zone 2), measured

1. Partly held. The move derived one deltaMs from local-midnight cells. resize-end did not: it set the drop day's clock from the old end with setHours(h, m, s, 0), so it already kept hours, minutes and seconds across a DST change. On base, the March 8th end drag passed and the November 2nd one differed only in milliseconds. The resize guards compare day cells, as assumed.
2. Held: the week and day views do not ride. The time grid places a moved event at its snapped minutes on the drop day's own clock (setHours(0, snapped) on the drop column's day). A throwaway probe in a forked child under Los Angeles (not committed) moved a 10:00 event off November 1st and onto it in the week view. It wrote 10:00 both ways: 2026-11-03T18:00:00.000Z and 2026-11-01T18:00:00.000Z.
3. Held: the repair is redundant, and B is what makes it so. With B in the grid and the repair removed, slice 4's ten day moves pass in both zones. Ablation: put the base grid back under the committed head (repair still removed), and four of those ten go red in Los Angeles. They are exactly the four that slice 4 named (see Evidence).
4. The named file does not describe the repair. .changeset/10866-calendar-gantt-date-only-days.md (slice 1) does not describe the repair. Its calendar sentence "A datetime field keeps its instant" is about the stored type, so it stays true under the ruling's own reading, and the file is untouched. The repair is described in slice 4's .changeset/10866-calendar-dst-day-moves.md. Two phrases there go false at this change: "The month grid moves each date…" and "…the grid's own arithmetic does not change". Both are now scoped "at this change", followed by a dated note naming this card. The front matter is byte-identical (the md5 of the first six lines matches the base). Its gantt and core bullets are untouched. check-changeset-overwrite reports the modification (report-only, exit 0), and that is expected.

Evidence

All counts are read from vitest's own summary lines.

• New pin, red on base. Before the fix, in a forked child with OBJECTUI_DATE_ZONE_CHILD=1: Tests 8 failed | 9 passed (17). The eight red cases:

  • the six Los Angeles moves;
  • the Los Angeles November end drag (milliseconds only);
  • the suite-zone end drag (milliseconds only).

  The Los Angeles March end drag, the rigs, the fixture case and every Shanghai case passed on base.

• Head, all calendar zone pins driven. CalendarView.monthMoveCalendarDays-11005, ObjectCalendar.dstDayMove-10866, ObjectCalendar.endDateNoSchemaZone-10866, ObjectCalendar.dateOnlyZone-10866 and calendarViewRenderer.dateOnlyZone-10866, forked with the flag: Test Files 5 passed (5), Tests 104 passed (104).

• Ablation. Run on committed head 55d7add. The base blob of CalendarView.tsx was checked out on its own, with ObjectCalendar.tsx staying at head (repair removed).

  • Landing proof: after the mutation the file hashed to the base blob 0fbcb72b, and the deltaMs count went from 0 to 4 while the moveByCalendarDays count went from 5 to 0.
  • Result, forked, driven: Tests 13 failed | 32 passed (45). The red cases are the eight new-pin cases, slice 4's four Los Angeles day moves (Oct 29 to 31 moved two days, Nov 1 to 3 grabbed on the 2nd, Oct 31 to Nov 2 moved back one, Mar 5 to 9 moved back one), and the first Los Angeles datetime control.
  • Restore, from a trap on EXIT/INT/TERM with absolute paths: git checkout HEAD -- brought the file back to the HEAD blob 29701d6f, and git diff HEAD came back empty.

• Package suite at 600e84c. pnpm exec vitest run packages/plugin-calendar/: Test Files 55 passed (55), Tests 365 passed | 85 skipped (450). The skipped cases are zone pins, which run in the driver's child.

• Zone-pin driver at 600e84c. scripts/__tests__/date-only-zone-pins-10183.test.ts: Tests 24 passed (24), which is every registered pin plus the child-exit case.

• Tests outside the package that name an edited file, derived with git grep over test files for the edited paths and symbols. The zone pins are excluded because the driver ran them. 14 files: Test Files 14 passed (14), Tests 1067 passed (1067). The 16 test files that read .changeset/: Test Files 16 passed (16), Tests 618 passed (618).

• Type-check. The dependency closure was built with turbo run build --filter='@object-ui/plugin-calendar^...' --concurrency=2: 13 tasks, all restored from turbo's shared worktree cache, none of them in this diff. Then pnpm --filter @object-ui/plugin-calendar type-check, which echoed tsc --noEmit && tsc -p tsconfig.test.json, exited 0. tsc -p tsconfig.test.json --listFiles lists both edited pins.

• Gates, all exit 0:

  • check-changeset-presence: "4 source file(s) of 1 released package(s) changed, and this change declares 1 changeset(s)".
  • check-changeset-no-major, -fixed, -overwrite (report-only, see above) and -claims (report-only). For -claims, five pending changesets name ObjectCalendar.tsx, the README or the plugin page. Each was re-read: they concern the record source, filter, sort and the colour and all-day fields, and none is falsified.
  • check-pending-changeset-literals, check-control-bytes and check-new-cross-file-line-citations ("0 new citation(s)").
  • check-test-path-roots, the three check-vi-mock-* gates and check-unreferenced-sources.
  • check-doc-fence-languages, check-doc-component-types and check-doc-example-ids.
  • check-governed-queue-guard --test over the nine paths: NOT GOVERNED.

• NOT MEASURED: check-doc-snippet-types (exit 2), check-doc-example-types (exit 2) and check-readme-exports (exit 1). All three stopped on their prerequisite: packages outside this closure are unbuilt, reported as [unbuilt-package] and "not on disk — run the build first". That means the runs never reached a verdict, not that the gates failed. The README and doc edits here change table rows and bullets only, with no fenced block. These gates belong to CI.

• Lint, narrowed and declared as a narrowing.

  • Population: the root config lints **/*.{ts,tsx}, and this diff has five such files.
  • Count: eslint --no-inline-config --format json returned 5 results with no "ignored" message: 0 errors in total. Warnings equal each modified file's base blob (CalendarView.tsx 24, ObjectCalendar.tsx 31), and the three test files have 0.
  • Invariance: eslint.config.js sets no parserOptions, project or projectService, so linting is not type-aware and this diff cannot move the verdict for any untouched file.

  Repo-wide lint is CI's.

Acceptance notes

The dev records these here and files nothing; the seat decides.

• A week or day view move of an overnight timed event shortens it (class (a): reproduced, pre-existing, unrelated to DST).
  • The time grid clips a timed event into one piece per day it touches. A move takes the grabbed piece's duration (durationMin = entry.endMin - entry.startMin), not the event's.
  • Measured with a throwaway jsdom probe (not committed): a 4-hour event from January 12th 22:00 to January 13th 02:00, dragged by its first-day piece to January 14th at 10:00, reached onEventDrop as 10:00 to 12:00, which is 120 minutes. ObjectCalendar's default drop handler writes the newEnd it is handed (read, not driven through an app).
  • Reach: the calendar's week and day view drag.
  • Dedupe words: week view drag overnight event duration, TimeGridView move durationMin clipped piece, calendar time grid move shortens event.
• objectui#10866 slice 5, which is serial behind this card. Its ObjectCalendar mixed-event half (a date start with a datetime end) was not measured here. With the grid moving by calendar days, a date start now comes back at local midnight of the dropped day. Re-price that half against this head.
• Observation, not measured, and out of this card's scope. When a gantt summary bar is dragged, GanttView shifts it and its descendants by one deltaMs (the group move and its live preview). Its axis is continuous time, so it is not known to be the same defect. It is not touched here. Carrier: none.

Commits carry only the model-free trailer pair.

---

Generated by Claude Code

[github-actions]

changeset-claim-re-read

⚠️ 5 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/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).

• names content/docs/plugins/plugin-calendar.mdx → content/docs/plugins/plugin-calendar.mdx — edited by this change

  A widening. A node authoring staticData or data without objectName now validates (it always rendered — the read is resolveRecordSourceConfig(schema), keyed on the three). Every document that validated before still validates: objectName alone still parses, an empty one included, because presence is !== undefined. The one shape the refinement refuses (none of the three) was refused before too, at objectName. The two static-data examples in content/docs/plugins/plugin-calendar.mdx are now annotated ObjectCalendarSchema and compile under the doc-snippet gate.

.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/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.

• names packages/plugin-calendar/README.md → packages/plugin-calendar/README.md — 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.

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.

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

[github-actions]

✅ Console Performance Budget

Metric	Value	Budget
Eager closure (gzip, 330 chunks)	3105.2 KB	3149.4 KB
Main entry chunk (gzip)	149.4 KB	350 KB
Entry file	index-CDN106Dg.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.72KB	6.21KB
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.22KB	10.61KB
auth (AuthShell.js)	3.49KB	1.40KB
auth (ForgotPasswordForm.js)	12.21KB	3.45KB
auth (LoginForm.js)	18.17KB	5.40KB
auth (PreviewBanner.js)	0.90KB	0.50KB
auth (RegisterForm.js)	6.72KB	2.24KB
auth (SocialSignInButtons.js)	9.70KB	3.93KB
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.70KB	10.94KB
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)	558.92KB	133.97KB
core (index.js)	9.93KB	3.94KB
create-plugin (index.js)	27.94KB	9.51KB
data-objectstack (index.js)	227.62KB	63.16KB
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.35KB	9.18KB
i18n (useSafeTranslation.js)	5.60KB	2.33KB
layout (index.js)	39.32KB	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.53KB	4.89KB
permissions (PermissionContext.js)	0.31KB	0.25KB
permissions (PermissionGuard.js)	0.89KB	0.45KB
permissions (PermissionProvider.js)	6.25KB	2.17KB
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)	52.02KB	14.87KB
plugin-charts (index.js)	84.09KB	22.93KB
plugin-chatbot (index.js)	198.22KB	46.97KB
plugin-dashboard (index.js)	137.56KB	36.67KB
plugin-designer (index.js)	215.78KB	44.42KB
plugin-detail (index.js)	233.49KB	61.79KB
plugin-editor (index.js)	2.23KB	1.05KB
plugin-form (index.js)	162.67KB	41.95KB
plugin-gantt (index.js)	170.35KB	42.19KB
plugin-grid (index.js)	228.33KB	62.59KB
plugin-kanban (index.js)	48.43KB	15.11KB
plugin-list (index.js)	115.86KB	28.64KB
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.07KB	9.15KB
plugin-tree (index.js)	11.21KB	3.89KB
plugin-view (index.js)	89.54KB	22.44KB
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.39KB	2.17KB
types (api-types.js)	0.20KB	0.18KB
types (app.js)	3.83KB	1.49KB
types (base.js)	0.20KB	0.18KB
types (blocks.js)	0.20KB	0.18KB
types (complex.js)	3.19KB	1.62KB
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)	19.30KB	6.99KB
types (system-fields.js)	3.33KB	1.54KB
types (theme.js)	6.28KB	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: 600e84cb52cab4b9e59d956a86e3c3ed0421233a
Local-runs: none

① Derived judgments

Inputs read: card #11005 (body; comments 5874661711 decision-box, 5881826705 ruling B, 5882077455 claim, 5882783174 os-dev-report), PR #11036 (body, nine-file list, net diff against main), the 43 check-runs on the head (40 success; 3 skipped conditional lanes: coverage, coverage shard, dependabot; none failed, none pending), plus contents reads at the head for context only: CalendarView.tsx, ObjectCalendar.tsx, .changeset/10866-calendar-gantt-date-only-days.md, vitest.config.mts, the root listing. Nothing built, run or re-run.

1. Month-grid move — RIGHT. MonthView.handleDrop now counts calendarDaysBetween(anchorDay, newTargetDay) (difference of local Y/M/D taken on the UTC calendar, so always a whole number) and applies moveByCalendarDays (setDate on a copy) to the start and to the end. That is the ruled form in 5881826705: the calendar days between the grab cell and the drop cell, applied with setDate on a local copy, hours / minutes / seconds untouched. Public surface: the instants CalendarViewProps.onEventDrop receives from a month-view drag change across a DST change (10:00 stays 10:00; a local-midnight start lands at midnight of the dropped day). Ruled, deliberate, and stated in the changeset. The legacy no-sourceDay fallback (anchor at the event's start day) is preserved.
2. Month-grid resize-end — RIGHT. The end moves by calendarDaysBetween(oldEnd, newTargetDay) through moveByCalendarDays; the start is handed back unchanged; the two guards (same cell, drop before the start day) are kept. Read at the head: the handle renders only where isSpanEnd, and eventsByDate puts that on the end's own local day (a midnight end included), so the grabbed cell is the end's day and the ruling's grab-cell-to-drop-cell wording holds for the end drag. Milliseconds are now kept where the old setHours(h, m, s, 0) zeroed them: a consequence of the ruled setDate-on-a-copy form, not an addition.
3. ObjectCalendar day repair removed — RIGHT. toMovedDateValue, isStoredDay and DAY_MS are deleted (all module-private; no export touched) and the default drop handler writes through toStoredDateValue again. A date read at local midnight (toDisplayDate) and moved by setDate stays at local midnight of the dropped day, and toStoredDateValue writes its local day: the same day the repair wrote. The ruling's condition ("removed once measured redundant") is met: slice 4's ten day moves in ObjectCalendar.dstDayMove-10866 are untouched and green on the head, and the dev's ablation (base grid put back with the repair still gone: four Los Angeles day moves red) shows B is what makes it redundant.
4. Week and day views unchanged — RIGHT. The ruling has them ride only if their drop arithmetic is the same elapsed-time form. Read at the head: TimeGridView's move places the start with setHours(0, snapped) on the drop column's own day, and its two resizes with setHours(0, minutes) on that day; there is no two-midnights deltaMs. Not the ruled form, so not riding is the correct reading. (Its end is newStart plus durationMin in milliseconds, a same-day duration form; see ③.)
5. Ruled zone pins — RIGHT and complete. New CalendarView.monthMoveCalendarDays-11005: Los Angeles six moves and two end drags, including the card's exact case (Nov 1 00:00 PDT, grabbed on the 2nd, dropped on the 3rd, now Nov 2 00:00 PST); Shanghai four drags at exactly N x 24 h; two suite-zone cases; a rig case and a fixture-validity case per zone so a child whose zone did not move goes red. Registered in the driver's PINS; scripts/**/*.test.ts is in the root unit project, so the driver (which fails unless every pin ran and passed in a forks child) runs inside CI's Test shards, all success. The ruling's five pins map one to one: DST wall-clock kept; local-midnight instant lands on the dropped day; date-only unchanged (the ten day moves); zone without DST as before; resize-end under the same rule. The single changed expectation in dstDayMove-10866 (first Los Angeles datetime control's end, 09:00 to 10:00 PST on Nov 2) is exactly the ruled instant change; every other expectation there is untouched.
6. Docs (README gesture table, plugin mdx month-view bullets) — RIGHT. Prose only; each states the ruled behaviour (time of day kept for a move and for an end drag).
7. No other public-surface movement. export { CalendarView } and the test-only export are unchanged; no prop, type or config accept set moves. README Export Check success.

② Semver level

• .changeset/11005-month-grid-calendar-days.md: '@object-ui/plugin-calendar': patch — RIGHT. The diff publishes a behaviour fix inside one released package with no API added, removed or re-signed; the ruling prices it patch. Its prose matches the diff (move; end drag including milliseconds; date fields through the repair's removal; week and day views unchanged). Changeset Declaration, Changeset Bump Policy, Changeset Fixed Group Check, Changeset Claim Re-read and Changeset Overwrite Report: all success on the head.
• Reconciliation — RIGHT. .changeset/10866-calendar-dst-day-moves.md (slice 4) carried two sentences this diff falsifies ("The month grid moves each date of an event by the milliseconds…" and "the grid's own arithmetic does not change"); both are now scoped "at this change" with a dated note naming objectui#11005; the front matter is untouched (the hunk starts at line 7) and the gantt and core bullets are untouched. The order's named file, .changeset/10866-calendar-gantt-date-only-days.md (slice 1), read at the head: its "A datetime field keeps its instant" sits under Writes and describes the type split (instant, not day), which the ruling itself says still governs the binding; no sentence there is falsified, so leaving it untouched is right.
• Clause-②: no on the PR body — RIGHT; it matches the ruling's execution parameter and the claim's reading: the written instant changes by ruling, and no declared field shape, schema or accept set moves.

③ Boundary flags

Dev flags (deviations in os-dev-report 5882783174), each answered:

1. File-surface additions (driver PINS entry; packages/plugin-calendar/README.md; content/docs/plugins/plugin-calendar.mdx) — ACCEPTED. The PINS entry is the only way the runIf(DRIVEN) zone cases run at all, so it is part of "zone pins under Los Angeles and Shanghai"; the two docs are prose under the repo's docs-driven rule. Neither plugin-gantt nor an objectui#10866 slice-5 item is touched: both of the claim's ⛔ bounds hold.
2. Reconciled slice 4's changeset rather than the named slice-1 file — ACCEPTED (see ②): the named file is not falsified and the slice-4 file was; the conditional's purpose, that no false pending sentence ships, is served.
3. resize-end now keeps milliseconds — ACCEPTED. The ruled setDate-on-a-copy form keeps every sub-day component; "hours / minutes / seconds untouched" is a floor, not an instruction to zero milliseconds. Pinned, and stated in the changeset.
4. Commit-trailer form — NOT A CONTRACT ITEM. No gate reads it; the repo's AGENTS.md governs trailers.
5. Lint narrowed locally; check-doc-snippet-types, check-doc-example-types, check-readme-exports NOT MEASURED locally — ANSWERED BY THE HEAD'S CHECK-RUNS: Lint, Doc Snippet Type Check, Doc Component Type Check, Doc Example Id Check and README Export Check are all success.

open_questions: empty — nothing to answer.

For the seat, from the report's out-of-scope notes; none bears on this verdict: (a) a week or day view move of an overnight timed event shortens it to the grabbed piece's duration — pre-existing and DST-independent, and readable in the head source (durationMin: entry.endMin - entry.startMin, newEnd = newStart + durationMin); the same line also means a time-grid event spanning the transition hour itself gets an elapsed-duration end, a same-day form outside this ruling; carrier to be chosen. (b) objectui#10866 slice 5's mixed-event half is to be re-priced against this head, since a date start now comes back at local midnight of the dropped day. (c) GanttView moves a summary bar and its descendants by one deltaMs on a continuous axis: observation only, out of scope. The PR is still a draft.

Implemented-by: claude/issue-11005-month-grid-calendar-days
Reviewed-by: session_011p7ikEivgXefNDaE5S5Uec

VERDICT: PASS

---

Generated by Claude Code