Skip to content

Commit 448940f

Browse files
docs(qa): three studio-authoring knownGaps quote the vitest invocation the ui guard accepts (#29317)
<!-- claude-projects-attribution: {"github_login":"marchtian"} --> _Requested by **田騏** · [project thread](https://claude.ai/code/project/chan_01VmuUhXU9SSUzqJYyXSmYSi?thread=cmsg_01VmuUhXU9SSUzqJYyXSmYSi9paTx1Lu8ENYwwssthfK3h)_ Fixes #28750 Clause-②: no Metadata-protocol: none ## 维护者速读 - 改了什么:平台测试清单 `studio-authoring` 区里三个条目(对象设计器往返、记录页往返、权限矩阵编辑器)的 knownGaps[0],把跑 jsdom 单测的命令改成 ui vitest 守卫接受的写法(`cd ui && pnpm exec vitest run --maxWorkers=1 packages/PKG/src/FILE`),并注明旧的 `--filter` 写法会被拒绝;每个条目 revision +1、追加一行 history。第四个条目(打包自动化锁定)本来就是被接受的写法,未改动。 - 为什么改:旧命令在包目录里启动 vitest,守卫在加载配置时直接拒绝,一个测试都不跑。下一轮照着清单跑的人要么浪费时间找正确命令,要么把单测误记成 blocked(environment)。 - 风险与回滚:只改 QA 清单 JSON 里的说明文字,不动产品代码、不进任何发布包,没有任何判据被放宽。回滚就是 revert 本 PR。 - 先看:`docs/qa/platform-checklist/areas/studio-authoring.json` 中 `permission-matrix-editor-ux` 的 knownGaps[0] 与新 history 行(三处改动文字完全相同,看一处即可)。 - 两分钟验证:仓库根运行 `pnpm check:platform-checklist`,预期最后一行以 `check-platform-checklist: OK — 16 areas, 352 items` 开头。 - 需要你做的:无,席位落地。 ## What changes `docs/qa/platform-checklist/areas/studio-authoring.json` only. Three of the card's four items quoted `pnpm --filter @object-ui/PKG exec vitest run --maxWorkers=2 FILE` for their jsdom unit pin. That command runs Vitest in the package directory, and `ui/scripts/vitest-invocation-guard.mjs` (called from `ui/vitest.config.mts`) refuses any run whose Vitest root is not `ui/` (verdict `package-cwd`). Each of the three now carries, byte for byte, the sentence #28701 landed in `studio-authoring.expression-editors` knownGaps[1]: `cd ui && pnpm exec vitest run --maxWorkers=1 packages/PKG/src/FILE`, followed by the ⛔ note that the `--filter` form is refused and why. | # | item · clause | outcome | |---|---|---| | 1 | `studio-authoring.object-designer-roundtrip` fixtures.knownGaps[0] | edited; revision 10 → 11, one history row | | 2 | `studio-authoring.record-page-roundtrip` fixtures.knownGaps[0] | edited; revision 11 → 12, one history row | | 3 | `studio-authoring.permission-matrix-editor-ux` fixtures.knownGaps[0] | edited; revision 7 → 8, one history row | | 4 | `studio-authoring.packaged-automation-studio-lock` fixtures.knownGaps[1] | not edited, no revision bump: it already quotes `cd ui && pnpm exec vitest run --root . --maxWorkers=2 FILE`, which the guard accepts (measured below) | Each new history row cites #28656 (ref) and #28750, and says the change is wording only with no clause changed. Main's history is an exact prefix of each edited item's history, and no field other than `revision`, `history` and the one knownGaps string changed in any item (checked against a parsed copy of `HEAD` before the merge of `origin/main`). ## Tests Docs only: no package source changes, so no build closure and no package test suite is owed. `skip-changeset`: the diff touches only `docs/qa/platform-checklist/areas/studio-authoring.json`, which no package ships. The guard verdicts were measured two ways at this head: - `evaluateVitestInvocation` from `ui/scripts/vitest-invocation-guard.mjs`, called directly: the new form (cwd `ui/`) is accepted; item 4's `--root .` form (cwd `ui/`) is accepted; the old `--filter` form (cwd `ui/packages/app-shell`) is refused with `package-cwd`. - A real run of item 3's pin with the new form, under the verify lock: `cd ui && pnpm exec vitest run --maxWorkers=1 packages/app-shell/src/views/metadata-admin/PermissionMatrixEditor.fieldBulk.test.tsx` printed `RUN v4.1.12 .../ui`, `Test Files 1 passed (1)`, `Tests 3 passed (3)`, lock VERDICT command-exit 0. The control, `pnpm --filter @object-ui/app-shell exec vitest run --maxWorkers=2 src/views/metadata-admin/PermissionMatrixEditor.fieldBulk.test.tsx`, exited 1 with the guard's package-cwd refusal (vitest root `ui/packages/app-shell`). Every pin file the four items name under `ui/` exists at this head: `PermissionMatrixEditor.fieldBulk.test.tsx`, `.readonly.test.tsx`, `.artifactTier.test.tsx`, `StudioDesignSurface.automationsReadOnly-11124.test.tsx`, `ui/e2e/live/studio-object-designer.spec.ts`, `ui/e2e/live/studio-editor.spec.ts`. ## Acceptance notes - Item 4 is left untouched because its command is an accepted form. Its explanatory sentence still says the `pnpm --filter @object-ui/app-shell exec vitest run FILE` form "misses the ui/ setup". The measured behaviour today is a refusal at config load (package-cwd), not a run with the wrong setup. The command a runner copies is correct, so this is wording only and is left for the seat to decide. - The landed sentence this PR mirrors starts its last clause with a lower-case "a ui/e2e/live spec" after a full stop. It is copied byte for byte so that the four knownGaps stay identical and greppable; not changed here. - `meta-save-preconditions-and-draft-rows`, `multi-package-item-rows` and `save-door-runs-authoring-rules` quote `pnpm --filter PKG exec vitest run --maxWorkers=2 FILE` in a verify. Their `automated.ref` files are all under `packages/` (backend packages), not `ui/`, so the ui guard does not apply; not touched. ## Verification <details><summary>Gates (head bfd7def, after one merge of origin/main)</summary> `node scripts/pm/dispatch-gates.mjs --commands --repo objectstack-ai/objectstack` derived 16 families at `bfd7def6fb`: 1 path, +12 / -9, under the 3000 human-merge line. Each ran with stdin from /dev/null, exit captured before any pipe: - `node scripts/check-adr-links.mjs` :: exit 0 - `node scripts/check-adr-links.mjs --self-test` :: exit 0 - `node scripts/check-closing-keyword-parity.mjs` :: exit 0 - `node scripts/check-closing-keyword-parity.mjs --self-test` :: exit 0 - `node scripts/check-comment-mask-corpus.mjs` :: exit 0 - `node scripts/ci/plan-test-core-shards.mjs --self-test` :: exit 0 - `pnpm --filter @objectstack/lint run check:doc-formula-expressions` :: exit 0, after `turbo run build --filter=@objectstack/formula --filter=@objectstack/lint` (lock VERDICT command-exit 0) - `pnpm check:ci-filter-parity` :: exit 0 - `pnpm check:cross-package-test-inputs` :: exit 0 - `pnpm check:doc-authoring` :: exit 0 - `pnpm check:driver-memory-census` :: exit 0 - `pnpm check:gitlink-declared` :: exit 0 - `pnpm check:nul-bytes` :: exit 0 - `pnpm check:platform-checklist` :: exit 0 (`OK — 16 areas, 352 items`) - `pnpm check:refd-timer-probe` :: exit 0 - `pnpm check:watch-hint-literal` :: exit 0 `--ran` reconciliation: 16 derived, 16 run, 0 NOT-MEASURED, 0 UNRUN (a derived zero: all 16 recorded an exit code). </details> 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude <noreply@anthropic.com>
1 parent aeac74b commit 448940f

1 file changed

Lines changed: 12 additions & 9 deletions

File tree

‎docs/qa/platform-checklist/areas/studio-authoring.json‎

Lines changed: 12 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -102,7 +102,7 @@
102102
"title": "Object designer round-trip: field add/edit/reorder persists to metadata, identifiers derive and survive typing",
103103
"since": "v16",
104104
"status": "active",
105-
"revision": 10,
105+
"revision": 11,
106106
"priority": "P1",
107107
"surface": "mixed",
108108
"personas": ["admin"],
@@ -112,7 +112,7 @@
112112
"a writable package to author into (create one via the Studio wizard or POST /api/v1/packages — the source-loaded com.example.showcase is read-only and rejects designer saves server-side)"
113113
],
114114
"knownGaps": [
115-
"AUTOMATION LIVES UNDER ui/ — `automated.ref` names objectui specs, and since objectui was imported into this repository they resolve at ui/PATH in this checkout. A jsdom unit pin runs here (`pnpm --filter @object-ui/PKG exec vitest run --maxWorkers=2 FILE`); a ui/e2e/live spec runs from ui/ with `pnpm test:e2e:live SPEC` against a live backend and the console dev server (the prerequisites are in ui/playwright.live.config.ts). Cite the output naming the commit, or drive the item by hand in the browser and score it as a manual run. ⛔ Never score it as covered on the strength of the `automated` field alone — an unrun pin is a claim, not evidence. Full protocol: RUNNER.md, the objectui-pinned-automation standing fact."
115+
"AUTOMATION LIVES UNDER ui/ — `automated.ref` names objectui specs, and since objectui was imported into this repository they resolve at ui/PATH in this checkout. A jsdom unit pin runs from ui/, the objectui root, with its path written relative to ui/: `cd ui && pnpm exec vitest run --maxWorkers=1 packages/PKG/src/FILE`. ⛔ Not `pnpm --filter @object-ui/PKG exec vitest run FILE`: that runs in the package directory, and the ui vitest guard (ui/scripts/vitest-invocation-guard.mjs, which ui/vitest.config.mts calls) refuses any run whose Vitest root is not ui/ (its package-cwd verdict). a ui/e2e/live spec runs from ui/ with `pnpm test:e2e:live SPEC` against a live backend and the console dev server (the prerequisites are in ui/playwright.live.config.ts). Cite the output naming the commit, or drive the item by hand in the browser and score it as a manual run. ⛔ Never score it as covered on the strength of the `automated` field alone — an unrun pin is a claim, not evidence. Full protocol: RUNNER.md, the objectui-pinned-automation standing fact."
116116
]
117117
},
118118
"steps": [
@@ -211,7 +211,8 @@
211211
"change": "steps[0], [1], [4] and [5], acceptance[1].verify, acceptance[2] (clause, verify) and automated.ref re-pointed to Studio as the door (checklist-accuracy finding of the Data card of QA run #26715, at 3fcafcd3; re-read at 43731031). Studio's New object dialog applies the package namespace itself (prefixObjectName, so the author types repair_asset and the stored name is NS_repair_asset), Studio has no Save button (autosave, then Publish → Publish all), and the Form tab's reorder is dnd-kit (a 4 px pointer activation and a keyboard sensor), not native HTML5 drag. The objectui pins drive the Setup designer route, so automated.ref says they are evidence at a sibling door. The run passed every clause this way. Not loosened: the typed underscore must survive and the stored name must carry the prefix",
212212
"ref": "#26715"
213213
},
214-
{ "revision": 10, "date": "2026-10-31", "change": "steps[1] names the New object dialog's confirm button: 'Save as draft', not Create, in both places the step named it. Every Studio create dialog takes its submit label from engine.studio.createDraft (ui/packages/i18n/src/namespaces/studio/en.ts; ui/packages/app-shell/src/views/studio-design/StudioDesignSurface.tsx, the engine.studio.data.newObject dialog). Accuracy finding of QA run #27438. No clause changed. Wave anchor #27377, wave-3 accuracy slice S2; read at base a0f865491d", "ref": "#27438" }
214+
{ "revision": 10, "date": "2026-10-31", "change": "steps[1] names the New object dialog's confirm button: 'Save as draft', not Create, in both places the step named it. Every Studio create dialog takes its submit label from engine.studio.createDraft (ui/packages/i18n/src/namespaces/studio/en.ts; ui/packages/app-shell/src/views/studio-design/StudioDesignSurface.tsx, the engine.studio.data.newObject dialog). Accuracy finding of QA run #27438. No clause changed. Wave anchor #27377, wave-3 accuracy slice S2; read at base a0f865491d", "ref": "#27438" },
215+
{ "revision": 11, "date": "2026-11-02", "change": "fixtures.knownGaps[0] names the invocation the ui vitest guard accepts, the form revision 8 of studio-authoring.expression-editors landed in its knownGaps[1] (#28701): a jsdom unit pin runs from ui/ as cd ui && pnpm exec vitest run --maxWorkers=1 packages/PKG/src/FILE. The pnpm --filter @object-ui/PKG exec form it quoted runs in the package directory, which the guard refuses (ui/scripts/vitest-invocation-guard.mjs, verdict package-cwd), so a runner following it is refused at config load, before any test runs. Wording only; no clause changed. Checklist-accuracy finding of QA run #28656 (W3-RT), carried by #28750", "ref": "#28656" }
215216
]
216217
},
217218
{
@@ -294,15 +295,15 @@
294295
"title": "Record-page authoring round-trip: created bound to its object, seeded from the default layout, block-edited, published, rendered",
295296
"since": "v16",
296297
"status": "active",
297-
"revision": 11,
298+
"revision": 12,
298299
"priority": "P1",
299300
"surface": "mixed",
300301
"personas": ["admin (authors)", "end user (opens the record). On stock no non-admin persona reads showcase_contact (auditor.demo is refused 'You don't have access to Contact records', QA run #24604), so the viewer is the admin unless a grant is provisioned — e.g. a member bound to the `manager` position, whose showcase_manager set reads showcase_contact (examples/app-showcase/src/security/permission-sets.ts); record which"],
301302
"fixtures": {
302303
"app": "showcase",
303304
"requires": ["seeded showcase_contact records to render the published page against (stock showcase seed). ⛔ Not showcase_invoice: it ships the package default record page showcase_invoice_document (isDefault: true, examples/app-showcase/src/ui/pages/invoice-document.page.ts), which wins by design (objectui react usePageAssignment: the default record page, else the first), and authoring a second isDefault page answers 422 DEFAULT_RECORD_PAGE_CONFLICT. showcase_project, showcase_task and showcase_preference ship defaults too; showcase_contact ships no record page (QA runs #24571 and #24604)"],
304305
"knownGaps": [
305-
"AUTOMATION LIVES UNDER ui/ — `automated.ref` names objectui specs, and since objectui was imported into this repository they resolve at ui/PATH in this checkout. A jsdom unit pin runs here (`pnpm --filter @object-ui/PKG exec vitest run --maxWorkers=2 FILE`); a ui/e2e/live spec runs from ui/ with `pnpm test:e2e:live SPEC` against a live backend and the console dev server (the prerequisites are in ui/playwright.live.config.ts). Cite the output naming the commit, or drive the item by hand in the browser and score it as a manual run. ⛔ Never score it as covered on the strength of the `automated` field alone — an unrun pin is a claim, not evidence. Full protocol: RUNNER.md, the objectui-pinned-automation standing fact."
306+
"AUTOMATION LIVES UNDER ui/ — `automated.ref` names objectui specs, and since objectui was imported into this repository they resolve at ui/PATH in this checkout. A jsdom unit pin runs from ui/, the objectui root, with its path written relative to ui/: `cd ui && pnpm exec vitest run --maxWorkers=1 packages/PKG/src/FILE`. ⛔ Not `pnpm --filter @object-ui/PKG exec vitest run FILE`: that runs in the package directory, and the ui vitest guard (ui/scripts/vitest-invocation-guard.mjs, which ui/vitest.config.mts calls) refuses any run whose Vitest root is not ui/ (its package-cwd verdict). a ui/e2e/live spec runs from ui/ with `pnpm test:e2e:live SPEC` against a live backend and the console dev server (the prerequisites are in ui/playwright.live.config.ts). Cite the output naming the commit, or drive the item by hand in the browser and score it as a manual run. ⛔ Never score it as covered on the strength of the `automated` field alone — an unrun pin is a claim, not evidence. Full protocol: RUNNER.md, the objectui-pinned-automation standing fact."
306307
]
307308
},
308309
"steps": [
@@ -398,7 +399,8 @@
398399
"ref": "#25848"
399400
},
400401
{ "revision": 10, "date": "2026-10-28", "change": "automated.ref, acceptance[0].verify and source[0] drop ui/e2e/live/studio-record-page.spec.ts, deleted by the triage of the live specs that ran in no CI lane (ruling Q3 B): measured red on the workspace backend at 1e8e5296, alone, twice: a Studio-created record page is saved kind slotted with no copied regions unless the author picks full (fd73f2b3, the page createSeed in ui/packages/app-shell/src/views/metadata-admin/anchors.ts; both outcomes unit-pinned in anchors.page-seed.test.ts beside it), so the spec's seeded-regions assertion reads a superseded design. acceptance[0] is hand-driven again; its clause still asks for seeded regions, which now holds only for a page the author creates full, and is left for the ledger's owner. studio-editor.spec.ts keeps acceptance[1]. No clause changed", "ref": "#25914" },
401-
{ "revision": 11, "date": "2026-10-31", "change": "steps[0], steps[2], acceptance[0] and negative[0] create the record page with Kind = full, and automated.ref carries a warm-console note. The page create form has a Kind field; a record page defaults to slotted, which saves regions [] and renders the synthesized default by design, and only an explicit full copies the default's regions into the draft (the createSeed in ui/packages/app-shell/src/views/metadata-admin/anchors.ts, fd73f2b3). Revision 10 left the seeded-regions clause for the ledger's owner; it now holds as written on the create it names, and a slotted page's empty regions are no longer read as #1541. QA run #27438 also found studio-editor.spec.ts timing out at metadata-edit-page (5 s) on a cold dev console and passing warm. The clause is unchanged in strength: a full create without seeded regions is still the FAIL. Accuracy findings of QA run #27438. Wave anchor #27377, wave-3 accuracy slice S2; read at base a0f865491d", "ref": "#27438" }
402+
{ "revision": 11, "date": "2026-10-31", "change": "steps[0], steps[2], acceptance[0] and negative[0] create the record page with Kind = full, and automated.ref carries a warm-console note. The page create form has a Kind field; a record page defaults to slotted, which saves regions [] and renders the synthesized default by design, and only an explicit full copies the default's regions into the draft (the createSeed in ui/packages/app-shell/src/views/metadata-admin/anchors.ts, fd73f2b3). Revision 10 left the seeded-regions clause for the ledger's owner; it now holds as written on the create it names, and a slotted page's empty regions are no longer read as #1541. QA run #27438 also found studio-editor.spec.ts timing out at metadata-edit-page (5 s) on a cold dev console and passing warm. The clause is unchanged in strength: a full create without seeded regions is still the FAIL. Accuracy findings of QA run #27438. Wave anchor #27377, wave-3 accuracy slice S2; read at base a0f865491d", "ref": "#27438" },
403+
{ "revision": 12, "date": "2026-11-02", "change": "fixtures.knownGaps[0] names the invocation the ui vitest guard accepts, the form revision 8 of studio-authoring.expression-editors landed in its knownGaps[1] (#28701): a jsdom unit pin runs from ui/ as cd ui && pnpm exec vitest run --maxWorkers=1 packages/PKG/src/FILE. The pnpm --filter @object-ui/PKG exec form it quoted runs in the package directory, which the guard refuses (ui/scripts/vitest-invocation-guard.mjs, verdict package-cwd), so a runner following it is refused at config load, before any test runs. Wording only; no clause changed. Checklist-accuracy finding of QA run #28656 (W3-RT), carried by #28750", "ref": "#28656" }
402404
]
403405
},
404406
{
@@ -868,7 +870,7 @@
868870
"title": "Permission-matrix editor UX: field-filter + bulk apply to EXACTLY the visible fields, and the Bulk column never clips at narrow widths",
869871
"since": "v16",
870872
"status": "active",
871-
"revision": 7,
873+
"revision": 8,
872874
"priority": "P2",
873875
"surface": "mixed",
874876
"personas": ["admin"],
@@ -881,7 +883,7 @@
881883
"in package scope, the package's objects PUBLISHED before the set is opened: while they are only drafts, the Studio Access matrix lists none of them ('0 objects') — a defect QA run #26715 recorded (the matrix lists objects without the draft preview); publish them first, or record the leg blocked(fixture) citing the run"
882884
],
883885
"knownGaps": [
884-
"AUTOMATION LIVES UNDER ui/ — `automated.ref` names objectui specs, and since objectui was imported into this repository they resolve at ui/PATH in this checkout. A jsdom unit pin runs here (`pnpm --filter @object-ui/PKG exec vitest run --maxWorkers=2 FILE`); a ui/e2e/live spec runs from ui/ with `pnpm test:e2e:live SPEC` against a live backend and the console dev server (the prerequisites are in ui/playwright.live.config.ts). Cite the output naming the commit, or drive the item by hand in the browser and score it as a manual run. ⛔ Never score it as covered on the strength of the `automated` field alone — an unrun pin is a claim, not evidence. Full protocol: RUNNER.md, the objectui-pinned-automation standing fact."
886+
"AUTOMATION LIVES UNDER ui/ — `automated.ref` names objectui specs, and since objectui was imported into this repository they resolve at ui/PATH in this checkout. A jsdom unit pin runs from ui/, the objectui root, with its path written relative to ui/: `cd ui && pnpm exec vitest run --maxWorkers=1 packages/PKG/src/FILE`. ⛔ Not `pnpm --filter @object-ui/PKG exec vitest run FILE`: that runs in the package directory, and the ui vitest guard (ui/scripts/vitest-invocation-guard.mjs, which ui/vitest.config.mts calls) refuses any run whose Vitest root is not ui/ (its package-cwd verdict). a ui/e2e/live spec runs from ui/ with `pnpm test:e2e:live SPEC` against a live backend and the console dev server (the prerequisites are in ui/playwright.live.config.ts). Cite the output naming the commit, or drive the item by hand in the browser and score it as a manual run. ⛔ Never score it as covered on the strength of the `automated` field alone — an unrun pin is a claim, not evidence. Full protocol: RUNNER.md, the objectui-pinned-automation standing fact."
885887
]
886888
},
887889
"steps": [
@@ -982,7 +984,8 @@
982984
"change": "steps[0], steps[6], acceptance[5] (clause, verify) and fixtures.requires[3] corrected from the Access card of QA run #26715 (at 3fcafcd3; re-read at 43731031). (1) The metadata-admin door is /_console/apps/com.objectstack.setup/metadata/permission/NAME; the com.objectstack.studio route renders nothing useful, the studio app being unloaded on a stock boot. (2) In read-only Studio the field bulk buttons are absent, not disabled (FieldsSubTable renders them only while writable), and the object-row bulk shows only on hover or focus and is disabled there. (3) In package scope the matrix lists no object while the package's objects are only drafts, so the fixture publishes them first. No other clause changed",
983985
"ref": "#26715"
984986
},
985-
{ "revision": 7, "date": "2026-10-31", "change": "steps[3], [5], [6], acceptance[1], [4], [5], variants[0] and source[0] read the matrix as it renders. The field bulk that revokes write is labelled 'Read-only all' (perm.field.bulk.readable, ui/packages/i18n/src/namespaces/studio/en.ts), not 'Read all', and both matrix tables carry min-w-[1304px], not min-w-[960px], inside the overflow-auto container (ui/packages/app-shell/src/views/metadata-admin/PermissionMatrixEditor.tsx; Studio's table is data-testid perm-studio-matrix). Accuracy findings of QA run #27438. No clause changed. Wave anchor #27377, wave-3 accuracy slice S2; read at base a0f865491d", "ref": "#27438" }
987+
{ "revision": 7, "date": "2026-10-31", "change": "steps[3], [5], [6], acceptance[1], [4], [5], variants[0] and source[0] read the matrix as it renders. The field bulk that revokes write is labelled 'Read-only all' (perm.field.bulk.readable, ui/packages/i18n/src/namespaces/studio/en.ts), not 'Read all', and both matrix tables carry min-w-[1304px], not min-w-[960px], inside the overflow-auto container (ui/packages/app-shell/src/views/metadata-admin/PermissionMatrixEditor.tsx; Studio's table is data-testid perm-studio-matrix). Accuracy findings of QA run #27438. No clause changed. Wave anchor #27377, wave-3 accuracy slice S2; read at base a0f865491d", "ref": "#27438" },
988+
{ "revision": 8, "date": "2026-11-02", "change": "fixtures.knownGaps[0] names the invocation the ui vitest guard accepts, the form revision 8 of studio-authoring.expression-editors landed in its knownGaps[1] (#28701): a jsdom unit pin runs from ui/ as cd ui && pnpm exec vitest run --maxWorkers=1 packages/PKG/src/FILE. The pnpm --filter @object-ui/PKG exec form it quoted runs in the package directory, which the guard refuses (ui/scripts/vitest-invocation-guard.mjs, verdict package-cwd), so a runner following it is refused at config load, before any test runs. Wording only; no clause changed. Checklist-accuracy finding of QA run #28656 (W3-RT), carried by #28750", "ref": "#28656" }
986989
]
987990
},
988991
{

0 commit comments

Comments
 (0)