Conduitry

Is your concern that the _preprocessor_ isn't transforming that? I wouldn't expect it to. That's valid input to the compiler as of Svelte 5 - and then the compiler handles...

These feel like two related although potentially distinct issues that we need to make sure are both addressed. One is about `class:foo` directives, and the other is about pseudoclasses.

Ugh. There are type changes. I haven't looked yet whether we can deal with them internally or whether some of them will affect end-users.

After an embarrassing number of commits, this _is_ green now in CI, but I'm a bit worried about the effect this might have on end users. Any type changes here...

I've pushed another change to remove `@types/cookie`, as `cookie` now provides its own types. I'm still not sure what to do about the `string | undefined` stuff.

Ben has opened https://github.com/jshttp/cookie/issues/216 asking about this type change. It looks like a user-specified `decode` callback is now allowed to return `undefined`, and this is used as-is in the `parse()`...

If we just want to filter out cookies with a decoded value of `undefined` from the array returned in `getAll()`, we can do something like this: ```diff diff --git a/packages/kit/src/exports/public.d.ts...

@benmccann Have you confirmed whether it's the dev tools URL-decoding the values for you when displaying them for convenience? If you 'copy as curl', what are the actual header values?

Per Rich, maybe we want to change the behavior of `$effect.tracking()` here, rather than trying to document the current behavior. The only cases where this would matter would be toy...

I don't have an especially strong opinion about this. This PR arose from me doing a global search in the repo for ... something, I no longer remember what. And...