Krzysztof kuhy Rudnicki 71133a808f Judge peer dependencies by range, and check the packageManager pin ... Two npm-specific corrections found by running the gate over web_ui. **`peerDependencies` must not be exact-pinned.** The gate was reporting `react: ">=19"` as "not exact-pinned", and acting on that would have been actively harmful: a peer range declares what a CONSUMER may bring, so pinning it forces every consumer of @kuhyx/web-ui onto one exact React. Peers are now judged the way toolchain ranges are -- does the range still admit latest? -- and only reported when it does not. **`packageManager` is a real dependency.** corepack enforces it, so `pnpm@10.13.1` is an exact pin that nothing was checking. It is now read and compared, which immediately surfaced that both TS packages sit on pnpm 10.13.1 against 11.24.0. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CRykabMwPgDzFHcARoqpaK		2026-08-28 13:38:40 +02:00
..
__init__.py	Add the shared dependency-freshness gate	2026-08-28 13:00:35 +02:00
_lines.py	Add the shared dependency-freshness gate	2026-08-28 13:00:35 +02:00
fvm.py	Add the shared dependency-freshness gate	2026-08-28 13:00:35 +02:00
golang.py	Add the shared dependency-freshness gate	2026-08-28 13:00:35 +02:00
javascript.py	Judge peer dependencies by range, and check the packageManager pin	2026-08-28 13:38:40 +02:00
pubspec.py	Add the shared dependency-freshness gate	2026-08-28 13:00:35 +02:00
python.py	Add the shared dependency-freshness gate	2026-08-28 13:00:35 +02:00
rust.py	Add the shared dependency-freshness gate	2026-08-28 13:00:35 +02:00