One seat rule for the console and every service that enforces it

Verschifft

24. September 2026 um 17:11 UTC

Autor

Kamo

Ausschuss

ad88f89

The resolver reads the member with its organization fetched and opens no transaction of its own, so a seat is decided correctly on a thread with no persistence context (the AI WebSocket) and a failed read really fails open instead of throwing UnexpectedRollbackException past the catch.