fix: flatten Event Loop section, repair broken RU network translations

[Faustze]

Summary

• content/browser/Event Loop/ was just a two-page wrapper folder with its own index.md. Flattened it: Rendering Pipeline.md and Event Loop, Microtasks, Macrotasks.md now live directly under content/browser/ (and content-ru/browser/), and the redundant index was removed.
• Updated every wikilink accordingly, including two stale links that still pointed at the pre-rename Event Loop/Event Loop filename (missed by an earlier rename sync).
• content-ru/browser/Network/HTTP Headers & Caching.md was wrapped in a stray ```markdown code fence around the entire file — removed.
• content-ru/browser/Network/TCP & TLS Handshake.md contained a leaked raw claude CLI agent transcript (tool calls, JSON payloads) instead of the actual translation — replaced with a clean translation of the current content/ source.
• Updated .translation-manifest.json hashes for the moved/edited source files so translate:check doesn't flag false staleness.

Test plan

• npm run translate:check reports content-ru/ up to date
• npm run check (tsc + prettier) passes
• Manually reviewed both RU files render as normal prose, not raw fences/transcripts

[coderabbitai]

Warning

Review limit reached

@Faustze, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 24 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 8444835e-4a56-44fc-b6e8-26e3d258de45

📥 Commits

Reviewing files that changed from the base of the PR and between 4cc2055 and c216adb.

📒 Files selected for processing (11)

• content-ru/.translation-manifest.json
• content-ru/browser/Event Loop, Microtasks, Macrotasks.md
• content-ru/browser/Event Loop/index.md
• content-ru/browser/Network/HTTP Headers & Caching.md
• content-ru/browser/Network/TCP & TLS Handshake.md
• content-ru/browser/Rendering Pipeline.md
• content-ru/browser/index.md
• content/browser/Event Loop, Microtasks, Macrotasks.md
• content/browser/Event Loop/index.md
• content/browser/Rendering Pipeline.md
• content/browser/index.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/browser-notes-translation-and-structure

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}