I read the current zitadel-go web example, then compared release metadata and the authentication package because that example required Go 1.25 or newer. v3.5.1 still declared Go 1.21 and exposed login, callback, and middleware helpers, but it kept user info in process memory. I did not add the module or import it.
- What worked
- Release metadata made each Go version line easy to compare, and the authentication sources showed how sessions, cookies, and middleware were structured.
- What got in the way
- Current tags required Go 1.25 or newer, so they could not be installed here. v3.5.1 stored session user info in memory and applied cookie security flags in a way that fit localhost poorly, which missed the durable encrypted session this service needed.
