Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@projects/site/package.json`:
- Around line 204-211: The current package.json test task watches all source
files via the "files" array which causes tests defined in the "command" (e.g.,
metadata.test.ts, links.test.ts, site-urls.test.ts, api.test.ts) to re-run on
any src change; update the "files" array to only match test files (for example
restrict to patterns like src/**/*.{test,spec}.ts or src/**/*.test.ts and
include matching .js/.md if you have test variants) so that vitest only reruns
when test files change, leaving the "command" unchanged.

In `@projects/site/src/_11ty/layouts/links.test.ts`:
- Around line 6-9: The four regex constants RELATIVE_INTERNAL_LINK_PATTERN,
BASE_PREFIXED_INTERNAL_LINK_PATTERN, JS_RELATIVE_INTERNAL_LINK_PATTERN, and
JS_BASE_PREFIXED_INTERNAL_LINK_PATTERN only account for "./" relative paths;
update each pattern to also match one or more "../" segments so "../docs/...",
"../examples/...", and "../starters/..." are caught too — modify the group that
currently matches (?:\.\/)? to allow sequences like (?:\.\.\/|\.\/)+ or a more
concise (?:\.\.\/)*\.\/? depending on desired strictness so both single and
multi-level parent traversals are rejected for both HTML and JS forms.

In `@projects/site/src/docs/metrics/testing-and-performance.11ty.js`:
- Around line 29-32: Remove the duplicate selected attribute from the wrong tab:
the first <nve-tabs-item> that links to "/docs/metrics/" currently has selected
but the page's correct active tab is the <nve-tabs-item> for "Testing &
Performance" (the one linking to "/docs/metrics/testing-and-performance/");
remove the selected attribute from the Metrics tab so only the Testing &
Performance <nve-tabs-item> remains selected to prevent conflicting active-state
behavior.

In `@projects/site/src/docs/metrics/wireit.11ty.js`:
- Line 59: Duplicate selected attribute: remove the extra selected on the
Metrics tab so only the Wireit Explorer tab remains selected. Locate the
<nve-tabs-item> element that renders the "Metrics" tab (the tag containing "<a
href=\"/docs/metrics/\">Metrics</a>") and delete the selected attribute from
that element, leaving the selected attribute only on the "Wireit Explorer"
<nve-tabs-item>.

---

Outside diff comments:
In `@projects/site/src/_11ty/layouts/docs.11ty.js`:
- Around line 50-54: The code builds baseTabUrl by stripping the leading '/'
from data.page.url then later prepends '/' again when creating hrefs; to
simplify, stop removing the leading slash: remove the initial .replace('/', '')
from the baseTabUrl expression (leave data.page.url as-is when applying the
subsequent .replace('/api/', '/'), .replace('/examples/', '/'), and
.replace(/(.*\/data-grid\/).+/, '$1')), and update all call sites that currently
do href="/${baseTabUrl}" to use href="${baseTabUrl}" (references: the baseTabUrl
variable and the href usages that add '/').

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@projects/site/src/_11ty/layouts/common.js`:
- Around line 132-396: In the renderDocsNav function, there are two issues to
fix. First, remove the dead code pattern in the first nve-tree-node where the
expanded attribute checks include a redundant `/./` pattern that never occurs
naturally in URLs. The check `data.page.url.includes('/./') || data.page.url ===
'/'` should be simplified to just `data.page.url === '/'` since the OR condition
with the root path already handles all necessary cases. Second, fix the path
inconsistency in the final nve-tree-node for the Internal Examples section where
the URL checks use `'examples/'` without a leading slash, but the href attribute
uses `'/examples/'` with a leading slash. Update all the URL check patterns in
this section to use `'/examples/'` with a leading slash to be consistent with
how all other navigation sections check their paths (e.g.,
`includes('/docs/...')`).

In `@projects/site/src/_11ty/transforms/site-urls.test.ts`:
- Around line 94-121: The test cases for siteUrlsTransform in the test file
currently only cover module scripts with type="module" attributes, leaving
non-module script URL rewriting behavior untested. Add test assertions within
one or both of the existing test cases (the production output test and the local
preview test) that verify the expected behavior when a regular non-module script
tag with a src attribute is processed by siteUrlsTransform. Include an assertion
that confirms the URL transformation for a non-module script follows the same
transformation rules as the other assets being tested.

