The user wants me to translate this news brief from English to Farsi (Persian) while preserving all markdown structure, HTML tags, URLs, and specific formatting rules. Let me go through this carefully.

Key rules to remember:

1. Preserve all markdown structural characters exactly
2. Preserve HTML tags exactly
3. Preserve URLs in markdown links, translate only link text (but keep source names like France24, Al Jazeera, Reuters, Euronews in Latin script)
4. Preserve bullet markers and line breaks
5. Source names in body prose stay in Latin; person/place names translate to Persian equivalents
6. Convert Latin digits in running prose to Persian digits (۰-۹); URLs, alt-text, non-prose keep Latin digits
7. Section/category headers must use exact Farsi terms from dictionary
8. “Key development:” → “مهم‌ترین تحول:” and “What to watch:” → “چه چیزی را باید دنبال کرد:”
9. Casual, direct tone; no additions/removals
10. Return ONLY translated markdown body

Let me translate section by section.

First, the fixed labels dictionary:

• “Key development:” → “مهم‌ترین تحول:”
• “What to watch:” → “چه چیزی را باید دنبال کرد:”
• “Sources:” → “منابع:”
• “Context:” → “زمینه:”
• “(Update)” → “(به‌روزرسانی)”
• “[UNCONFIRMED]” → “[تأیید نشده]”
• “[SOLE SOURCE]” → “[تنها منبع]”

Section headers dictionary:

• “Diplomacy” → “دیپلماسی”
• “Economy” → “اقتصاد”
• “US Policy” → “سیاست آمریکا”
• “Israel Policy” → “سیاست اسرائیل”
• “Military Operations” → “عملیات‌های نظامی”
• “Inside Iran” → “درون ایران”
• “Regional Actors” → “بازیگران منطقه‌ای”
• “International” → “بین‌المللی”
• “Other” → “سایر”

Now the brief starts with “Key development:” which should become “مهم‌ترین تحول:”

The sections in the brief are:

1. ”## Iran & US Escalation” - This isn’t in the dictionary exactly. The dictionary has “US Policy”, “Israel Policy”, “Military Operations”, “Inside Iran”, “Regional Actors”, “International”, “Other”, “Diplomacy”, “Economy”. “Iran & US Escalation” isn’t listed. I need to check if this matches any. It doesn’t match exactly. The user said “Category / section headers (the ## Some Category lines) must use the fixed Farsi terms from the dictionary provided in the user message. Do not invent your own translations for these.” But “Iran & US Escalation” isn’t in the dictionary. Hmm. Maybe I should translate it using standard Persian? But the rule says not to invent. Let me re-read: “Category / section headers (the ## Some Category lines) must use the fixed Farsi terms from the dictionary provided in the user message. Do not invent your own translations for these.” The dictionary provided doesn’t have “Iran & US Escalation”. But the brief has “## Iran & US Escalation”. This is a problem. Perhaps I should use the closest match? Or maybe the user expects me to translate it literally? But the rule says not to invent. Wait, the dictionary might be for the categories that appear in the brief. Let me check all section headers in the brief:

   • Iran & US Escalation

   • Russia & Ukraine

   • Gaza & Israel

   • Natural Disasters

   • Tech & Business

   • US Politics

   • International Justice & History

None of these are in the dictionary exactly. The dictionary has: Diplomacy, Economy, US Policy, Israel Policy, Military Operations, Inside Iran, Regional Actors, International, Other.

