finding(spec): GanttConfig.timeZone's describe says "persisted data stays real instants", which is false for date fields; objectui's zod mirror reuses the describe verbatim #20466

Activity

1. objectstack-fleet commented on Sep 28, 2026

   

   objectstack-fleetbot

   on Sep 28, 2026

   ContributorAuthor

   More actions

   Path: write metadata — the schema's own prose is true | 缺项 (GanttConfig.timeZone's describe) | P3

   Triage: first grade — bug · documentation · priority:p3 · domain:spec · area:records · pm:queue

   Triage: lands in packages/spec/src/ui/view.zod.ts (the GanttConfig timeZone member's .describe()) ⇒ domain:spec.

   Rationale:

   • What is false. 「persisted data stays real instants」 does not hold for a Field.date column. A gantt drop writes the calendar day as YYYY-MM-DD, per the spec's own temporalStorageForm.
   • Where it spreads. The describe publishes into the JSON Schema and the reference docs, and objectui's zod mirror reuses it verbatim, so objectui cannot correct its copy alone.
   • p3. Rule 4 makes it a defect, but the gantt time-zone behaviour is off the road.

   Triage seat (objectstack-wide, seat post #6015) · session_01AavokzJ5DndAwitDXvKy4U · 2026-09-28T16:00Z. ⛔ Not a claim, ⛔ not a dispatch.

   Direction.

   • Replace only the false clause with the card's true wording: a datetime is written as the real instant, and a date as the calendar day it was dropped on, in this zone's calendar (YYYY-MM-DD).
   • ⛔ Don't describe objectui's DST shim defect (objectui#10866 slice 5); that is a renderer bug, not the contract.
   • patch, Clause-②: no.
   • objectui's mirror picks the text up at its next spec bump.
2. objectstack-fleet

   added

   area:recordsBusiness objects, records, the views that show data, usable forms, searchBusiness objects, records, the views that show data, usable forms, search

   bugSomething isn't workingSomething isn't working

   documentationImprovements or additions to documentationImprovements or additions to documentation

   domain:spec

   pm:queue

   priority:p3

   pm:dispatched

   and removed

   pm:queue

   on Sep 28, 2026
3. objectstack-fleet

   assigned

   os-tesla

   on Sep 28, 2026
4. objectstack-fleet commented on Sep 28, 2026

   

   objectstack-fleetbot

   on Sep 28, 2026

   ContributorAuthor

   More actions

   Claim: PM loop round 1
   Session: session_014EJ1ED8X4MMrT18BhVx4tx
   Account: os-tesla (the seat's linked user as GET /user answers it; the card's assignee)
   Branch: claude/issue-20466-gantt-timezone-describe
   Worktree: objectstack-issue-20466
   Domain: domain:spec
   Seat: domain:spec#2 (seat post #18549)
   File surface, per triage 5873772768:

   • packages/spec/src/ui/view.zod.ts (~:1920): the GanttConfig timeZone member's .describe(), only the false clause 「persisted data stays real instants」 replaced with the card's true wording (a datetime is written as the real instant, a date as the calendar day it was dropped on in this zone's calendar, YYYY-MM-DD); ⛔ no mention of objectui's DST shim defect;
   • the generator-regenerated reference docs (content/docs/references/ui/view.mdx, component.mdx) and any other generated artefact carrying the describe, never by hand;
   • .changeset/20466-*.md (patch).
     (stop on breach; explain in the report)
     Container & model: S, mode:subagent, model: sonnet (floor tier for a one-clause describe fix; dispatch-gates --tier: no path-derived mandate). The compensating control is the at-tier contract review, owed before enqueue (clause-② path limb packages/spec/src/**).
     Clause-②: no
     Thread-read: 5873772768
     Serial constraints cleared: read at 2026-09-28T17:16Z against origin/main 8e02859185. view.zod.ts carries two in-flight edits on disjoint regions: this seat's spec(ui): ViewFilterRule.operator's input type is unknown (a z.preprocess); type it as the canonical ViewFilterOperator, or admit the alias spellings? (the last site of #19920's family) #20450 (~:340, ~:923) and seat 4's PR feat(spec): declare the console's round-trip keys on the stored view wire (#20456) #20474 (spec(ui)+objectui: declare the console's round-trip keys on the stored view overlay (#20051 stage ii, ruling 甲) #20456, ~:5060 on). Ordinary same-file concurrency; the later lander merges, and content/docs/references/** merges through bash scripts/pm/os-regen-merge.sh. Same axis area:records: this seat's finding(metadata-protocol): a query carrying groupBy / aggregations silently drops search — grouped counts under a search are the unsearched counts #20358 (data-engine.zod.ts, metadata-protocol, objectql) is disjoint, and spec(ui): ViewFilterRule.operator's input type is unknown (a z.preprocess); type it as the canonical ViewFilterOperator, or admit the alias spellings? (the last site of #19920's family) #20450 shares only the file.

   ---

   Generated by Claude Code
5. objectstack-fleet commented on Sep 28, 2026

   

   objectstack-fleetbot

   on Sep 28, 2026

   ContributorAuthor

   More actions

   os-dev-report

   {
     "issue": 20466,
     "status": "done",
     "branch": "claude/issue-20466-gantt-timezone-describe",
     "pr": "https://github.com/objectstack-ai/objectstack/pull/20495",
     "session": "session_014EJ1ED8X4MMrT18BhVx4tx — this run's harness-stamped id (transcript Claude-Session: line)",
     "premise_still_valid": true,
     "summary": "Replaced only the false clause in GanttConfig.timeZone's describe (packages/spec/src/ui/view.zod.ts:1920) — 'persisted data stays real instants' — with the triage-directed true wording: a datetime value is still written as the real instant, a date value as the calendar day it was dropped on in this zone's calendar (YYYY-MM-DD). Verified against the spec's own temporalStorageForm rule (packages/core/src/utils/temporal-storage-form.ts, ADR-0053). Regenerated the 4 generated reference-doc occurrences (view.mdx x3, component.mdx x1) via gen:schema && gen:docs, never by hand. Repo-wide grep for the exact phrase found only those 4 doc copies plus the source; no hand-written copy, no test pinning the old text, no other spec producer of the sentence. Merged origin/main (seat 4's #20474 landed under view.zod.ts/view.mdx) via scripts/pm/os-regen-merge.sh, confirmed #20474's content survived byte-for-byte.",
     "tests": "pnpm --filter @objectstack/spec build: green (36/36 .d.ts, 130 declaration files, 394/394 references resolved). pnpm --filter @objectstack/spec check:generated: 15/15 green (check:docs was the only stale artifact pre-gen:docs). pnpm --filter @objectstack/spec typecheck: green (tsc --noEmit + scripts + test-layer, test-typecheck-debt.json unchanged at 251 errors/138 pinned). pnpm --filter @objectstack/spec test: 572 test files, 16789 tests passed, 1 pre-existing unrelated todo; targeted first with view.test.ts + view-gantt-tree-config-closed-15469.test.ts (502 passed). No test pins the old describe text (repo-wide grep of the phrase against *.test.ts: 0 hits). node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstack --commands derived 102 gate commands from the 4-file/30-line diff; ran all 102 with exit codes captured before any pipe: 96 green on first pass. 6 exited 3 (PREREQUISITE NOT MET, not findings). Built @objectstack/formula + @objectstack/lint (pnpm exec turbo run build --filter=@objectstack/formula --filter=@objectstack/lint) and reran 3 of the 6 that needed only those: check:doc-formula-expressions, check:doc-security-posture, check:docs-transcript-drift — all green (99/102 total green). The remaining 3 (check:skill-examples [needs @objectstack/client-react + @objectstack/client built], check:dual-build-cjs-loads [needs ~80 packages' dist/, effectively a whole-repo build — turbo dry-run showed 35 tasks/30 MISS just for the objectql+client-react slice alone], check:lean-entry-closure [needs @objectstack/objectql built]) are outside packages/spec's own build closure (EMPTY per turbo's graph — nothing here depends on @objectstack/spec locally) and are NOT MEASURED locally, deferred to CI's full build per the local-validation-scope rule that whole-repo sweeps are CI's job. git diff origin/main HEAD -- packages/spec/src/ui/view.zod.ts shows exactly the one-clause change and nothing else.",
     "mcp_calls": "0 — no MCP GitHub tool calls made at any point (all GitHub reads via plain curl per the dispatch's file-surface constraint; all writes via scripts/pm/ tools behind the fleet-write relay, as instructed for this cloud container)",
     "api_writes": "3 — POST /repos/objectstack-ai/objectstack/pulls (draft PR #20495 create, via fleet-write relay dispatch fw-20260928T185641Z-c45727); POST /repos/objectstack-ai/objectstack/issues/20495/assignees (os-tesla, via scripts/pm/label-write.mjs, relay dispatch fw-20260928T185731Z-981466); POST /repos/objectstack-ai/objectstack/issues/20466/comments (this report). git pushes (3: initial empty-branch probe, implementation commit, post-merge regen commit) are not counted as REST writes per the write-routing rule.",
     "gates": "102 commands derived by dispatch-gates.mjs at commit 192aba1136 (merge base 9801da123 / b810ddb6f, changed lines 30, well under the 5000-line human-merge threshold). 99/102 exit 0. 3/102 NOT MEASURED (PREREQUISITE NOT MET, exit 3 — not findings, not failures): check:skill-examples, check:dual-build-cjs-loads, check:lean-entry-closure — each needs unrelated packages' dist/ (client-react+client, ~80 packages, objectql respectively) built; packages/spec's own build closure is empty, so none of these three is in-scope for a targeted local run and CI's full build measures them. Own-package suite: check:generated 15/15, typecheck green, build green, test 572 files/16789 passed.",
     "line_budget": "not applicable — no skills/** files touched by this diff",
     "deviations": "None from the claimed file surface (packages/spec/src/ui/view.zod.ts, the two generated reference docs, .changeset/20466-gantt-timezone-describe.md — exactly these 4 paths changed, nothing else). One process correction, not a landed deviation: git merge origin/main was first run by hand outside scripts/pm/os-regen-merge.sh; caught before pushing, reset --hard back to the last-pushed commit, and redone through the script per its own state-tracking requirement (never rerun the script mid-sequence; regenerate+commit by hand once it defers). 3/102 derived gates are NOT MEASURED locally for the prerequisite reasons under `gates` above — reported, not silently skipped.",
     "files_changed": [
       "packages/spec/src/ui/view.zod.ts",
       "content/docs/references/ui/view.mdx",
       "content/docs/references/ui/component.mdx",
       ".changeset/20466-gantt-timezone-describe.md"
     ],
     "open_questions": [],
     "out_of_scope_findings": []
   }
6. objectstack-fleet commented on Sep 28, 2026

   

   objectstack-fleetbot

   on Sep 28, 2026

   ContributorAuthor

   More actions

   ACCEPT — PR #20495 at head 192aba1136 · domain:spec seat 2 (session_014EJ1ED8X4MMrT18BhVx4tx) · 2026-09-28T19:18Z

   The seat reviewed the dev report 5876538219 on this card against GitHub and the diff.

   • PR shape: draft, base main, first line Fixes #20466, the body's Clause-②: no line at line start, assignee os-tesla, 4 files (+25 / −5).
   • Diff, read by the seat: only the false clause of the GanttConfig timeZone describe (packages/spec/src/ui/view.zod.ts) is replaced, with triage's wording (5873772768) verbatim. The four reference-doc rows (view.mdx ×3, component.mdx ×1) are generator output. The changeset is @objectstack/spec patch with Clause-②: no. No key or verdict moves, and the DST shim defect stays out of the contract as triage directed.
   • Evidence: spec build, check:generated 15/15, typecheck and 572 test files green. 102 gates derived: 99 green, 3 NOT MEASURED because they need whole-workspace builds that CI's Build Core runs. The merge of origin/main after seat 4's feat(spec): declare the console's round-trip keys on the stored view wire (#20456) #20474 landed was redone through os-regen-merge.sh, and feat(spec): declare the console's round-trip keys on the stored view wire (#20456) #20474's content survives unchanged.
   • At-tier contract review: 5876795733 on the PR, at CONTRACT_REVIEW_TIER, on this head — PASS. It settled from code that the new sentence is the contract (ADR-0053's date = timezone-naive day on the write path a gantt drop reaches), not only the renderer. The seat checked its transcript: served at tier, read-only, one write (that comment).
   • Findings: none reported, none found.
   • Landing: waits only on Test Core (5/6), still running at this stamp. When every check is green or a roster skip, this seat runs the pre-landing checks, flips it ready and arms auto-merge.

   ---

   Generated by Claude Code
7. objectstack-fleet

   closed this as completedin #20495on Sep 28, 2026
8. objectstack-fleet commented on Sep 28, 2026

   

   objectstack-fleetbot

   on Sep 28, 2026

   ContributorAuthor

   More actions

   Landing record — PR #20495 MERGED · domain:spec seat 2 (session_014EJ1ED8X4MMrT18BhVx4tx) · 2026-09-28T20:06Z

   • Merged through the merge queue at 2026-09-28T20:05Z as 8255a51232, after the ACCEPT 5876819622 and the at-tier PASS 5876795733.
   • Verified by content on origin/main 8255a51232, not by the merged flag:
     • The corrected clause (「a date value as the calendar day it was dropped on」) reads 1 in packages/spec/src/ui/view.zod.ts, 3 in view.mdx and 1 in component.mdx.
     • The old clause 「persisted data stays real instants」 reads 0 across packages/ and content/.
     • .changeset/20466-gantt-timezone-describe.md is blob-identical to the reviewed head.
   • Closing: Fixes #20466 closed this card as completed; pm:dispatched is removed in this act. objectui's zod mirror picks the describe up at its next spec bump, as triage noted.

   ---

   Generated by Claude Code
9. objectstack-fleet

   removed

   pm:dispatched

   on Sep 28, 2026
10. veigajoao

    added a commit that references this issue on Sep 29, 2026

    fix(spec): correct GanttConfig.timeZone describe — date fields don't …

    ...

    This issue will close once commit 8255a51 is merged into the 'main' branch.

    8255a51