In `@projects/site/src/docs/about/support.md`:
- Line 31: The Lit button on line 31 has a closing `</a>` tag without a
corresponding opening `<a>` tag, breaking the link functionality. Add an opening
`<a>` tag with href="/docs/integrations/lit/" before the svg-logo template tag
in the Lit button element to properly pair with the existing closing `</a>` tag
and match the structure of the other framework buttons (TypeScript, Angular,
Vue, Preact) which all have properly formed anchor links.

In `@projects/site/src/docs/foundations/layout/index.md`:
- Around line 102-104: The anchor reference in the link pointing to
`/docs/api-design/styles/#internal-host` is incorrect because the actual heading
in the styles documentation is `## **_REMOVED_** Host`, not `## Internal Host`.
Update the anchor portion of this link to match the actual heading structure in
the styles documentation so it resolves correctly. Verify what the actual anchor
should be based on the current heading in that document and correct the
reference accordingly.

In `@projects/site/src/docs/foundations/popovers.md`:
- Line 15: Fix the hyphenation in two compound adjectives in the popovers.md
documentation. In the tooltip link description, change "contextual text only
hints" to "contextual text-only hints" by adding a hyphen between "text" and
"only". Additionally, in the notification-related text, change "async non
contextual notification" to "async non-contextual notification" by adding a
hyphen between "non" and "contextual". These hyphens are necessary because the
adjectives modify the nouns that follow them as compound modifiers.

In `@projects/site/src/docs/internal/guidelines/testing.md`:
- Line 44: All the markdown links in the test type list (lines 41-45) are using
incorrect paths pointing to `/docs/internal/testing/*/` which doesn't exist.
Update all five links to use the correct path structure
`/docs/internal/guidelines/testing-*/` instead. Specifically, ensure line 44
updates the Visual Regression Tests link from `/docs/internal/testing/ssr/` to
`/docs/internal/guidelines/testing-visual/`, and apply similar corrections to
the other test type links on lines 41, 42, 43, and 45 by replacing the
`/docs/internal/testing/` portion with `/docs/internal/guidelines/testing-` in
each link.

---

Duplicate comments:
In `@projects/site/src/docs/metrics/testing-and-performance.11ty.js`:
- Around line 29-34: The first nve-tabs-item element with href="/docs/metrics/"
has a duplicate selected attribute that should not be there. Remove the selected
attribute from the first nve-tabs-item element (Metrics tab) so that only the
third nve-tabs-item element with href="/docs/metrics/testing-and-performance/"
(Testing & Performance tab) retains the selected attribute, ensuring only the
current page's tab is marked as selected.

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@projects/core/src/tabs/tabs.examples.ts`:
- Around line 148-154: The `@summary` documentation for this tabs example in
projects/core/src/tabs/tabs.examples.ts is inaccurate—it claims to demonstrate
routing-based tab switching and page navigation, but the code only uses
hash-only anchors (href="`#links`") which enable same-page fragment scrolling, not
routing or page navigation. Update the `@summary` tag that precedes this example
to correctly state "Tabs with hash-only anchor links for same-page navigation
and fragment scrolling within a single page" to accurately reflect the actual
functionality and prevent users from misapplying this pattern.

In `@projects/site/eleventy.config.js`:
- Around line 227-236: The `.filter(page => page.data.tag)` condition in the
componentDocs collection is filtering out all component documentation pages
since none of the files in the src/docs directories have a tag property in their
frontmatter, resulting in an empty collection that breaks API documentation
generation. Either remove the entire .filter(page => page.data.tag) filter from
the chain after getFilteredByGlob to restore all documentation files to the
collection, or systematically add a tag property to the frontmatter of all
component documentation files across the src/docs/elements/, src/docs/code/,
src/docs/monaco/, and src/docs/markdown/ directories.

In `@projects/site/src/_11ty/plugins/llms-txt.js`:
- Around line 52-69: In the createLlmsTxtContent function, the MCP entry on the
line containing [MCP] is incorrectly pointing to the CLI documentation path
instead of a dedicated MCP context file. Fix this by changing the link target
from `${base}/context/cli.md` to `${base}/context/mcp.md` to ensure the MCP
entry links to its own documentation. Alternatively, if a separate MCP
documentation file does not exist or is not planned, remove the separate MCP
entry line entirely and integrate MCP information as part of the CLI entry
description instead.

In `@projects/site/src/_11ty/transforms/site-urls.js`:
- Line 48: The URL.canParse method used in the site-urls.js file requires
Node.js 19.0.0+ but this minimum version requirement is not enforced in the
project. Either add an engines field to package.json specifying node version
19.0.0 or higher, or implement a fallback/polyfill that checks the Node.js
version and provides an alternative method to validate URLs for versions below
19.0.0 when calling URL.canParse.

