build(deps-dev): bump @sveltejs/kit from 2.53.4 to 2.59.0 in /src/ui

[dependabot]

Bumps @sveltejs/kit from 2.53.4 to 2.59.0.

Release notes

Sourced from @​sveltejs/kit's releases.

@​sveltejs/kit@​2.59.0

Minor Changes

• feat: support query.batch in requested(...) (#15751)

• breaking: on the server, make the promise returned from refresh represent adding the refresh to the map, not the time it takes to run the remote function (#15705)

• feat: experimental query.live function (#15705)

Patch Changes

• fix: unwrap Promise in RemoteCommand output type (#15771)

• fix: empty call to .updates() on a command/form invocation means "don't update anything" (#15705)

• fix: form.fields.foo.as('checkbox', default_value) now works (#15752)

• fix: remote forms with default values defined by field.as('text', defaultValue) now correctly reset to the provided default values once submitted (#15753)

• fix: make sure queries always get started correctly (#15705)

• fix: allow plain functions as overrides in updates (#15705)

@​sveltejs/kit@​2.58.0

Minor Changes

• breaking: require limit in requested (as originally intended) (#15739)

• feat: RemoteQueryFunction gains an optional third generic parameter Validated (defaulting to Input) that represents the argument type after schema validation/transformation (#15739)

• breaking: requested now yields { arg, query } entries instead of the validated argument (#15739)

Patch Changes

• fix: allow query().current, .error, .loading, and .ready to work in non-reactive contexts (#15699)

• fix: prevent deep_set crash on nullish nested values (#15600)

• fix: restore correct RemoteFormFields typing for nullable array fields (e.g. when a schema uses .default([])), so .as('checkbox') and friends work again (#15723)

... (truncated)

Changelog

Sourced from @​sveltejs/kit's changelog.

2.59.0

Minor Changes

• feat: support query.batch in requested(...) (#15751)

• breaking: on the server, make the promise returned from refresh represent adding the refresh to the map, not the time it takes to run the remote function (#15705)

• feat: experimental query.live function (#15705)

Patch Changes

• fix: unwrap Promise in RemoteCommand output type (#15771)

• fix: empty call to .updates() on a command/form invocation means "don't update anything" (#15705)

• fix: form.fields.foo.as('checkbox', default_value) now works (#15752)

• fix: remote forms with default values defined by field.as('text', defaultValue) now correctly reset to the provided default values once submitted (#15753)

• fix: make sure queries always get started correctly (#15705)

• fix: allow plain functions as overrides in updates (#15705)

2.58.0

Minor Changes

• breaking: require limit in requested (as originally intended) (#15739)

• feat: RemoteQueryFunction gains an optional third generic parameter Validated (defaulting to Input) that represents the argument type after schema validation/transformation (#15739)

• breaking: requested now yields { arg, query } entries instead of the validated argument (#15739)

Patch Changes

• fix: allow query().current, .error, .loading, and .ready to work in non-reactive contexts (#15699)

... (truncated)

Commits

• 522ac32 Version Packages (#15769)
• a416bb0 docs: improve description for read config parameter (#15673)
• af248a7 fix: unwrap Promise in RemoteCommand output type (#15771)
• 1c8e573 fix: remote forms with default values defined by `field.as('text', defaultVal...
• 5b28e23 feat: support query.batch in requested (#15751)
• a074dc1 fix: .as('checkbox', value) was completely broken (#15752)
• 055ac24 feat: experimental query.live remote function (#15705)
• c1d3633 chore: fix IDE typescript errors (#15756)
• a21582c Version Packages (#15716)
• f499a45 breaking: return bound query instance from requested (#15739)
• Additional commits viewable in compare view

[DTTerastar]

@claude How can we verify everything still works after this change?

[claude]

Claude finished @DTTerastar's task in 50s —— View job

---

Verifying the @sveltejs/kit upgrade

• Analyze the breaking changes in the release notes
• Check if any breaking features are used in this project
• Review existing test infrastructure
• Provide verification steps

---

Are the breaking changes a risk?

No — the breaking changes in 2.58.0 and 2.59.0 are all scoped to experimental remote query/form APIs (requested(...), query.live, query.batch, RemoteQueryFunction, RemoteCommand). This project doesn't use any of them (grep across all .ts/.svelte files returns nothing). The only things imported from @sveltejs/kit in this codebase are:

• LoadEvent type (route loaders)
• $app/paths and $app/stores (standard SvelteKit APIs — unchanged)

Verification steps

Run these in src/ui/:

1. Install the new dependencies

pnpm install

2. Type-check the full project

pnpm check

This runs svelte-kit sync + svelte-check and catches any type errors introduced by the new version.

3. Build for production

pnpm build

Confirms the static adapter and all routes compile cleanly.

4. Run unit tests

pnpm test:unit

Vitest unit tests cover Modal and related utilities.

5. Run Playwright end-to-end tests

pnpm test

There are 10 Playwright test files covering: index page, map, 3D map, devices table, tooltip, modal, calibration matrix, calibration anchor, and firmware recovery. These are the most valuable tests for confirming nothing regressed at the UI level.

Quick smoke test checklist (manual)

If CI passes, spot-check these pages against a running backend:

• / — map renders, devices show up, WebSocket updates work
• /devices — device list loads, settings can be saved
• /nodes — node list loads, status indicators correct
• /calibration — calibration matrix renders, RSSI values display

The CI on this PR already runs the test suite, so if all checks are green the upgrade is safe to merge.