You're significantly more experienced than me, so I'll defer to you here. What you're saying doesn't make sense to me though.

You're probably more experienced than I am with Rust!

I might be misunderstanding go, but I think the big difference is you use anyhow to get looses error handling at the edges of binaries. It'd be weird to see in a published library, and unusual to see deep in an internal library that supports a binary. Whereas in go you do that sort of error handling everywhere.

I think %w makes sense in libraries, too. They're structured errors that behave like strings. It's a neat trick.