chore(deps): pin every direct dependency to an exact version

[FelixTJDietrich]

Summary

Strip every ^ / ~ from dependencies, devDependencies, and optionalDependencies across all 7 in-tree package.json files. Each range is replaced with the exact version currently resolved in the matching package-lock.json, so the install graph does not move.

File	Pins applied
package.json	13
library/package.json	6 (devDeps only — runtime dependencies shipped to library consumers were already exact)
standalone/webapp/package.json	2
standalone/server/package.json	2
vscode-extension/package.json	14
vscode-extension/menu/package.json	21
vscode-extension/editor/package.json	21
Total	79

peerDependencies are intentionally untouched (none today; the rule documents intent for future deps).

Subtle case worth flagging

vscode-extension/package.json previously declared "@tumaet/apollon": "^4.2.16". It is an npm workspace member; pinning to an exact version would force npm to fetch the published 4.2.16 from the registry instead of using the workspace symlink (which is currently at 4.2.22), breaking local development of the VS Code extension against in-tree library changes. Changed to "*" — the same convention standalone/server and standalone/webapp already use. The non-workspace consumer vscode-extension/editor/package.json keeps a real exact pin (4.2.16) since it depends on the published package.

Verification

• No install drift. After running npm install in the root, vscode-extension/menu, and vscode-extension/editor, every node_modules/* entry in all three lockfiles has the same version as before. The lockfile diffs are exclusively the packages[""].{dependencies,…} manifest mirrors.
• npm run format:check ✅
• npm run lint ✅
• npm run build ✅ (library + server + webapp + vscode)
• npm test ✅ 781/781
• grep -rE '"\\^|"~' across all 7 project package.json files returns nothing.

Renovate interaction

The repo's renovate.json extends config:best-practices, which uses the replace range strategy — Renovate will simply rewrite each pin with the new exact version when an update is approved, so this change is fully compatible with the existing dependency-dashboard workflow.

🤖 Generated with Claude Code