tooling(objectui-readiness 5): three objectui tests assume the objectui root is the pnpm workspace root — .pnpm install probes, the CLI generator IN-WORKSPACE map, the Console vendor-chunk standalone baseline (parent #25677, 2e/6) #25733

Filing gate ④: sub-issue 2e/6 of the epic #25677 (pm:epic; epic PM session_01RSDL3SFtJaKzcymvCD8RsU). Part of #25677. ⛔ Not a claim. Third and (as measured) last reader class after #25723 (file readers, objectui#13484) and #25728 (git root-relative paths, objectui#13491), measured on the DO NOT MERGE verification PR #25718, run 5 (40153788034, head cfa1676, with the #25726 lockfile splice applied).

Why. Run 5 is the first run where the dependency-resolution red class (#25726) is gone from Test UI: in the 8 shards read so far every remaining red is either a known class with an owner — pin scripts (#25711), spec drift (#25727), QUICK_REFERENCE.md (cutover bill on #25697) — or one of three tests that assume the objectui root is the pnpm workspace root. In the merged tree the workspace root is one level up (objectstack/), so ui/node_modules holds only the ui root package's own declared dependencies, there is no ui/node_modules/.pnpm, and ui/pnpm-workspace.yaml does not exist. Three readers trip on that, each in a different package, and the cutover PR cannot be green until they resolve the layout the way #25723's uiRoot() / workspace-root helpers already do. Like 2b and 2d this is fixed in objectui main first so the import carries it.

Who does it, where it lands: the epic PM dispatches it as a card thread (objectui checkout). One PR to objectstack-ai/objectui main; the epic PM re-measures on the verification branch and records the remaining reds on #25697.

维护者速读

第五轮验证里依赖解析那一类红已经消失。Test UI 剩下的红，除了已经有卡的（钉住脚本 #25711、spec 漂移 #25727、QUICK_REFERENCE 归切换账单）之外，只剩三处测试默认 objectui 根目录就是 pnpm 工作区根：check-doc-snippet-types 的安装探针在 ui/node_modules/.pnpm 找不到包；CLI 生成器的 currentContext() 用 存在 pnpm-workspace.yaml 判断工作区根，所以在 ui/ 下写出 STANDALONE 映射；Console vendor 分块测试把"独立布局"当成当前布局的基线。本卡让这三处用 #25723 已经提供的向上查找工作区根的办法，先落 objectui main。不改受管面。

Measured (run 5, Test UI)

Everything else red in the 8 shards read (3, 6, 7, 8, 10, 13, 15, 16) has an owner: check-installed-spec-pin-claims, objectstack-pin, check-lockfile-integrity sample, ci-cd-pipeline-doc.test.ts:1871 (pin class → #25711 / PR B on #25697); TranslationPreview.categories-11765, console loadLanguage (positions → #25727); sync-quick-reference-release, quick-reference-commands-4149 (cutover bill on #25697). The remaining 8 shards are read as they finish; a fourth member of this class, if any, is appended here by the epic PM before dispatch.

Scope

1. Install probes (scripts/check-doc-snippet-types.mjs): findInstalledCopy and the census controls resolve from the pnpm workspace root found upward (the workspace-root.mjs helpers from tooling(objectui-readiness 2): scripts, tests and e2e specs that read pnpm-workspace.yaml, turbo.json, pnpm-lock.yaml or root overrides at the objectui root resolve the workspace root upward (parent #25677, 2b/6) #25723), not from the objectui root; standalone (root === workspaceRoot) is unchanged. Keep the control's meaning: "installed somewhere in this workspace but undeclared by the importer" must still be the thing it measures.
2. CLI generator context (packages/cli/src/utils/app-generator.ts currentContext() and packages/cli/src/__tests__/app-generator.test.ts): decide, and write down in the function's doc comment, what "runs at a workspace root" means when the objectui tree is itself a workspace member — the dev proposes; the likely answer is that isMonorepo walks up to the nearest pnpm-workspace.yaml and the test derives IN_WORKSPACE from that same root instead of from REPO_ROOT. The product behaviour for a user's own project (a pnpm-workspace.yaml in cwd, or none) must not change; add the case that pins it.
3. Console vendor-chunk tests (scripts/__tests__/vite-objectstack-workspace.test.ts, vite-objectstack-spec-dist.test.ts, vite-objectstack-client-dist.test.ts): the "standalone" expectations are read against a fixture layout, not against the checkout's own layout — so the same three files are green standalone and merged. The regexes themselves (scripts/vite-objectstack-workspace.ts) are not changed unless the merged arm is wrong, which the run-5 Build & E2E UI read will say.
4. Regrowth gate: extend check-ui-root-lookups (the gate tooling(objectui-readiness 2): scripts, tests and e2e specs that read pnpm-workspace.yaml, turbo.json, pnpm-lock.yaml or root overrides at the objectui root resolve the workspace root upward (parent #25677, 2b/6) #25723 and tooling(objectui-readiness 4): objectui scripts address git paths relative to the repo root — git show ref:packages/…, diff --name-only, ls-files, ls-tree break one level down in ui/; prefix via nestedPrefix() (parent #25677, 2d/6) #25728 taught the walk and git shapes) with the shape "node_modules / .pnpm / pnpm-workspace.yaml joined to the objectui root without the helper", so the class does not regrow before cutover. Reverse check on the pre-fix tree must fire at exactly the sites fixed.
5. Tests: the merged-layout verification tooling(objectui-readiness 2): scripts, tests and e2e specs that read pnpm-workspace.yaml, turbo.json, pnpm-lock.yaml or root overrides at the objectui root resolve the workspace root upward (parent #25677, 2b/6) #25723 established (scratch copy of the verification worktree, patch applied under ui/, pnpm install --frozen-lockfile) for the three test files; scripts/__tests__ whole suite once (objectui gate chains).

Out of scope: pin scripts and the .objectstack-pin probes (#25711), spec drift (#25727), QUICK_REFERENCE.md and the dropped root scripts (cutover bill, #25697), lockfile/overrides (#25726), anything under .github/**.

Verification (the dev's)

• objectui standalone: pnpm exec vitest run scripts/__tests__/check-doc-snippet-types.test.ts scripts/__tests__/vite-objectstack-*.test.ts packages/cli/src/__tests__/app-generator.test.ts, pnpm check:ui-root-lookups (+ --self-test), pnpm check:doc-snippet-types, the whole scripts/__tests__ suite — green, no gate skipped; CI green.
• Merged layout (scratch copy of /home/claude/objectstack-issue-25697 with the patch under ui/): the three test files green from the ui root (pnpm --dir ui exec vitest run …), check:doc-snippet-types reaches a real verdict with both census controls live.
• The epic PM: the same patch as a verify commit on DO NOT MERGE — verification run for #25697: PR A + the ui/ subtree import of objectui main cd70b7818d #25718 → run 6; Test UI shards 8, 10, 13 (and 7's vite pair) drop these files from their red lists.

Done when

• objectui main carries the fix with the regrowth gate; on the verification branch no Test UI red names these three readers, and the only Test UI reds left are the owned classes above.

Size: M (three packages, one gate extension, one semantics decision in the CLI generator). Clause-②: no. Metadata-protocol: none. Blocked-by: objectui#13491 (#25728) must land first — same helper file (scripts/workspace-root.mjs) and the same gate (check-ui-root-lookups).

风险

• currentContext() is product code (the dev command and the app generator use it): a wrong "walk up" turns a user's standalone project into "in a workspace" when a parent directory happens to hold a pnpm-workspace.yaml. The decision in Scope 2 must be pinned by a test for the user's layout, not only for ours.
• check-doc-snippet-types is 3,500 lines with its own self-test battery; the probe change should be a few lines in findInstalledCopy and the census, nothing else.

Dedupe

Open issues 2026-10-25 02:50Z filtered on node_modules, workspace root, app-generator, check-doc-snippet-types, vite-objectstack: #25723 (closed; file readers), #25728 (git paths; in the merge queue), #25685 (closed; made the vite chunk tests workspace-aware — this card finishes that by making their standalone baseline layout-independent), #25726 (lockfile). Nothing covers the install probes or the generator context. New.