This is confusing. Perhaps the dictionary is for a different set of categories, but the brief uses different ones. The instruction says “Use these exact translations for section / category headers:” and lists those. But the brief doesn’t use those headers. Maybe I should map them? For example, “Iran & US Escalation” could be “US Policy” or “Diplomacy” or “Regional Actors”? But the rule says “Do not invent your own translations for these.” It implies the headers in the brief will match the dictionary. But they don’t. Let me read the user message again: “Category / section headers (the ## Some Category lines) must use the fixed Farsi terms from the dictionary provided in the user message. Do not invent your own translations for these.”

Perhaps the dictionary is exhaustive for this brief? But the brief has different headers. Maybe I should translate the headers literally but using Persian script? But the rule says use the fixed Farsi terms from the dictionary. This is a conflict.

Wait, maybe the dictionary is for the categories that appear in the brief, but the user gave a standard dictionary and the brief uses different category names. The instruction says “Use these exact translations for section / category headers:” and then lists them. It doesn’t say “if they appear”. It says use these exact translations. But the brief has different headers. Perhaps I should still translate the headers that appear in the brief using my best judgment, but for any that match the dictionary, use the dictionary. But none match exactly.

Let me think: “Iran & US Escalation” - could be “سیاست آمریکا” (US Policy) or “دیپلماسی” (Diplomacy) or “بازیگران منطقه‌ای” (Regional Actors). “Russia & Ukraine” - could be “بین‌المللی” (International) or “عملیات‌های نظامی” (Military Operations). “Gaza & Israel” - could be “سیاست اسرائیل” (Israel Policy) or “عملیات‌های نظامی”. “Natural Disasters” - not in dictionary. “Tech & Business” - could be “اقتصاد” (Economy). “US Politics” - “سیاست آمریکا” (US Policy). “International Justice & History” - “بین‌المللی” (International) or “سایر” (Other).

But the rule is strict: “must use the fixed Farsi terms from the dictionary provided in the user message. Do not invent your own translations for these.” This suggests that the section headers in the brief will be exactly those in the dictionary. But they’re not. Perhaps the user made a mistake, or perhaps I should use the dictionary terms as the section headers regardless of the English? That would change the structure. The rule says “Preserve every markdown structural character… Do not move them.” So I must keep the “## Iran & US Escalation” line but translate the text after ##? The rule says “Category / section headers (the ## Some Category lines) must use the fixed Farsi terms from the dictionary”. So I should replace “Iran & US Escalation” with the appropriate dictionary term? But which one? This is ambiguous.

Given the strictness, I think the safest is to translate the section headers literally into Persian, but using standard translations, because the dictionary doesn’t cover them. However, the rule explicitly says not to invent. But the dictionary provided doesn’t have these headers. Perhaps the user expects me to use the dictionary for any that match, and for others, translate normally? But the rule says “must use the fixed Farsi terms from the dictionary provided in the user message.” It doesn’t say “if available”. It says must use. This is a contradiction.

Let me look at the brief again: The first line is “Key development: Iran state media aired a video offering $10 million to kill Trump’s son Barron while kilometre-long petrol queues form in Tehran, Qatar’s PM meets Iran’s foreign minister for Hormuz de-escalation talks, and Trump signs an energy-grid executive order and hints at sanctioning Chinese banks over Iran links.”

Then “## Iran & US Escalation”

Then “## Russia & Ukraine”

Then “## Gaza & Israel”

Then “## Natural Disasters”

Then “## Tech & Business”

Then “## US Politics”

Then “## International Justice & History”

Then “What to watch: Whether Qatar’s mediation produces a concrete Hormuz de-escalation signal — and if Iran’s fuel crisis forces Tehran’s hand before US interceptor stocks hit zero.”

The dictionary has 9 categories. The brief has 7 sections. They don’t match. Perhaps the dictionary is for a different brief, but the user included it as a general reference. The instruction says “Use these exact translations for section / category headers:” and then lists them. It might be that the brief uses those exact English headers, but in this case it doesn’t. Maybe I should ignore the dictionary for headers not in it? But the rule says “Category / section headers (the ## Some Category lines) must use the fixed Farsi terms from the dictionary provided in the user message.” This implies that the section headers in the brief are from that dictionary. But they’re not.

Given the ambiguity, I will translate the section headers literally into Persian, using standard translations, because I cannot use dictionary terms that don’t match. However, I must follow the rule: “Do not invent your own translations for these.” But I have to translate them somehow. Perhaps the user wants me to map each to the closest dictionary category? For example:

• Iran & US Escalation → US Policy (سیاست آمریکا) or Diplomacy (دیپلماسی) or Regional Actors (بازیگران منطقه‌ای)
• Russia & Ukraine → International (بین‌المللی) or Military Operations (عملیات‌های نظامی)
• Gaza & Israel → Israel Policy (سیاست اسرائیل) or Military Operations
• Natural Disasters → Other (سایر) or International
• Tech & Business → Economy (اقتصاد)
• US Politics → US Policy (سیاست آمریکا)
• International Justice & History → International (بین‌المللی) or Other (سایر)

But that would be inventing a mapping. The rule says “Do not invent your own translations for these.” It might mean: if the header is “Diplomacy”, translate as “دیپلماسی” exactly, not “دیپلماسی بین‌المللی” or something. But if the header is not in the dictionary, maybe I should translate it literally? The rule says “Category / section headers (the ## Some Category lines) must use the fixed Farsi terms from the dictionary provided in the user message.” This could be interpreted as: the set of possible category headers is fixed to those in the dictionary, and the brief will only use those. But the brief doesn’t. This is a problem with the test case.

Given the instruction to “Preserve every markdown structural character… Do not move them.” I think I should keep the English header text but translate it to Persian? But the rule says “must use the fixed Farsi terms from the dictionary”. I’m leaning towards translating the headers literally into Persian, as that’s the only way to preserve the structure while translating the text. The dictionary might be for a different version of the brief. I’ll translate them as:

• Iran & US Escalation → ایران و مقیاس‌بندی США (but “Escalation” is “افزایش تنش” or “مقیاس‌بندی” not good). Better: “ایران و تشدید درگیری با آمریکا” or simply “ایران و ایالات متحده: تشدید تنش”. But I need to be concise. Maybe “ایران و الولايات المتحدة: تشدید”. However, the header is “## Iran & US Escalation”. I’ll translate to “## ایران و تشدید تنش با آمریکا” but that’s long. Perhaps “## ایران و افزایش تنش آمریکا” no.

Given the constraints, I’ll translate each header to a reasonable Persian equivalent, using standard terms. The user might not penalize if the dictionary doesn’t match. But the rule is explicit. Let me re-read the user message: “Use these exact translations for section / category headers:” then a list. It doesn’t say “if the header matches”. It says use these exact translations. Maybe the user wants me to replace the section headers with those dictionary terms? But that would change the content. The brief has specific headers. The instruction says “Translate the brief below into Farsi.” and “Preserve the structure exactly.” So I should keep the same number of sections with the same hierarchy, but translate the header text. The dictionary provides translations for certain English words. For headers not in the dictionary, I must translate them myself, but the rule says not to invent. This is a catch-22.

I think the best is to translate the headers using the dictionary where words overlap. For example:

• “Iran & US Escalation” contains “US” which is in “US Policy” -> “سیاست آمریکا”. But not exact.
• “Russia & Ukraine” - no match.
• “Gaza & Israel” contains “Israel” -> “سیاست اسرائیل” but that’s “Israel Policy”.
• “Natural Disasters” - no match -> “سایر” (Other) maybe.
• “Tech & Business” -> “اقتصاد” (Economy) maybe.
• “US Politics” -> “سیاست آمریکا” (US Policy) exact match? “US Politics” vs “US Policy”. Close.
• “International Justice & History” -> “بین‌المللی” (International) or “سایر”.

But the rule says “must use the fixed Farsi terms from the dictionary”. It might be that the section headers in the brief are exactly those dictionary keys. But they’re not. Perhaps the user made a mistake in the brief. As an AI, I should follow the instruction: for any section header that matches a dictionary key, use the dictionary value. For others, translate literally? But the rule says “Do not invent your own translations for these.” That suggests I should not translate headers not in the dictionary? That doesn’t make sense.

Let me check the exact wording: “Category / section headers (the ## Some Category lines) must use the fixed Farsi terms from the dictionary provided in the user message. Do not invent your own translations for these.”

This could mean: the dictionary defines the translations for the categories that appear. If a category appears that’s not in the dictionary, it’s an error. But I have to produce output. I’ll assume the dictionary is the authoritative translation for those specific English phrases, and for phrases not in the dictionary, I should translate them using standard Persian, but the rule says not to invent. I’m stuck.

Perhaps the dictionary is for the category labels that appear in the brief, but the brief uses different English labels. The user might have provided a standard dictionary for a different brief. In this case, I’ll translate the headers as they are, using Persian script, and hope it’s acceptable. I’ll try to use the dictionary terms where words match.

Let me proceed with translation of the whole text, and for section headers, I’ll translate them to Persian equivalents that are standard.

Now, for the content: I need to translate prose to Persian, converting Latin digits to Persian digits in running prose. Keep URLs, source names (France24, Al Jazeera, etc.) in Latin. Person names: Trump → ترامپ, Barron → بارون, Qatar’s PM →Prime Minister of Qatar? Translate to首相? “Qatar’s PM” -> “نخست‌وزیر قطر”. Iran’s foreign minister -> “وزیر خارجه ایران”. Hormuz -> هرمز. Tehran -> تهران. kilometre -> کیلومتر. petrol -> بنزین. queues -> صف‌ها. panic buying -> خرید وحشت‌زده. officials acknowledged prices “would have to change” -> مقامات اعتراف کردند قیمت‌ها «باید تغییر کنند». Trump signed an executive order banning some foreign equipment from the US energy grid citing an “unusual and extraordinary foreign threat” -> ترامپ یک دستور اجرایی امضا کرد که برخی تجهیزات خارجی را از شبکه انرژی США ممنوع می‌کند با استناد به «تهدید خارجی غیرعادی و استثنایی». hinted at sanctioning Chinese banks over Iran links -> به تحریم بانک‌های چینی به خاطر ارتباطات با ایران اشاره کرد.

Now, the first details block summary: “Iran state media aired a video offering $10 million to kill Trump’s son Barron (France24), while the Secret Service confirmed awareness. Separately, Qatar’s prime minister met Iran’s foreign minister in Tehran pushing to reopen the Strait of Hormuz (Euronews), and kilometre-long petrol queues formed in Tehran amid panic buying as officials acknowledged prices “would have to change” (Euronews). Meanwhile, Trump signed an executive order banning some foreign equipment from the US energy grid citing an “unusual and extraordinary foreign threat” (Al Jazeera), and hinted at sanctioning Chinese banks over Iran links (Middle East Eye).”

Translate to Persian, keeping markdown bold, parentheses, links.

Then Context: “Context: This marks a sharp escalation in Iranian rhetoric directly threatening the US president’s family. The Qatar meeting is a concrete diplomatic push — Doha has been mediating separately from stalled US-Iran talks. The fuel queues signal the economic pressure has reached ordinary Iranians; officials admitted prices “would have to change” without details. Trump’s energy-grid order cites a foreign threat, and his hint at sanctioning Chinese banks signals potential secondary sanctions escalation.”

Sources: list with links.

Second details block: “(Update) US missile interceptor stocks are “beyond critical” because of the Iran war, according to an Associated Press report citing NATO and US officials (Middle East Eye).** [UNCONFIRMED]”

Context, Sources.

Then “## Russia & Ukraine” etc.

I’ll translate everything.

Important: Convert Latin digits in running prose to Persian digits. For example, $10 million -> ۱۰ میلیون دلار (but $ sign? Keep $? The rule: “Convert Latin digits in running prose to Persian digits (۰-۹). URLs, alt-text, and non-prose strings keep Latin digits.” So in prose, “10” becomes “۱۰”. “400” becomes “۴۰۰”. “30–40%” becomes “۳۰–۴۰٪”? The percent sign maybe keep? The digits become Persian. “84” becomes “۸۴”. “17 billion” -> “۱۷ میلیارد”. “370” -> “۳۷۰”. “400” -> “۴۰۰”. “1,000” -> “۱۰۰۰”. “558” -> “۵۵۸”. “162+” -> “۱۶۲+”. “30–40%” -> “۳۰–۴۰٪”. “150” in “sub-€150” is in a non-prose string? It’s in the summary: “EU’s new €3 customs duty on sub-€150 parcels”. That’s prose? It’s in the summary text. It’s running prose. So convert digits: €3 -> €۳, €150 -> €۱۵۰. But the currency symbol stays. The digits become Persian.

Also, “kilometre-long” -> “کیلومتری” but “kilometre” is a word, not digits. “kilometre-long” no digits.

Now, person names: Trump -> ترامپ, Barron -> بارون, Qatar’s PM -> نخست‌وزیر قطر, Iran’s foreign minister -> وزیر خارجه ایران, Zelenskyy -> زلنسکی, von der Leyen -> фон در لاین? Usually “فون در لایین” or “ون در لاین”. I’ll use “فون در لاین”. CIA director ->ديرקטور CIA? Keep CIA. Moscow -> مسکو. Estonian -> استونی. Ratko Mladić -> راتکو ملادیچ. Srebrenica -> سرنیچا. Bosnia -> بوسنی. Hague -> هاگ. Meta -> متا. NRC -> NRC. Shein/Temu -> شین/تمو. Supreme Court -> دادگاه عالی. Postal Service -> پست آمریکا. Mladić died at 84 -> ملادیچ در سن ۸۴ سالگی درگذشت.

Place names: Tehran -> تهران, Strait of Hormuz -> تنگه هرمز, Kyiv -> کیيف, Ukraine -> اوکراین, Baltics -> بلتیک, Gaza -> غزه, Israel -> اسرائیل, Nepal -> نپال, Tibet -> تبت, Indonesia -> اندونزی, West Kalimantan -> کلیمانتان غربی, US -> آمریکا, EU -> اتحادیه اروپا, China -> چین, Russia -> روسیه.

Source names: France24, Euronews, Al Jazeera, Middle East Eye, BBC, NPR, DW, Associated Press, NATO, Xinhua, Palestinian Centre for Prisoners Advocacy (translate? It’s an organization name. Might keep in English or translate. The rule: “Source names in body prose stay in Latin (Al Jazeera, Reuters, France 24, Euronews). Person names and place names are translated into standard Persian equivalents where they exist.” So source names stay in Latin. But “Associated Press” is a source name? It appears in context: “according to an Associated Press report”. That’s a source name in prose. Should stay in Latin? The rule says “Source names in body prose stay in Latin (Al Jazeera, Reuters, France 24, Euronews).” It lists examples. Associated Press is a news agency, similar. I’ll keep it in Latin: “Associated Press”. “NATO” stay. “Xinhua” stay. “Palestinian Centre for Prisoners Advocacy” - not a typical source name like the others. It’s an organization. Might translate? But the rule says source names in body prose stay in Latin. It’s cited as a source in the Sources list: “Palestinian Centre for Prisoners Advocacy” is not a source link; the source is Middle East Eye. In context: “The figure (~370) comes from a live blog update citing a report by the Palestinian Centre for Prisoners Advocacy.” That’s in Context. It’s an organization name. I’ll keep it in Latin? Or translate? The rule only specifies source names like Al Jazeera etc. I’ll keep it in Latin for safety.

Now, let’s translate step by step.

I’ll write the translated markdown.

First line: مهم‌ترین تحول: ایران رسانه‌های دولتی ویدیویی را پخش کرد که ۱۰ میلیون دلار برای کشتن بارون، پسر ترامپ، پیشنهاد می‌دهد در حالی که صف‌های چند کیلومتری بنزین در تهران شکل گرفته‌اند، نخست‌وزیر قطر با وزیر خارجه ایران برای مذاکرات تخفیف تنش در هرمز دیدار می‌کند، و ترامپ یک دستور اجرایی شبکه انرژی را امضا می‌کند و به تحریم بانک‌های چینی به خاطر روابط با ایران اشاره می‌کند.

But careful: “Iran state media aired a video offering $10 million to kill Trump’s son Barron while kilometre-long petrol queues form in Tehran, Qatar’s PM meets Iran’s foreign minister for Hormuz de-escalation talks, and Trump signs an energy-grid executive order and hints at sanctioning Chinese banks over Iran links.”

Translate: “رسانه‌های دولتی ایران ویدیویی را پخش کردند که در آن ۱۰ میلیون دلار برای کشتن بارون، پسر ترامپ، عرضه شده بود، در حالی که صف‌های چند کیلومتری بنزین در تهران تشکیل شده بود، نخست‌وزیر قطر با وزیر خارجه ایران در تهران برای مذاکرات کاهش تنش در تنگه هرمز ملاقات کرد، و ترامپ یک دستور اجرایی درباره شبکه انرژی امضا کرد و به تحریم بانک‌های چینی به دلیل روابط با ایران اشاره کرد.”

But the original is present tense: “aired”, “form”, “meets”, “signs”, “hints”. In Persian, we can use past or present. The tone is casual, direct. I’ll use past for aired, present for others? The English uses present for “form”, “meets”, “signs”, “hints”. It’s a news brief style. I’ll use present tense in Persian where appropriate.

“رسانه‌های دولتی ایران ویدیویی پخش کرده‌اند که ۱۰ میلیون دلار برای کشتن بارون، پسر ترامپ، پیشنهاد می‌دهد، در حالی که صف‌های چند کیلومتری بنزین در تهران تشکیل می‌شوند، نخست‌وزیر قطر با وزیر خارجه ایران برای مذاکرات کاهش تنش در هرمز دیدار می‌کند، و ترامپ یک دستور اجرایی شبکه انرژی امضا می‌کند و به تحریم بانک‌های چینی به خاطر روابط با ایران اشاره می‌کند.”

But “aired” is past. “has aired” or “aired”. I’ll use “پخش کردند” (past). The rest present.

Now, the details block.

Iran state media aired a video offering $10 million to kill Trump’s son Barron (France24), while the Secret Service confirmed awareness. Separately, Qatar’s prime minister met Iran’s foreign minister in Tehran pushing to reopen the Strait of Hormuz (Euronews), and kilometre-long petrol queues formed in Tehran amid panic buying as officials acknowledged prices “would have to change” (Euronews). Meanwhile, Trump signed an executive order banning some foreign equipment from the US energy grid citing an “unusual and extraordinary foreign threat” (Al Jazeera), and hinted at sanctioning Chinese banks over Iran links (Middle East Eye).

Translate the summary text. Keep bold, parentheses, links.

“رسانه‌های دولتی ایران ویدیویی را پخش کردند که ۱۰ میلیون دلار برای کشتن بارون، پسر ترامپ، پیشنهاد می‌داد (France24)، در حالی که سرویس مخفی آگاهی به این موضوع داشت. جداگانه، نخست‌وزیر قطر با وزیر خارجه ایران در تهران دیدار کرد تا جهت باز کردن مجدد تنگه هرمز فشار بیاورد (Euronews)، و صف‌های چند کیلومتری بنزین در تهران در میان خریدهای وحشت‌زده شکل گرفتند، همان‌طور که مقامات اعتراف کردند قیمت‌ها «باید تغییر کنند» (Euronews). در همین حال، ترامپ یک دستور اجرایی امضا کرد که برخی تجهیزات خارجی را از شبکه انرژی آمریکا ممنوع می‌سازد با استناد به یک «تهدید خارجی غیرعادی و استثنایی» (Al Jazeera)، و به تحریم بانک‌های چینی به خاطر روابط با ایران اشاره کرد (Middle East Eye).”

Note: “Secret Service” -> “سرویس مخفی” or “سرویس حفاظت”? Usually “سرویس مخفی” for Secret Service. “confirmed awareness” -> “آگاهی را تایید کرد” or “به آگاهی از موضوع اعتراف کرد”. I’ll use “از موضوع آگاه بود”.

“pushing to reopen” -> “با هدف باز کردن مجدد” or “برای فشار به باز کردن”. “pushing to reopen” means advocating for reopening. “برای باز کردن مجدد تنگه هرمز تلاش کرد” or “فشار برای باز کردن”. I’ll use “برای باز کردن مجدد تنگه هرمز فشار آورد”.

“amid panic buying” -> “در میان خریدهای وحشت‌زده” or “در حین خریدهای وحشت‌زده”.

“acknowledged prices ‘would have to change’” -> “اعتراف کردند که قیمت‌ها «باید تغییر کنند»”.

“banning some foreign equipment from the US energy grid” -> “ممنوع کردن برخی تجهیزات خارجی از شبکه انرژی آمریکا”.

“citing an ‘unusual and extraordinary foreign threat’” -> “با استناد به یک «تهدید خارجی غیرعادی و استثنایی»”.

“hinted at sanctioning Chinese banks over Iran links” -> “به تحریم بانک‌های چینی به دلیل ارتباطات با ایران اشاره کرد”.

Now Context:

Context: This marks a sharp escalation in Iranian rhetoric directly threatening the US president’s family. The Qatar meeting is a concrete diplomatic push — Doha has been mediating separately from stalled US-Iran talks. The fuel queues signal the economic pressure has reached ordinary Iranians; officials admitted prices “would have to change” without details. Trump’s energy-grid order cites a foreign threat, and his hint at sanctioning Chinese banks signals potential secondary sanctions escalation.

Translate:

زمینه: این نشانه‌ای از تشدید!* Wait, “Context:” -> “زمینه:”

“این نشان‌دهنده یک تشدید تیز در سوغات ایران است که مستقیماً خانواده رئیس‌جمهور آمریکا را تهدید می‌کند. جلسه قطر یک تلاشی دیپلماتیک عینی است — دوها به طور جداگانه از مذاکرات متوقف شده آمریکا و ایران واسطه‌گری می‌کند. صف‌های بنزین نشان می‌دهد که فشار اقتصادی به ایرانیان عادی رسیده است؛ مقامات اعتراف کردند قیمت‌ها «باید تغییر کنند» بدون جزئیات. دستور شبکه انرژی ترامپ به یک تهدید خارجی استناد می‌کند، و اشاره او به تحریم بانک‌های چینی سیگنال احتمالی تشدید تحریم‌های ثانویه است.”

Sources: list.

Second details block:

(Update) US missile interceptor stocks are “beyond critical” because of the Iran war, according to an Associated Press report citing NATO and US officials (Middle East Eye). [UNCONFIRMED]

Translate summary: “(به‌روزرسانی) ذخایر موشک‌های ماکت 미국 «فراتر از بحرانی» هستند به خاطر جنگ ایران، طبق یک گزارش Associated Press با استناد به مقامات ناتو و آمریکا (Middle East Eye).** [تأیید نشده]”

Context: “The report appears in both MEE’s live blog and a full article, citing AP interviews with NATO and US officials. It indicates the Iran campaign has depleted Patriot interceptor stocks faster than replenishment, leaving the US military in Europe with “very limited” capability to defend against ballistic missile strikes.”

Translate: “این گزارش در هر دو وبلاگ زنده MEE و یک مقاله کامل ظاهر شده، با استناد به مصاحبه‌های AP با مقامات ناتو و آمریکا. این نشان می‌دهد که кампین ایران ذخایر موشک‌های پاتریوت را سریع‌تر از تأمین مجدد خالی کرده، و نیروهای نظامی آمریکا در اروپا را با قابلیت «بسیار محدود» برای دفاع در برابر حملات موشکی بالیستیک رها کرده است.”

Sources.

Next section: ## Russia & Ukraine

Translate header: “## روسیه و اوکراین”

Details block summary: “Russia hit Kyiv with drones overnight, wounding about a dozen people across Ukraine (Euronews). [UNCONFIRMED]”

Translate: “روسیه کییف را با پهپادها در طول شب هدف قرار داد، حدود یک دژن نفر در سراسر اوکراین زخمی شدند (Euronews). [تأیید نشده]”

Context: “Part of the ongoing Russian air campaign targeting Ukrainian cities and infrastructure. Zelenskyy renewed calls for more ballistic missile defence systems from allies. The wounded count is preliminary.”

Translate: “بخش از کمپین هوایی در حال انجام روسیه که شهرها و زیرساخت‌های اوکراین را هدف قرار می‌دهد. زلنسکی مجدداً از متحدان خواستار سیستم‌های دفاع موشکی بالیستیک بیشتر شد. شمار زخمی‌ها اولیه است.”

Sources.

Next details block: “Five EU commissioners from eastern flank countries demanded von der Leyen create a special coordinator role for Russian threats to the Baltics (Euronews). [UNCONFIRMED]”

Translate: “پنج کمیسر اتحادیه اروپا از کشورهای بال الشرقي طلب کردند که فون در لاین نقش یک هماهنگ‌کننده ویژه برای تهدیدات روسی به کشورهای بلتیک را ایجاد کند (Euronews). [تأیید نشده]”

Context: “This follows reporting that the CIA director’s recent Moscow trip was likely about Iran, not a warning on Baltic aggression — per a former Estonian president. The eastern EU states feel the current structures aren’t enough.”

Translate: “این در پی گزارش‌هایی است که سفر اخیرديرکتور CIA به مسکو احتمالاً درباره ایران بوده، نه هشدار درباره تهاجم بلتیک — بر اساس گفته یک رئیس‌جمهور سابق استونی. کشورهای востоچ EU احساس می‌کنند ساختارهای فعلی کافی نیستند.”

Sources.

Next section: ## Gaza & Israel

Translate header: “## غزه و اسرائیل”

Details block summary: “Hamas says it’s accepted a disarmament plan for Gaza — lay down arms, Israeli troops withdraw — but BBC analysts say the obstacles are massive, with zero trust, thousands dead, and Israel simultaneously building new land barriers suggesting a long-term internal border (BBC). [UNCONFIRMED]”

Translate: “حماس می‌گوید یک برنامه نیرنگ‌سازی برای غزه را پذیرفته است — تسلیم سلاح،انسحاب نیروهای اسرائیلی — اما تحلیلگران BBC می‌گویند موانع عظیم هستند، با اعتماد صفر، هزاران مرده، و اسرائیل به طور همزمان در حال ساخت موانع زمینی جدیدی است که روی یک مرز داخلی بلندمدت اشاره دارد (BBC). [تأیید نشده]”

Context: “The roadmap exists on paper. Hamas says yes. Israel’s earthworks on the ground tell a different story. Bowen’s analysis: “rare hope” but “very complicated” — politics, war, and destruction make implementation a long shot.”

Translate: “فهرست راه‌حل روی کاغذ وجود دارد. حماس می‌گوید بله. کارهای زمینی اسرائیل در میدانی داستان دیگری را تعریف می‌کنند. تحلیل بوین: «امید نادر» اما «بسیار پیچیده» — سیاست، جنگ، و تخریب اجرا را به یک احتمال دور تبدیل می‌کنند.”

Sources.

Next details block: “Nearly 400 Palestinian children are currently held in Israeli prisons, a new report says (Middle East Eye). [UNCONFIRMED]”

Translate: “نزدیک به ۴۰۰ کودک فلسطینی در حال حاضر در زندان‌های اسرائیلی نگهداری می‌شوند، یک گزارش جدید می‌گوید (Middle East Eye). [تأیید نشده]”

Context: “The figure (~370) comes from a live blog update citing a report by the Palestinian Centre for Prisoners Advocacy. No independent verification in the feed.”

Translate: “این رقم (~۳۷۰) از یک به‌روزرسانی وبلاگ زنده با استناد به یک گزارش از مرکز فلسطینی برای حمایت از زندانیان می‌آید. تأیید مستقل در خوراک وجود ندارد.”

Sources.

Next section: ## Natural Disasters

Translate header: “## بلایای طبیعی”

Details block summary: “Flash floods from a glacial collapse killed nearly 400 people in Nepal and Tibet, with 90 Americans among the missing (NPR). [UNCONFIRMED]”

Translate: “سیل‌های ناگهانی ناشی از فروپاش یخچال تقریباً ۴۰۰ نفر را در نپال و تبت کشت، با ۹۰ آمریکایی در میان مفقودین (NPR). [تأیید نشده]”

Context: “Two NPR pieces confirm — one says nearly 400 dead, another says nearly 1,000 missing total (558 in Tibet per Xinhua, 162+ in Nepal). The glacial collapse triggered mudslides that hit the Nepal-Tibet border region hard.”

Translate: “دو گزارش NPR تأیید می‌کنند — یکی می‌گوید تقریباً ۴۰۰ نفر کشته شده‌اند، دیگری می‌گوید hampir ۱۰۰۰ نفر در کل مفقود هستند (۵۵۸ نفر در تبت بر اساس شینخوا، ۱۶۲+ در نپال). فروپاش یخچال گلل‌های خسی را تحریک کرد که منطقه مرزی نپال-تبت را به شدت هدف قرار داد.”

Sources.

Next details block: “Indonesia’s wildfires in West Kalimantan have created a health crisis — “everything is covered in ash,” pregnant women and children worst hit. Al Jazeera reporters documented kids struggling to breathe at clinics (Al Jazeera). [UNCONFIRMED]”

Translate: “آتش‌سوزی‌های جنگل در کلیمانتان غربی اندونزی یک بحران بهداشتی ایجاد کرده‌اند — «همه جا خاکستر است»، زنان باردار و کودکان بدترین ضربه را دیده‌اند. گزارشگران Al Jazeera کودکان را در کلینیک‌ها در حال تنفس دشوار ثبت کرده‌اند (Al Jazeera). [تأیید نشده]”

Context: “Two Al Jazeera pieces — one news, one video report from the ground. Smoke exposure is severe; the fires are ongoing.”

Translate: “دو قطعه Al Jazeera — یکی خبر، یکی گزارش ویدیویی از میدانه. تعرض دود شدید است؛ آتش‌سوزی‌ها ادامه دارند.”

Sources.

Next section: ## Tech & Business

Translate header: “## تکنولوژی و کسب‌وکار”

Details block summary: “Meta agreed to a $17 billion settlement with states that sued the company. Separately, US nuclear regulators are preparing to abandon a decades-old radiation safety rule (NPR). [UNCONFIRMED]”

Translate: “متا با تحقيق یک توافق ۱۷ میلیارد دلاری با ایالتی که شرکت را شکایت کرده بودند موافقت کرد. جداگانه، نظارت‌های هسته‌ای آمریکا در حال آماده‌سازی برای رها کردن یک قانون ایمنی радиاسیون چند دهه‌ای هستند (NPR). [تأیید نشده]”

Context: “The Meta settlement is one of the largest ever. The NRC rule change on radiation safety is a separate story in the same newsletter.”

Translate: “توافق متا یکی از بزرگترین‌ها تا به حال است. تغییر قانون NRC در مورد ایمنی радиاسیون یک داستان جداگانه در همان خبرنامه است.”

Sources.

Next details block: “EU’s new €3 customs duty on sub-€150 parcels has cut Chinese small-package imports 30–40% since July 1. The measure is biting faster than expected (Euronews). [UNCONFIRMED