chore(deps-dev): bump svelte-check-rs from 0.9.13 to 0.9.15 (#2750)

Bumps [svelte-check-rs](https://github.com/pheuter/svelte-check-rs) from 0.9.13 to 0.9.15.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/pheuter/svelte-check-rs/releases">svelte-check-rs's releases</a>.</em></p>
<blockquote>
<h2>v0.9.15</h2>
<h2>What's Changed</h2>
<h3>Bug Fixes</h3>
<ul>
<li><strong>windows</strong>: Full cross-platform support for separators, shim probing, and modern JS extensions. <code>resolve_tsgo</code> / <code>find_bun_in_bin</code> / <code>find_sveltekit_binary</code> now probe <code>.exe</code> / <code>.cmd</code> / <code>.bat</code> siblings before the extensionless Unix shim (which fails <code>CreateProcess</code> with os error 193), and switch from <code>.exists()</code> to <code>.is_file()</code> so a like-named directory can't short-circuit discovery. Path-separator normalization at every cross-boundary site fixes a source-map back-mapping miss (HashMap keys were <code>\</code>, lookups <code>/</code>), silently no-op <code>tsconfig</code> excludes via <code>globset</code>, mixed-separator tsconfig overlay glob patterns, and cross-OS <code>svelte-kit sync</code> manifest churn. SvelteKit <code>Params</code> matchers, hooks, route signatures, and sync-skip manifests now recognize <code>.mts</code> / <code>.cts</code> / <code>.mjs</code> / <code>.cjs</code> in addition to <code>.ts</code> / <code>.js</code>. <code>kit_file_kind</code> anchors <code>src/params/</code> to the project root so vendored <code>params/</code> subdirs don't get spurious <code>ParamMatcher</code> augmentation. (<a href="https://redirect.github.com/pheuter/svelte-check-rs/issues/138">#138</a>)</li>
<li><strong>transformer</strong>: Close 10 TypeScript errors that <code>svelte-check-rs</code> was silently dropping vs upstream <code>svelte-check@4</code>.
<ul>
<li><strong>Param-matcher narrowing</strong>: the params transform no longer forces <code>: boolean</code> onto the matcher's return type, which was killing TS 5.5+ inferred type predicates and widening <code>RouteParams[X]</code> back to <code>string</code>. The <code>ParamMatcher</code> contract is enforced via a trailing <code>void (match satisfies import('@sveltejs/kit').ParamMatcher)</code> instead.</li>
<li><strong>HTTP-method param annotation</strong>: when the user writes <code>export const GET: RequestHandler = ...</code>, the route transform no longer injects an inner <code>params: RequestEvent</code> annotation that was overriding the loose <code>@sveltejs/kit</code> typing and masking real <code>params.X is string | undefined</code> errors.</li>
<li><strong><code>bind:value={expr}</code> write-direction check</strong>: the component-prop slot now threads the bound expression through to the prop slot instead of emitting <code>value: undefined as any</code>, so TypeScript checks assignability (e.g. <code>string | null</code> bound to a <code>string | undefined</code> prop now reports TS2322). The comma-form <code>bind:value={getter, setter}</code> still routes through the existing <code>__bind_pair</code> path. (<a href="https://redirect.github.com/pheuter/svelte-check-rs/issues/139">#139</a>)</li>
</ul>
</li>
</ul>
<h3>Tests</h3>
<ul>
<li>New unit tests in <code>crates/tsgo-runner/src/kit.rs</code> covering matcher arrow + fn-decl + <code>satisfies</code> + no-match cases and HTTP-method typed/untyped/fn-decl cases.</li>
<li>New transformer snapshot tests for <code>bind:value</code> flow-through + getter/setter fallback.</li>
<li>New end-to-end integration tests in <code>crates/svelte-check-rs/tests/integration_parity.rs</code> driving real <code>tsgo</code> against fixtures in <code>test-fixtures/projects/sveltekit-bundler/</code>.</li>
<li>New unit coverage for each Windows fix: shim ordering, <code>is_file()</code> vs <code>.exists()</code>, forward-slash overlay patterns, cross-OS manifest stability, <code>.mts</code> / <code>.cts</code> / <code>.mjs</code> / <code>.cjs</code> recognition, <code>Params</code> anchoring, and absolute-input guards on <code>relative_import_path</code>.</li>
</ul>
<h3>Docs</h3>
<ul>
<li>Docs site refresh: trimmed to a two-section structure (<code>context</code> + <code>cli</code>), dropped ornamental treatments. Dark-default theming, scroll tracking, copy-to-clipboard, and clickable benchmarks all preserved. (<a href="https://redirect.github.com/pheuter/svelte-check-rs/issues/139">#139</a>)</li>
</ul>
<h2>Full Changelog</h2>
<p><a href="https://github.com/pheuter/svelte-check-rs/compare/v0.9.14...v0.9.15">https://github.com/pheuter/svelte-check-rs/compare/v0.9.14...v0.9.15</a></p>
<h2>v0.9.14</h2>
<h2>What's Changed</h2>
<h3>Bug Fixes</h3>
<ul>
<li><strong>transformer</strong>: <code>$props()</code> LHS type extraction no longer crosses prior statement boundaries. When <code>let { x } = $props()</code> was preceded by a typed <code>const</code>, a function with a return-type annotation, or other LHS-annotated declaration, the backward scan for <code>: Type =</code> could grab the prior statement's type and emit invalid TypeScript that broke tsgo. The scan now bails on top-level <code>;</code>, top-level <code>=</code> (catches the ASI case where the prior statement omits its trailing semicolon), and a second top-level <code>{...}</code> exit that isn't separated by a type-continuation operator. Multi-brace LHS annotations like <code>{A} | {B}</code>, <code>{A} &amp; {B}</code>, <code>[{A}, {B}]</code>, <code>({A} | {B})</code>, and <code>Foo&lt;{A}, {B}&gt;</code> are preserved by gating brace tracking on <code>paren_depth == 0 &amp;&amp; bracket_depth == 0</code> and tracking <code>|</code> / <code>&amp;</code> / <code>,</code> / <code>&lt;</code> / <code>&gt;</code> / <code>?</code> between successive brace exits. (<a href="https://redirect.github.com/pheuter/svelte-check-rs/issues/137">#137</a>, fixes <a href="https://redirect.github.com/pheuter/svelte-check-rs/issues/136">#136</a>, supersedes <a href="https://redirect.github.com/pheuter/svelte-check-rs/issues/135">#135</a>)</li>
</ul>
<h3>Tests</h3>
<ul>
<li>New unit, snapshot, integration, and corpus fixtures covering prior typed <code>const</code>, function return type, multi-brace union / intersection / tuple / parenthesized / generic LHS annotations, and the ASI variant of the original bug.</li>
<li>Replaced <code>?</code>-propagating per-entry I/O in the integration test helper <code>find_transformed_cache_content</code> with <code>let Ok(...) else { continue }</code> so a transient stat error on one cache sibling no longer aborts the search.</li>
</ul>
<h2>Full Changelog</h2>
<p><a href="https://github.com/pheuter/svelte-check-rs/compare/v0.9.13...v0.9.14">https://github.com/pheuter/svelte-check-rs/compare/v0.9.13...v0.9.14</a></p>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/pheuter/svelte-check-rs/commit/f5d1047c1162ca12ddea175055d64228882c2cc9"><code>f5d1047</code></a> chore: release v0.9.15</li>
<li><a href="https://github.com/pheuter/svelte-check-rs/commit/28b74b5ddf1db6f19abc510e62829007d06ba5fc"><code>28b74b5</code></a> fix(transformer): close diagnostic-parity gaps vs upstream svelte-check + doc...</li>
<li><a href="https://github.com/pheuter/svelte-check-rs/commit/e2eddd2beda040eb44bcdf6f4b57eaa19d634a06"><code>e2eddd2</code></a> fix(windows): full cross-platform support for separators, shim probing, and m...</li>
<li><a href="https://github.com/pheuter/svelte-check-rs/commit/fc0bb6e199a5951cf3d919aecd0b9ee05deed072"><code>fc0bb6e</code></a> chore: release v0.9.14</li>
<li><a href="https://github.com/pheuter/svelte-check-rs/commit/a68d302680594bd166909ef8e55b176c0da533fb"><code>a68d302</code></a> fix(transformer): stop extract_type_from_lhs crossing statement boundaries (#...</li>
<li>See full diff in <a href="https://github.com/pheuter/svelte-check-rs/compare/v0.9.13...v0.9.15">compare view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=svelte-check-rs&package-manager=npm_and_yarn&previous-version=0.9.13&new-version=0.9.15)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)


</details>

Author: dependabot[bot]

frontend/package.json

@@ -62,7 +62,7 @@
     "mode-watcher": "^1.1.0",
     "paneforge": "^1.0.2",
     "runed": "^0.37.1",
-    "svelte-check-rs": "^0.9.13",
+    "svelte-check-rs": "^0.9.15",
     "svelte-sonner": "^1.1.1",
     "svelte-toolbelt": "^0.10.6",
     "sveltekit-superforms": "^2.30.1",