Improve Dutch coverage and prepare international language starter packs

[sridharkalaibala]

Dutch had roughly 280 untranslated newer UI messages, and adding regional language codes exposed selection and packaging gaps. Complete Dutch UI-key coverage, add missing operational messages across existing packs, make the picker searchable by native/English name and code, and retain Chinese script and RTL choices correctly.

This is an internationalization expansion with beta starter packs, not a completed translation release. It adds 40 starter packs (58 choices including English), covering the remaining EU official languages, major non-EU European languages and additional widely spoken languages. The new packs currently cover approximately 3% of UI keys. Untranslated text remains English; the picker exposes coverage and beta status. Full translation and native-speaker review remain outstanding. Customer-menu/Captain/native-window localization remain separate work. Bundled receipt fonts and regression samples now cover all offered languages, including CJK, Bengali, Gujarati, Gurmukhi and Hebrew; original font licences and checksums are included.

Also fix escaped-apostrophe truncation in the English catalogue, retain glossary metadata during seeding, and reject damaged Unicode or changed interpolation placeholders. Existing coverage baselines are preserved; Dutch is raised to 100% UI-key coverage, which is not a native-review claim.

Validation: 115 localization tests, 94 receipt/desktop regression tests, 29 affected API tests, and two starter-fallback tests passed. Translation validation, production frontend build and attribution checks passed. Coverage tests allow English fallback only for explicitly marked starter packs; established packs remain strict. GitHub CI validates the updated merge against develop.

[sridharkalaibala]

Heads-up on the draft's CI blockers: the new starter packs are missing existing required keys (for example lang_bill_number_year, lang_settlement, lang_cancel_whole_order, lang_fulfilment_help, and the busy-kitchen keys), the receipt-sample and bundled-font checks do not yet cover the added languages (for example zh-CN is missing glyph 添), and API unit tests fail for the same missing translation keys. Filling or deliberately scoping the starter-pack contract and updating the receipt/font coverage fixtures should make the draft reviewable.

[sridharkalaibala]

Thanks for refreshing this draft. The new head still has two concrete translation-contract blockers: Desktop's language coverage test and API unit tests report missing fulfillment and busy-kitchen keys in one or more packs (including lang_fulfilment_help, lang_tell_customers_the_kitchen_is_busy, and lang_tell_customers_the_kitchen_is_busy_help). Please add those required keys consistently to every starter pack, then rerun the failing suites. Once they are green, this will be ready for a full review.

[github-actions]

Merged to develop. Anyone can test this - you do not need write access.

Try it at https://develop.posnic.io, or run it yourself:

git fetch origin develop && git checkout develop
npm install && npm --prefix api install
npm run dev   # then http://localhost:3000

When you have tested it, say what you did and what happened, and set
QA passed or QA failed. If you cannot set labels, just comment -
a maintainer will.

Reporting that something is broken is as useful as fixing it. It is
better found here than by a shopkeeper.