[sheremet-va]

Follow-up to #11424. When running vitest related or vitest --changed, test files that were filtered out are now listed with a magenta ○ icon alongside the files that ran. The agent (minimal) reporter doesn't print them.

 RUN  v5.0.3 /root

 ✓ related.test.ts (1 test) 1ms
 ✓ deep-related-exports.test.ts (1 test) 1ms
 ✓ deep-related-imports.test.ts (1 test) 1ms
 ○ not-related.test.ts (not affected)

 Test Files  3 passed (3)
   Affected  3 of 4 test files (related to src/sourceA.ts)
      Tests  3 passed (3)

[netlify]

✅ Deploy Preview for vitest-dev ready!

Name	Link
🔨 Latest commit	b105a51
🔍 Latest deploy log	https://app.netlify.com/projects/vitest-dev/deploys/6abe2df92f32010007c433a1
😎 Deploy Preview	https://deploy-preview-11427--vitest-dev.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
🤖 Make changes	Run an agent on this branch

---

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

[sheremet-va]

Not sure if it's a good idea, but maybe worth exploring 🤷 Printing it at the end also might be a bad idea because users want to see tests that were actually running

[hi-ogawa]

Not sure if it's a good idea, but maybe worth exploring 🤷 Printing it at the end also might be a bad idea because users want to see tests that were actually running

Was about to approve but good point. For visibility, can vitest list and related/changed work together to surface affected vs not affected and that's enough? (since agents sees summary only anyway for normal run)