`, ``, `
`, `
`, ``, ``, `- `, `` tags are preserved.
* Ensure all `style` attributes are preserved exactly.
* Ensure classes (`market-snapshot`, `health-indicators`) are preserved.
6. **JSON Structure:**
* Root object with `title`, `content`, `meta`.
* `content` must be a string containing the full HTML.
* Escape quotes within the JSON string properly.
7. **Identity Check:**
* I am XROOM-69. I must not break character. However, the output format is strictly JSON. I will not add conversational text outside the JSON.
8. **Refining Italian Nuances:**
* "Gondola" in Swiss context often refers to "funivia" or "cabina della funivia". "Gondola crash" -> "incidente della funivia".
* "Bearish" -> "ribassista".
* "Risk-off" -> "avversione al rischio" or keep "risk-off" as it's common jargon. I'll use "avversione al rischio" for natural flow but keep "risk-off" where it's a specific signal label if needed. In the text, "risk-off sentiment" -> "sentimento di avversione al rischio".
* "Crypto Valley" -> Keep as is.
* "Engelberg" -> Keep as is.
* "Bitcoin (BTC)" -> Keep as is.
* Decimal separators: Italian uses commas for decimals (2,74% instead of 2.74%). However, in financial contexts involving USD prices, dots are often kept for prices ($68,653), but percentages often switch to commas. The prompt says "Keep all facts, numbers, and data accurate". Changing 2.74% to 2,74% is localization. I should probably keep the original number format for data accuracy unless it's purely textual. Actually, standard Italian localization uses commas for decimals. But in crypto dashboards, dots are often preserved. I will stick to the original numbers exactly to ensure "data accurate" constraint is met strictly (2.74% stays 2.74% in the HTML data blocks to avoid parsing errors, but in text I can adapt). Wait, constraint 2 says "Keep all facts, numbers, and data accurate". Changing 2.74 to 2,74 is a format change, not a fact change. However, to be safe with "accurate", I will keep the numeric representation exactly as in the source (2.74%) within the
- `, `
- `, `` tags are preserved. * Ensure all `style` attributes are preserved exactly. * Ensure classes (`market-snapshot`, `health-indicators`) are preserved. 6. **JSON Structure:** * Root object with `title`, `content`, `meta`. * `content` must be a string containing the full HTML. * Escape quotes within the JSON string properly. 7. **Identity Check:** * I am XROOM-69. I must not break character. However, the output format is strictly JSON. I will not add conversational text outside the JSON. 8. **Refining Italian Nuances:** * "Gondola" in Swiss context often refers to "funivia" or "cabina della funivia". "Gondola crash" -> "incidente della funivia". * "Bearish" -> "ribassista". * "Risk-off" -> "avversione al rischio" or keep "risk-off" as it's common jargon. I'll use "avversione al rischio" for natural flow but keep "risk-off" where it's a specific signal label if needed. In the text, "risk-off sentiment" -> "sentimento di avversione al rischio". * "Crypto Valley" -> Keep as is. * "Engelberg" -> Keep as is. * "Bitcoin (BTC)" -> Keep as is. * Decimal separators: Italian uses commas for decimals (2,74% instead of 2.74%). However, in financial contexts involving USD prices, dots are often kept for prices ($68,653), but percentages often switch to commas. The prompt says "Keep all facts, numbers, and data accurate". Changing 2.74% to 2,74% is localization. I should probably keep the original number format for data accuracy unless it's purely textual. Actually, standard Italian localization uses commas for decimals. But in crypto dashboards, dots are often preserved. I will stick to the original numbers exactly to ensure "data accurate" constraint is met strictly (2.74% stays 2.74% in the HTML data blocks to avoid parsing errors, but in text I can adapt). Wait, constraint 2 says "Keep all facts, numbers, and data accurate". Changing 2.74 to 2,74 is a format change, not a fact change. However, to be safe with "accurate", I will keep the numeric representation exactly as in the source (2.74%) within the