perf: AI experiments with ordering

[sheremet-va]

Description

Resolves #issue-number

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

• It's really useful if your PR references an issue where it is discussed ahead of time. If the feature is substantial or introduces breaking changes without a discussion, PR might be closed.
• Ideally, include a test that fails without this PR but passes with it.
• Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.
• Please check Allow edits by maintainers to make review process faster. Note that this option is not available for repositories that are owned by Github organizations.

Tests

• Run the tests with pnpm test:ci.

Documentation

• If you introduce new functionality, document it. You can run documentation with pnpm run docs command.

Changesets

• Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.

[netlify]

✅ Deploy Preview for vitest-dev ready!

Name	Link
🔨 Latest commit	5035a50
🔍 Latest deploy log	https://app.netlify.com/projects/vitest-dev/deploys/68ff64ecd11a010008f4e460
😎 Deploy Preview	https://deploy-preview-8771--vitest-dev.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[pkg-pr-new]

@vitest/browser

npm i https://pkg.pr.new/@vitest/browser@8771

@vitest/browser-playwright

npm i https://pkg.pr.new/@vitest/browser-playwright@8771

@vitest/browser-preview

npm i https://pkg.pr.new/@vitest/browser-preview@8771

@vitest/browser-webdriverio

npm i https://pkg.pr.new/@vitest/browser-webdriverio@8771

@vitest/coverage-istanbul

npm i https://pkg.pr.new/@vitest/coverage-istanbul@8771

@vitest/coverage-v8

npm i https://pkg.pr.new/@vitest/coverage-v8@8771

@vitest/expect

npm i https://pkg.pr.new/@vitest/expect@8771

@vitest/mocker

npm i https://pkg.pr.new/@vitest/mocker@8771

@vitest/pretty-format

npm i https://pkg.pr.new/@vitest/pretty-format@8771

@vitest/runner

npm i https://pkg.pr.new/@vitest/runner@8771

@vitest/snapshot

npm i https://pkg.pr.new/@vitest/snapshot@8771

@vitest/spy

npm i https://pkg.pr.new/@vitest/spy@8771

@vitest/ui

npm i https://pkg.pr.new/@vitest/ui@8771

@vitest/utils

npm i https://pkg.pr.new/@vitest/utils@8771

vitest

npm i https://pkg.pr.new/vitest@8771

@vitest/web-worker

npm i https://pkg.pr.new/@vitest/web-worker@8771

@vitest/ws-client

npm i https://pkg.pr.new/@vitest/ws-client@8771

commit: 5035a50

[AriPerkkio]

It wouldn't be populated at this point though? Only in watch mode re-runs. And even then we don't automatically re-run the tests where module graph didn't change. Or is it included in the cache?