Scapegoat VS Enumeratum

I've since figured this out (Scapegoat/FinalModifierOnCaseClass and WartRemover/FinalCaseClass). I plan to add it to the next version of the article.

The support for scala 3 has been requested a while ago: https://github.com/scapegoat-scala/scapegoat/issues/521 but the original author has stepped down as a maintainer https://github.com/scapegoat-scala/scapegoat/issues/567 and recently most of the changes are just dependency updates.

I'm not sure I understand what Cats or cats-effect has to do with what you're trying to do. As far as I can tell, it sounds like what you're asking is simply "what's the best way to implement an enumerated type in Scala?" The best answer to that I'm aware of is Enumeratum.

In Scala 2: enumeratum which is, essentially, option 3 from your post.

And for exactly the same reasons one shouldn't override equals and hashCode in a case class, they shouldn't manually implement an enumeration and instead let a well-tested macro (2.x) or the compiler itself (3.x) handle reliably doing the automated code generation. The more code that is generated by the compiler, the smaller the defects, technical debt, and security vulnerability surface areas.

For Scala, check out the enumeratum library (https://github.com/lloydmeta/enumeratum). In my opinion its the best enum implementation I know of. It has all the features defined in the table, and the syntax is really clean. It even supports unique associated values (eg. unique String/Int keys).