In `@projects/site/src/docs/elements/index.11ty.js`:
- Around line 29-30: The docsByTag Map is overwriting multiple components that
share the same tag, keeping only the last one and making href/title selection
order-dependent. Instead of mapping each tag to a single component, modify the
Map creation to store an array of components for each tag. For each component in
the filter/map operation, check if the tag already exists in the docsByTag Map -
if it does, push the component to the existing array; if not, create a new array
with the component. Then update all references to docsByTag throughout the file
(including the logic around lines 34-43) to iterate over the component arrays
instead of expecting a single component per tag.
- Line 71: The createComponentCatalog function call on line 71 accesses
data.collections.componentDocs without validating that it exists or is defined.
Add a defensive check by using the nullish coalescing operator to provide an
empty array as a safe default fallback, ensuring the code is robust even if the
componentDocs collection is undefined or missing. Update the call to
createComponentCatalog to pass data.collections.componentDocs with the null
coalescing operator and an empty array as the fallback value.

In `@projects/site/src/docs/internal/guidelines/testing.md`:
- Around line 41-45: The Visual Regression Tests entry in the testing guidelines
list has an incorrect link destination. Locate the line that defines Visual
Regression Tests (`.test.visual.ts`) and change its link from
`/docs/internal/testing/ssr/` to `/docs/internal/testing/visual/` to correctly
point to the visual testing documentation. This will prevent the duplication
where both Visual Regression Tests and SSR Tests link to the same
`/docs/internal/testing/ssr/` path.

---

Outside diff comments:
In `@projects/site/src/docs/metrics/bundle-explorer.11ty.js`:
- Line 26: The iframe element with id="bundle" uses a relative path in its src
attribute ("docs/metrics/bundle-explorer-report/") while the navigation anchors
use absolute paths ("/docs/metrics/..."). Update the iframe's src attribute to
use the absolute path "/docs/metrics/bundle-explorer-report/" instead of the
relative path to maintain consistency with the navigation path normalization
strategy used in the rest of the file.

---

Duplicate comments:
In `@projects/site/src/_11ty/layouts/common.js`:
- Line 138: Remove the dead logic `includes('/./')` from the nve-tree-node
condition on line 138 in the common.js file, as this pattern will never match
valid URLs. Additionally, update the path predicates at lines 396-398 to include
leading slashes when checking for `examples/` paths, changing them from
`examples/` to `/examples/` to ensure the navigation expanded and selected
states are properly matched for paths under the examples directory.

In `@projects/site/src/_11ty/layouts/links.test.ts`:
- Around line 6-9: The regex patterns RELATIVE_INTERNAL_LINK_PATTERN and
JS_RELATIVE_INTERNAL_LINK_PATTERN currently only match optional `./` paths using
`(?:\.\/)?` but fail to catch parent directory `../` paths. Update both patterns
to expand the relative path matching group to include both `./` and `../`
patterns, ensuring all relative path variants that bypass the internal link
validation are properly rejected.

In `@projects/site/src/_11ty/transforms/site-urls.test.ts`:
- Around line 94-121: The test cases for siteUrlsTransform only verify module
script behavior with type="module" attributes but lack coverage for regular
script tags without the module type. Add new test cases that include regular
<script src> tags (without type="module") in the HTML input for both the
production build test and the local preview test, and verify that these regular
script src attributes are transformed correctly according to the standard URL
transformation rules, similar to how img src attributes are currently being
tested.

In `@projects/site/src/docs/about/support.md`:
- Line 31: The Lit button on line 31 of the support.md file is missing its
opening anchor tag. Add an opening `<a>` tag with the href attribute pointing to
`/docs/integrations/lit/` before the SVG logo element (before the svg-logo 'lit'
reference) to properly pair with the existing closing `</a>` tag, matching the
structure of the other framework buttons like TypeScript, Angular, Vue, Preact,
NextJS, React, SolidJS, and JavaScript.

