SqlErrors bubble up through the service all the way up to the handler. Naturally, I do not want to have SqlErrors be part of the public REST API and I was curious what you recommend doing here. Using a combination of Effect.tapErrorTag and Effect.catchTag to map SqlError onto some generic "internal server error" type? Or do you recommend something different?