Bug: 157 orphaned i18n analytics keys in DE/ES/FR with no EN counterpart

[mrveiss]

Problem

During bulk i18n translation work (#1555), 157 orphaned translation keys were discovered in DE and ES locale files (147 in FR) under the analytics section. These keys have translations but no corresponding key in en.json, meaning they are dead translations that inflate file size and could cause confusion.

LV, PL, PT are clean (0 extra keys).

Discovered During

Working on #1555 (bulk i18n translation)

Affected Files

• autobot-frontend/src/i18n/locales/de.json — 157 orphaned keys
• autobot-frontend/src/i18n/locales/es.json — 157 orphaned keys
• autobot-frontend/src/i18n/locales/fr.json — 147 orphaned keys

Breakdown by subsection

Section	Count
analytics.evolution	33
analytics.bi	31
analytics.sources	31
analytics.findings	28
analytics.header	14
analytics.views	5
analytics.precommit	4
analytics.advanced	3
analytics.codeIntelligence	3
analytics.logPatterns	3
analytics.declarations	2

Root Cause

These keys were likely added by the translation scripts in the previous session for analytics subsections that don't exist (or were restructured) in EN. The scripts translated keys based on a broader mapping that included keys not present in the current en.json.

Fix

Write a script to remove any key from locale JSON files that doesn't exist in en.json. Run across all 6 non-EN locales to ensure parity.

Impact

Low — orphaned keys are harmless (vue-i18n ignores unused keys), but they increase file size unnecessarily and could mislead future translation work.

[mrveiss]

Fixed in commit 331760f (merged to Dev_new_gui). Pruned 157 orphaned analytics keys from DE/ES, 147 from FR. All 6 locales now have exact key parity with EN (5,384 keys each, 0 missing, 0 extra).