`ExpectationResult` of a custom asymmetric matcher is ignored

Describe the bug

When I have a custom asymmetric matcher, Vitest applies it correctly but disregards the matcher's ExpectationResult properties like message, actual, and expected if the matcher fails. I expect the inverse assertions (.not) to have the same problem.

Reproduction

Here's a sandbox: https://stackblitz.com/edit/vitest-dev-vitest-je43znvc?file=vite.config.ts,vitest.setup.ts,test%2Fbasic.test.ts&initialPath=__vitest__/

System Info

Irrelevant.

Used Package Manager

npm

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

Start with the linked StackBlitz reproduction, especially vite.config.ts, vitest.setup.ts, and test/basic.test.ts, and run the failing custom asymmetric matcher case. Trace how the matcher’s ExpectationResult is handled on failure and verify that message, actual, and expected are preserved for both normal and inverse assertions.