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

Inline comments:
In `@docs/head/1.guides/build-plugins/0.overview.md`:
- Around line 87-95: The docs list a devtools option but the plugin types lack
it; either remove the `devtools` row and the related bulleted reference in the
overview documentation, or add `devtools` to the plugin API by extending the
VitePluginOptions interface with a `devtools?: boolean | object` (or appropriate
type) and update the plugin implementation to read and honor this option
(references: VitePluginOptions and the plugin's option-handling logic).

In `@docs/head/1.guides/build-plugins/1.tree-shaking.md`:
- Around line 63-73: The example uses the old default name unhead but the
library now exports the named constructor Unhead; update the snippet to call
Unhead({...}) instead of unhead({...}) so the example matches the new named
export (reference the Unhead function in the docs snippet and replace any
occurrences of unhead with Unhead).

In `@docs/head/1.guides/build-plugins/2.seo-meta-transform.md`:
- Around line 59-73: The example uses the old lowercase factory name `unhead`;
update it to the new named export `Unhead` so the snippet matches the PR's named
export convention—replace the `unhead({...})` invocation with `Unhead({...})` in
the `transformSeoMeta` example and ensure the rest of the options (`imports`,
`importPaths`, `filter`) remain unchanged.

In `@docs/head/1.guides/build-plugins/3.minify-transform.md`:
- Around line 71-85: The example uses the wrong function name casing: change the
call from unhead({...}) to the named export Unhead({...}) so the code example
matches the current API (replace the identifier "unhead" with "Unhead" in the
minify example block).

In `@docs/head/1.guides/plugins/6.template-params.md`:
- Around line 20-21: The docs import the non-existent package
'@unhead/dynamic-import'; replace it by importing TemplateParamsPlugin from
'unhead/plugins' and import createHead from the appropriate entry for the
intended runtime: use 'unhead/server' if this guide is server-side or
'unhead/client' (or framework-specific client like 'unhead/vue/client' or
'unhead/react/client') if it’s client-side; update the example imports for
createHead and TemplateParamsPlugin (referencing createHead and
TemplateParamsPlugin) to use those real package paths so the snippet matches the
target runtime.

In `@docs/head/1.guides/plugins/canonical.md`:
- Line 57: The doc examples use two different import paths for CanonicalPlugin;
standardize them to the actual plugin location by replacing imports like "import
{ CanonicalPlugin } from '@unhead/dynamic-import/plugins'" with "import {
CanonicalPlugin } from 'unhead/plugins'" wherever CanonicalPlugin is referenced
(e.g., the examples around the current imports and later examples), ensuring all
occurrences use the single canonical path "unhead/plugins".

In `@docs/head/1.guides/plugins/infer-seo-meta-tags.md`:
- Line 48: The documentation import for InferSeoMetaPlugin is wrong; update the
import statement that currently references `@unhead/dynamic-import/plugins` to
import InferSeoMetaPlugin from unhead/plugins instead so the symbol
InferSeoMetaPlugin resolves correctly in examples and avoids import errors for
users.

In `@docs/head/1.guides/plugins/minify.md`:
- Line 25: The import paths in the docs are wrong: replace any imports
referencing '@unhead/dynamic-import/plugins' and '@unhead/dynamic-import/minify'
with the correct unscoped package imports (e.g., change the import that brings
in MinifyPlugin from '@unhead/dynamic-import/plugins' to import it from
'unhead/plugins', and similarly change any imports for minify utilities from
'@unhead/dynamic-import/minify' to 'unhead/minify'); update all occurrences in
this guide so symbols like MinifyPlugin and any minify-related identifiers
import from 'unhead' subpaths rather than the non-existent scoped package.

In `@docs/head/1.guides/plugins/validate.md`:
- Line 26: The import path for ValidatePlugin is incorrect — update the import
statement that currently references ValidatePlugin from
'@unhead/dynamic-import/plugins' to import ValidatePlugin from 'unhead/plugins';
search for other occurrences of '@unhead/dynamic-import/*' in docs and replace
them with the corresponding 'unhead/*' plugin imports to avoid "package not
found" errors.

In `@docs/head/7.api/composables/0.use-head.md`:
- Line 370: Update the TypeScript example imports that currently reference the
non-existent path '@unhead/dynamic-import/types' so they import the types from
'unhead/types' instead; specifically change the imports for GenericLink and
GenericScript to use 'unhead/types' (replace the import source for the
GenericLink and GenericScript type imports).

In `@docs/head/7.api/plugins.md`:
- Around line 30-38: The example incorrectly calls head.resolveTags(); change it
to use the utility function resolveTags(head) instead: update the hook in
defineHeadPlugin (the 'entries:updated' handler) to call resolveTags(head) and
ensure you add the import for resolveTags from 'unhead/utils'; remove the
incorrect head.resolveTags() usage and replace it with resolveTags(head) so the
example matches the actual API.

In `@packages/bundler/src/unplugin/CreateHeadTransform.ts`:
- Around line 71-77: The current matching uses only the callee name and causes
false positives; update CreateHeadTransform.ts so before using HEAD_FACTORIES
you verify the callee actually refers to an import from Unhead: when callee is
an Identifier, resolve its binding via path.scope.getBinding(callee.name) and
ensure the binding.path is an ImportSpecifier/ImportDefaultSpecifier whose
parent.source.value matches Unhead module names; when callee is a
MemberExpression, ensure the object is an Identifier bound to an
ImportNamespaceSpecifier from an Unhead source and the property.name matches a
HEAD_FACTORIES entry; only proceed with rewriting/injecting imports/plugins if
the binding origin confirms the symbol comes from Unhead.

In `@packages/bundler/src/unplugin/SSRStaticReplace.ts`:
- Around line 43-48: The vite plugin's apply hook currently returns false which
disables the plugin; update the vite.apply implementation so that when
env.isSsrBuild sets ssr = true the hook returns true (not false) to allow the
plugin to run during SSR builds; locate the vite: { apply(_config: UserConfig,
env: ConfigEnv) { ... } } block and change the return value so the plugin is
enabled (preserve the ssr side effect on the ssr variable).

---

Outside diff comments:
In `@docs/0.angular/schema-org/guides/get-started/0.installation.md`:
- Line 138: The documentation line containing the phrase "Your Nuxt app is now
serving basic Schema.org" is incorrect for the Angular guide; update that
sentence to reference Angular (e.g., "Your Angular app is now serving basic
Schema.org") so the guide consistently refers to Angular. Locate the exact
string "Your Nuxt app is now serving basic Schema.org" in the get-started
installation content and replace "Nuxt" with "Angular" (or reword to "Your
Angular app") to correct the copy-paste error.

In `@docs/head/7.api/composables/3.use-seo-meta.md`:
- Around line 27-28: The docs import is using a non-existent package; update the
import sources for useSeoMeta so examples import from the correct package: for
framework-agnostic examples import useSeoMeta from "unhead", and for
framework-specific examples import useSeoMeta from "@unhead/vue",
"@unhead/react", or "@unhead/solid-js" respectively (apply this change to the
instances showing useSeoMeta at the Basic Usage / Complete SEO Setup and the
Vue/React/Solid example sections).

In `@packages/bundler/src/unplugin/UseSeoMetaTransform.ts`:
- Line 48: The options.imports assignment currently uses truthy fallback which
ignores an explicit false; update the assignment in UseSeoMetaTransform (where
options.imports is set) to use nullish coalescing so explicit false is honored
(e.g., replace "options.imports = options.imports || true" with "options.imports
= options.imports ?? true" or equivalent) and ensure the rest of the code treats
false as a valid value.

---

Duplicate comments:
In `@docs/head/1.guides/plugins/infer-seo-meta-tags.md`:
- Line 101: The import for InferSeoMetaPlugin is using the wrong module path;
replace the import statement that references '@unhead/dynamic-import/plugins'
with the correct 'unhead/plugins' path so that the symbol InferSeoMetaPlugin is
imported from unhead/plugins (this is a duplicate of the earlier incorrect
import near line 48, so update both occurrences).

---

Nitpick comments:
In `@docs/head/7.api/plugins.md`:
- Line 6: Update the phrasing "hooks based architecture" to the hyphenated form
"hooks-based architecture" in the Unhead description so the compound modifier is
grammatically correct; locate the sentence starting with "Unhead uses a hooks
based architecture" and replace it with "Unhead uses a hooks-based architecture"
(preserving the rest of the sentence and the reference to unjs/hookable).

In `@packages/bundler/src/unplugin/CreateHeadTransform.ts`:
- Around line 93-95: The loop that calls s.prepend for each entry in
envRegistrations can emit duplicate import lines; before the for-loop dedupe
entries by their import alias and source (use reg.import.as and
reg.import.source as the uniqueness key), collect unique registrations, then
iterate that deduped list to call s.prepend so each import statement is emitted
only once; update the code referencing envRegistrations, reg.import.name,
reg.import.as and reg.import.source accordingly.

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

Inline comments:
In `@docs/6.migration-guide/1.v3.md`:
- Around line 69-76: The fenced code block inside the ::tip admonition is
missing a blank line after the closing ``` fence which violates MD031; update
the ::tip block around the shown fenced block (the block containing import {
Unhead } from '@unhead/vue/vite') so there is an empty line after the closing
``` and ensure there is a blank line before and after the fenced code block
within the ::tip so the closing fence is followed by a blank line before the
terminating :: marker.

In `@docs/head/7.api/plugins.md`:
- Line 6: Replace the phrase "hooks based" with the hyphenated compound
adjective "hooks-based" in the sentence that reads "Unhead uses a hooks based
architecture powered by unjs/hookable" so the line becomes "Unhead uses a
hooks-based architecture powered by unjs/hookable" to improve grammar and
readability.

---

Duplicate comments:
In `@packages/bundler/src/unplugin/CreateHeadTransform.ts`:
- Around line 61-63: The rewrite currently matches calls by identifier name only
(using directCreateHeadNames / namespaceNames) and rewrites shadowed local
bindings; change the transform to resolve each callsite's binding before
rewriting: for Identifier calls (createHead) use the AST traversal path to get
the binding (e.g., path.scope.getBinding(id.name)) and verify the binding is the
import from `@unhead/`* (check binding.path.isImportSpecifier /
binding.path.parent.source.value), and for namespace calls check the object
identifier's binding similarly to ensure it’s the imported namespace; skip
rewriting when no binding or when the binding is a local shadow so only true
imports from `@unhead/`* trigger the injection.

---

Nitpick comments:
In `@packages/bundler/src/unplugin/SSRStaticReplace.ts`:
- Around line 39-47: The plugin currently only flips the shared ssr flag to
true, allowing stale state between runs; update the webpack hook and vite.apply
to assign ssr explicitly instead of only setting true: in the webpack(ctx)
function set ssr = (ctx.name === 'server'), and in vite.apply(_config:
UserConfig, env: ConfigEnv) set ssr = env.isSsrBuild so each invocation
deterministically sets SSR mode for this plugin instance.

In `@packages/bundler/test/createHeadTransform.test.ts`:
- Around line 135-140: The test for shadowing in createHead is incomplete
because it only checks a local-only definition; add a variant where createHead
is also imported (e.g., import { createHead } from '@unhead/some' or similar)
and then a local function createHead() shadows that import to ensure the
transform (created via createPlugin and accessed as transform) does not rewrite
the local symbol; update the test in createHeadTransform.test.ts to call
transform with source containing both the import and the local createHead
declaration and assert the result remains undefined, using the same
createPlugin/test harness (createPlugin, transform) as the existing test.