CI to generate manifest.json

[teamssUTXO]

This issue tracks Phase 1 of the BTCPay Server translations revamp roadmap.

Goal

Create a CI file to generate the manifest.json at the translator repo root on every merge.

Should contains 15 available languages with :

• BCP47 code
• Native Name
• File Path
• SHA of the translation json file
• maintainer
• Update Date

Example :

{
  "languages": [
    { "code": "fr",
      "bcp47": "fr-FR",
      "name": "French",
      "native": "Francais",
      "file": "translations/french.json",
      "sha": "...",
      "maintainer": "teamssUTXO|https://github.com/teamssUTXO",
      "updated": "2026-04-12T10:30:00Z" }
  ],
  "_redirect": null
}

Target

Should be merged before issue #7331.

Phase 1 target completion: 2026-05-04 (2 weeks from 2026-04-23).

[coderabbitai]

🔗 Related PRs

#40 - Fix French translations: remove 7 AI slop entries, translate 5 missin… [merged]
#50 - Core language-pack validation + cleanup for issue #34 (rebased from #47) [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[r1ckstardev]

Shipped via PR #54: 3d09010

manifest.json will be auto-generated by the CI workflow at .github/workflows/manifest.yml whenever Translator/translations/**.json changes (or via manual workflow_dispatch). All acceptance criteria from this issue are met: 15 languages, BCP47 / native / file / SHA-256 / maintainer / updated fields, SHA-stable timestamps so unchanged files do not churn on regeneration. Thanks @teamssUTXO.