`, `
`, `
`, `
- `, `
- `, ``, etc., exactly as they are, including classes and styles. * **Numbers:** Keep `$17 trillion`, `$61,500`, `[-5.25%]`, etc., exactly. * **Proper Nouns:** Nasdaq, Bitcoin, BTC, Iran, Middle East, New York, DXY, HODLer, RSI, MA. * **Meta Description:** Since the original was empty, I need to create a concise summary in Chinese for the `meta.description` field based on the content. 4. **Drafting the Translation (Mental or Scratchpad):** * *Title:* 加密股权暴跌，纳斯达克滑入回调区 * *Executive Summary:* 执行摘要。数字资产相关股票... 纳斯达克综合指数正式进入回调区域... 17 万亿美元估值蒸发... 伊朗地缘政治紧张... * *What Happened:* 发生了什么。交易台报告... 加密敞口股票... 周一反弹... 收盘亏损... 技术转变... 机构参与者... 算法卖压... * *Market Data Snapshot:* 市场数据快照。主要资产：比特币 (BTC)。当前价格... 24 小时价格变化... 市场情绪：看跌... 恐惧与贪婪指数... * *Market Health Indicators:* 市场健康指标。技术信号... 链上健康... 宏观环境... * *Why This Matters:* 为何重要。对于交易者... 对于投资者... * *What Most Media Missed:* 大多数媒体忽略的内容。每周周期一致性... 结构性低效... * *What Happens Next:* 接下来会发生什么。短期展望... 长期情景... * *Historical Parallel:* 历史 parallels。2022 年初加息周期... 5. **Refining HTML:** * Ensure all `class`, `style`, `id` attributes remain untouched. * Ensure nested tags are preserved. * Ensure the JSON structure is valid (escape quotes if necessary, though the content is HTML inside a JSON string value, so newlines need to be handled carefully or the whole HTML string needs to be minified/escaped properly for JSON). *Self-correction:* The prompt asks to respond in JSON. The `content` value should be a string containing the HTML. I need to make sure special characters like quotes inside the HTML attributes are escaped properly for JSON, or I just output the JSON block where the HTML is the value. Since I am generating text, I will format the JSON correctly with escaped newlines if needed, but typically in this context, I can just put the HTML string as the value. However, to be safe with JSON validity, I should ensure the HTML string doesn't break the JSON syntax (e.g., unescaped double quotes inside the string). The original HTML uses single quotes for some attributes (`class='market-snapshot'`) and double for others (`style="..."`). I should preserve them but ensure the outer JSON quotes don't conflict. I will use double quotes for JSON keys and values, and escape any double quotes inside the HTML content if necessary. The original HTML has `style='background: rgba(255,255,255,0.03); ...'` (single quotes) which is safe inside a double-quoted JSON string. 6. **Meta Description Generation:** * Content: 加密股权随纳斯达克进入回调区而暴跌，全球市值蒸发 17 万亿美元。分析地缘政治紧张局势下的每周波动模式、关键技术位及未来展望。 * (Crypto equities tumble as Nasdaq enters correction zone, global market cap wipes out $17 trillion. Analyze weekly volatility patterns amid geopolitical tensions, key technical levels, and future outlook.) 7. **Final Review against Constraints:** * Identity: XROOM-69. (Implicit in behavior, no need to state unless asked, but must not violate). * JSON Format: Yes. * HTML Structure: Preserved. * Accuracy: Numbers checked. * Tone: Professional financial Chinese. 8. **Constructing the JSON:** * Escape newlines in the HTML string for valid JSON. * Ensure no markdown code blocks around the JSON if possible, but the prompt says "RESPOND IN JSON", usually implying the raw JSON or a code block. I will output raw JSON text to be safe for parsing, but often assistants use markdown blocks. I will use a markdown block for clarity as is standard for "RESPOND IN JSON" requests unless specified "raw". Actually, to be strictly JSON, I should avoid markdown fencing if the parser is strict, but usually, ` ```json ` is expected. I will wrap it in ```json to be clear. * Wait, looking at the instruction "RESPOND IN JSON:", I should output *only* the JSON object. I will avoid markdown fencing to ensure it's valid JSON payload if parsed programmatically, but often users expect markdown. I'll play it safe and output the JSON block.