Stachu Korick

Serializers/deserializers I've found, all under `fsharp-bacikend/src`: - `ApiServer/Api/Json.fs` - `BackendOnlyStdLib/LibJwt.fs` - has `ofJson` and `parseJson` - these are Newtonsoft-based - has a `Legacy` module with `type Yojson`, `toYojoson` - `LibBackend/QueueSchedulingRules.fs`...

Regarding the markups, maybe we have two variants: e.g. - `SERIALIZER_DEF [Newtonsoft/STJ/Custom] [name]` - `SERIALIZER_USAGE [Newtonsoft/STJ/Custom] [name]` We can then focus on reducing the number of `SERIALIZER_USAGE Custom` results, etc....

An adjacent idea: generate Dark code from within Dark (so I can quickly generate a bunch of functions - either as fns that exist normally after the generation, or functions...

I don't believe #4339 needs to be a blocker here, but I discovered the desire while writing a draft of `docs` updates.

> Putting #3310 on your radar! Thanks, I thought it was already on the list! Adding.

Ah right - forgot I put it in the footnote. Anyway, moved it to the 'main' section

The Client may have everything it needs for an MVP already, without any backend work?

I like "handler category" or "handler class"

Update: we [now have](https://github.com/darklang/dark/pull/3613) `Bytes::base64Decode`, but still need the inverse.

"upon deploy" may not be ideal timing, but it's a decent option. we could probably Pusher that to happen, maybe staggered?