`objectui check` 把每个 JSON 文件的根 `type` 都当成组件键判定,于是在任何 Node 工程里都对 package.json 的 `"type": "module"` 报未知类型

[yinlianghui]

发现于 #5115 的实施(PR #5128)反向验证的探针目录里。半径外,未夹带进 PR。Filed unassigned, not claiming.

现象

packages/cli/src/commands/check.ts 把 cwd 下所有 JSON 文件(除 node_modules / dist / .git)glob 出来,凡是根对象有 type 字符串的,就拿去和组件键集合比:

const files = globSync('**/*.{json,yaml,yml}', { cwd, ignore: [...] });
...
if (content && typeof content === 'object' && content.type) {
  if (typeof content.type === 'string' && !isKnownSchemaType(content.type)) {
    console.log(chalk.yellow(`⚠️ Unknown schema type "${content.type}" in ${file}`));
  }
}

type 在 JSON 里远不止「SDUI 组件键」一种词汇表 —— 最常见的就是 package.json 的 "type": "module"。实测(探针目录里放一个最小 package.json):

$ node packages/cli/dist/cli.js check
Object UI Schema Check
Analyzing 8 files...
⚠️ Unknown schema type "module" in package.json      # 不是 schema,是包清单
⚠️ Unknown schema type "totally-made-up-xyz" in g-bogus.json
...
✓ All checks passed

任何用户在自己的工程根目录跑 objectui check,第一行警告就是自己的 package.json。同族的还有 tsconfig.json 派生文件、.eslintrc.json、各类 *.schema.json(JSON-Schema 的 "type": "object")—— 凡根上带 type 的都会中招。

与 #5115 的边界

#5115 修的是判定用的键集合(手写副本 vs 注册表推导),PR #5128 已把集合换成推导并双向钉住。这条是另一件事:集合再准,拿它去判一个根本不属于该词汇表的 type 也还是误报。两者独立 —— PR #5128 既不引入也不修复本条(修复前后 package.json 都报),只是让它在探针里显形。

scripts/check-doc-component-types.mjs 的头注释已经把「type 至少承载七种不同词汇表」这件事写透,并明确拒绝了按父键路径分类的判别器(measured 后否决:TS 注解形和 items 的双关让它在两个方向上都会静默错判)。文档面它的选择是「一律当组件键 + 逐 (文件,值) 声明豁免」;CLI 面没有豁免机制,所以同一个策略在这里只剩误报。

可能的方向(不预断,交分诊)

