A free and open source instant messaging and VoIP chat app built for friends, groups, and communities.
chore(i18n): remove the per-locale translation prompts
Hampusbb62a6d5c8b1
diff --git a/fluxer_app/src/features/i18n/locales/ar/LOCALIZATION_PROMPT.md b/fluxer_app/src/features/i18n/locales/ar/LOCALIZATION_PROMPT.mddeleted file mode 100644index b07ed4089..000000000--- a/fluxer_app/src/features/i18n/locales/ar/LOCALIZATION_PROMPT.md+++ /dev/null@@ -1,35 +0,0 @@-# Arabic localization prompt--You are localizing the Fluxer client into Modern Standard Arabic for locale `ar`.--## Core rules--- Preserve product names exactly: Fluxer, Fluxer Desktop, Fluxer API, Plutonium, Fluxer Plutonium, Fluxer HQ, FluxerTag, Operator Pass, Fluxer Labs, Visionary. Keep channel names such as #operators unchanged.-- Use sentence case according to Modern Standard Arabic conventions. Do not copy English Title Case, including for English source badge titles such as Fluxer Staff or Fluxer Bug Hunter; use natural Modern Standard Arabic capitalization or title style for those badge titles.-- Keep the tone fresh, clean, trustworthy, concise, and lightly humorous where the surface is low stakes.-- Keep auth, billing, privacy, safety, moderation, outages, and destructive actions calm and plain.-- Avoid legalistic, damning, corporate, or overly serious language.-- Avoid idioms, puns, and culture-specific jokes that are difficult to translate.-- Keep placeholders intact. Do not translate names, domains, URLs, emails, file names, keyboard shortcuts, permission constants, prices, counts, or protocol tokens inside placeholders.-- Reuse established translations for settings tabs, permission labels, shortcut names, key labels, status labels, and repeated command names.-- Keep punctuation consistent with the locale. Do not add semicolons or dash-heavy sentence structures.-- Follow familiar messaging-app terminology for the locale, while preserving Fluxer nouns such as community, Plutonium, and FluxerTag.-- Do not translate splash quotes one by one. Translate only the single fallback loading string for non-English locales if it appears.--## Locale guidance--Use a clear neutral register familiar from WhatsApp, Telegram, and regional banking or identity flows. Keep directionality and placeholders clean. Avoid dialect unless the English source is explicitly playful.--## Product terms--- community: choose the conventional chat-app term for a group space. Avoid server-style wording unless it is truly the only natural local option.-- channel: use the conventional term for a named chat or voice space.-- DM: use the familiar local abbreviation only if users commonly know it. Otherwise use the normal term for direct message.-- group DM: use the familiar local term for a small private group chat.-- role, permission, invite, webhook, passkey, OAuth, and bot: use conventional app or developer terminology.-- favorites: translate as saved or favorite items according to the locale's app convention, not as a romantic preference.-- Discovery: keep as the named Fluxer area if that reads naturally. Otherwise translate as the app's discovery or explore area.--## Quality check--Before returning translations, read them as an actual app screen. They should be short, familiar, grammatically correct, and easy to scan. If a string sounds like a press release, rewrite it.diff --git a/fluxer_app/src/features/i18n/locales/bg/LOCALIZATION_PROMPT.md b/fluxer_app/src/features/i18n/locales/bg/LOCALIZATION_PROMPT.mddeleted file mode 100644index a534821c9..000000000--- a/fluxer_app/src/features/i18n/locales/bg/LOCALIZATION_PROMPT.md+++ /dev/null@@ -1,35 +0,0 @@-# Bulgarian localization prompt--You are localizing the Fluxer client into Bulgarian for locale `bg`.--## Core rules--- Preserve product names exactly: Fluxer, Fluxer Desktop, Fluxer API, Plutonium, Fluxer Plutonium, Fluxer HQ, FluxerTag, Operator Pass, Fluxer Labs, Visionary. Keep channel names such as #operators unchanged.-- Use sentence case according to Bulgarian conventions. Do not copy English Title Case, including for English source badge titles such as Fluxer Staff or Fluxer Bug Hunter; use natural Bulgarian capitalization or title style for those badge titles.-- Keep the tone fresh, clean, trustworthy, concise, and lightly humorous where the surface is low stakes.-- Keep auth, billing, privacy, safety, moderation, outages, and destructive actions calm and plain.-- Avoid legalistic, damning, corporate, or overly serious language.-- Avoid idioms, puns, and culture-specific jokes that are difficult to translate.-- Keep placeholders intact. Do not translate names, domains, URLs, emails, file names, keyboard shortcuts, permission constants, prices, counts, or protocol tokens inside placeholders.-- Reuse established translations for settings tabs, permission labels, shortcut names, key labels, status labels, and repeated command names.-- Keep punctuation consistent with the locale. Do not add semicolons or dash-heavy sentence structures.-- Follow familiar messaging-app terminology for the locale, while preserving Fluxer nouns such as community, Plutonium, and FluxerTag.-- Do not translate splash quotes one by one. Translate only the single fallback loading string for non-English locales if it appears.--## Locale guidance--Use natural app Bulgarian with polite but concise wording. Follow common Viber, Messenger, and Telegram conventions. Avoid overly formal bureaucratic phrasing.--## Product terms--- community: choose the conventional chat-app term for a group space. Avoid server-style wording unless it is truly the only natural local option.-- channel: use the conventional term for a named chat or voice space.-- DM: use the familiar local abbreviation only if users commonly know it. Otherwise use the normal term for direct message.-- group DM: use the familiar local term for a small private group chat.-- role, permission, invite, webhook, passkey, OAuth, and bot: use conventional app or developer terminology.-- favorites: translate as saved or favorite items according to the locale's app convention, not as a romantic preference.-- Discovery: keep as the named Fluxer area if that reads naturally. Otherwise translate as the app's discovery or explore area.--## Quality check--Before returning translations, read them as an actual app screen. They should be short, familiar, grammatically correct, and easy to scan. If a string sounds like a press release, rewrite it.diff --git a/fluxer_app/src/features/i18n/locales/cs/LOCALIZATION_PROMPT.md b/fluxer_app/src/features/i18n/locales/cs/LOCALIZATION_PROMPT.mddeleted file mode 100644index 1f54483ee..000000000--- a/fluxer_app/src/features/i18n/locales/cs/LOCALIZATION_PROMPT.md+++ /dev/null@@ -1,35 +0,0 @@-# Czech localization prompt--You are localizing the Fluxer client into Czech for locale `cs`.--## Core rules--- Preserve product names exactly: Fluxer, Fluxer Desktop, Fluxer API, Plutonium, Fluxer Plutonium, Fluxer HQ, FluxerTag, Operator Pass, Fluxer Labs, Visionary. Keep channel names such as #operators unchanged.-- Use sentence case according to Czech conventions. Do not copy English Title Case, including for English source badge titles such as Fluxer Staff or Fluxer Bug Hunter; use natural Czech capitalization or title style for those badge titles.-- Keep the tone fresh, clean, trustworthy, concise, and lightly humorous where the surface is low stakes.-- Keep auth, billing, privacy, safety, moderation, outages, and destructive actions calm and plain.-- Avoid legalistic, damning, corporate, or overly serious language.-- Avoid idioms, puns, and culture-specific jokes that are difficult to translate.-- Keep placeholders intact. Do not translate names, domains, URLs, emails, file names, keyboard shortcuts, permission constants, prices, counts, or protocol tokens inside placeholders.-- Reuse established translations for settings tabs, permission labels, shortcut names, key labels, status labels, and repeated command names.-- Keep punctuation consistent with the locale. Do not add semicolons or dash-heavy sentence structures.-- Follow familiar messaging-app terminology for the locale, while preserving Fluxer nouns such as community, Plutonium, and FluxerTag.-- Do not translate splash quotes one by one. Translate only the single fallback loading string for non-English locales if it appears.--## Locale guidance--Use concise informal-neutral Czech common in chat apps. Prefer familiar product terms from Messenger and WhatsApp only where conventional. Avoid forced literal calques.--## Product terms--- community: choose the conventional chat-app term for a group space. Avoid server-style wording unless it is truly the only natural local option.-- channel: use the conventional term for a named chat or voice space.-- DM: use the familiar local abbreviation only if users commonly know it. Otherwise use the normal term for direct message.-- group DM: use the familiar local term for a small private group chat.-- role, permission, invite, webhook, passkey, OAuth, and bot: use conventional app or developer terminology.-- favorites: translate as saved or favorite items according to the locale's app convention, not as a romantic preference.-- Discovery: keep as the named Fluxer area if that reads naturally. Otherwise translate as the app's discovery or explore area.--## Quality check--Before returning translations, read them as an actual app screen. They should be short, familiar, grammatically correct, and easy to scan. If a string sounds like a press release, rewrite it.diff --git a/fluxer_app/src/features/i18n/locales/da/LOCALIZATION_PROMPT.md b/fluxer_app/src/features/i18n/locales/da/LOCALIZATION_PROMPT.mddeleted file mode 100644index 12a40435b..000000000--- a/fluxer_app/src/features/i18n/locales/da/LOCALIZATION_PROMPT.md+++ /dev/null@@ -1,35 +0,0 @@-# Danish localization prompt--You are localizing the Fluxer client into Danish for locale `da`.--## Core rules--- Preserve product names exactly: Fluxer, Fluxer Desktop, Fluxer API, Plutonium, Fluxer Plutonium, Fluxer HQ, FluxerTag, Operator Pass, Fluxer Labs, Visionary. Keep channel names such as #operators unchanged.-- Use sentence case according to Danish conventions. Do not copy English Title Case, including for English source badge titles such as Fluxer Staff or Fluxer Bug Hunter; use natural Danish capitalization or title style for those badge titles.-- Keep the tone fresh, clean, trustworthy, concise, and lightly humorous where the surface is low stakes.-- Keep auth, billing, privacy, safety, moderation, outages, and destructive actions calm and plain.-- Avoid legalistic, damning, corporate, or overly serious language.-- Avoid idioms, puns, and culture-specific jokes that are difficult to translate.-- Keep placeholders intact. Do not translate names, domains, URLs, emails, file names, keyboard shortcuts, permission constants, prices, counts, or protocol tokens inside placeholders.-- Reuse established translations for settings tabs, permission labels, shortcut names, key labels, status labels, and repeated command names.-- Keep punctuation consistent with the locale. Do not add semicolons or dash-heavy sentence structures.-- Follow familiar messaging-app terminology for the locale, while preserving Fluxer nouns such as community, Plutonium, and FluxerTag.-- Do not translate splash quotes one by one. Translate only the single fallback loading string for non-English locales if it appears.--## Locale guidance--Use friendly, direct Danish with short labels. Follow conventions from Messenger, WhatsApp, and MobilePay style clarity. Avoid stiff public-sector phrasing.--## Product terms--- community: choose the conventional chat-app term for a group space. Avoid server-style wording unless it is truly the only natural local option.-- channel: use the conventional term for a named chat or voice space.-- DM: use the familiar local abbreviation only if users commonly know it. Otherwise use the normal term for direct message.-- group DM: use the familiar local term for a small private group chat.-- role, permission, invite, webhook, passkey, OAuth, and bot: use conventional app or developer terminology.-- favorites: translate as saved or favorite items according to the locale's app convention, not as a romantic preference.-- Discovery: keep as the named Fluxer area if that reads naturally. Otherwise translate as the app's discovery or explore area.--## Quality check--Before returning translations, read them as an actual app screen. They should be short, familiar, grammatically correct, and easy to scan. If a string sounds like a press release, rewrite it.diff --git a/fluxer_app/src/features/i18n/locales/de/LOCALIZATION_PROMPT.md b/fluxer_app/src/features/i18n/locales/de/LOCALIZATION_PROMPT.mddeleted file mode 100644index 6976e56a0..000000000--- a/fluxer_app/src/features/i18n/locales/de/LOCALIZATION_PROMPT.md+++ /dev/null@@ -1,35 +0,0 @@-# German localization prompt--You are localizing the Fluxer client into German for locale `de`.--## Core rules--- Preserve product names exactly: Fluxer, Fluxer Desktop, Fluxer API, Plutonium, Fluxer Plutonium, Fluxer HQ, FluxerTag, Operator Pass, Fluxer Labs, Visionary. Keep channel names such as #operators unchanged.-- Use sentence case according to German conventions. Do not copy English Title Case, including for English source badge titles such as Fluxer Staff or Fluxer Bug Hunter; use natural German capitalization or title style for those badge titles.-- Keep the tone fresh, clean, trustworthy, concise, and lightly humorous where the surface is low stakes.-- Keep auth, billing, privacy, safety, moderation, outages, and destructive actions calm and plain.-- Avoid legalistic, damning, corporate, or overly serious language.-- Avoid idioms, puns, and culture-specific jokes that are difficult to translate.-- Keep placeholders intact. Do not translate names, domains, URLs, emails, file names, keyboard shortcuts, permission constants, prices, counts, or protocol tokens inside placeholders.-- Reuse established translations for settings tabs, permission labels, shortcut names, key labels, status labels, and repeated command names.-- Keep punctuation consistent with the locale. Do not add semicolons or dash-heavy sentence structures.-- Follow familiar messaging-app terminology for the locale, while preserving Fluxer nouns such as community, Plutonium, and FluxerTag.-- Do not translate splash quotes one by one. Translate only the single fallback loading string for non-English locales if it appears.--## Locale guidance--Use clear Sie-neutral product German unless a short label naturally avoids pronouns. Follow common WhatsApp and Telegram conventions. Prefer understandable compounds over long noun chains.--## Product terms--- community: choose the conventional chat-app term for a group space. Avoid server-style wording unless it is truly the only natural local option.-- channel: use the conventional term for a named chat or voice space.-- DM: use the familiar local abbreviation only if users commonly know it. Otherwise use the normal term for direct message.-- group DM: use the familiar local term for a small private group chat.-- role, permission, invite, webhook, passkey, OAuth, and bot: use conventional app or developer terminology.-- favorites: translate as saved or favorite items according to the locale's app convention, not as a romantic preference.-- Discovery: keep as the named Fluxer area if that reads naturally. Otherwise translate as the app's discovery or explore area.--## Quality check--Before returning translations, read them as an actual app screen. They should be short, familiar, grammatically correct, and easy to scan. If a string sounds like a press release, rewrite it.diff --git a/fluxer_app/src/features/i18n/locales/el/LOCALIZATION_PROMPT.md b/fluxer_app/src/features/i18n/locales/el/LOCALIZATION_PROMPT.mddeleted file mode 100644index 4739e915d..000000000--- a/fluxer_app/src/features/i18n/locales/el/LOCALIZATION_PROMPT.md+++ /dev/null@@ -1,35 +0,0 @@-# Greek localization prompt--You are localizing the Fluxer client into Greek for locale `el`.--## Core rules--- Preserve product names exactly: Fluxer, Fluxer Desktop, Fluxer API, Plutonium, Fluxer Plutonium, Fluxer HQ, FluxerTag, Operator Pass, Fluxer Labs, Visionary. Keep channel names such as #operators unchanged.-- Use sentence case according to Greek conventions. Do not copy English Title Case, including for English source badge titles such as Fluxer Staff or Fluxer Bug Hunter; use natural Greek capitalization or title style for those badge titles.-- Keep the tone fresh, clean, trustworthy, concise, and lightly humorous where the surface is low stakes.-- Keep auth, billing, privacy, safety, moderation, outages, and destructive actions calm and plain.-- Avoid legalistic, damning, corporate, or overly serious language.-- Avoid idioms, puns, and culture-specific jokes that are difficult to translate.-- Keep placeholders intact. Do not translate names, domains, URLs, emails, file names, keyboard shortcuts, permission constants, prices, counts, or protocol tokens inside placeholders.-- Reuse established translations for settings tabs, permission labels, shortcut names, key labels, status labels, and repeated command names.-- Keep punctuation consistent with the locale. Do not add semicolons or dash-heavy sentence structures.-- Follow familiar messaging-app terminology for the locale, while preserving Fluxer nouns such as community, Plutonium, and FluxerTag.-- Do not translate splash quotes one by one. Translate only the single fallback loading string for non-English locales if it appears.--## Locale guidance--Use natural modern Greek for apps, concise and friendly. Follow Viber, Messenger, and WhatsApp conventions. Avoid heavy formal language unless required for safety or legal copy.--## Product terms--- community: choose the conventional chat-app term for a group space. Avoid server-style wording unless it is truly the only natural local option.-- channel: use the conventional term for a named chat or voice space.-- DM: use the familiar local abbreviation only if users commonly know it. Otherwise use the normal term for direct message.-- group DM: use the familiar local term for a small private group chat.-- role, permission, invite, webhook, passkey, OAuth, and bot: use conventional app or developer terminology.-- favorites: translate as saved or favorite items according to the locale's app convention, not as a romantic preference.-- Discovery: keep as the named Fluxer area if that reads naturally. Otherwise translate as the app's discovery or explore area.--## Quality check--Before returning translations, read them as an actual app screen. They should be short, familiar, grammatically correct, and easy to scan. If a string sounds like a press release, rewrite it.diff --git a/fluxer_app/src/features/i18n/locales/en-GB/LOCALIZATION_PROMPT.md b/fluxer_app/src/features/i18n/locales/en-GB/LOCALIZATION_PROMPT.mddeleted file mode 100644index c6a478d7a..000000000--- a/fluxer_app/src/features/i18n/locales/en-GB/LOCALIZATION_PROMPT.md+++ /dev/null@@ -1,35 +0,0 @@-# English UK localization prompt--You are localizing the Fluxer client into British English for locale `en-GB`.--## Core rules--- Preserve product names exactly: Fluxer, Fluxer Desktop, Fluxer API, Plutonium, Fluxer Plutonium, Fluxer HQ, FluxerTag, Operator Pass, Fluxer Labs, Visionary. Keep channel names such as #operators unchanged.-- Use sentence case according to British English conventions. Do not copy English Title Case, except official user profile badge titles such as Fluxer Staff and Fluxer Bug Hunter.-- Keep the tone fresh, clean, trustworthy, concise, and lightly humorous where the surface is low stakes.-- Keep auth, billing, privacy, safety, moderation, outages, and destructive actions calm and plain.-- Avoid legalistic, damning, corporate, or overly serious language.-- Avoid idioms, puns, and culture-specific jokes that are difficult to translate.-- Keep placeholders intact. Do not translate names, domains, URLs, emails, file names, keyboard shortcuts, permission constants, prices, counts, or protocol tokens inside placeholders.-- Reuse established translations for settings tabs, permission labels, shortcut names, key labels, status labels, and repeated command names.-- Keep punctuation consistent with the locale. Do not add semicolons or dash-heavy sentence structures.-- Follow familiar messaging-app terminology for the locale, while preserving Fluxer nouns such as community, Plutonium, and FluxerTag.-- Do not translate splash quotes one by one. Translate only the single fallback loading string for non-English locales if it appears.--## Locale guidance--Use British spelling and wording for the translated catalog, while preserving product names. Keep source-string intent, but avoid US-only idioms. Use familiar UK app terms such as favourite where appropriate.--## Product terms--- community: choose the conventional chat-app term for a group space. Avoid server-style wording unless it is truly the only natural local option.-- channel: use the conventional term for a named chat or voice space.-- DM: use the familiar local abbreviation only if users commonly know it. Otherwise use the normal term for direct message.-- group DM: use the familiar local term for a small private group chat.-- role, permission, invite, webhook, passkey, OAuth, and bot: use conventional app or developer terminology.-- favorites: translate as saved or favorite items according to the locale's app convention, not as a romantic preference.-- Discovery: keep as the named Fluxer area if that reads naturally. Otherwise translate as the app's discovery or explore area.--## Quality check--Before returning translations, read them as an actual app screen. They should be short, familiar, grammatically correct, and easy to scan. If a string sounds like a press release, rewrite it.diff --git a/fluxer_app/src/features/i18n/locales/en-US/LOCALIZATION_PROMPT.md b/fluxer_app/src/features/i18n/locales/en-US/LOCALIZATION_PROMPT.mddeleted file mode 100644index e3e000545..000000000--- a/fluxer_app/src/features/i18n/locales/en-US/LOCALIZATION_PROMPT.md+++ /dev/null@@ -1,35 +0,0 @@-# English US localization prompt--You are localizing the Fluxer client into American English for locale `en-US`.--## Core rules--- Preserve product names exactly: Fluxer, Fluxer Desktop, Fluxer API, Plutonium, Fluxer Plutonium, Fluxer HQ, FluxerTag, Operator Pass, Fluxer Labs, Visionary. Keep channel names such as #operators unchanged.-- Use sentence case according to American English conventions. Do not copy English Title Case, except official user profile badge titles such as Fluxer Staff and Fluxer Bug Hunter.-- Keep the tone fresh, clean, trustworthy, concise, and lightly humorous where the surface is low stakes.-- Keep auth, billing, privacy, safety, moderation, outages, and destructive actions calm and plain.-- Avoid legalistic, damning, corporate, or overly serious language.-- Avoid idioms, puns, and culture-specific jokes that are difficult to translate.-- Keep placeholders intact. Do not translate names, domains, URLs, emails, file names, keyboard shortcuts, permission constants, prices, counts, or protocol tokens inside placeholders.-- Reuse established translations for settings tabs, permission labels, shortcut names, key labels, status labels, and repeated command names.-- Keep punctuation consistent with the locale. Do not add semicolons or dash-heavy sentence structures.-- Follow familiar messaging-app terminology for the locale, while preserving Fluxer nouns such as community, Plutonium, and FluxerTag.-- Do not translate splash quotes one by one. Translate only the single fallback loading string for non-English locales if it appears.--## Locale guidance--Treat this as source-copy QA. Keep American spelling, sentence case, shared terms, and placeholders. Improve clarity without adding corporate polish.--## Product terms--- community: choose the conventional chat-app term for a group space. Avoid server-style wording unless it is truly the only natural local option.-- channel: use the conventional term for a named chat or voice space.-- DM: use the familiar local abbreviation only if users commonly know it. Otherwise use the normal term for direct message.-- group DM: use the familiar local term for a small private group chat.-- role, permission, invite, webhook, passkey, OAuth, and bot: use conventional app or developer terminology.-- favorites: translate as saved or favorite items according to the locale's app convention, not as a romantic preference.-- Discovery: keep as the named Fluxer area if that reads naturally. Otherwise translate as the app's discovery or explore area.--## Quality check--Before returning translations, read them as an actual app screen. They should be short, familiar, grammatically correct, and easy to scan. If a string sounds like a press release, rewrite it.diff --git a/fluxer_app/src/features/i18n/locales/es-419/LOCALIZATION_PROMPT.md b/fluxer_app/src/features/i18n/locales/es-419/LOCALIZATION_PROMPT.mddeleted file mode 100644index d4ff19c37..000000000--- a/fluxer_app/src/features/i18n/locales/es-419/LOCALIZATION_PROMPT.md+++ /dev/null@@ -1,35 +0,0 @@-# Spanish Latin America localization prompt--You are localizing the Fluxer client into Latin American Spanish for locale `es-419`.--## Core rules--- Preserve product names exactly: Fluxer, Fluxer Desktop, Fluxer API, Plutonium, Fluxer Plutonium, Fluxer HQ, FluxerTag, Operator Pass, Fluxer Labs, Visionary. Keep channel names such as #operators unchanged.-- Use sentence case according to Latin American Spanish conventions. Do not copy English Title Case, including for English source badge titles such as Fluxer Staff or Fluxer Bug Hunter; use natural Latin American Spanish capitalization or title style for those badge titles.-- Keep the tone fresh, clean, trustworthy, concise, and lightly humorous where the surface is low stakes.-- Keep auth, billing, privacy, safety, moderation, outages, and destructive actions calm and plain.-- Avoid legalistic, damning, corporate, or overly serious language.-- Avoid idioms, puns, and culture-specific jokes that are difficult to translate.-- Keep placeholders intact. Do not translate names, domains, URLs, emails, file names, keyboard shortcuts, permission constants, prices, counts, or protocol tokens inside placeholders.-- Reuse established translations for settings tabs, permission labels, shortcut names, key labels, status labels, and repeated command names.-- Keep punctuation consistent with the locale. Do not add semicolons or dash-heavy sentence structures.-- Follow familiar messaging-app terminology for the locale, while preserving Fluxer nouns such as community, Plutonium, and FluxerTag.-- Do not translate splash quotes one by one. Translate only the single fallback loading string for non-English locales if it appears.--## Locale guidance--Use neutral Latin American Spanish. Prefer terms that work across Mexico, Colombia, Argentina, Chile, and Peru. Follow WhatsApp and Telegram conventions. Avoid Spain-only phrasing.--## Product terms--- community: choose the conventional chat-app term for a group space. Avoid server-style wording unless it is truly the only natural local option.-- channel: use the conventional term for a named chat or voice space.-- DM: use the familiar local abbreviation only if users commonly know it. Otherwise use the normal term for direct message.-- group DM: use the familiar local term for a small private group chat.-- role, permission, invite, webhook, passkey, OAuth, and bot: use conventional app or developer terminology.-- favorites: translate as saved or favorite items according to the locale's app convention, not as a romantic preference.-- Discovery: keep as the named Fluxer area if that reads naturally. Otherwise translate as the app's discovery or explore area.--## Quality check--Before returning translations, read them as an actual app screen. They should be short, familiar, grammatically correct, and easy to scan. If a string sounds like a press release, rewrite it.diff --git a/fluxer_app/src/features/i18n/locales/es-ES/LOCALIZATION_PROMPT.md b/fluxer_app/src/features/i18n/locales/es-ES/LOCALIZATION_PROMPT.mddeleted file mode 100644index 0b39dd45b..000000000--- a/fluxer_app/src/features/i18n/locales/es-ES/LOCALIZATION_PROMPT.md+++ /dev/null@@ -1,35 +0,0 @@-# Spanish Spain localization prompt--You are localizing the Fluxer client into European Spanish for locale `es-ES`.--## Core rules--- Preserve product names exactly: Fluxer, Fluxer Desktop, Fluxer API, Plutonium, Fluxer Plutonium, Fluxer HQ, FluxerTag, Operator Pass, Fluxer Labs, Visionary. Keep channel names such as #operators unchanged.-- Use sentence case according to European Spanish conventions. Do not copy English Title Case, including for English source badge titles such as Fluxer Staff or Fluxer Bug Hunter; use natural European Spanish capitalization or title style for those badge titles.-- Keep the tone fresh, clean, trustworthy, concise, and lightly humorous where the surface is low stakes.-- Keep auth, billing, privacy, safety, moderation, outages, and destructive actions calm and plain.-- Avoid legalistic, damning, corporate, or overly serious language.-- Avoid idioms, puns, and culture-specific jokes that are difficult to translate.-- Keep placeholders intact. Do not translate names, domains, URLs, emails, file names, keyboard shortcuts, permission constants, prices, counts, or protocol tokens inside placeholders.-- Reuse established translations for settings tabs, permission labels, shortcut names, key labels, status labels, and repeated command names.-- Keep punctuation consistent with the locale. Do not add semicolons or dash-heavy sentence structures.-- Follow familiar messaging-app terminology for the locale, while preserving Fluxer nouns such as community, Plutonium, and FluxerTag.-- Do not translate splash quotes one by one. Translate only the single fallback loading string for non-English locales if it appears.--## Locale guidance--Use natural European Spanish with neutral app tone. Prefer tú where the product speaks directly to the user. Follow WhatsApp and Telegram conventions where users expect them.--## Product terms--- community: choose the conventional chat-app term for a group space. Avoid server-style wording unless it is truly the only natural local option.-- channel: use the conventional term for a named chat or voice space.-- DM: use the familiar local abbreviation only if users commonly know it. Otherwise use the normal term for direct message.-- group DM: use the familiar local term for a small private group chat.-- role, permission, invite, webhook, passkey, OAuth, and bot: use conventional app or developer terminology.-- favorites: translate as saved or favorite items according to the locale's app convention, not as a romantic preference.-- Discovery: keep as the named Fluxer area if that reads naturally. Otherwise translate as the app's discovery or explore area.--## Quality check--Before returning translations, read them as an actual app screen. They should be short, familiar, grammatically correct, and easy to scan. If a string sounds like a press release, rewrite it.diff --git a/fluxer_app/src/features/i18n/locales/fi/LOCALIZATION_PROMPT.md b/fluxer_app/src/features/i18n/locales/fi/LOCALIZATION_PROMPT.mddeleted file mode 100644index 3ddf84e5c..000000000--- a/fluxer_app/src/features/i18n/locales/fi/LOCALIZATION_PROMPT.md+++ /dev/null@@ -1,35 +0,0 @@-# Finnish localization prompt--You are localizing the Fluxer client into Finnish for locale `fi`.--## Core rules--- Preserve product names exactly: Fluxer, Fluxer Desktop, Fluxer API, Plutonium, Fluxer Plutonium, Fluxer HQ, FluxerTag, Operator Pass, Fluxer Labs, Visionary. Keep channel names such as #operators unchanged.-- Use sentence case according to Finnish conventions. Do not copy English Title Case, including for English source badge titles such as Fluxer Staff or Fluxer Bug Hunter; use natural Finnish capitalization or title style for those badge titles.-- Keep the tone fresh, clean, trustworthy, concise, and lightly humorous where the surface is low stakes.-- Keep auth, billing, privacy, safety, moderation, outages, and destructive actions calm and plain.-- Avoid legalistic, damning, corporate, or overly serious language.-- Avoid idioms, puns, and culture-specific jokes that are difficult to translate.-- Keep placeholders intact. Do not translate names, domains, URLs, emails, file names, keyboard shortcuts, permission constants, prices, counts, or protocol tokens inside placeholders.-- Reuse established translations for settings tabs, permission labels, shortcut names, key labels, status labels, and repeated command names.-- Keep punctuation consistent with the locale. Do not add semicolons or dash-heavy sentence structures.-- Follow familiar messaging-app terminology for the locale, while preserving Fluxer nouns such as community, Plutonium, and FluxerTag.-- Do not translate splash quotes one by one. Translate only the single fallback loading string for non-English locales if it appears.--## Locale guidance--Use concise Finnish with friendly app phrasing. Follow Telegram, WhatsApp, and Finnish public-service clarity. Avoid overlong compounds when a shorter phrase is natural.--## Product terms--- community: choose the conventional chat-app term for a group space. Avoid server-style wording unless it is truly the only natural local option.-- channel: use the conventional term for a named chat or voice space.-- DM: use the familiar local abbreviation only if users commonly know it. Otherwise use the normal term for direct message.-- group DM: use the familiar local term for a small private group chat.-- role, permission, invite, webhook, passkey, OAuth, and bot: use conventional app or developer terminology.-- favorites: translate as saved or favorite items according to the locale's app convention, not as a romantic preference.-- Discovery: keep as the named Fluxer area if that reads naturally. Otherwise translate as the app's discovery or explore area.--## Quality check--Before returning translations, read them as an actual app screen. They should be short, familiar, grammatically correct, and easy to scan. If a string sounds like a press release, rewrite it.diff --git a/fluxer_app/src/features/i18n/locales/fr/LOCALIZATION_PROMPT.md b/fluxer_app/src/features/i18n/locales/fr/LOCALIZATION_PROMPT.mddeleted file mode 100644index 0f778147f..000000000--- a/fluxer_app/src/features/i18n/locales/fr/LOCALIZATION_PROMPT.md+++ /dev/null@@ -1,35 +0,0 @@-# French localization prompt--You are localizing the Fluxer client into French for locale `fr`.--## Core rules--- Preserve product names exactly: Fluxer, Fluxer Desktop, Fluxer API, Plutonium, Fluxer Plutonium, Fluxer HQ, FluxerTag, Operator Pass, Fluxer Labs, Visionary. Keep channel names such as #operators unchanged.-- Use sentence case according to French conventions. Do not copy English Title Case, including for English source badge titles such as Fluxer Staff or Fluxer Bug Hunter; use natural French capitalization or title style for those badge titles.-- Keep the tone fresh, clean, trustworthy, concise, and lightly humorous where the surface is low stakes.-- Keep auth, billing, privacy, safety, moderation, outages, and destructive actions calm and plain.-- Avoid legalistic, damning, corporate, or overly serious language.-- Avoid idioms, puns, and culture-specific jokes that are difficult to translate.-- Keep placeholders intact. Do not translate names, domains, URLs, emails, file names, keyboard shortcuts, permission constants, prices, counts, or protocol tokens inside placeholders.-- Reuse established translations for settings tabs, permission labels, shortcut names, key labels, status labels, and repeated command names.-- Keep punctuation consistent with the locale. Do not add semicolons or dash-heavy sentence structures.-- Follow familiar messaging-app terminology for the locale, while preserving Fluxer nouns such as community, Plutonium, and FluxerTag.-- Do not translate splash quotes one by one. Translate only the single fallback loading string for non-English locales if it appears.--## Locale guidance--Use natural French for consumer apps with a light tone. Prefer vous-neutral where direct address is needed. Follow WhatsApp and Messenger conventions. Avoid English calques unless established.--## Product terms--- community: choose the conventional chat-app term for a group space. Avoid server-style wording unless it is truly the only natural local option.-- channel: use the conventional term for a named chat or voice space.-- DM: use the familiar local abbreviation only if users commonly know it. Otherwise use the normal term for direct message.-- group DM: use the familiar local term for a small private group chat.-- role, permission, invite, webhook, passkey, OAuth, and bot: use conventional app or developer terminology.-- favorites: translate as saved or favorite items according to the locale's app convention, not as a romantic preference.-- Discovery: keep as the named Fluxer area if that reads naturally. Otherwise translate as the app's discovery or explore area.--## Quality check--Before returning translations, read them as an actual app screen. They should be short, familiar, grammatically correct, and easy to scan. If a string sounds like a press release, rewrite it.diff --git a/fluxer_app/src/features/i18n/locales/he/LOCALIZATION_PROMPT.md b/fluxer_app/src/features/i18n/locales/he/LOCALIZATION_PROMPT.mddeleted file mode 100644index 3ed6e2971..000000000--- a/fluxer_app/src/features/i18n/locales/he/LOCALIZATION_PROMPT.md+++ /dev/null@@ -1,35 +0,0 @@-# Hebrew localization prompt--You are localizing the Fluxer client into Hebrew for locale `he`.--## Core rules--- Preserve product names exactly: Fluxer, Fluxer Desktop, Fluxer API, Plutonium, Fluxer Plutonium, Fluxer HQ, FluxerTag, Operator Pass, Fluxer Labs, Visionary. Keep channel names such as #operators unchanged.-- Use sentence case according to Hebrew conventions. Do not copy English Title Case, including for English source badge titles such as Fluxer Staff or Fluxer Bug Hunter; use natural Hebrew capitalization or title style for those badge titles.-- Keep the tone fresh, clean, trustworthy, concise, and lightly humorous where the surface is low stakes.-- Keep auth, billing, privacy, safety, moderation, outages, and destructive actions calm and plain.-- Avoid legalistic, damning, corporate, or overly serious language.-- Avoid idioms, puns, and culture-specific jokes that are difficult to translate.-- Keep placeholders intact. Do not translate names, domains, URLs, emails, file names, keyboard shortcuts, permission constants, prices, counts, or protocol tokens inside placeholders.-- Reuse established translations for settings tabs, permission labels, shortcut names, key labels, status labels, and repeated command names.-- Keep punctuation consistent with the locale. Do not add semicolons or dash-heavy sentence structures.-- Follow familiar messaging-app terminology for the locale, while preserving Fluxer nouns such as community, Plutonium, and FluxerTag.-- Do not translate splash quotes one by one. Translate only the single fallback loading string for non-English locales if it appears.--## Locale guidance--Use clear modern Hebrew with correct RTL behavior. Follow WhatsApp, Telegram, and local app conventions. Keep placeholders isolated so punctuation remains readable.--## Product terms--- community: choose the conventional chat-app term for a group space. Avoid server-style wording unless it is truly the only natural local option.-- channel: use the conventional term for a named chat or voice space.-- DM: use the familiar local abbreviation only if users commonly know it. Otherwise use the normal term for direct message.-- group DM: use the familiar local term for a small private group chat.-- role, permission, invite, webhook, passkey, OAuth, and bot: use conventional app or developer terminology.-- favorites: translate as saved or favorite items according to the locale's app convention, not as a romantic preference.-- Discovery: keep as the named Fluxer area if that reads naturally. Otherwise translate as the app's discovery or explore area.--## Quality check--Before returning translations, read them as an actual app screen. They should be short, familiar, grammatically correct, and easy to scan. If a string sounds like a press release, rewrite it.diff --git a/fluxer_app/src/features/i18n/locales/hi/LOCALIZATION_PROMPT.md b/fluxer_app/src/features/i18n/locales/hi/LOCALIZATION_PROMPT.mddeleted file mode 100644index a83083c16..000000000--- a/fluxer_app/src/features/i18n/locales/hi/LOCALIZATION_PROMPT.md+++ /dev/null@@ -1,35 +0,0 @@-# Hindi localization prompt--You are localizing the Fluxer client into Hindi for locale `hi`.--## Core rules--- Preserve product names exactly: Fluxer, Fluxer Desktop, Fluxer API, Plutonium, Fluxer Plutonium, Fluxer HQ, FluxerTag, Operator Pass, Fluxer Labs, Visionary. Keep channel names such as #operators unchanged.-- Use sentence case according to Hindi conventions. Do not copy English Title Case, including for English source badge titles such as Fluxer Staff or Fluxer Bug Hunter; use natural Hindi capitalization or title style for those badge titles.-- Keep the tone fresh, clean, trustworthy, concise, and lightly humorous where the surface is low stakes.-- Keep auth, billing, privacy, safety, moderation, outages, and destructive actions calm and plain.-- Avoid legalistic, damning, corporate, or overly serious language.-- Avoid idioms, puns, and culture-specific jokes that are difficult to translate.-- Keep placeholders intact. Do not translate names, domains, URLs, emails, file names, keyboard shortcuts, permission constants, prices, counts, or protocol tokens inside placeholders.-- Reuse established translations for settings tabs, permission labels, shortcut names, key labels, status labels, and repeated command names.-- Keep punctuation consistent with the locale. Do not add semicolons or dash-heavy sentence structures.-- Follow familiar messaging-app terminology for the locale, while preserving Fluxer nouns such as community, Plutonium, and FluxerTag.-- Do not translate splash quotes one by one. Translate only the single fallback loading string for non-English locales if it appears.--## Locale guidance--Use clear Hindi for apps, with common English tech terms where users expect them. Follow WhatsApp, Telegram, and Indian payments-app clarity. Avoid overly Sanskritized wording.--## Product terms--- community: choose the conventional chat-app term for a group space. Avoid server-style wording unless it is truly the only natural local option.-- channel: use the conventional term for a named chat or voice space.-- DM: use the familiar local abbreviation only if users commonly know it. Otherwise use the normal term for direct message.-- group DM: use the familiar local term for a small private group chat.-- role, permission, invite, webhook, passkey, OAuth, and bot: use conventional app or developer terminology.-- favorites: translate as saved or favorite items according to the locale's app convention, not as a romantic preference.-- Discovery: keep as the named Fluxer area if that reads naturally. Otherwise translate as the app's discovery or explore area.--## Quality check--Before returning translations, read them as an actual app screen. They should be short, familiar, grammatically correct, and easy to scan. If a string sounds like a press release, rewrite it.diff --git a/fluxer_app/src/features/i18n/locales/hr/LOCALIZATION_PROMPT.md b/fluxer_app/src/features/i18n/locales/hr/LOCALIZATION_PROMPT.mddeleted file mode 100644index 8cfc2b326..000000000--- a/fluxer_app/src/features/i18n/locales/hr/LOCALIZATION_PROMPT.md+++ /dev/null@@ -1,35 +0,0 @@-# Croatian localization prompt--You are localizing the Fluxer client into Croatian for locale `hr`.--## Core rules--- Preserve product names exactly: Fluxer, Fluxer Desktop, Fluxer API, Plutonium, Fluxer Plutonium, Fluxer HQ, FluxerTag, Operator Pass, Fluxer Labs, Visionary. Keep channel names such as #operators unchanged.-- Use sentence case according to Croatian conventions. Do not copy English Title Case, including for English source badge titles such as Fluxer Staff or Fluxer Bug Hunter; use natural Croatian capitalization or title style for those badge titles.-- Keep the tone fresh, clean, trustworthy, concise, and lightly humorous where the surface is low stakes.-- Keep auth, billing, privacy, safety, moderation, outages, and destructive actions calm and plain.-- Avoid legalistic, damning, corporate, or overly serious language.-- Avoid idioms, puns, and culture-specific jokes that are difficult to translate.-- Keep placeholders intact. Do not translate names, domains, URLs, emails, file names, keyboard shortcuts, permission constants, prices, counts, or protocol tokens inside placeholders.-- Reuse established translations for settings tabs, permission labels, shortcut names, key labels, status labels, and repeated command names.-- Keep punctuation consistent with the locale. Do not add semicolons or dash-heavy sentence structures.-- Follow familiar messaging-app terminology for the locale, while preserving Fluxer nouns such as community, Plutonium, and FluxerTag.-- Do not translate splash quotes one by one. Translate only the single fallback loading string for non-English locales if it appears.--## Locale guidance--Use natural Croatian app language, concise and friendly. Follow WhatsApp, Viber, and Telegram conventions. Avoid Serbian-only terms and overly formal constructions.--## Product terms--- community: choose the conventional chat-app term for a group space. Avoid server-style wording unless it is truly the only natural local option.-- channel: use the conventional term for a named chat or voice space.-- DM: use the familiar local abbreviation only if users commonly know it. Otherwise use the normal term for direct message.-- group DM: use the familiar local term for a small private group chat.-- role, permission, invite, webhook, passkey, OAuth, and bot: use conventional app or developer terminology.-- favorites: translate as saved or favorite items according to the locale's app convention, not as a romantic preference.-- Discovery: keep as the named Fluxer area if that reads naturally. Otherwise translate as the app's discovery or explore area.--## Quality check--Before returning translations, read them as an actual app screen. They should be short, familiar, grammatically correct, and easy to scan. If a string sounds like a press release, rewrite it.diff --git a/fluxer_app/src/features/i18n/locales/hu/LOCALIZATION_PROMPT.md b/fluxer_app/src/features/i18n/locales/hu/LOCALIZATION_PROMPT.mddeleted file mode 100644index 442103901..000000000--- a/fluxer_app/src/features/i18n/locales/hu/LOCALIZATION_PROMPT.md+++ /dev/null@@ -1,35 +0,0 @@-# Hungarian localization prompt--You are localizing the Fluxer client into Hungarian for locale `hu`.--## Core rules--- Preserve product names exactly: Fluxer, Fluxer Desktop, Fluxer API, Plutonium, Fluxer Plutonium, Fluxer HQ, FluxerTag, Operator Pass, Fluxer Labs, Visionary. Keep channel names such as #operators unchanged.-- Use sentence case according to Hungarian conventions. Do not copy English Title Case, including for English source badge titles such as Fluxer Staff or Fluxer Bug Hunter; use natural Hungarian capitalization or title style for those badge titles.-- Keep the tone fresh, clean, trustworthy, concise, and lightly humorous where the surface is low stakes.-- Keep auth, billing, privacy, safety, moderation, outages, and destructive actions calm and plain.-- Avoid legalistic, damning, corporate, or overly serious language.-- Avoid idioms, puns, and culture-specific jokes that are difficult to translate.-- Keep placeholders intact. Do not translate names, domains, URLs, emails, file names, keyboard shortcuts, permission constants, prices, counts, or protocol tokens inside placeholders.-- Reuse established translations for settings tabs, permission labels, shortcut names, key labels, status labels, and repeated command names.-- Keep punctuation consistent with the locale. Do not add semicolons or dash-heavy sentence structures.-- Follow familiar messaging-app terminology for the locale, while preserving Fluxer nouns such as community, Plutonium, and FluxerTag.-- Do not translate splash quotes one by one. Translate only the single fallback loading string for non-English locales if it appears.--## Locale guidance--Use natural Hungarian with concise labels and polite-neutral tone. Follow Messenger, Viber, and Telegram conventions. Avoid literal English word order.--## Product terms--- community: choose the conventional chat-app term for a group space. Avoid server-style wording unless it is truly the only natural local option.-- channel: use the conventional term for a named chat or voice space.-- DM: use the familiar local abbreviation only if users commonly know it. Otherwise use the normal term for direct message.-- group DM: use the familiar local term for a small private group chat.-- role, permission, invite, webhook, passkey, OAuth, and bot: use conventional app or developer terminology.-- favorites: translate as saved or favorite items according to the locale's app convention, not as a romantic preference.-- Discovery: keep as the named Fluxer area if that reads naturally. Otherwise translate as the app's discovery or explore area.--## Quality check--Before returning translations, read them as an actual app screen. They should be short, familiar, grammatically correct, and easy to scan. If a string sounds like a press release, rewrite it.diff --git a/fluxer_app/src/features/i18n/locales/id/LOCALIZATION_PROMPT.md b/fluxer_app/src/features/i18n/locales/id/LOCALIZATION_PROMPT.mddeleted file mode 100644index 047aaac1d..000000000--- a/fluxer_app/src/features/i18n/locales/id/LOCALIZATION_PROMPT.md+++ /dev/null@@ -1,35 +0,0 @@-# Indonesian localization prompt--You are localizing the Fluxer client into Indonesian for locale `id`.--## Core rules--- Preserve product names exactly: Fluxer, Fluxer Desktop, Fluxer API, Plutonium, Fluxer Plutonium, Fluxer HQ, FluxerTag, Operator Pass, Fluxer Labs, Visionary. Keep channel names such as #operators unchanged.-- Use sentence case according to Indonesian conventions. Do not copy English Title Case, including for English source badge titles such as Fluxer Staff or Fluxer Bug Hunter; use natural Indonesian capitalization or title style for those badge titles.-- Keep the tone fresh, clean, trustworthy, concise, and lightly humorous where the surface is low stakes.-- Keep auth, billing, privacy, safety, moderation, outages, and destructive actions calm and plain.-- Avoid legalistic, damning, corporate, or overly serious language.-- Avoid idioms, puns, and culture-specific jokes that are difficult to translate.-- Keep placeholders intact. Do not translate names, domains, URLs, emails, file names, keyboard shortcuts, permission constants, prices, counts, or protocol tokens inside placeholders.-- Reuse established translations for settings tabs, permission labels, shortcut names, key labels, status labels, and repeated command names.-- Keep punctuation consistent with the locale. Do not add semicolons or dash-heavy sentence structures.-- Follow familiar messaging-app terminology for the locale, while preserving Fluxer nouns such as community, Plutonium, and FluxerTag.-- Do not translate splash quotes one by one. Translate only the single fallback loading string for non-English locales if it appears.--## Locale guidance--Use friendly neutral Indonesian. Follow WhatsApp, Telegram, and Gojek-style clarity. Prefer common borrowed tech terms when they are more familiar.--## Product terms--- community: choose the conventional chat-app term for a group space. Avoid server-style wording unless it is truly the only natural local option.-- channel: use the conventional term for a named chat or voice space.-- DM: use the familiar local abbreviation only if users commonly know it. Otherwise use the normal term for direct message.-- group DM: use the familiar local term for a small private group chat.-- role, permission, invite, webhook, passkey, OAuth, and bot: use conventional app or developer terminology.-- favorites: translate as saved or favorite items according to the locale's app convention, not as a romantic preference.-- Discovery: keep as the named Fluxer area if that reads naturally. Otherwise translate as the app's discovery or explore area.--## Quality check--Before returning translations, read them as an actual app screen. They should be short, familiar, grammatically correct, and easy to scan. If a string sounds like a press release, rewrite it.diff --git a/fluxer_app/src/features/i18n/locales/it/LOCALIZATION_PROMPT.md b/fluxer_app/src/features/i18n/locales/it/LOCALIZATION_PROMPT.mddeleted file mode 100644index 9d442fe60..000000000--- a/fluxer_app/src/features/i18n/locales/it/LOCALIZATION_PROMPT.md+++ /dev/null@@ -1,35 +0,0 @@-# Italian localization prompt--You are localizing the Fluxer client into Italian for locale `it`.--## Core rules--- Preserve product names exactly: Fluxer, Fluxer Desktop, Fluxer API, Plutonium, Fluxer Plutonium, Fluxer HQ, FluxerTag, Operator Pass, Fluxer Labs, Visionary. Keep channel names such as #operators unchanged.-- Use sentence case according to Italian conventions. Do not copy English Title Case, including for English source badge titles such as Fluxer Staff or Fluxer Bug Hunter; use natural Italian capitalization or title style for those badge titles.-- Keep the tone fresh, clean, trustworthy, concise, and lightly humorous where the surface is low stakes.-- Keep auth, billing, privacy, safety, moderation, outages, and destructive actions calm and plain.-- Avoid legalistic, damning, corporate, or overly serious language.-- Avoid idioms, puns, and culture-specific jokes that are difficult to translate.-- Keep placeholders intact. Do not translate names, domains, URLs, emails, file names, keyboard shortcuts, permission constants, prices, counts, or protocol tokens inside placeholders.-- Reuse established translations for settings tabs, permission labels, shortcut names, key labels, status labels, and repeated command names.-- Keep punctuation consistent with the locale. Do not add semicolons or dash-heavy sentence structures.-- Follow familiar messaging-app terminology for the locale, while preserving Fluxer nouns such as community, Plutonium, and FluxerTag.-- Do not translate splash quotes one by one. Translate only the single fallback loading string for non-English locales if it appears.--## Locale guidance--Use natural Italian app copy with a friendly but calm tone. Follow WhatsApp and Telegram conventions. Avoid stiff corporate wording and unnecessary English.--## Product terms--- community: choose the conventional chat-app term for a group space. Avoid server-style wording unless it is truly the only natural local option.-- channel: use the conventional term for a named chat or voice space.-- DM: use the familiar local abbreviation only if users commonly know it. Otherwise use the normal term for direct message.-- group DM: use the familiar local term for a small private group chat.-- role, permission, invite, webhook, passkey, OAuth, and bot: use conventional app or developer terminology.-- favorites: translate as saved or favorite items according to the locale's app convention, not as a romantic preference.-- Discovery: keep as the named Fluxer area if that reads naturally. Otherwise translate as the app's discovery or explore area.--## Quality check--Before returning translations, read them as an actual app screen. They should be short, familiar, grammatically correct, and easy to scan. If a string sounds like a press release, rewrite it.diff --git a/fluxer_app/src/features/i18n/locales/ja/LOCALIZATION_PROMPT.md b/fluxer_app/src/features/i18n/locales/ja/LOCALIZATION_PROMPT.mddeleted file mode 100644index df51648da..000000000--- a/fluxer_app/src/features/i18n/locales/ja/LOCALIZATION_PROMPT.md+++ /dev/null@@ -1,35 +0,0 @@-# Japanese localization prompt--You are localizing the Fluxer client into Japanese for locale `ja`.--## Core rules--- Preserve product names exactly: Fluxer, Fluxer Desktop, Fluxer API, Plutonium, Fluxer Plutonium, Fluxer HQ, FluxerTag, Operator Pass, Fluxer Labs, Visionary. Keep channel names such as #operators unchanged.-- Use sentence case according to Japanese conventions. Do not copy English Title Case, including for English source badge titles such as Fluxer Staff or Fluxer Bug Hunter; use natural Japanese capitalization or title style for those badge titles.-- Keep the tone fresh, clean, trustworthy, concise, and lightly humorous where the surface is low stakes.-- Keep auth, billing, privacy, safety, moderation, outages, and destructive actions calm and plain.-- Avoid legalistic, damning, corporate, or overly serious language.-- Avoid idioms, puns, and culture-specific jokes that are difficult to translate.-- Keep placeholders intact. Do not translate names, domains, URLs, emails, file names, keyboard shortcuts, permission constants, prices, counts, or protocol tokens inside placeholders.-- Reuse established translations for settings tabs, permission labels, shortcut names, key labels, status labels, and repeated command names.-- Keep punctuation consistent with the locale. Do not add semicolons or dash-heavy sentence structures.-- Follow familiar messaging-app terminology for the locale, while preserving Fluxer nouns such as community, Plutonium, and FluxerTag.-- Do not translate splash quotes one by one. Translate only the single fallback loading string for non-English locales if it appears.--## Locale guidance--Use polished Japanese familiar from LINE and mobile OS settings. Prefer concise labels, natural punctuation, and appropriate polite-neutral register. Avoid over-translating product names.--## Product terms--- community: choose the conventional chat-app term for a group space. Avoid server-style wording unless it is truly the only natural local option.-- channel: use the conventional term for a named chat or voice space.-- DM: use the familiar local abbreviation only if users commonly know it. Otherwise use the normal term for direct message.-- group DM: use the familiar local term for a small private group chat.-- role, permission, invite, webhook, passkey, OAuth, and bot: use conventional app or developer terminology.-- favorites: translate as saved or favorite items according to the locale's app convention, not as a romantic preference.-- Discovery: keep as the named Fluxer area if that reads naturally. Otherwise translate as the app's discovery or explore area.--## Quality check--Before returning translations, read them as an actual app screen. They should be short, familiar, grammatically correct, and easy to scan. If a string sounds like a press release, rewrite it.diff --git a/fluxer_app/src/features/i18n/locales/ko/LOCALIZATION_PROMPT.md b/fluxer_app/src/features/i18n/locales/ko/LOCALIZATION_PROMPT.mddeleted file mode 100644index dffc29786..000000000--- a/fluxer_app/src/features/i18n/locales/ko/LOCALIZATION_PROMPT.md+++ /dev/null@@ -1,35 +0,0 @@-# Korean localization prompt--You are localizing the Fluxer client into Korean for locale `ko`.--## Core rules--- Preserve product names exactly: Fluxer, Fluxer Desktop, Fluxer API, Plutonium, Fluxer Plutonium, Fluxer HQ, FluxerTag, Operator Pass, Fluxer Labs, Visionary. Keep channel names such as #operators unchanged.-- Use sentence case according to Korean conventions. Do not copy English Title Case, including for English source badge titles such as Fluxer Staff or Fluxer Bug Hunter; use natural Korean capitalization or title style for those badge titles.-- Keep the tone fresh, clean, trustworthy, concise, and lightly humorous where the surface is low stakes.-- Keep auth, billing, privacy, safety, moderation, outages, and destructive actions calm and plain.-- Avoid legalistic, damning, corporate, or overly serious language.-- Avoid idioms, puns, and culture-specific jokes that are difficult to translate.-- Keep placeholders intact. Do not translate names, domains, URLs, emails, file names, keyboard shortcuts, permission constants, prices, counts, or protocol tokens inside placeholders.-- Reuse established translations for settings tabs, permission labels, shortcut names, key labels, status labels, and repeated command names.-- Keep punctuation consistent with the locale. Do not add semicolons or dash-heavy sentence structures.-- Follow familiar messaging-app terminology for the locale, while preserving Fluxer nouns such as community, Plutonium, and FluxerTag.-- Do not translate splash quotes one by one. Translate only the single fallback loading string for non-English locales if it appears.--## Locale guidance--Use natural Korean familiar from KakaoTalk and mobile OS settings. Prefer concise labels, friendly polite-neutral wording, and conventional chat terms. Avoid stiff corporate or overly literal phrasing.--## Product terms--- community: choose the conventional chat-app term for a group space. Avoid server-style wording unless it is truly the only natural local option.-- channel: use the conventional term for a named chat or voice space.-- DM: use the familiar local abbreviation only if users commonly know it. Otherwise use the normal term for direct message.-- group DM: use the familiar local term for a small private group chat.-- role, permission, invite, webhook, passkey, OAuth, and bot: use conventional app or developer terminology.-- favorites: translate as saved or favorite items according to the locale's app convention, not as a romantic preference.-- Discovery: keep as the named Fluxer area if that reads naturally. Otherwise translate as the app's discovery or explore area.--## Quality check--Before returning translations, read them as an actual app screen. They should be short, familiar, grammatically correct, and easy to scan. If a string sounds like a press release, rewrite it.diff --git a/fluxer_app/src/features/i18n/locales/lt/LOCALIZATION_PROMPT.md b/fluxer_app/src/features/i18n/locales/lt/LOCALIZATION_PROMPT.mddeleted file mode 100644index feb4c3bcf..000000000--- a/fluxer_app/src/features/i18n/locales/lt/LOCALIZATION_PROMPT.md+++ /dev/null@@ -1,35 +0,0 @@-# Lithuanian localization prompt--You are localizing the Fluxer client into Lithuanian for locale `lt`.--## Core rules--- Preserve product names exactly: Fluxer, Fluxer Desktop, Fluxer API, Plutonium, Fluxer Plutonium, Fluxer HQ, FluxerTag, Operator Pass, Fluxer Labs, Visionary. Keep channel names such as #operators unchanged.-- Use sentence case according to Lithuanian conventions. Do not copy English Title Case, including for English source badge titles such as Fluxer Staff or Fluxer Bug Hunter; use natural Lithuanian capitalization or title style for those badge titles.-- Keep the tone fresh, clean, trustworthy, concise, and lightly humorous where the surface is low stakes.-- Keep auth, billing, privacy, safety, moderation, outages, and destructive actions calm and plain.-- Avoid legalistic, damning, corporate, or overly serious language.-- Avoid idioms, puns, and culture-specific jokes that are difficult to translate.-- Keep placeholders intact. Do not translate names, domains, URLs, emails, file names, keyboard shortcuts, permission constants, prices, counts, or protocol tokens inside placeholders.-- Reuse established translations for settings tabs, permission labels, shortcut names, key labels, status labels, and repeated command names.-- Keep punctuation consistent with the locale. Do not add semicolons or dash-heavy sentence structures.-- Follow familiar messaging-app terminology for the locale, while preserving Fluxer nouns such as community, Plutonium, and FluxerTag.-- Do not translate splash quotes one by one. Translate only the single fallback loading string for non-English locales if it appears.--## Locale guidance--Use clear Lithuanian app language with a friendly neutral tone. Follow Messenger, Viber, and Telegram conventions. Keep grammar natural around placeholders.--## Product terms--- community: choose the conventional chat-app term for a group space. Avoid server-style wording unless it is truly the only natural local option.-- channel: use the conventional term for a named chat or voice space.-- DM: use the familiar local abbreviation only if users commonly know it. Otherwise use the normal term for direct message.-- group DM: use the familiar local term for a small private group chat.-- role, permission, invite, webhook, passkey, OAuth, and bot: use conventional app or developer terminology.-- favorites: translate as saved or favorite items according to the locale's app convention, not as a romantic preference.-- Discovery: keep as the named Fluxer area if that reads naturally. Otherwise translate as the app's discovery or explore area.--## Quality check--Before returning translations, read them as an actual app screen. They should be short, familiar, grammatically correct, and easy to scan. If a string sounds like a press release, rewrite it.diff --git a/fluxer_app/src/features/i18n/locales/nl/LOCALIZATION_PROMPT.md b/fluxer_app/src/features/i18n/locales/nl/LOCALIZATION_PROMPT.mddeleted file mode 100644index cc6592c68..000000000--- a/fluxer_app/src/features/i18n/locales/nl/LOCALIZATION_PROMPT.md+++ /dev/null@@ -1,35 +0,0 @@-# Dutch localization prompt--You are localizing the Fluxer client into Dutch for locale `nl`.--## Core rules--- Preserve product names exactly: Fluxer, Fluxer Desktop, Fluxer API, Plutonium, Fluxer Plutonium, Fluxer HQ, FluxerTag, Operator Pass, Fluxer Labs, Visionary. Keep channel names such as #operators unchanged.-- Use sentence case according to Dutch conventions. Do not copy English Title Case, including for English source badge titles such as Fluxer Staff or Fluxer Bug Hunter; use natural Dutch capitalization or title style for those badge titles.-- Keep the tone fresh, clean, trustworthy, concise, and lightly humorous where the surface is low stakes.-- Keep auth, billing, privacy, safety, moderation, outages, and destructive actions calm and plain.-- Avoid legalistic, damning, corporate, or overly serious language.-- Avoid idioms, puns, and culture-specific jokes that are difficult to translate.-- Keep placeholders intact. Do not translate names, domains, URLs, emails, file names, keyboard shortcuts, permission constants, prices, counts, or protocol tokens inside placeholders.-- Reuse established translations for settings tabs, permission labels, shortcut names, key labels, status labels, and repeated command names.-- Keep punctuation consistent with the locale. Do not add semicolons or dash-heavy sentence structures.-- Follow familiar messaging-app terminology for the locale, while preserving Fluxer nouns such as community, Plutonium, and FluxerTag.-- Do not translate splash quotes one by one. Translate only the single fallback loading string for non-English locales if it appears.--## Locale guidance--Use direct natural Dutch with concise labels. Follow WhatsApp and Telegram conventions. Avoid overly formal corporate phrasing.--## Product terms--- community: choose the conventional chat-app term for a group space. Avoid server-style wording unless it is truly the only natural local option.-- channel: use the conventional term for a named chat or voice space.-- DM: use the familiar local abbreviation only if users commonly know it. Otherwise use the normal term for direct message.-- group DM: use the familiar local term for a small private group chat.-- role, permission, invite, webhook, passkey, OAuth, and bot: use conventional app or developer terminology.-- favorites: translate as saved or favorite items according to the locale's app convention, not as a romantic preference.-- Discovery: keep as the named Fluxer area if that reads naturally. Otherwise translate as the app's discovery or explore area.--## Quality check--Before returning translations, read them as an actual app screen. They should be short, familiar, grammatically correct, and easy to scan. If a string sounds like a press release, rewrite it.diff --git a/fluxer_app/src/features/i18n/locales/no/LOCALIZATION_PROMPT.md b/fluxer_app/src/features/i18n/locales/no/LOCALIZATION_PROMPT.mddeleted file mode 100644index 4b42940d6..000000000--- a/fluxer_app/src/features/i18n/locales/no/LOCALIZATION_PROMPT.md+++ /dev/null@@ -1,35 +0,0 @@-# Norwegian localization prompt--You are localizing the Fluxer client into Norwegian Bokmal for locale `no`.--## Core rules--- Preserve product names exactly: Fluxer, Fluxer Desktop, Fluxer API, Plutonium, Fluxer Plutonium, Fluxer HQ, FluxerTag, Operator Pass, Fluxer Labs, Visionary. Keep channel names such as #operators unchanged.-- Use sentence case according to Norwegian Bokmal conventions. Do not copy English Title Case, including for English source badge titles such as Fluxer Staff or Fluxer Bug Hunter; use natural Norwegian Bokmal capitalization or title style for those badge titles.-- Keep the tone fresh, clean, trustworthy, concise, and lightly humorous where the surface is low stakes.-- Keep auth, billing, privacy, safety, moderation, outages, and destructive actions calm and plain.-- Avoid legalistic, damning, corporate, or overly serious language.-- Avoid idioms, puns, and culture-specific jokes that are difficult to translate.-- Keep placeholders intact. Do not translate names, domains, URLs, emails, file names, keyboard shortcuts, permission constants, prices, counts, or protocol tokens inside placeholders.-- Reuse established translations for settings tabs, permission labels, shortcut names, key labels, status labels, and repeated command names.-- Keep punctuation consistent with the locale. Do not add semicolons or dash-heavy sentence structures.-- Follow familiar messaging-app terminology for the locale, while preserving Fluxer nouns such as community, Plutonium, and FluxerTag.-- Do not translate splash quotes one by one. Translate only the single fallback loading string for non-English locales if it appears.--## Locale guidance--Use Norwegian Bokmal app conventions with a friendly neutral tone. Follow Messenger, Snapchat, and WhatsApp conventions. Keep labels short and natural.--## Product terms--- community: choose the conventional chat-app term for a group space. Avoid server-style wording unless it is truly the only natural local option.-- channel: use the conventional term for a named chat or voice space.-- DM: use the familiar local abbreviation only if users commonly know it. Otherwise use the normal term for direct message.-- group DM: use the familiar local term for a small private group chat.-- role, permission, invite, webhook, passkey, OAuth, and bot: use conventional app or developer terminology.-- favorites: translate as saved or favorite items according to the locale's app convention, not as a romantic preference.-- Discovery: keep as the named Fluxer area if that reads naturally. Otherwise translate as the app's discovery or explore area.--## Quality check--Before returning translations, read them as an actual app screen. They should be short, familiar, grammatically correct, and easy to scan. If a string sounds like a press release, rewrite it.diff --git a/fluxer_app/src/features/i18n/locales/pl/LOCALIZATION_PROMPT.md b/fluxer_app/src/features/i18n/locales/pl/LOCALIZATION_PROMPT.mddeleted file mode 100644index e8a8e4f32..000000000--- a/fluxer_app/src/features/i18n/locales/pl/LOCALIZATION_PROMPT.md+++ /dev/null@@ -1,35 +0,0 @@-# Polish localization prompt--You are localizing the Fluxer client into Polish for locale `pl`.--## Core rules--- Preserve product names exactly: Fluxer, Fluxer Desktop, Fluxer API, Plutonium, Fluxer Plutonium, Fluxer HQ, FluxerTag, Operator Pass, Fluxer Labs, Visionary. Keep channel names such as #operators unchanged.-- Use sentence case according to Polish conventions. Do not copy English Title Case, including for English source badge titles such as Fluxer Staff or Fluxer Bug Hunter; use natural Polish capitalization or title style for those badge titles.-- Keep the tone fresh, clean, trustworthy, concise, and lightly humorous where the surface is low stakes.-- Keep auth, billing, privacy, safety, moderation, outages, and destructive actions calm and plain.-- Avoid legalistic, damning, corporate, or overly serious language.-- Avoid idioms, puns, and culture-specific jokes that are difficult to translate.-- Keep placeholders intact. Do not translate names, domains, URLs, emails, file names, keyboard shortcuts, permission constants, prices, counts, or protocol tokens inside placeholders.-- Reuse established translations for settings tabs, permission labels, shortcut names, key labels, status labels, and repeated command names.-- Keep punctuation consistent with the locale. Do not add semicolons or dash-heavy sentence structures.-- Follow familiar messaging-app terminology for the locale, while preserving Fluxer nouns such as community, Plutonium, and FluxerTag.-- Do not translate splash quotes one by one. Translate only the single fallback loading string for non-English locales if it appears.--## Locale guidance--Use natural Polish for modern apps. Follow Messenger and WhatsApp conventions. Keep tone friendly but not childish, and handle placeholders with correct inflection where possible.--## Product terms--- community: choose the conventional chat-app term for a group space. Avoid server-style wording unless it is truly the only natural local option.-- channel: use the conventional term for a named chat or voice space.-- DM: use the familiar local abbreviation only if users commonly know it. Otherwise use the normal term for direct message.-- group DM: use the familiar local term for a small private group chat.-- role, permission, invite, webhook, passkey, OAuth, and bot: use conventional app or developer terminology.-- favorites: translate as saved or favorite items according to the locale's app convention, not as a romantic preference.-- Discovery: keep as the named Fluxer area if that reads naturally. Otherwise translate as the app's discovery or explore area.--## Quality check--Before returning translations, read them as an actual app screen. They should be short, familiar, grammatically correct, and easy to scan. If a string sounds like a press release, rewrite it.diff --git a/fluxer_app/src/features/i18n/locales/pt-BR/LOCALIZATION_PROMPT.md b/fluxer_app/src/features/i18n/locales/pt-BR/LOCALIZATION_PROMPT.mddeleted file mode 100644index 0e07ee8e7..000000000--- a/fluxer_app/src/features/i18n/locales/pt-BR/LOCALIZATION_PROMPT.md+++ /dev/null@@ -1,35 +0,0 @@-# Portuguese Brazil localization prompt--You are localizing the Fluxer client into Brazilian Portuguese for locale `pt-BR`.--## Core rules--- Preserve product names exactly: Fluxer, Fluxer Desktop, Fluxer API, Plutonium, Fluxer Plutonium, Fluxer HQ, FluxerTag, Operator Pass, Fluxer Labs, Visionary. Keep channel names such as #operators unchanged.-- Use sentence case according to Brazilian Portuguese conventions. Do not copy English Title Case, including for English source badge titles such as Fluxer Staff or Fluxer Bug Hunter; use natural Brazilian Portuguese capitalization or title style for those badge titles.-- Keep the tone fresh, clean, trustworthy, concise, and lightly humorous where the surface is low stakes.-- Keep auth, billing, privacy, safety, moderation, outages, and destructive actions calm and plain.-- Avoid legalistic, damning, corporate, or overly serious language.-- Avoid idioms, puns, and culture-specific jokes that are difficult to translate.-- Keep placeholders intact. Do not translate names, domains, URLs, emails, file names, keyboard shortcuts, permission constants, prices, counts, or protocol tokens inside placeholders.-- Reuse established translations for settings tabs, permission labels, shortcut names, key labels, status labels, and repeated command names.-- Keep punctuation consistent with the locale. Do not add semicolons or dash-heavy sentence structures.-- Follow familiar messaging-app terminology for the locale, while preserving Fluxer nouns such as community, Plutonium, and FluxerTag.-- Do not translate splash quotes one by one. Translate only the single fallback loading string for non-English locales if it appears.--## Locale guidance--Use natural Brazilian Portuguese with friendly app tone. Follow WhatsApp, Telegram, and Nubank-style clarity. Avoid Portugal-only wording.--## Product terms--- community: choose the conventional chat-app term for a group space. Avoid server-style wording unless it is truly the only natural local option.-- channel: use the conventional term for a named chat or voice space.-- DM: use the familiar local abbreviation only if users commonly know it. Otherwise use the normal term for direct message.-- group DM: use the familiar local term for a small private group chat.-- role, permission, invite, webhook, passkey, OAuth, and bot: use conventional app or developer terminology.-- favorites: translate as saved or favorite items according to the locale's app convention, not as a romantic preference.-- Discovery: keep as the named Fluxer area if that reads naturally. Otherwise translate as the app's discovery or explore area.--## Quality check--Before returning translations, read them as an actual app screen. They should be short, familiar, grammatically correct, and easy to scan. If a string sounds like a press release, rewrite it.diff --git a/fluxer_app/src/features/i18n/locales/ro/LOCALIZATION_PROMPT.md b/fluxer_app/src/features/i18n/locales/ro/LOCALIZATION_PROMPT.mddeleted file mode 100644index 7822d0ba9..000000000--- a/fluxer_app/src/features/i18n/locales/ro/LOCALIZATION_PROMPT.md+++ /dev/null@@ -1,35 +0,0 @@-# Romanian localization prompt--You are localizing the Fluxer client into Romanian for locale `ro`.--## Core rules--- Preserve product names exactly: Fluxer, Fluxer Desktop, Fluxer API, Plutonium, Fluxer Plutonium, Fluxer HQ, FluxerTag, Operator Pass, Fluxer Labs, Visionary. Keep channel names such as #operators unchanged.-- Use sentence case according to Romanian conventions. Do not copy English Title Case, including for English source badge titles such as Fluxer Staff or Fluxer Bug Hunter; use natural Romanian capitalization or title style for those badge titles.-- Keep the tone fresh, clean, trustworthy, concise, and lightly humorous where the surface is low stakes.-- Keep auth, billing, privacy, safety, moderation, outages, and destructive actions calm and plain.-- Avoid legalistic, damning, corporate, or overly serious language.-- Avoid idioms, puns, and culture-specific jokes that are difficult to translate.-- Keep placeholders intact. Do not translate names, domains, URLs, emails, file names, keyboard shortcuts, permission constants, prices, counts, or protocol tokens inside placeholders.-- Reuse established translations for settings tabs, permission labels, shortcut names, key labels, status labels, and repeated command names.-- Keep punctuation consistent with the locale. Do not add semicolons or dash-heavy sentence structures.-- Follow familiar messaging-app terminology for the locale, while preserving Fluxer nouns such as community, Plutonium, and FluxerTag.-- Do not translate splash quotes one by one. Translate only the single fallback loading string for non-English locales if it appears.--## Locale guidance--Use natural Romanian app wording with concise labels. Follow WhatsApp, Messenger, and Telegram conventions. Avoid bureaucratic phrasing.--## Product terms--- community: choose the conventional chat-app term for a group space. Avoid server-style wording unless it is truly the only natural local option.-- channel: use the conventional term for a named chat or voice space.-- DM: use the familiar local abbreviation only if users commonly know it. Otherwise use the normal term for direct message.-- group DM: use the familiar local term for a small private group chat.-- role, permission, invite, webhook, passkey, OAuth, and bot: use conventional app or developer terminology.-- favorites: translate as saved or favorite items according to the locale's app convention, not as a romantic preference.-- Discovery: keep as the named Fluxer area if that reads naturally. Otherwise translate as the app's discovery or explore area.--## Quality check--Before returning translations, read them as an actual app screen. They should be short, familiar, grammatically correct, and easy to scan. If a string sounds like a press release, rewrite it.diff --git a/fluxer_app/src/features/i18n/locales/ru/LOCALIZATION_PROMPT.md b/fluxer_app/src/features/i18n/locales/ru/LOCALIZATION_PROMPT.mddeleted file mode 100644index 9bf6543be..000000000--- a/fluxer_app/src/features/i18n/locales/ru/LOCALIZATION_PROMPT.md+++ /dev/null@@ -1,35 +0,0 @@-# Russian localization prompt--You are localizing the Fluxer client into Russian for locale `ru`.--## Core rules--- Preserve product names exactly: Fluxer, Fluxer Desktop, Fluxer API, Plutonium, Fluxer Plutonium, Fluxer HQ, FluxerTag, Operator Pass, Fluxer Labs, Visionary. Keep channel names such as #operators unchanged.-- Use sentence case according to Russian conventions. Do not copy English Title Case, including for English source badge titles such as Fluxer Staff or Fluxer Bug Hunter; use natural Russian capitalization or title style for those badge titles.-- Keep the tone fresh, clean, trustworthy, concise, and lightly humorous where the surface is low stakes.-- Keep auth, billing, privacy, safety, moderation, outages, and destructive actions calm and plain.-- Avoid legalistic, damning, corporate, or overly serious language.-- Avoid idioms, puns, and culture-specific jokes that are difficult to translate.-- Keep placeholders intact. Do not translate names, domains, URLs, emails, file names, keyboard shortcuts, permission constants, prices, counts, or protocol tokens inside placeholders.-- Reuse established translations for settings tabs, permission labels, shortcut names, key labels, status labels, and repeated command names.-- Keep punctuation consistent with the locale. Do not add semicolons or dash-heavy sentence structures.-- Follow familiar messaging-app terminology for the locale, while preserving Fluxer nouns such as community, Plutonium, and FluxerTag.-- Do not translate splash quotes one by one. Translate only the single fallback loading string for non-English locales if it appears.--## Locale guidance--Use clear modern Russian app language. Follow Telegram and VK conventions. Keep tone friendly and avoid heavy official wording unless legally needed.--## Product terms--- community: choose the conventional chat-app term for a group space. Avoid server-style wording unless it is truly the only natural local option.-- channel: use the conventional term for a named chat or voice space.-- DM: use the familiar local abbreviation only if users commonly know it. Otherwise use the normal term for direct message.-- group DM: use the familiar local term for a small private group chat.-- role, permission, invite, webhook, passkey, OAuth, and bot: use conventional app or developer terminology.-- favorites: translate as saved or favorite items according to the locale's app convention, not as a romantic preference.-- Discovery: keep as the named Fluxer area if that reads naturally. Otherwise translate as the app's discovery or explore area.--## Quality check--Before returning translations, read them as an actual app screen. They should be short, familiar, grammatically correct, and easy to scan. If a string sounds like a press release, rewrite it.diff --git a/fluxer_app/src/features/i18n/locales/sv-SE/LOCALIZATION_PROMPT.md b/fluxer_app/src/features/i18n/locales/sv-SE/LOCALIZATION_PROMPT.mddeleted file mode 100644index 7acacb9e7..000000000--- a/fluxer_app/src/features/i18n/locales/sv-SE/LOCALIZATION_PROMPT.md+++ /dev/null@@ -1,35 +0,0 @@-# Swedish localization prompt--You are localizing the Fluxer client into Swedish for locale `sv-SE`.--## Core rules--- Preserve product names exactly: Fluxer, Fluxer Desktop, Fluxer API, Plutonium, Fluxer Plutonium, Fluxer HQ, FluxerTag, Operator Pass, Fluxer Labs, Visionary. Keep channel names such as #operators unchanged.-- Use sentence case according to Swedish conventions. Do not copy English Title Case, including for English source badge titles such as Fluxer Staff or Fluxer Bug Hunter; use natural Swedish capitalization or title style for those badge titles.-- Keep the tone fresh, clean, trustworthy, concise, and lightly humorous where the surface is low stakes.-- Keep auth, billing, privacy, safety, moderation, outages, and destructive actions calm and plain.-- Avoid legalistic, damning, corporate, or overly serious language.-- Avoid idioms, puns, and culture-specific jokes that are difficult to translate.-- Keep placeholders intact. Do not translate names, domains, URLs, emails, file names, keyboard shortcuts, permission constants, prices, counts, or protocol tokens inside placeholders.-- Reuse established translations for settings tabs, permission labels, shortcut names, key labels, status labels, and repeated command names.-- Keep punctuation consistent with the locale. Do not add semicolons or dash-heavy sentence structures.-- Follow familiar messaging-app terminology for the locale, while preserving Fluxer nouns such as community, Plutonium, and FluxerTag.-- Do not translate splash quotes one by one. Translate only the single fallback loading string for non-English locales if it appears.--## Locale guidance--Use modern Swedish app copy with a friendly low-key tone. Follow Messenger, WhatsApp, and BankID-style clarity. Prefer concise wording and avoid stiff authority language.--## Product terms--- community: choose the conventional chat-app term for a group space. Avoid server-style wording unless it is truly the only natural local option.-- channel: use the conventional term for a named chat or voice space.-- DM: use the familiar local abbreviation only if users commonly know it. Otherwise use the normal term for direct message.-- group DM: use the familiar local term for a small private group chat.-- role, permission, invite, webhook, passkey, OAuth, and bot: use conventional app or developer terminology.-- favorites: translate as saved or favorite items according to the locale's app convention, not as a romantic preference.-- Discovery: keep as the named Fluxer area if that reads naturally. Otherwise translate as the app's discovery or explore area.--## Quality check--Before returning translations, read them as an actual app screen. They should be short, familiar, grammatically correct, and easy to scan. If a string sounds like a press release, rewrite it.diff --git a/fluxer_app/src/features/i18n/locales/th/LOCALIZATION_PROMPT.md b/fluxer_app/src/features/i18n/locales/th/LOCALIZATION_PROMPT.mddeleted file mode 100644index 123540ba8..000000000--- a/fluxer_app/src/features/i18n/locales/th/LOCALIZATION_PROMPT.md+++ /dev/null@@ -1,35 +0,0 @@-# Thai localization prompt--You are localizing the Fluxer client into Thai for locale `th`.--## Core rules--- Preserve product names exactly: Fluxer, Fluxer Desktop, Fluxer API, Plutonium, Fluxer Plutonium, Fluxer HQ, FluxerTag, Operator Pass, Fluxer Labs, Visionary. Keep channel names such as #operators unchanged.-- Use sentence case according to Thai conventions. Do not copy English Title Case, including for English source badge titles such as Fluxer Staff or Fluxer Bug Hunter; use natural Thai capitalization or title style for those badge titles.-- Keep the tone fresh, clean, trustworthy, concise, and lightly humorous where the surface is low stakes.-- Keep auth, billing, privacy, safety, moderation, outages, and destructive actions calm and plain.-- Avoid legalistic, damning, corporate, or overly serious language.-- Avoid idioms, puns, and culture-specific jokes that are difficult to translate.-- Keep placeholders intact. Do not translate names, domains, URLs, emails, file names, keyboard shortcuts, permission constants, prices, counts, or protocol tokens inside placeholders.-- Reuse established translations for settings tabs, permission labels, shortcut names, key labels, status labels, and repeated command names.-- Keep punctuation consistent with the locale. Do not add semicolons or dash-heavy sentence structures.-- Follow familiar messaging-app terminology for the locale, while preserving Fluxer nouns such as community, Plutonium, and FluxerTag.-- Do not translate splash quotes one by one. Translate only the single fallback loading string for non-English locales if it appears.--## Locale guidance--Use clear Thai app language with polite-neutral tone. Follow LINE, Messenger, and Thai banking-app conventions. Avoid overly formal royal or bureaucratic wording.--## Product terms--- community: choose the conventional chat-app term for a group space. Avoid server-style wording unless it is truly the only natural local option.-- channel: use the conventional term for a named chat or voice space.-- DM: use the familiar local abbreviation only if users commonly know it. Otherwise use the normal term for direct message.-- group DM: use the familiar local term for a small private group chat.-- role, permission, invite, webhook, passkey, OAuth, and bot: use conventional app or developer terminology.-- favorites: translate as saved or favorite items according to the locale's app convention, not as a romantic preference.-- Discovery: keep as the named Fluxer area if that reads naturally. Otherwise translate as the app's discovery or explore area.--## Quality check--Before returning translations, read them as an actual app screen. They should be short, familiar, grammatically correct, and easy to scan. If a string sounds like a press release, rewrite it.diff --git a/fluxer_app/src/features/i18n/locales/tr/LOCALIZATION_PROMPT.md b/fluxer_app/src/features/i18n/locales/tr/LOCALIZATION_PROMPT.mddeleted file mode 100644index d3357ad8b..000000000--- a/fluxer_app/src/features/i18n/locales/tr/LOCALIZATION_PROMPT.md+++ /dev/null@@ -1,35 +0,0 @@-# Turkish localization prompt--You are localizing the Fluxer client into Turkish for locale `tr`.--## Core rules--- Preserve product names exactly: Fluxer, Fluxer Desktop, Fluxer API, Plutonium, Fluxer Plutonium, Fluxer HQ, FluxerTag, Operator Pass, Fluxer Labs, Visionary. Keep channel names such as #operators unchanged.-- Use sentence case according to Turkish conventions. Do not copy English Title Case, including for English source badge titles such as Fluxer Staff or Fluxer Bug Hunter; use natural Turkish capitalization or title style for those badge titles.-- Keep the tone fresh, clean, trustworthy, concise, and lightly humorous where the surface is low stakes.-- Keep auth, billing, privacy, safety, moderation, outages, and destructive actions calm and plain.-- Avoid legalistic, damning, corporate, or overly serious language.-- Avoid idioms, puns, and culture-specific jokes that are difficult to translate.-- Keep placeholders intact. Do not translate names, domains, URLs, emails, file names, keyboard shortcuts, permission constants, prices, counts, or protocol tokens inside placeholders.-- Reuse established translations for settings tabs, permission labels, shortcut names, key labels, status labels, and repeated command names.-- Keep punctuation consistent with the locale. Do not add semicolons or dash-heavy sentence structures.-- Follow familiar messaging-app terminology for the locale, while preserving Fluxer nouns such as community, Plutonium, and FluxerTag.-- Do not translate splash quotes one by one. Translate only the single fallback loading string for non-English locales if it appears.--## Locale guidance--Use natural Turkish app language with concise labels. Follow WhatsApp and Telegram conventions. Avoid literal English structure and keep placeholders grammatically safe.--## Product terms--- community: choose the conventional chat-app term for a group space. Avoid server-style wording unless it is truly the only natural local option.-- channel: use the conventional term for a named chat or voice space.-- DM: use the familiar local abbreviation only if users commonly know it. Otherwise use the normal term for direct message.-- group DM: use the familiar local term for a small private group chat.-- role, permission, invite, webhook, passkey, OAuth, and bot: use conventional app or developer terminology.-- favorites: translate as saved or favorite items according to the locale's app convention, not as a romantic preference.-- Discovery: keep as the named Fluxer area if that reads naturally. Otherwise translate as the app's discovery or explore area.--## Quality check--Before returning translations, read them as an actual app screen. They should be short, familiar, grammatically correct, and easy to scan. If a string sounds like a press release, rewrite it.diff --git a/fluxer_app/src/features/i18n/locales/uk/LOCALIZATION_PROMPT.md b/fluxer_app/src/features/i18n/locales/uk/LOCALIZATION_PROMPT.mddeleted file mode 100644index 00aaf0184..000000000--- a/fluxer_app/src/features/i18n/locales/uk/LOCALIZATION_PROMPT.md+++ /dev/null@@ -1,36 +0,0 @@-# Ukrainian localization prompt--You are localizing the Fluxer client into Ukrainian for locale `uk`.--## Core rules--- Preserve product names exactly: Fluxer, Fluxer Desktop, Fluxer API, Plutonium, Fluxer Plutonium, Fluxer HQ, FluxerTag, Operator Pass, Fluxer Labs, Visionary. Keep channel names such as #operators unchanged.-- Use sentence case according to Ukrainian conventions. Do not copy English Title Case, including for English source badge titles such as Fluxer Staff or Fluxer Bug Hunter; use natural Ukrainian capitalization or title style for those badge titles.-- Keep the tone fresh, clean, trustworthy, concise, and lightly humorous where the surface is low stakes.-- Keep auth, billing, privacy, safety, moderation, outages, and destructive actions calm and plain.-- Avoid legalistic, damning, corporate, or overly serious language.-- Avoid idioms, puns, and culture-specific jokes that are difficult to translate.-- Keep placeholders intact. Do not translate names, domains, URLs, emails, file names, keyboard shortcuts, permission constants, prices, counts, or protocol tokens inside placeholders.-- Reuse established translations for settings tabs, permission labels, shortcut names, key labels, status labels, and repeated command names.-- Keep punctuation consistent with the locale. Do not add semicolons or dash-heavy sentence structures.-- Follow familiar messaging-app terminology for the locale, while preserving Fluxer nouns such as community, Plutonium, and FluxerTag.-- Do not translate splash quotes one by one. Translate only the single fallback loading string for non-English locales if it appears.--## Locale guidance--Use natural Ukrainian app language with friendly neutral tone. Follow Telegram, Viber, and Diia-style clarity. Avoid Russian calques.--## Product terms--- community: choose the conventional chat-app term for a group space. Avoid server-style wording unless it is truly the only natural local option.-- channel: use the conventional term for a named chat or voice space.-- DM: use the familiar local abbreviation only if users commonly know it. Otherwise use the normal term for direct message.-- group DM: use the familiar local term for a small private group chat.-- role, permission, invite, webhook, passkey, OAuth, and bot: use conventional app or developer terminology.-- favorites: translate as saved or favorite items according to the locale's app convention, not as a romantic preference.-- Discovery: keep as the named Fluxer area if that reads naturally. Otherwise translate as the app's discovery or explore area.-- emoji: always use «емоджі», never «емодзі».--## Quality check--Before returning translations, read them as an actual app screen. They should be short, familiar, grammatically correct, and easy to scan. If a string sounds like a press release, rewrite it.diff --git a/fluxer_app/src/features/i18n/locales/vi/LOCALIZATION_PROMPT.md b/fluxer_app/src/features/i18n/locales/vi/LOCALIZATION_PROMPT.mddeleted file mode 100644index bb6d1f2db..000000000--- a/fluxer_app/src/features/i18n/locales/vi/LOCALIZATION_PROMPT.md+++ /dev/null@@ -1,35 +0,0 @@-# Vietnamese localization prompt--You are localizing the Fluxer client into Vietnamese for locale `vi`.--## Core rules--- Preserve product names exactly: Fluxer, Fluxer Desktop, Fluxer API, Plutonium, Fluxer Plutonium, Fluxer HQ, FluxerTag, Operator Pass, Fluxer Labs, Visionary. Keep channel names such as #operators unchanged.-- Use sentence case according to Vietnamese conventions. Do not copy English Title Case, including for English source badge titles such as Fluxer Staff or Fluxer Bug Hunter; use natural Vietnamese capitalization or title style for those badge titles.-- Keep the tone fresh, clean, trustworthy, concise, and lightly humorous where the surface is low stakes.-- Keep auth, billing, privacy, safety, moderation, outages, and destructive actions calm and plain.-- Avoid legalistic, damning, corporate, or overly serious language.-- Avoid idioms, puns, and culture-specific jokes that are difficult to translate.-- Keep placeholders intact. Do not translate names, domains, URLs, emails, file names, keyboard shortcuts, permission constants, prices, counts, or protocol tokens inside placeholders.-- Reuse established translations for settings tabs, permission labels, shortcut names, key labels, status labels, and repeated command names.-- Keep punctuation consistent with the locale. Do not add semicolons or dash-heavy sentence structures.-- Follow familiar messaging-app terminology for the locale, while preserving Fluxer nouns such as community, Plutonium, and FluxerTag.-- Do not translate splash quotes one by one. Translate only the single fallback loading string for non-English locales if it appears.--## Locale guidance--Use natural Vietnamese app copy with friendly neutral tone. Follow Zalo, Messenger, and Telegram conventions. Prefer common tech terms users know.--## Product terms--- community: choose the conventional chat-app term for a group space. Avoid server-style wording unless it is truly the only natural local option.-- channel: use the conventional term for a named chat or voice space.-- DM: use the familiar local abbreviation only if users commonly know it. Otherwise use the normal term for direct message.-- group DM: use the familiar local term for a small private group chat.-- role, permission, invite, webhook, passkey, OAuth, and bot: use conventional app or developer terminology.-- favorites: translate as saved or favorite items according to the locale's app convention, not as a romantic preference.-- Discovery: keep as the named Fluxer area if that reads naturally. Otherwise translate as the app's discovery or explore area.--## Quality check--Before returning translations, read them as an actual app screen. They should be short, familiar, grammatically correct, and easy to scan. If a string sounds like a press release, rewrite it.diff --git a/fluxer_app/src/features/i18n/locales/zh-CN/LOCALIZATION_PROMPT.md b/fluxer_app/src/features/i18n/locales/zh-CN/LOCALIZATION_PROMPT.mddeleted file mode 100644index 9ac976298..000000000--- a/fluxer_app/src/features/i18n/locales/zh-CN/LOCALIZATION_PROMPT.md+++ /dev/null@@ -1,35 +0,0 @@-# Chinese Simplified localization prompt--You are localizing the Fluxer client into Simplified Chinese for locale `zh-CN`.--## Core rules--- Preserve product names exactly: Fluxer, Fluxer Desktop, Fluxer API, Plutonium, Fluxer Plutonium, Fluxer HQ, FluxerTag, Operator Pass, Fluxer Labs, Visionary. Keep channel names such as #operators unchanged.-- Use sentence case according to Simplified Chinese conventions. Do not copy English Title Case, including for English source badge titles such as Fluxer Staff or Fluxer Bug Hunter; use natural Simplified Chinese capitalization or title style for those badge titles.-- Keep the tone fresh, clean, trustworthy, concise, and lightly humorous where the surface is low stakes.-- Keep auth, billing, privacy, safety, moderation, outages, and destructive actions calm and plain.-- Avoid legalistic, damning, corporate, or overly serious language.-- Avoid idioms, puns, and culture-specific jokes that are difficult to translate.-- Keep placeholders intact. Do not translate names, domains, URLs, emails, file names, keyboard shortcuts, permission constants, prices, counts, or protocol tokens inside placeholders.-- Reuse established translations for settings tabs, permission labels, shortcut names, key labels, status labels, and repeated command names.-- Keep punctuation consistent with the locale. Do not add semicolons or dash-heavy sentence structures.-- Follow familiar messaging-app terminology for the locale, while preserving Fluxer nouns such as community, Plutonium, and FluxerTag.-- Do not translate splash quotes one by one. Translate only the single fallback loading string for non-English locales if it appears.--## Locale guidance--Use concise Simplified Chinese familiar from WeChat, QQ, and mobile OS settings. Use Mainland terminology. Keep tone friendly and avoid stiff enterprise language.--## Product terms--- community: choose the conventional chat-app term for a group space. Avoid server-style wording unless it is truly the only natural local option.-- channel: use the conventional term for a named chat or voice space.-- DM: use the familiar local abbreviation only if users commonly know it. Otherwise use the normal term for direct message.-- group DM: use the familiar local term for a small private group chat.-- role, permission, invite, webhook, passkey, OAuth, and bot: use conventional app or developer terminology.-- favorites: translate as saved or favorite items according to the locale's app convention, not as a romantic preference.-- Discovery: keep as the named Fluxer area if that reads naturally. Otherwise translate as the app's discovery or explore area.--## Quality check--Before returning translations, read them as an actual app screen. They should be short, familiar, grammatically correct, and easy to scan. If a string sounds like a press release, rewrite it.diff --git a/fluxer_app/src/features/i18n/locales/zh-TW/LOCALIZATION_PROMPT.md b/fluxer_app/src/features/i18n/locales/zh-TW/LOCALIZATION_PROMPT.mddeleted file mode 100644index aabc2e8e9..000000000--- a/fluxer_app/src/features/i18n/locales/zh-TW/LOCALIZATION_PROMPT.md+++ /dev/null@@ -1,35 +0,0 @@-# Chinese Traditional Taiwan localization prompt--You are localizing the Fluxer client into Traditional Chinese for Taiwan for locale `zh-TW`.--## Core rules--- Preserve product names exactly: Fluxer, Fluxer Desktop, Fluxer API, Plutonium, Fluxer Plutonium, Fluxer HQ, FluxerTag, Operator Pass, Fluxer Labs, Visionary. Keep channel names such as #operators unchanged.-- Use sentence case according to Traditional Chinese for Taiwan conventions. Do not copy English Title Case, including for English source badge titles such as Fluxer Staff or Fluxer Bug Hunter; use natural Traditional Chinese for Taiwan capitalization or title style for those badge titles.-- Keep the tone fresh, clean, trustworthy, concise, and lightly humorous where the surface is low stakes.-- Keep auth, billing, privacy, safety, moderation, outages, and destructive actions calm and plain.-- Avoid legalistic, damning, corporate, or overly serious language.-- Avoid idioms, puns, and culture-specific jokes that are difficult to translate.-- Keep placeholders intact. Do not translate names, domains, URLs, emails, file names, keyboard shortcuts, permission constants, prices, counts, or protocol tokens inside placeholders.-- Reuse established translations for settings tabs, permission labels, shortcut names, key labels, status labels, and repeated command names.-- Keep punctuation consistent with the locale. Do not add semicolons or dash-heavy sentence structures.-- Follow familiar messaging-app terminology for the locale, while preserving Fluxer nouns such as community, Plutonium, and FluxerTag.-- Do not translate splash quotes one by one. Translate only the single fallback loading string for non-English locales if it appears.--## Locale guidance--Use Traditional Chinese familiar from LINE and mobile OS settings in Taiwan. Use Taiwan terminology. Avoid Mainland-only phrasing.--## Product terms--- community: choose the conventional chat-app term for a group space. Avoid server-style wording unless it is truly the only natural local option.-- channel: use the conventional term for a named chat or voice space.-- DM: use the familiar local abbreviation only if users commonly know it. Otherwise use the normal term for direct message.-- group DM: use the familiar local term for a small private group chat.-- role, permission, invite, webhook, passkey, OAuth, and bot: use conventional app or developer terminology.-- favorites: translate as saved or favorite items according to the locale's app convention, not as a romantic preference.-- Discovery: keep as the named Fluxer area if that reads naturally. Otherwise translate as the app's discovery or explore area.--## Quality check--Before returning translations, read them as an actual app screen. They should be short, familiar, grammatically correct, and easy to scan. If a string sounds like a press release, rewrite it.