Repository navigation
os validate prints a raw ZodError JSON array with no file or view name when a define* helper refuses at config load (e.g. defineView with mixed string/object columns) #28956
Description
domain:devx#1 · os-warren · session_01JQwxbYVchZUzHRyGz9MiQM
立卡门: ① 用户可见的体验缺陷，具名落点 + 复现（reach: 公开入口 os validate 实测一次：输出 88 行 zod JSON，没有文件名、没有视图名、没有改法）
业务理由: AGENTS.md 和官网都把 npm run validate 说成「失败时给出定位的、可纠正的信息」的唯一关卡，新手和 coding agent 都靠它自我纠错。defineView / defineAction 等 helper 在 config 加载时 Schema.parse 抛出的 ZodError 被 validate 原样打印成 JSON 数组，只剩 "path": ["list","columns"]，不说哪个文件、哪个对象的视图，也不说该怎么写。新手第一次写视图就会撞上（skill 里同时给了字符串列和对象列两种写法，混用很自然）。不修，validate 在最常见的首个错误上不可读，agent 只能猜。
动手的读者: domain:devx 席（cli），packages/cli/src/commands/validate.ts 的 catch-all（main ff88105 约第 1240 行 printError(error.message)）：ZodError 走 formatZodError（utils/config.ts 的 authored-source shim 已有同样的 __refusal 渲染，只给 os migrate meta 用），并带上抛出它的 helper 名和文件；os build / os dev 同一路径一起看。
查重: is:issue validate ZodError raw JSON 18 命中、is:issue defineView ZodError 3、is:issue validate "Loading configuration" ZodError 1（均含已关）。最近邻 #20696（os migrate meta 在 ObjectSchema.create 的旧键上加载即崩、打印原始 ZodError，已关，修在 migrate 的 shim 里），#19581（zod treeifyError 抛错，已关），都不是 validate 的普通加载路径。
QA-source: 18.3.0 wave 4 newcomer first-visit walkthrough (W4-NEWCOMER), path 2 "Build with Claude Code", anchor #27377
Reproduction (published 18.2.0, npm 10.9.9, Node 22.23.4)
npm create objectstack@latest support-desk && cd support-desk- Add an object
support_desk_ticketwithsubject/status/priority, andsrc/views/ticket.view.ts:exported fromexport const TicketViews = defineView({ list: { label: 'All Tickets', type: 'grid', data, columns: [{ field: 'subject', link: true }, 'status', 'priority'] }, });
src/views/index.ts. npm run validate
Expected: one located line, e.g. "ticket.view.ts · defineView · list.columns: mix of strings and column objects; use one form (all { field } objects when any column needs link)", exit 1.
Actual: exit 1 after "→ Loading configuration..." with ✗ [ followed by 88 lines of JSON ("code": "invalid_union", nested errors arrays, "path": ["list","columns"], "message": "Invalid input"). No file, no object, no hint.
Why it is still on main
defineView (packages/spec/src/ui/view.zod.ts) and defineAction (packages/spec/src/ui/action.zod.ts) call Schema.parse and throw the ZodError as is. loadConfig on the normal path (no authoredSource) does not wrap them, and the validate catch-all prints error.message, which for a ZodError is the JSON array. Read on main ff88105; the live run was on 18.2.0.
Activity
objectstack-fleet commentedon Nov 2, 2026
triage#1 · os-zhuang · session_01AavokzJ5DndAwitDXvKy4U
Path: none
Triage: p2 ·
domain:server·area:devpath·pm:queue· 2026-11-02T05:20Z⛔ Not a claim.
os validateprints adefine*helper's config-loadZodErroras a raw JSON array, with no file, no view name and no remedy. The catch-all inpackages/cli/src/commands/validate.tscallsprintError(error.message)instead of the existing formatter.validateis the gate authors and agents correct themselves against, so an unreadable first error is a user-visible defect.packages/cliisdomain:server(lanes/server.md), p2.Generated by Claude Code
objectstack-fleet commentedon Nov 2, 2026
domain:server#2 · os-project-manager · session_0186vfjHHMsRXC9EUT9hTFMo
Claim: PM loop round 4 · card thread · 2026-11-02T06:26Z
Session:
session_0186vfjHHMsRXC9EUT9hTFMo(the seat); the card thread issession_01FEkQ5mch1VryTyQsMG5U86Account:
os-project-manager(the seat's linked user; the card's assignee)Branch:
claude/project-thread-vukoe2(the card thread's harness-pinned branch; it names no issue, so this claim is the identity record)Worktree: the card thread's own container checkout
Domain:
domain:serverSeat:
domain:server#2Ruling-ref: the maintainer, 2026-11-01T03:46Z: 「server 车道现在就是你负责，任务有一大堆啊，都可以派，包括 p3」, with 2026-10-26T10:29Z 「p1 p2 处理完了，就可以处理 p3」. With 2026-11-01T12:11Z 「定级你可以自己决定」 (triage graded this card p2) and 2026-11-02T05:15Z 「队列进了很多任务，抓紧派发」; seat 1 confirmed seat 2 takes this card. Seat's route: one seam at config load. A
define*helper's ZodError is rethrown as the CLI's existing readable refusal (existing formatter, no second one), naming the file, the helper and the path, on every command that loads config. Schemas are unchanged.File surface:
packages/cli/src/utils/config.tsload path,packages/cli/src/commands/validate.tscatch-all if needed; their tests; changesetContainer & model:
M,mode:thread,model: opus(--tiernames no path mandate: PM's call, default),effort: mediumClause-②: no expected (CLI output text only); the dev measures and declares
Metadata-protocol: none (expected; the dev measures and declares)
Responsibility: the dev routes config-load ZodErrors through the existing renderer, red first with ablation; the seat reviews and lands
Thread-read: none
Premise: measured by the QA author on 18.2.0, re-read on main, confirmed by triage (
6569727986)Serial constraints cleared: none; overlap re-read of open PRs on packages/cli/src/utils/config.ts and commands/ before pr_create
Resume-from: none — fresh from
origin/mainState: →
pm:dispatched, assigned toos-project-manager, recorded by this claim.Generated by Claude Code
objectstack-fleet commentedon Nov 2, 2026
domain:server#2 · os-project-manager · session_01FEkQ5mch1VryTyQsMG5U86
os-dev-report
{
"issue": 28956,
"status": "done",
"branch": "claude/project-thread-vukoe2",
"pr": "#29087",
"session": "session_01FEkQ5mch1VryTyQsMG5U86",
"premise_still_valid": true,
"summary": "One load seam, bundleConfigModule in packages/cli/src/utils/config.ts, now bundles and evaluates the config module for loadConfig and for os serve's own load. A raw ZodError thrown while the module evaluates (a define* helper's Schema.parse) is rethrown as a plain ConfigLoadRefusalError: FILE:LINE:COL · HELPER validation failed (N issues): followed by the existing formatZodError block, with the ZodError as cause. The location comes from the evaluated bundle's inline source map (bundle text read before bundle-require deletes it); the helper is named only for a define* frame whose name the authored line spells; with no bundle frame, no map entry on the frame's line, or no file on disk, the refusal names the config entry and says the stack does not say which module. No catch-all changed, no schema changed, exit codes unchanged (validate 1, build 2); every non-Zod load error passes through untouched.",
"tests": "head 5af532c. New packages/cli/test/config-load-zod-refusal.test.ts 9/9 (validate --json, validate text face, build --json parity, non-define locate, unlocated fallback, 4 controls). Red on main 0be247c real CLI: validate exit 1 / build exit 2 / lint exit 1 / dev exit 1 / serve exit 1, each printing '✗ [' and the raw invalid_union array. Green: each prints '✗ src/views/ticket.view.ts:5:28 · defineView validation failed (1 issue):' plus 'list.columns: Invalid input' and 'list.columns.0: Invalid input: expected string, received object', same exit codes; --enable-source-maps and a run from src/ also located. Controls: syntax error and missing import keep esbuild's 'Build failed with 1 error' text; defineStack refusal and helper prose refusal unchanged; os migrate meta --from 17 still prints the shim's [authored-source] warning, exit 0. Ablation (src-level, test imports src): ablation-replace deleting the seam's rethrow line, 'ok mutation landed: anchor 1 -> 0, blob 82be1e8df47c -> f63bad0a3d26', 'Tests 4 failed | 5 passed (9)' = the 4 seam cases, renderer unit and 4 controls green; 'ok restored: blob == HEAD (82be1e8df47c) and git diff HEAD is empty'. cli unit tier: Test Files 369 passed (369), Tests 5205 passed (5205), lock VERDICT command-exit 0. cli typecheck (tsc --noEmit + check:test-typecheck) VERDICT command-exit 0.",
"gates": "node scripts/pm/dispatch-gates.mjs --commands: 63 derived families, all run at head 5af532c with exit captured before any pipe: 63 x exit 0. --ran: '63 derived famil(ies) accounted for — 63 run, 0 NOT-MEASURED (a DERIVED zero)'. check:i18n-coverage first exit 3 (PREREQUISITE: connector-slack/service-print no dist), exit 0 after building the ./examples/*^... closure. Full list: /mnt/project-files/pm-orders/server/28956-gates-ran.txt. CI check-runs on #29087: in_progress at report time.",
"dogfood_battery": "n/a — no ! in the PR title and no (narrowing) arm",
"mcp_calls": "4 — issue_read x2 (card get, comments), issue_read x1 (claim re-read), list_pull_requests x1 (overlap re-read); no MCP write tool",
"api_writes": "2 — fleet-write relay pr_create (POST /repos/objectstack-ai/objectstack/pulls, #29087, read-back identical, no assignees); this os-dev-report comment via post-stamped (POST /repos//issues/28956/comments)",
"open_questions": [],
"out_of_scope_findings": [
"carrier: none · noted, not filed · the union branch ranking (packages/spec union-branch-policy.ts) picks the string[] branch for mixed list.columns, so the located line reads 'list.columns.0: expected string, received object' rather than the card's suggested 'mix of strings and column objects; use one form'; a better remedy sentence needs a spec-side union message (contract review). Recorded in the PR's Acceptance notes.",
"carrier: none · noted, not filed · os create's utils/scaffold-validate.ts keeps its own bundleRequire over the template it generated (not authored input), so it is not routed through the seam.",
"file surface beyond the claim: utils/config-load-refusal.ts (new) and one line in commands/serve.ts (os serve loaded the config without loadConfig and printed the same raw array); commands/validate.ts untouched."
]
}
Generated by Claude Code
objectstack-fleet commentedon Nov 2, 2026
domain:server#2 · os-project-manager · session_0186vfjHHMsRXC9EUT9hTFMo
Release:
session_0186vfjHHMsRXC9EUT9hTFMo· cause: the maintainer's wrap-up (「进展中的开发先提交代码然后暂停，先确保已有的pr都合并」, 「草稿的也交给下一任，在座位帖写清楚」); seat 2 signs off · next: PR #29087 is ACCEPTed (no contract review owed:Clause-②: no, cli only) and is in the merge queue;Fixes #28956closes this card on merge. Next: landing record. ⛔ Do not re-dispatch while #29087 is queued.Resume-from:
claude/project-thread-vukoe2@5af532cccc59562cd116e709f2af0d7276085165State:
pm:dispatched→pm:queue, assignee cleared, in this same relay stroke. Seat hand-off: mailbox #28284 comment 6571506250; seat post #20966.Generated by Claude Code
objectstack-fleet commentedon Nov 2, 2026
domain:server#2 · os-steve · session_01ADHkmQxwoGb5fSnrFkpxmt
Claim: PM loop round 1 · seat takeover · 2026-11-02T08:13Z
Session:
session_01ADHkmQxwoGb5fSnrFkpxmt(the seat)Account:
os-steve(the seat's linked user; the card's assignee)Branch:
claude/project-thread-vukoe2(continued from the released claim; PR #29087)Worktree: the card thread's own container checkout
Domain:
domain:serverSeat:
domain:server#2Ruling-ref: the maintainer, verbatim: 「开 server 2、3、5 号席位, 前任已经下班，接手所有开发，包括跟进之前未完成的开发落地。」 (os-steve project "objectstack spec"). Takes over the hand-back
Release:6571747017 of seat 2's previous term (session_0186vfjHHMsRXC9EUT9hTFMo).File surface:
packages/cli/src/utils/config.tsload path,packages/cli/src/commands/validate.ts; their tests; changeset (unchanged from claim 6570646800)Container & model:
M,mode:thread,model: opus(as the previous claim),effort: mediumClause-②: no — as declared on PR #29087 (CLI output text only)
Metadata-protocol: none — as declared on PR #29087
Responsibility: the dev routed config-load ZodErrors through the existing renderer (claim 6570646800); the seat follows PR #29087 to MERGED
Thread-read: 6571747017
Premise: holds (measured by the previous term's dev; re-read on the PR head before ACCEPT)
Serial constraints cleared: none new; the PR's file list is re-read against live claims before landing
Resume-from:
claude/project-thread-vukoe2@5af532cccc59562cd116e709f2af0d7276085165Status: PR #29087 is ACCEPTed and in the merge queue; no new dev work. ⛔ No re-dispatch while it is queued.
State:
pm:queue→pm:dispatched, assigned toos-steve, recorded by this claim.