• A. 只扫可识别为 schema 的文件:例如约定目录(schemas/**)或 CLI 配置里的 glob,而不是整棵树。契约最清楚,但要定「什么算 schema 文件」这个新契约。
• B. 排除已知的非 schema 清单(package.json / tsconfig*.json / .eslintrc.json / *.schema.json …)。成本最低,但排除表是第二份要维护的手写清单 —— 与 objectui check 的 knownTypes 是手写的注册表副本,已与真实注册表漂移:crud 通过校验但无任何渲染器,运行时落 unknown-component 占位符 #5115 刚消灭的那种副本同形,长期取向上可疑。
• C. 要求 schema 文件有正向标记才参与判定(如 $schema 指向 ObjectUI,或存在 children/body 等结构键)。可防错性最好(声明即判定),但会让现存没有标记的 schema 文件退出判定面。

三条对「让 AI 写的元数据难以出错」这条轴的取向差别很大(B 是消费端容忍,C 是生产端声明),不自裁。

复核方式

以 REPO 代表仓库根目录:

mkdir -p /tmp/oc && cd /tmp/oc
printf '{"type":"module","name":"x"}' > package.json
node "$REPO/packages/cli/dist/cli.js" check       # 报 Unknown schema type "module"
sed -n '18,45p' "$REPO/packages/cli/src/commands/check.ts"

注:警告不影响退出码(只有 JSON 解析失败才 errors++),所以这是噪音级缺陷而非阻断级 —— 但它是用户跑这条命令看到的第一行输出。

[os-support-ai]

Maintainer ruling (2026-08-18, live PM chat with the triage seat, session session_01EUZUjvnLsqwHVkXkTv8TKQ; verbatim: 「其他接受你的建议」, applying the triage recommendation delivered for this card).

Ruled: direction C — positive marker required for a file to enter type judgement. A JSON/YAML file participates in the unknown-component-type check only when it positively reads as an ObjectUI schema: $schema pointing at ObjectUI, or the presence of structural keys (children/body-class). package.json, tsconfig*, .eslintrc*, JSON-Schema files and every other root-type vocabulary are simply never judged — no exclusion list (direction B is rejected: a second hand-maintained list of the #5115 shape). Producer-side declaration over consumer-side tolerance.

Dispatch note: the dev measures and reports how many currently-judged real schema files would exit the judgement surface under C (the structural-keys arm should retain the mainstream ones); if that exit surface is materially large, report back rather than silently shrinking coverage. Promoted to pm:queue (type stays Bug).

---

Generated by Claude Code

[os-support-ai]

Claim: PM loop round 6
Session: session_01RV6yuVCxymHYE16PL9vQkE
Branch: claude/issue-5127-schema-file-positive-marker
Worktree: objectui-issue-5127
Domain: repo:objectui (execution seat)
File surface: packages/cli/src/commands/check.ts, packages/cli/src/utils/known-schema-types.ts (read-only unless the marker predicate belongs beside it), plus tests under packages/cli. ⛔ OUT: packages/auth + packages/app-shell/src/providers (#5198, dispatched this round), packages/components/src/renderers/form/** (#4259), packages/plugin-view / plugin-list (#5177, PR5231 open), packages/types (#5186 just merged).
Container & model: S, mode:subagent, model: opus — the edit is small; the judgement is in the measurement the ruling demands (below).
Clause-②: no — it narrows which files enter a warning heuristic in a CLI. No contract accept/reject boundary moves, no public surface widens. (objectui check's exit code is untouched: only a JSON parse failure increments errors.)
Serial constraints cleared: nothing open touches packages/cli. #5115's PR5128 (the derived key set) is merged and is the direct predecessor — build on it, do not revisit it.

Zone 1 — the direction is RULED. Do not re-open the A/B/C choice.

Maintainer, 2026-08-18, verbatim: 「其他接受你的建议」, recorded on this card:

> Ruled: direction C — positive marker required for a file to enter type judgement. A JSON/YAML file participates in the unknown-component-type check only when it positively reads as an ObjectUI schema: $schema pointing at ObjectUI, or the presence of structural keys (children/body-class). package.json, tsconfig*, .eslintrc*, JSON-Schema files and every other root-type vocabulary are simply never judged — no exclusion list (direction B is rejected: a second hand-maintained list of the #5115 shape). Producer-side declaration over consumer-side tolerance.

⛔ Direction B is explicitly rejected. If you find yourself writing a list of filenames to skip — package.json, tsconfig.json, … — you have implemented B and you must stop. The whole point is that no second hand-maintained list gets created; #5115 just finished deleting one of that exact shape.

Premise — verified on origin/main this round

packages/cli/src/commands/check.ts still globs **/*.{json,yaml,yml} (ignoring node_modules/dist/.git) and judges any root type string through isKnownSchemaType. The isKnownSchemaType import and its derived-universe comment (from #5115) are in place. So the card is live and its boundary against #5115 is exactly as described: the key set is now correct, and judging a file that was never in that vocabulary is the separate remaining defect.

Note the glob also matches .yaml/.yml, but only .json is parsed and judged (if (file.endsWith('.json'))). Whatever marker predicate you write, be clear about which arm it applies to and do not silently extend judgement to YAML as a side effect.

Zone 2 — the measurement the ruling requires is a deliverable, not a nicety

From the ruling's dispatch note:

> the dev measures and reports how many currently-judged real schema files would exit the judgement surface under C (the structural-keys arm should retain the mainstream ones); if that exit surface is materially large, report back rather than silently shrinking coverage.

This is binding. Produce the number, over real in-repo schema files, and show your method. If the exit surface is materially large, stop and report — do not land a change that quietly shrinks coverage and do not "fix" it by loosening the marker until the number looks acceptable. A large exit surface is a finding about how in-repo schema files are actually written, and it goes to the maintainer.

Tests

• package.json with "type": "module" produces no warning. This is the card's headline symptom — the first line a user sees running objectui check in their own project.
• The same for a JSON-Schema file ("type": "object"), a tsconfig-derived file, and an .eslintrc.json.
• A real ObjectUI schema file still is judged, both marker arms: one via $schema, one via structural keys.
• An ObjectUI schema file carrying a genuinely unknown component type still warns — the check must keep doing its job. A test suite that only proves things stopped warning would pass a change that disabled the feature entirely.
• Invalid JSON still increments errors and exits non-zero, unchanged.

Reverse-verify: restore check.ts, keep the tests, predict which go red before running, report predicted vs observed.

Gates

Derive from your diff (scripts/pm/dispatch-gates.mjs is objectstack-only; here derive from .github/workflows and package.json). Changeset required (@object-ui/cli); patch or minor, ⛔ never major.

⛔ Do not background a long check and end your turn. Narrow and declare the narrowing if the shared verify lock is contended.

Deliver

Draft PR against main, first body line Fixes #5127. Push the branch early. Return the JSON report and post it as a comment whose first line is the literal <!-- os-dev-report --> marker.

---

Generated by Claude Code