chore(deps): override transitive pins to clear npm audit findings

AGENTS.md

@@ -4,6 +4,24 @@
 
 Use conventional commit style messages.
 
+## Dependency overrides
+
+Both `package.json` files carry an `overrides` block whose only job is to clear `npm audit` findings
+that an upstream pin holds open: a dependency asking for a vulnerable range when a patched release
+already exists. Every entry is temporary. When upgrading dependencies, check whether each override
+is still needed by removing it, reinstalling and re-running `npm audit`, and drop the ones upstream
+has caught up on.
+
+Key each override on the range the dependent asks for (`"uuid@8": "^11.1.1"`) rather than nesting
+it under a parent (`"sockjs": { "uuid": ... }`). A keyed rule only applies to edges whose requested
+range intersects the key, so every other dependent keeps the version it asked for. Nesting under a
+parent looks tighter but is not: once the overridden copy is hoisted, npm dedupes other dependents
+onto it too, which is how `"docusaurus-plugin-llms": { "minimatch": "^9.0.7" }` replaced
+serve-handler's own `minimatch@3.1.5` with 9.0.9 and left `docusaurus serve` calling an export that
+is no longer a function. A bare key (`"argparse": "^2.0.1"`) applies to every request of that
+package, which is fine when every dependent accepts the new range. After changing an override, check
+`npm ls <package>` for the dependents that should not have moved.
+
 ## Formatting
 
 **ALWAYS run `npm run format` after making any change.** This is not optional and applies to every

CHANGELOG.md

@@ -4,6 +4,24 @@ All notable changes to this project will be documented in this file.
 
 ## [Unreleased]
 
+### Changed
+
+- **Cleared the `npm audit` findings that upstream pins were holding open.** Both `package.json`
+  files now carry an `overrides` block for transitive dependencies whose parent asks for a
+  vulnerable range even though a patched release exists. At the root, `get-uri` (reached through
+  release-it, `proxy-agent` and `pac-proxy-agent`) pins `basic-ftp` 5, so it is overridden to
+  6.2.1+. The lockfile also moves release-it's `undici` to 7.30.1 for its batch of advisories, so
+  the root audit is clean. In the docs site, `docusaurus-plugin-llms` pins `minimatch` and `yaml`
+  exactly (overridden to 11.0.1+ and 2.8.3+), `sockjs` gets `uuid` 11, `argparse` 2 replaces the
+  js-yaml 3 CLI-only dependency that pulled in `sprintf-js`, and `postcss-selector-parser` 7.1.6+,
+  `serialize-javascript` 7.1.3+ and `tinypool` 2.1.2+ replace the majors Docusaurus 3.10 still
+  resolves. In-range lockfile bumps clear the `joi`, `follow-redirects`, `qs`, `body-parser` and
+  `fast-uri` advisories. Each override is keyed on the range the dependent asks for
+  (`"minimatch@9": "^11.0.1"`) so it stops at that dependent, and serve-handler keeps its own
+  `minimatch` 3.1.5. Two advisories have no patched release yet and remain: `minimatch` 3.1.5 in
+  serve-handler (only used by `docusaurus serve`) and a low-severity `deepmerge` advisory under
+  `@svgr/plugin-svgo`. No changes to the published library.
+
 ## [8.1.3] - 2026-10-31
 
 ### Security