Make LLM translation of new UI strings a PR requirement, drop Crowdin dependency

[dnch13]

What problem would this solve?

• New UI strings routinely ship untranslated across most of the 27 locales; Crowdin sync + human translation lag behind releases.
• Contributors can't complete translations inside their PR and rarely bother with Crowdin.

What do you propose?

Make in-PR, LLM-generated translations the default pipeline instead of Crowdin (chat with good LLM is now available for anyone):

• Add the section below to AGENTS.md, so AI agents (Copilot, Claude, etc.) generate all translations whenever a PR adds/changes translatable strings, update CONTRIBUTE.md guide.
• Add a CI check that every locale file has the same keys as en-US — fail the PR otherwise.
• Crowdin, if kept at all, becomes optional post-hoc review, not a blocker.

If necessary - can implement myself, just ask :D

[salif]

I just checked the Bulgarian translations in Crowdin, and they seem to be made with LLM and I find them to be of extremely poor quality. I personally contribute my own translations to Forgejo and they are incomparably better.

[dnch13]

@salif
that pretty-much depends on the quality of the LLM, your comment would have been valid maybe even a year ago, but now everyone got access to models like glm-5.3 or newest claude-sonnet. Also, since Crowdin has LLM-generated translations - why even use it ahahahahah? Literally pointless)) Seems fair to just edit/correct incorrect or bad translations post-factum after somone faces it, maybe adding a note about it. But my bet - just use good LLM and everything is gonna be just fine.

[techknowlogick]

We as the TOC have decided that we will not force contributors to use an LLM.
We are uncertain if your proposal would help improve the quality of translations.
Furthermore, as noted above, LLM generated translations may even worsen the quality of translations.
Using or not using an LLM must remain a personal choice.