In `@projects/site/src/docs/foundations/layout/index.md`:
- Around line 102-104: The anchor reference in the link
`/docs/api-design/styles/#internal-host` is broken because the styles
documentation does not contain a matching anchor with that exact name. Locate
the correct anchor name for the internal-host pattern in the styles
documentation file by checking the actual heading format used there, and update
the link in the layout documentation to match the correct anchor. Alternatively,
if the internal-host pattern is not documented in the styles file, identify the
correct page that documents this pattern and update the link destination
accordingly.

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@projects/site/src/_11ty/layouts/page.11ty.js`:
- Line 25: The nve-button element with the "Starters" link in page.11ty.js has
an href of /starters/ which causes an unnecessary redirect to
/docs/integrations/. Change the href attribute from /starters/ to
/docs/integrations/ to match the consistent navigation target used in common.js
and eliminate the redirect overhead.

In `@projects/site/src/_11ty/transforms/site-urls.js`:
- Around line 27-29: The isSameSiteUrl function currently checks only the origin
of a URL, which is too broad and can incorrectly identify URLs from other
projects on shared origins as internal links. Modify the isSameSiteUrl function
to also validate that the URL pathname is within the same project path, not just
that the origin matches ELEMENTS_SITE_ORIGIN or DEPLOYED_SITE_ORIGIN. This will
prevent the link rewriting logic at lines 53 and 65 from incorrectly rewriting
links to other projects that share the same origin.

In `@projects/site/src/docs/elements/index.11ty.js`:
- Around line 15-17: The isLibraryComponentDoc function filter at line 16 is
incomplete and only checks for two paths in the array passed to some(), but the
componentDocs collection includes additional valid paths. Add the missing
'/docs/code/' and '/docs/media/' paths to the array of paths being checked by
the some() method in isLibraryComponentDoc to ensure all component documentation
routes are properly included in the catalog output.

In `@projects/site/src/docs/foundations/layout/responsive/container.md`:
- Line 42: The anchor fragment references in the container.md file are using
incorrect paths that don't match the actual anchor definitions in grid.md.
Update the three anchor links (at the specified line numbers) by removing the
"layout-" prefix from the fragment identifiers: change `#layout-gap-spacing` to
`#gap-spacing` and change `#layout-padding` to `#padding` so that the links correctly
target the actual anchor sections defined in the grid.md documentation file.

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@projects/core/src/tabs/tabs.examples.ts`:
- Around line 148-154: The `@summary` description for the tabs example in the
examples file incorrectly states "routing-based tab switching and page
navigation" when the actual example code demonstrates hash-only anchor links for
same-page fragment navigation. Locate the `@summary` comment associated with this
example block that contains the nve-tabs-item elements with href="`#links`"
anchors and update the description to "Tabs with hash-only anchor links for
same-page navigation and fragment scrolling" to accurately reflect the
demonstrated behavior.

In `@projects/site/src/docs/metrics/bundle-explorer.11ty.js`:
- Around line 17-22: The tab navigation hrefs have been correctly updated to use
root-relative paths, but the iframe src attribute on line 26 remains as a
relative path (docs/metrics/bundle-explorer-report/) instead of a root-relative
path. Update the iframe src attribute to match the consistency of the navigation
links by converting it to a root-relative path format that starts with a forward
slash, similar to how the href attributes in the nve-tabs-item elements are
structured.

---

Duplicate comments:
In `@projects/site/src/_11ty/layouts/links.test.ts`:
- Around line 6-9: The regex patterns RELATIVE_INTERNAL_LINK_PATTERN on line 6
and JS_RELATIVE_INTERNAL_LINK_PATTERN on line 8 currently only match optional
`./` prefixes using the pattern `(?:\.\/)?`, which allows `../` relative paths
to bypass the test. Modify both patterns to also catch `../` paths by updating
the prefix matching group from `(?:\.\/)?` to `(?:\.\.?\/)?`, which will match
either `.` or `..` followed by a forward slash, ensuring that paths like
`../docs/...`, `../examples/...`, and `../starters/...` are properly caught.

In `@projects/site/src/_11ty/layouts/page.11ty.js`:
- Line 25: The nve-button element containing the "Starters" link currently
points to "/starters/" which creates an unnecessary redirect. Update the href
attribute on this nve-button from "/starters/" to "/docs/integrations/" to align
with the navigation target used in the shared docs header, ensuring consistent
navigation behavior across layouts and eliminating the redirect hop.

In `@projects/site/src/docs/elements/index.11ty.js`:
- Around line 29-30: The docsByTag Map on line 29 overwrites entries when
multiple components share the same tag, causing the wrong document (such as API
or examples pages) to be used for catalog card links instead of overview docs.
Modify the Map creation logic to check if a tag already exists before adding it,
and ensure that overview documentation takes priority over API or examples
pages. When filtering components and creating the Map, add logic to skip adding
a component to the Map if its tag is already present, or implement a
prioritization check to keep overview docs and discard non-overview pages with
the same tag. Apply the same fix to the similar code referenced in lines 34-47.