fix(parse/html): astro fence

[ematipico]

Summary

Closes #8882
Closes #9108
Closes #9125

The code was generated via Claude Code. It suggested a different approach to the solution.

Test Plan

Added more tests.

Docs

[changeset-bot]

🦋 Changeset detected

Latest commit: 9ff934a

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 13 packages

Name	Type
@biomejs/biome	Patch
@biomejs/cli-win32-x64	Patch
@biomejs/cli-win32-arm64	Patch
@biomejs/cli-darwin-x64	Patch
@biomejs/cli-darwin-arm64	Patch
@biomejs/cli-linux-x64	Patch
@biomejs/cli-linux-arm64	Patch
@biomejs/cli-linux-x64-musl	Patch
@biomejs/cli-linux-arm64-musl	Patch
@biomejs/wasm-web	Patch
@biomejs/wasm-bundler	Patch
@biomejs/wasm-nodejs	Patch
@biomejs/backend-jsonrpc	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[coderabbitai]

Walkthrough

This PR updates the Astro frontmatter lexer to reliably detect the closing --- fence when frontmatter contains comments, mixed-quote strings or escaped quotes. It adds a unified QuotesSeen state machine and QuotesSeenComment enum to track current quote, escape state and comment context; replaces ad-hoc per-quote tracking; and broadens tests covering multi-line/single-line comments, mixed quotes and escape edge cases (addresses issues #8882 and #9108). No public API changes.

Possibly related PRs

• fix(html): fix comment detection in Astro frontmatter #7989: Modifies the same QuotesSeen logic in crates/biome_html_parser/src/lexer/mod.rs to fix comment detection and fence recognition.
• fix(html): parse frontmatter inside quotes #7907: Introduces a QuotesSeen quote-tracking helper and tests in the HTML parser lexer to improve Astro frontmatter quote/comment handling.

Suggested reviewers

• dyc3

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'fix(parse/html): astro fence' is concise and directly references the main change—fixing Astro frontmatter fence detection in the HTML parser.
Linked Issues check	✅ Passed	The PR addresses both linked issues: #8882 (multi-line comments in frontmatter) and #9108 (unclosed quotes in strings) through lexer state machine improvements to properly track quotes and comments.
Out of Scope Changes check	✅ Passed	All changes directly support the objectives: the lexer refactor handles quote/comment tracking, new test files validate the fixes, and the changeset documents the patch release.
Description check	✅ Passed	The PR description clearly relates to the changeset, addressing Astro frontmatter fence detection issues with specific issue references and test additions.

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

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/astro-fence-lexing

---

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

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@crates/biome_html_parser/src/lexer/mod.rs`:
- Around line 1505-1508: The is_empty() method currently only checks
current_quote and therefore treats being inside a comment as "empty"; update
is_empty() to also consider comment state so that being inside a comment counts
as non-empty. Specifically, modify fn is_empty(&self) -> bool in the lexer to
return true only when self.current_quote.is_none() AND whatever field tracks
comments (e.g. self.comment / self.current_comment / self.in_comment) indicates
not in a comment, so that frontmatter fences like '---' inside comments won't be
treated as closing.

[codspeed-hq]

Merging this PR will not alter performance

✅ 4 untouched benchmarks
⏩ 152 skipped benchmarks¹

---

_{Comparing fix/astro-fence-lexing (9ff934a) with main (aa40fc2)}

Footnotes

1. 152 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

[ematipico]

Going to merge this, let me know if there are any concerns and i will address them