fix: declare the stryker vitest-runner plugin explicitly

[HugoRCD]

The weekly mutation workflow has failed on every run since it was added: Stryker's default @stryker-mutator/* plugin discovery globs the node_modules directory five levels above @stryker-mutator/core, which under pnpm's isolated layout is core's own .pnpm install dir — it only ever contains core's dependencies (api, util, instrumenter, all ignored by the loader), never the vitest runner. No TestRunner plugin loads and the run dies before the first mutant.

Declaring plugins: ["@stryker-mutator/vitest-runner"] explicitly makes Stryker import it as a bare specifier, which resolves through pnpm's hoisted fallback.

Verified locally: dry run passes (1264 tests via the vitest runner) and the full mutation run completes with a score of 59.15 against the break threshold of 50.

Internal tooling only, no changeset.

[changeset-bot]

⚠️ No Changeset found

Latest commit: cf73afd

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
evi	Ready	Preview	Aug 10, 2026 8:19am
evlog-telemetry	Ready	Preview	Aug 10, 2026 8:19am

3 Skipped Deployments

Project	Deployment	Actions	Updated (UTC)
evlog-docs	Skipped	v0	Aug 10, 2026 8:19am
evlog-render-lab	Skipped		Aug 10, 2026 8:19am
just-use-evlog	Skipped		Aug 10, 2026 8:19am

[github-actions]

Thank you for following the naming conventions! 🙏

[coderabbitai]

Warning

Review limit reached

@HugoRCD, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 26 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 04b7a48a-87f5-4180-8a37-69edbe1db5e4

📥 Commits

Reviewing files that changed from the base of the PR and between d323963 and cf73afd.

📒 Files selected for processing (1)

• packages/evlog/stryker.config.json

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[pkg-pr-new]

npm i https://pkg.pr.new/@evlog/cli@552

npm i https://pkg.pr.new/evlog@552

npm i https://pkg.pr.new/@evlog/nuxthub@552

npm i https://pkg.pr.new/@evlog/telemetry@552

commit: cf73afd