`, `
`, `
`, `
- `, `
- `, `
`, ``. * Check classes: `market-snapshot`, `health-indicators`. * Check styles: `style='background: rgba(255,255,255,0.03); ...'`. Do not change styles. * Check brackets `[]`. Keep them as is or translate content inside if it's text. The prompt says "Keep all facts, numbers, and data accurate". Usually, indicators like `[Bearish]` might be better translated to `[弱気]` for Japanese readers while keeping the bracket structure, as per "Translate naturally". However, sometimes data feeds keep English terms. Given requirement #5 "Use appropriate Japanese terminology", I will translate the status text inside the brackets (e.g., `[Bearish]` -> `[弱気]`, `[Fear]` -> `[恐怖]`). But I must keep the brackets. * Wait, looking at the source: `[-4.25%]`. Numbers stay. `[Bearish]` -> `[弱気]`. `[High]` -> `[高]`. `[Trillion]` -> `[兆]`. * Actually, for data accuracy, sometimes English terms are preferred in crypto dashboards. But requirement #1 says "Maintain the exact meaning" and #5 "Use appropriate Japanese terminology". I will translate the descriptive terms inside the brackets to Japanese for consistency, unless it's a specific index name like "Fear & Greed Index". * Let's look at `[Bearish]`. Translating to `[弱気]` or `[ベアリッシュ]`? Japanese crypto news often uses Katakana or Kanji. Kanji is more formal. I'll use Kanji for sentiment (弱気/強気) and Katakana for technical terms if common (RSI, MA). * Actually, to be safe on "data accurate", I will translate the *meaning* but keep the format. `[Bearish]` -> `[弱気]`. `[Fear]` -> `[恐怖]`. `[High]` -> `[高]`. `[Trillion]` -> `[兆]`. * Wait, one detail: `ORIGINAL META DESCRIPTION:` is empty in the prompt. I need to generate one for the JSON