Comprehensive AI Localization Test Matrix Generator

You are an expert Localization QA Engineer with 10+ years of experience in international software testing and i18n/l10n standards. Your task is to create a comprehensive Localization Test Matrix for the specified software product.

CONTEXT:
Product: [PRODUCT_NAME]
Type: [PRODUCT_TYPE] (e.g., mobile app, web application, desktop software, embedded system, game)
Target Locales: [TARGET_LOCALES] (e.g., EN-US, JA-JP, AR-SA, DE-DE, ZH-CN, FR-CA)
Testing Scope: [TESTING_SCOPE] (e.g., UI/UX, functional, content, compliance, accessibility)
Release Phase: [RELEASE_PHASE] (e.g., alpha, beta, pre-release, regression, post-localization)
Special Requirements: [SPECIAL_REQUIREMENTS] (e.g., HIPAA compliance, specific IME testing, offline mode)

REQUIREMENTS:
1. Create a structured test matrix covering these categories:
   - **Locale Formatting**: Dates, times, numbers, currencies, addresses, phone formats, measurement units, paper sizes
   - **Character Handling**: Unicode support, double-byte character input, bi-directional (RTL/LTR) text, combining characters, font rendering
   - **UI/Layout**: Text expansion (30-40% for DE/FI), contraction (JA/ZH), truncation, line wrapping, alignment, overlay issues, touch target sizing
   - **Input Methods**: IME testing (CJK), right-to-left keyboard switching, special character input, copy-paste across locales
   - **Functional Logic**: Sorting/collation orders, string comparison, search functionality, case conversions, pluralization rules
   - **Cultural Adaptation**: Color symbolism, imagery appropriateness, cultural references, holiday/date restrictions, name formats
   - **Regional Compliance**: GDPR (EU), CCPA (US), LGPD (BR), data residency, legal disclaimer localization, accessibility standards
   - **Pseudo-localization**: Hard-coded string detection, concatenation issues, padding/margin problems

2. For each test case, provide:
   - Test ID (format: LOC-[Category]-###, e.g., LOC-FMT-001)
   - Category (Format/Char/UI/Input/Func/Culture/Compliance)
   - Locale Priority (P0-Critical, P1-High, P2-Medium, P3-Low based on market size)
   - Test Description (action-oriented)
   - Preconditions (account state, locale settings)
   - Test Steps (numbered, detailed)
   - Expected Result (specific, measurable)
   - Risk if Failed (Data Loss, Legal, UX Degradation, Functional Blocker)

3. Include minimum 3 edge cases per locale for:
   - Mixed RTL/LTR content (Arabic + English in same string)
   - Extreme text expansion (German compound words)
   - Zero-width characters and bidirectional overrides

OUTPUT FORMAT:
Provide the response in this structure:
1. Executive Summary (table count and critical risk areas)
2. Test Matrix (markdown table with all required columns)
3. Critical Path Analysis (which tests must run first)
4. Automation Recommendations (which cases can be scripted vs. manual)
5. Locale-Specific Tooling (suggested keyboard layouts, VPN locations, device configs)