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

Inline comments:
In `@crates/biome_service/src/file_handlers/html.rs`:
- Around line 1788-1789: The update_snippets branch is using
html_string_literal(snippet.new_code.as_str()) which always emits double-quoted
literals and can break attributes that used single quotes; fix by making the
helper quote-aware or escaping inner quotes before wrapping: inspect the
original attribute quote style from value_token (or the node/attribute context)
and either call the existing html_string_literal_single_quotes() when the
original used single quotes or extend html_string_literal to accept a quote
parameter and pass the detected quote char, then call
mutation.replace_token(value_token, new_token) with the correctly quoted/escaped
new_token (or escape inner quotes in snippet.new_code when you must keep double
quotes). Ensure changes touch html_string_literal (and optionally add a
signature compatible with html_string_literal_single_quotes) and the
update_snippets branch where snippet.new_code is converted so attribute quoting
is preserved.

In `@crates/biome_service/src/file_handlers/tailwind.rs`:
- Around line 167-170: The ParserCapabilities block in tailwind.rs currently
leaves parse and parse_embedded_nodes as None, so downstream code cannot obtain
a TwRoot; replace those Nones with the Tailwind parser functions (e.g. set parse
= Some(parse_tailwind) and parse_embedded_nodes = Some(parse_tailwind_embedded)
or the actual parse_tailwind* helpers you have) where ParserCapabilities is
constructed so the handler can produce TwRoot for the lint/code-action/fix-all
paths and the new tailwind ruledoc source.

In `@crates/biome_service/src/settings.rs`:
- Line 733: The new tailwind field (LanguageSettings<TailwindLanguage>) was
added but OverrideSettings::override_analyzer_rules() still only merges
JS/JSON/CSS/GraphQL/HTML metadata so Tailwind overrides are ignored; update
OverrideSettings::override_analyzer_rules() to include Tailwind in the merge
logic and in any pattern-matching/enable/disable code paths (where
JS/JSON/CSS/GraphQL/HTML are handled) so that rules under languages.tailwind are
applied for matching paths, referencing the tailwind field and the
OverrideSettings::override_analyzer_rules() function to locate where to add the
merge/override handling.

In `@crates/biome_service/src/workspace/server.rs`:
- Around line 755-798: The current loop handling embedded_snippets calls
fix_file_with_embeds and then extends results.actions and uses
document_services, which is wrong because actions' ranges are in snippet-local
coordinates and snippet-specific services should be used; update the loop in
parse_embedded_language_snippets handling so that for each embedded_snippet you
(1) obtain the snippet-local services from the snippet (use
embedded_snippet.parse() / embedded_snippet.file_source_index() to find them)
and pass those services into fix_file_with_embeds instead of the outer
document_services, and (2) when merging results.actions into actions, map/offset
each action's range by embedded_snippet.content_offset() so the reported spans
are shifted into host file coordinates before extending actions (keep creating
UpdateSnippetsNodes with results.code as before).

In
`@crates/biome_tailwind_analyze/src/lint/nursery/use_tailwind_shorthand_classes.rs`:
- Around line 433-450: The current all-or-nothing logic for
effective_replacement_bases drops every replacement base if any one of them
already exists in the class list; change this to produce a filtered list of only
the missing bases: iterate replacement_bases and keep only those rb for which
candidates does NOT contain a TwFunctionalCandidate or TwStaticCandidate whose
base_token().text_trimmed() == rb, then use that filtered collection as
effective_replacement_bases (or set to &[] only if the filtered collection is
empty). Update the construction of effective_replacement_bases and, if needed,
the surrounding types so you can return either the filtered Vec/borrowed slice
or an empty slice while preserving the existing code paths that consume
effective_replacement_bases; reference replacement_bases,
effective_replacement_bases, candidates, AnyTwCandidate, TwFunctionalCandidate
and TwStaticCandidate when locating the change.
- Around line 309-313: The special-case branch that returns
Some(TailwindShorthandViolation { uncompressed_nodes: matched,
replacement_bases: &["truncate"], replace_whole_node: true }) must skip emitting
a replacement when the shorthand "truncate" is already present in the matched
nodes; add the same “shorthand already present” guard used by the generic path
to inspect matched (or uncompressed_nodes) for an existing "truncate" class and
return None (or fall through) instead of returning the violation, so you don't
produce "truncate truncate".

