chore: manual sync

[dyc3]

Summary

[netlify]

✅ Deploy Preview for biomejs ready!

Name	Link
🔨 Latest commit	e0ee7d9
🔍 Latest deploy log	https://app.netlify.com/projects/biomejs/deploys/698224a5a15b6b0008f4bc3f
😎 Deploy Preview	https://deploy-preview-3902--biomejs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[coderabbitai]

Walkthrough

This PR: (1) repins Biome crate git revisions in Cargo.toml and updates the @biomejs/wasm-web devDependency in package.json to a newer commit; (2) adds several new linter rules (metadata, MDX docs, examples, and rules.json entries); (3) updates redirects.js with new route mappings; and (4) extends codegen Markdown handling to accept block-level HTML events. No public API signatures were altered.

Possibly related PRs

• chore: fix sync job #3879: Similar workspace dependency repins and additions to linter docs/redirects — strong overlap in files changed.
• feat: codegen and domains #3795: Edits to codegen (lintdoc) and dependency rev bumps — directly related to the codegen/src/lintdoc.rs change.
• chore: fix lockfile #3777: Updates the @biomejs/wasm-web devDependency to the same commit hash — directly related dependency bump in package.json.

Suggested reviewers

• ematipico

🚥 Pre-merge checks | ❌ 2

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description is completely empty except for a template placeholder, providing no information about the changes or motivation.	Add a meaningful description explaining what's being synced, why it matters, and what new rules are being added.
Title check	❓ Inconclusive	The title 'chore: manual sync' is vague and doesn't clearly convey the main changes—adding seven new linter rules and updating Biome dependencies.	Consider a more descriptive title like 'chore: add new linter rules and update Biome dependencies' to better reflect the substantive changes.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch dyc3/manual-sync

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ast-grep (0.40.5)

src/pages/metadata/rules.json.js

Important

Action Needed: IP Allowlist Update

If your organization protects your Git platform with IP whitelisting, please add the new CodeRabbit IP address to your allowlist:

• ✨ 136.113.208.247/32 (new)
• 34.170.211.100/32
• 35.222.179.152/32

Failure to add the new IP will result in interrupted reviews.

---

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

[dyc3]

The codegen is expected to fail here temporarily, I have another PR in the main repo to resolve it after this is merged.

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@src/content/docs/linter/rules/no-hex-colors.mdx`:
- Around line 82-86: Update the broken relative link in the Related links list:
replace the string '/linter#configure-the-code-fix' with
'/linter/#configure-the-code-fix' so the "Configure the code fix" link matches
the anchor used elsewhere (update the link in the block containing the three
bullet items).

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Fix the missing slash in the “Configure the code fix” link. Line 85 uses /linter#configure-the-code-fix, which won’t match the anchor used elsewhere; it should be /linter/#configure-the-code-fix.

🩹 Suggested fix

- [Configure the code fix](/linter#configure-the-code-fix)
+ [Configure the code fix](/linter/#configure-the-code-fix)

🤖 Prompt for AI Agents

In `@src/content/docs/linter/rules/no-hex-colors.mdx` around lines 82 - 86, Update
the broken relative link in the Related links list: replace the string
'/linter#configure-the-code-fix' with '/linter/#configure-the-code-fix' so the
"Configure the code fix" link matches the anchor used elsewhere (update the link
in the block containing the three bullet items).