search params API surface

Hey @tim-smart first off, thank you for the awesome library, its been a blast to use so far, I just had a couple of questions if you have a minute.

a few things I've heard was that effect-atom might be brought into the effect ecosystem as a first class module to support the effect ecosystem

is this true? and if so, any idea on when?

if it is true, any plans to handle the search params api differently? I love the ergonomics of @effect/platform and how it abstracts over the runtime.

and there are currently some apis for supporting client/server hydration, so it would be cool if there was a way to either use the search param api and have it be a no-op in a server context, or, be able to provide an adapter to tell effect-atom where to get the search params from in a server context (url of request).

any info on this stuff would be greatly appreciated! :)

Start with the issue's questions about the search params API, Effect ecosystem integration, and client/server hydration. No file, test, or entry point is named; the work would first need a decided scope for server no-op behavior or a request-URL adapter, with the chosen API behavior documented and validated.