Pin @mdit/plugin-tex to ~1.0.2 to fix docs build npm install ERESOLVE

[Copilot]

The build job in the docs deploy workflow fails during npm install (run via DocumenterVitepress) with an ERESOLVE peer dependency conflict. ^1.0.2 now resolves @mdit/plugin-tex to 1.1.0, which needs markdown-it@^15, while docs/package.json pins markdown-it@^14.1.0.

• docs/package.json: Change @mdit/plugin-tex from ^1.0.2 to ~1.0.2. That keeps it on the 1.0.x line, which peers on markdown-it@^14.2.0 and is satisfied by the installed 14.3.0.

-    "@mdit/plugin-tex": "^1.0.2",
+    "@mdit/plugin-tex": "~1.0.2",

Upgrading markdown-it to ^15 would let the plugin float, but I haven't tried it. vitepress@1.6.3 depends on markdown-it 14, so this change takes the lower-risk path of pinning the plugin.

[kescobo]

@copilot This seems brittle, I think we should work with the version of DocumenterVitepress rather than messing with the internals

[Copilot]

@copilot This seems brittle, I think we should work with the version of DocumenterVitepress rather than messing with the internals

Agreed. In 7208ced I dropped the pin and replaced docs/package.json with the template DocumenterVitepress v0.3.7 ships (the version compat = "0.3" resolves to). That template uses @mdit/plugin-tex ^0.24 plus @mdit/plugin-mathjax, which don't hit the markdown-it 15 conflict. A local npm install resolves cleanly. I haven't run the full docs build in CI.