In `@crates/biome_tailwind_analyze/src/suppression_action.rs`:
- Around line 10-12: The default SuppressionAction inserts a comment trivia at
token start which breaks Tailwind syntax; add an override of
apply_top_level_suppression(&self, _node: &JsSyntaxNode, _suppression_text:
&str) -> Option<JsSyntaxToken> in the Tailwind implementation to be a no-op
(return None) similar to the existing apply_inline_suppression() override, and
keep suppression_top_level_comment() unchanged or unused; ensure the method
signature matches the SuppressionAction trait so the default behavior is
suppressed for Tailwind.

---

Outside diff comments:
In `@crates/biome_service/src/file_handlers/html.rs`:
- Around line 1377-1382: The snippet is currently created with
EmbeddedSnippet::new using value.range(), but update_snippets() only rewrites
keys for AnyEmbeddedContent, HtmlAttribute, and HtmlTextExpression so directive
attribute initializers (e.g. `@click`="...", :prop="...", v-if="...") are lost;
fix by keying EmbeddedSnippet instances to the owning attribute (the
HtmlAttribute node) instead of value.range(), or alternatively add a matching
branch for HtmlAttributeInitializerClause in update_snippets() so it recognizes
and rewrites snippets created from value.range(); update the creation site
(EmbeddedSnippet::new call) and the update_snippets() matcher to use the same
unique identifier (owner attribute node id or HtmlAttributeInitializerClause) so
directive attribute snippets persist on write-back.

In `@crates/biome_service/src/file_handlers/mod.rs`:
- Around line 1088-1133: The Tailwind analyzer was wired into Features
(TailwindFileHandler) but missing registry visitor implementations and registry
calls; add RegistryVisitor<TailwindLanguage> impls for SyntaxVisitor,
LintVisitor, and AssistsVisitor following the same pattern used for
CssLanguage/JsonLanguage (use AnalyzerVisitorBuilder with TailwindLanguage), and
ensure you call biome_tailwind_analyze::visit_registry(&mut registry) inside
each of the three registry-building functions that build the lint/fix/assists
registries (the same locations where other languages call their visit_registry
functions). This will register Tailwind rules from biome_tailwind_analyze so
lint, fix, and code-action passes see Tailwind files.

---

Nitpick comments:
In `@crates/biome_cli/tests/cases/tailwind.rs`:
- Around line 137-145: The Svelte test lacks the direct file-content assertion
present in the JS/HTML tests; after verifying result.is_ok() in the
should_apply_tailwind_shorthand_fixes_in_svelte test, open the rewritten Svelte
file from the test fs and assert its contents match the expected rewritten
content (the same check used in the JS/HTML cases) before calling
assert_cli_snapshot(SnapshotPayload::new(...)); this ensures a fast, explicit
failure when the file rewrite is incorrect while preserving the existing
snapshot call.

In `@crates/biome_tailwind_analyze/build.rs`:
- Line 37: The function signature for touch_file currently takes a &PathBuf
which is less flexible; change the parameter to accept &Path instead (fn
touch_file(path: &Path) -> io::Result<()>) and update any call sites to pass
&path or path.as_path() as needed; inside touch_file, update any uses that
required PathBuf methods to use Path-compatible methods or clone into a PathBuf
only when necessary (refer to the touch_file symbol to locate and adjust the
function and its callers).

In `@crates/biome_tailwind_parser/src/lib.rs`:
- Around line 96-107: The conversion currently calls parse.syntax() then
consumes parse with parse.into_diagnostics(), causing an unnecessary clone of
the root; change the From<TailwindParse> for AnyParse::from implementation to
consume TailwindParse and extract both the root node and diagnostics in one move
(destructure the TailwindParse value or use an API that returns both parts) and
pass the owned root into NodeParse::new (instead of calling syntax() on a
borrowed parse), and apply the same destructuring change to the other similar
impl at the 162-173 range so neither conversion clones the root.