fix: emit Paraglide TypeScript declarations

[samuelstroschein]

Summary

• configure the Paraglide addon with emitTsDeclarations: true
• verify that generated message declarations include the demo message
• update the all-addons snapshot and addon documentation
• add an sv patch changeset

Why

Paraglide message exports generated as JavaScript/JSDoc can remain stale in a long-lived TypeScript or Svelte language-server session after message keys change. Explicit declaration files provide an authoritative type surface that the language server watches and refreshes.

Validation

• pnpm build
• pnpm --filter sv check
• pnpm --filter sv lint
• pnpm test --project addons paraglide
• pnpm test --project cli -t create-with-all-addons
• pnpm exec changeset status --since=upstream/main

[pkg-svelte-dev]

Install the latest version of sv from b845c4f:

pnpm add https://pkg.svelte.dev/sv/c/b845c4fc978d89f99bfa15bfce0d96b40e9c66ea

Open in pkg.svelte.dev: https://pkg.svelte.dev/repos/cli/pr/1172

Note

This PR is from a fork. A maintainer must approve approve each commit before it can be built and installed.

[changeset-bot]

🦋 Changeset detected

Latest commit: b845c4f

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
sv	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR