Currently, MusicBrainz report strings are part of the same Server translation project as all other parts of the UI.

This is not wrong as such, but reports have a lot of long, sometimes complicated strings and are not particularly important for most users. Them being in the main Server component means translators spend time working on them early that could be better spent translating other strings a lot more important for daily use of the site, such as relationships and attributes (and the rest of the Server code). Since Server is one of the components we expect to be reasonably complete before we put a language on beta and pretty much complete before we put it on production, this also means an unnecessary delay in making translations available.

Report strings are also a lot more similar to each other than to the rest of the Server strings, so them being grouped seems like it would simplify translation.

As such, I'd suggest to move these strings under a separate translation component "Reports".