Ruled by the maintainer on 2026-08-20 (#5393, verbatim 「接受你的所有建议，现在开始处理。」). Item 5 of 5. Independent of the CI-workflow cards — different files.
The defect
assertCanonicalVitestInvocation exists to stop a package-cwd vitest run, because such a run uses a different config than CI does and can therefore go green on a suite CI would fail — a false green, which this repository treats as worse than a red.
It does not cover the packages that carry their own vitest.config.ts — measured at 17, and confirmed to include plugin-grid, packages/core, and packages/components, none of which re-export the root config. Its docstring claims otherwise. So the assertion that exists specifically to prevent false greens has a hole exactly where the risk is highest: the packages with divergent configs.
This is why every dispatch order in this lane has to carry "run vitest from the repo root" as a written instruction — the guard that should make that unnecessary cannot be relied on.
What to do
First establish the real number and the real shape. Do not inherit "17" from this card — count them yourself, list them, and for each say whether its config re-exports the root config or diverges. The interesting set is the divergent ones.
Then close the hole so that a package-cwd run in any package is refused, including those 17. ⛔ The fix is to make the guard cover them — not to relax the guard, and not to delete the packages' configs (some may diverge for good reason; establish that before touching them, and if a config's divergence looks wrong that is a separate card, not this one).
Reverse verification is the point of this card: demonstrate a package-cwd run in one of the 17 that is accepted today and refused after your change. Predict the outcome before running it. A fix that cannot show the before-state being accepted has not demonstrated the hole was real.
⚠️ If closing the hole turns out to make some currently-passing workflow fail — e.g. a script or doc that legitimately runs vitest in a package cwd — stop and report rather than carving an exemption. An exemption is how this guard got its hole in the first place.
⛔ Constraints
Context: surfaced repeatedly across this lane's dispatches; recorded in the seat post's platform facts. Ruling: #5393.
Ruled by the maintainer on 2026-08-20 (#5393, verbatim 「接受你的所有建议，现在开始处理。」). Item 5 of 5. Independent of the CI-workflow cards — different files.
The defect
assertCanonicalVitestInvocationexists to stop a package-cwd vitest run, because such a run uses a different config than CI does and can therefore go green on a suite CI would fail — a false green, which this repository treats as worse than a red.It does not cover the packages that carry their own
vitest.config.ts— measured at 17, and confirmed to includeplugin-grid,packages/core, andpackages/components, none of which re-export the root config. Its docstring claims otherwise. So the assertion that exists specifically to prevent false greens has a hole exactly where the risk is highest: the packages with divergent configs.This is why every dispatch order in this lane has to carry "run vitest from the repo root" as a written instruction — the guard that should make that unnecessary cannot be relied on.
What to do
First establish the real number and the real shape. Do not inherit "17" from this card — count them yourself, list them, and for each say whether its config re-exports the root config or diverges. The interesting set is the divergent ones.
Then close the hole so that a package-cwd run in any package is refused, including those 17. ⛔ The fix is to make the guard cover them — not to relax the guard, and not to delete the packages' configs (some may diverge for good reason; establish that before touching them, and if a config's divergence looks wrong that is a separate card, not this one).
Reverse verification is the point of this card: demonstrate a package-cwd run in one of the 17 that is accepted today and refused after your change. Predict the outcome before running it. A fix that cannot show the before-state being accepted has not demonstrated the hole was real.
⛔ Constraints
.github/workflows/ci.yml— ShardTest (coverage)4 ways and stop the Codecov upload being skipped by its implicitsuccess()#5403 owns it, in flight.Context: surfaced repeatedly across this lane's dispatches; recorded in the seat post's platform facts. Ruling: #5393.