chore(deps): update vitest monorepo to ^3.0.9

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@vitest/coverage-v8 (source)	^3.0.8 -> ^3.0.9
@vitest/expect (source)	^3.0.8 -> ^3.0.9
vitest (source)	^3.0.8 -> ^3.0.9

---

Configuration

📅 Schedule: Branch creation - "before 3am on the first day of the month" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate using a curated preset maintained by . View repository job log here

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
page-building-studio	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Mar 25, 2025 2:15pm
performance-studio	✅ Ready (Inspect)	Visit Preview		Mar 25, 2025 2:15pm
test-studio	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Mar 25, 2025 2:15pm

2 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
studio-workshop	⬜️ Ignored (Inspect)	Visit Preview		Mar 25, 2025 2:15pm
test-next-studio	⬜️ Ignored (Inspect)			Mar 25, 2025 2:15pm

[github-actions]

No changes to documentation

[github-actions]

Coverage Report

Status	Category	Percentage	Covered / Total
🔵	Lines	43.3%	56155 / 129684
🔵	Statements	43.3%	56155 / 129684
🔵	Functions	47.29%	2777 / 5872
🔵	Branches	79.71%	10462 / 13124

File Coverage

No changed files found.

Generated in workflow #32843 for commit 56bcabf by the Vitest Coverage Report Action

[github-actions]

📊 Playwright Test Report

Download Full E2E Report

This report contains test results, including videos of failing tests.

[github-actions]

⚡️ Editor Performance Report

Updated Tue, 25 Mar 2025 14:20:51 GMT

Benchmark	reference latency of sanity@latest	experiment latency of this branch	Δ (%) latency difference
article (title)	24.4 efps (41ms)	24.4 efps (41ms)	+0ms (-/-%)	✅
article (body)	78.1 efps (13ms)	74.9 efps (13ms)	+1ms (-/-%)	✅
article (string inside object)	27.4 efps (37ms)	26.7 efps (38ms)	+1ms (+2.7%)	✅
article (string inside array)	24.4 efps (41ms)	23.3 efps (43ms)	+2ms (+4.9%)	✅
recipe (name)	43.5 efps (23ms)	45.5 efps (22ms)	-1ms (-4.3%)	✅
recipe (description)	45.5 efps (22ms)	50.0 efps (20ms)	-2ms (-9.1%)	✅
recipe (instructions)	99.9+ efps (5ms)	99.9+ efps (5ms)	+0ms (-/-%)	✅
synthetic (title)	18.5 efps (54ms)	18.5 efps (54ms)	+0ms (-/-%)	✅
synthetic (string inside object)	18.9 efps (53ms)	18.7 efps (54ms)	+1ms (+0.9%)	✅

efps — editor "frames per second". The number of updates assumed to be possible within a second.

Derived from input latency. efps = 1000 / input_latency

Detailed information

🏠 Reference result

The performance result of sanity@latest

Benchmark	latency	p75	p90	p99	blocking time	test duration
article (title)	41ms	46ms	54ms	212ms	132ms	10.4s
article (body)	13ms	15ms	23ms	72ms	52ms	5.3s
article (string inside object)	37ms	39ms	41ms	53ms	33ms	6.9s
article (string inside array)	41ms	45ms	48ms	138ms	176ms	7.1s
recipe (name)	23ms	24ms	27ms	47ms	6ms	7.5s
recipe (description)	22ms	24ms	27ms	31ms	0ms	5.5s
recipe (instructions)	5ms	7ms	9ms	21ms	0ms	3.2s
synthetic (title)	54ms	60ms	67ms	243ms	1013ms	13.6s
synthetic (string inside object)	53ms	56ms	58ms	66ms	680ms	7.7s

🧪 Experiment result

The performance result of this branch

Benchmark	latency	p75	p90	p99	blocking time	test duration
article (title)	41ms	47ms	77ms	341ms	543ms	11.0s
article (body)	13ms	17ms	30ms	128ms	181ms	5.4s
article (string inside object)	38ms	41ms	44ms	321ms	332ms	7.1s
article (string inside array)	43ms	46ms	50ms	153ms	282ms	7.2s
recipe (name)	22ms	24ms	27ms	49ms	3ms	7.7s
recipe (description)	20ms	21ms	28ms	38ms	1ms	4.9s
recipe (instructions)	5ms	6ms	7ms	8ms	0ms	3.1s
synthetic (title)	54ms	59ms	77ms	411ms	1320ms	13.8s
synthetic (string inside object)	54ms	55ms	61ms	226ms	916ms	7.9s

📚 Glossary

column definitions

• benchmark — the name of the test, e.g. "article", followed by the label of the field being measured, e.g. "(title)".
• latency — the time between when a key was pressed and when it was rendered. derived from a set of samples. the median (p50) is shown to show the most common latency.
• p75 — the 75th percentile of the input latency in the test run. 75% of the sampled inputs in this benchmark were processed faster than this value. this provides insight into the upper range of typical performance.
• p90 — the 90th percentile of the input latency in the test run. 90% of the sampled inputs were faster than this. this metric helps identify slower interactions that occurred less frequently during the benchmark.
• p99 — the 99th percentile of the input latency in the test run. only 1% of sampled inputs were slower than this. this represents the worst-case scenarios encountered during the benchmark, useful for identifying potential performance outliers.
• blocking time — the total time during which the main thread was blocked, preventing user input and UI updates. this metric helps identify performance bottlenecks that may cause the interface to feel unresponsive.
• test duration — how long the test run took to complete.