* docs: enhance migration docs about accessors

related to #15134

* more

Bumps [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) from 5.4.14 to 6.0.9.
- [Release notes](https://github.com/vitejs/vite/releases)
- [Changelog](https://github.com/vitejs/vite/blob/main/packages/vite/CHANGELOG.md)
- [Commits](https://github.com/vitejs/vite/commits/v6.0.9/packages/vite)

---
updated-dependencies:
- dependency-name: vite
  dependency-type: direct:development
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* fix: ensure tracking returns true, even if in unowned

* fix: ensure tracking returns true, even if in unowned

* Update packages/svelte/tests/runtime-runes/samples/effect-tracking-unowned/main.svelte

---------

Co-authored-by: Simon H <5968653+dummdidumm@users.noreply.github.com>

* chore: add download/hash scripts for sandbox

* remove logging

…5201)

This reverts commit f67cf20.

Bumps [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) from 2.0.5 to 2.1.9.
- [Release notes](https://github.com/vitest-dev/vitest/releases)
- [Commits](https://github.com/vitest-dev/vitest/commits/v2.1.9/packages/vitest)

---
updated-dependencies:
- dependency-name: vitest
  dependency-type: direct:development
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Avoid going through the `element.value = element.__value = newValue` condition because `__value` is actually how Lit stores the current value on the element, and messing with that would break things: Lit would think the value hasn't changed (because `__value` is already set to the new value by us) and doesn't fire an update.

fixes #15194

* fix: ensure custom element updates don't run in hydration mode

When a custom element is created before Svelte hydration kicks in, it will scaffold itself, using the properties given via attributes.
Now when a custom element property is set during Svelte's hydration, the Svelte custom element component could run logic like updating an each block. Without turning off hydration mode during that time, the update would try to pick up existing element nodes (because it thinks they must be there because of hydration mode), and crash.

No test because it would require a setup where we can ensure the element is scaffolded before hydration runs.

Fixes #15213

* changeset

---------

Co-authored-by: Rich Harris <rich.harris@vercel.com>

Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>