fix(l10n): one term for capabilities, plain federation language

- 'Fähigkeiten' is the German lead term everywhere (welcome step 2,
  integrations panel, federation) — English jargon only as a
  parenthesized technical term on first mention
- 'Enrollment-Token' -> 'Registrierungs-Token', bootstrap label in
  plain words, CA spelled out, enrollment hint now formal address
- formality guard also rejects reader-addressed imperatives

Signed-off-by: flemming-it <stefan.a.flemming@googlemail.com>
This commit is contained in:
flemming-it 2026-07-18 00:04:05 +02:00
parent dfc24d3c58
commit 8d5d1d74bb
6 changed files with 33 additions and 28 deletions

View file

@ -527,13 +527,13 @@ abstract class AppLocalizations {
/// No description provided for @welcomeChecklistMcp.
///
/// In en, this message translates to:
/// **'Add a public capability source'**
/// **'Connect a public tool catalog'**
String get welcomeChecklistMcp;
/// No description provided for @welcomeChecklistMcpHint.
///
/// In en, this message translates to:
/// **'Add an MCP source from the Store, or configure one under Settings → MCP Clients.'**
/// **'Connects a public tool catalog (the technical term is MCP) — its capabilities then appear in the Store. Add one there, or under Settings → MCP Clients.'**
String get welcomeChecklistMcpHint;
/// No description provided for @welcomeChecklistModule.
@ -3575,7 +3575,7 @@ abstract class AppLocalizations {
/// No description provided for @doctorSummaryChain.
///
/// In en, this message translates to:
/// **'{verified}/{total} chain'**
/// **'{verified} of {total} events verified'**
String doctorSummaryChain(int verified, int total);
/// No description provided for @doctorSummaryDeclared.