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 @.claude/agents/component-worker.md:
- Around line 19-21: The routing marker in .claude/agents/component-worker.md
must be produced by the generator with the exact text "**Read USAGE.md first.**"
(not "(read USAGE.md first)"); update the template/rendering in
scripts/generate-routing.mjs (or the template that it uses) so it emits the
exact required marker string for all generated routing blocks (including the
ranges noted 37-103) and regenerate the routing files—do not hand-edit
.claude/agents/component-worker.md directly.

In @.claude/agents/usage-auditor.md:
- Around line 47-54: The fenced code block in .claude/agents/usage-auditor.md
(the block showing "Component: <path to source> ... Findings:") is missing a
language identifier and triggers MD040; update that fence to include a language
(e.g., "text") so it starts with ```text rather than ```, ensuring the block
remains otherwise unchanged and linting passes.

In `@package.json`:
- Line 35: Replace the npm lifecycle script that installs git hooks from
postinstall to a contributor-facing hook to avoid running on consumer installs:
update the package.json scripts entry that currently reads "postinstall":
"simple-git-hooks" so it instead uses "prepare": "simple-git-hooks" (or remove
the script and add documentation for contributor-only setup), ensuring
references to simple-git-hooks are only executed during local
development/prepublish rather than on dependency installation.

In `@scripts/emit-consumer-agents.mjs`:
- Around line 96-101: The script currently checks DIST_RUNTIME with existsSync
and calls process.exit(0) on missing artifacts which masks failure; update the
branch in emit-consumer-agents.mjs so that when existsSync(DIST_RUNTIME) is
false you log an error (use console.error or processLogger/error equivalent) and
call process.exit(1) instead of process.exit(0) so CI and downstream callers
detect the missing build artifact; reference the existsSync(DIST_RUNTIME) check
and the process.exit call to locate and change the behavior.
- Line 86: The current replace call on ROOTS[entry.kind] assumes the value
starts with "src/" which is fragile; update the logic around targetRoot in
scripts/emit-consumer-agents.mjs so it only performs .replace(/^src\//, "dist/")
when ROOTS[entry.kind] is a string that starts with "src/", otherwise fall back
to a safe default (e.g., prepend "dist/" or use the original value) to avoid
producing incorrect paths; reference the targetRoot assignment, ROOTS, and
entry.kind to locate and update the code.

In `@scripts/lib/load-entries.mjs`:
- Around line 19-20: The frontmatter regex in the content.match call only
accepts LF (`\n`) delimiters so CRLF files are skipped; update the regex used
where content.match(...) is called (the frontmatter parsing in parseFrontmatter
/ the match variable) to accept optional CR before newlines (use `\r?\n` for the
opening, capture group boundary, and closing delimiter) so `---\r\n... \r\n---`
is correctly detected; keep the same capture group and null-return behavior if
no frontmatter is found.

In `@scripts/lib/render-routing.mjs`:
- Around line 45-47: The fenceMarkdown function currently uses a fixed
triple-backtick fence which breaks if snippet contains ```; update fenceMarkdown
to emit a safer fence by computing the longest run of backticks inside snippet
and using a fence one backtick longer (or at minimum use a 4-backtick fence,
e.g. ````md ... ````) so nested triple-backtick blocks won’t close the outer
fence; locate and modify the fenceMarkdown function to implement this change.

In `@scripts/lib/render-template.mjs`:
- Around line 22-24: The block RegExp that strips variant blocks (created as
`new RegExp(..., "gm")` using the `blockVariant` template) only matches LF
(`\n`) line endings; update the pattern to accept optional CR before newline by
replacing each `\\n` in the template literal with `\\r?\\n` so both LF and CRLF
templates (`{{`#repo`}}...{{/repo}}`, `{{`#consumer`}}...{{/consumer}}`) are matched
and removed correctly while leaving flags (`"gm"`) unchanged.

In `@src/runtime/components/Button.USAGE.md`:
- Line 51: Fix the mismatched bold markers in the sentence containing "Loading
hides the icon and the icon-right slot." by replacing the stray four asterisks
around the first "Loading" with a proper pair so the bold formatting is balanced
(i.e., ensure the whole phrase you intend bolding is wrapped in exactly two
asterisks on each side); update the text near the phrase "Loading hides the icon
**and** the icon-right slot." and verify the closing bold marker remains
present.

In `@src/runtime/components/gallery/CarouselPreview.USAGE.md`:
- Line 6: The frontmatter key "invariants: false" in CarouselPreview.USAGE.md
may be incorrect given several non-trivial behaviors (ARIA state management via
aria-pressed, differing default fit value "cover" vs parent Carousel "contain",
lack of auto-scroll on external active-image changes, and specific
opacity/styling rules); review each behavior and either (a) if they are indeed
invariant guarantees of CarouselPreview, set invariants: true in the frontmatter
so the routing index marks "Read USAGE.md first" and ensure the USAGE text
explicitly lists those invariants (mentioning aria-pressed behavior, default
fit="cover", auto-scroll not triggered by external active-image changes, and
opacity/styling rules), or (b) if any are not strict invariants, update the
documentation to clarify they are implementation details/optional and keep
invariants: false — make the decision and update the frontmatter and
corresponding text accordingly.

In `@src/runtime/components/Selector.USAGE.md`:
- Around line 28-30: Update the wording in Selector.USAGE.md to correctly
describe the readonly v-model failure mode: replace the phrase that says
mutating a readonly v-model will "throw silently in dev or warn in prod" with a
statement that Selector.vue mutates the bound multi-select array in place via
modelValue.value.splice(...) / modelValue.value.push(...), and when the bound
v-model is a deep readonly value Vue blocks those mutations — logging a warning
in dev (e.g., "Set operation on key … failed: target is readonly") and
suppressing the warning in production (silent failure), so selection won’t
update; remove the incorrect "throw silently" claim and use the exact “warn in
dev / silent in prod” wording.

In `@src/runtime/composables/useApi.USAGE.md`:
- Around line 1-7: The frontmatter flag `invariants: false` contradicts the
presence of a "## Invariants" section; update the frontmatter to `invariants:
true` so it accurately reflects the document content (look for the YAML block at
top of src/runtime/composables/useApi.USAGE.md and change the `invariants`
value), ensuring consistency between the frontmatter and the "## Invariants"
section.

In `@src/runtime/composables/useFuzzySearch.USAGE.md`:
- Around line 1-7: Update the frontmatter key "invariants" in the document to
match the presence of the "## Invariants" section: change invariants: false to
invariants: true so the metadata reflects documented invariants; ensure the "##
Invariants" heading remains accurate and consistent with that frontmatter
change.

---

Nitpick comments:
In `@tests/scripts/render-template.spec.ts`:
- Around line 5-66: Add a regression test to
tests/scripts/render-template.spec.ts that verifies renderTemplate correctly
handles CRLF line endings for variant block markers: create a new it("handles
CRLF block markers", ...) which builds a template using ["shared line",
"{{`#repo`}}", "repo-only line", "{{/repo}}", "tail line"].join("\r\n") and
asserts that renderTemplate(template, { variant: "repo", vars: {} }) returns
"shared line\nrepo-only line\ntail line" (or otherwise normalized lines as
existing tests expect); this ensures the renderTemplate function correctly
parses {{#...}} / {{/...}} blocks when input uses "\r\n".