chore(deps-dev): bump vitest from 4.1.9 to 4.1.10

[dependabot]

Bumps vitest from 4.1.9 to 4.1.10.

Release notes

Sourced from vitest's releases.

v4.1.10

   🐞 Bug Fixes

• browser: Check fs access in builtin commands [backport to v4]  -  by @​hi-ogawa, Hiroshi Ogawa and OpenCode (claude-opus-4-8) in vitest-dev/vitest#10680 (5c18d)
• vm: Fix external module resolve error with deps optimizer query for encoded URI [backport to v4]  -  by @​SveLil and @​hi-ogawa in vitest-dev/vitest#10661 (bae52)

    View changes on GitHub

Commits

• db616d2 chore: release v4.1.10 (#10718)
• bae52b5 fix(vm): fix external module resolve error with deps optimizer query for enco...
• See full diff in compare view

---

Note

Low Risk
Dev-only dependency bump with no runtime or application code changes.

Overview
Bumps vitest from 4.1.9 to 4.1.10 in packages/agent, packages/ai, and packages/coding-agent devDependencies, with package-lock.json refreshed for the full @vitest/* stack and related toolchain (e.g. vite, rolldown).

This is a patch-level test-runner update; release notes cite browser fs-access checks and a VM external-module resolve fix with encoded URIs—no application source changes.

^{Reviewed by Cursor Bugbot for commit a0a6d38. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Bump vitest from 4.1.9 to 4.1.10 in agent, ai, and coding-agent packages

Updates the vitest devDependency to 4.1.10 across all packages and regenerates the lockfile.

^{Macroscope summarized a0a6d38.}

[snimu]

Superseded by #632, which incorporates this exact dependency update into the consolidated, policy-compliant lockfile and validation pass.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.