` remain intact.
* **Identity:** Do not mention AI identity in the output, just follow the system instruction regarding identity if asked (not asked here, just translating).
* **Accuracy:** Check numbers ($118.50, -2.15%, etc.).
6. **Refining German Terminology:**
* "Class-action lawsuit" -> "Sammelklage"
* "Certified" -> "bestätigt" or "zugelassen" (in legal context "certify a class" -> "Klasse zertifizieren/bestätigen"). "Bestätigt" works well.
* "Semiconductor giant" -> "Halbleiterriese"
* "Discovery processes" -> "Beweisaufnahmeverfahren"
* "Bearish" -> "Bärisch" (common financial German)
* "Fear & Greed Index" -> "Fear & Greed Index" (keep name)
* "Weak Hands" -> "Schwache Hände" (Crypto slang)
* "Risk-Off" -> "Risk-Off" (keep)
7. **Constructing the JSON:**
* Need to escape newlines and quotes within the JSON string values.
* Ensure the HTML inside the `content` string is properly escaped (e.g., `"` becomes `"`).
8. **Final Check:**
* Did I keep the `style` attributes in the `div`? Yes.
* Did I keep the `class` names? Yes.
* Are the numbers exact? Yes.
* Is the tone professional? Yes.
*Self-Correction on "Discovery":* In German legal reporting about US cases, "Discovery" is often used as is, but "Beweisaufnahme" is the functional equivalent. I will use "Beweisaufnahmephase" for clarity while maintaining the legal meaning.
*Self-Correction on "Weak Hands":* In German crypto communities, "Weak Hands" is often used as is, but "Schwache Hände" is the translation. I'll use "Schwache Hände" to meet the translation requirement while noting it's a specific behavior.
*Self-Correction on "HODLer":* Keep as "HODLer".
*Self-Correction on "Risk-Off":* Keep as "Risk-Off".
*HTML Escaping:* I need to be careful with quotes inside the HTML attributes when putting them into a JSON string. The original HTML uses single quotes `'` for attributes (e.g., `class='market-snapshot'`), which makes JSON escaping easier (only double quotes need escaping). However, I should ensure the JSON structure itself uses double quotes for keys and values.
*Meta Description:* "Federal judge certifies class-action lawsuit..." -> "Bundesrichter bestätigt Sammelklage gegen Nvidia wegen nicht offengelegter Krypto-Mining-Einnahmen..."
*Let's assemble the content.*
*Wait, one constraint check:* "RESPOND IN JSON". I must output *only* the JSON block, no markdown code fences around it? Usually, JSON responses are wrapped in ```json ... ``` for clarity, but the prompt says "RESPOND IN JSON". I will output the raw JSON string to be safe, or wrapped in code blocks if that's standard for this interface. Given the instruction "RESPOND IN JSON:", I will provide the JSON object directly. However, to ensure it's parsed correctly by the user, I will wrap it in a code block labeled json if possible, but strictly speaking, raw JSON is safer for automated parsing. I will output raw JSON
* Richter bestätigt Investoren-Klage gegen Nvidia wegen versteckter Krypto-Einnahmen
