Krzysztof kuhy Rudnicki 2a2f18ca56 Add the shared dependency-freshness gate ... "Are we on the newest version?" was not mechanically answerable across these repos: constraint styles had drifted per-ecosystem and a caret range is "newest-compatible" by definition, which gives a checker nothing to compare. This gate makes it answerable and then enforces the answer. Checks two things at once -- that every dependency carries an exact pin, and that the pin equals its registry's latest STABLE release -- across pub.dev, PyPI, npm, crates.io, the Go proxy, kuhyx/utils git tags, and the Flutter / Node / Python toolchains. Three deliberate design points: * Pre-releases are rejected per-ecosystem, because every ecosystem leaks them differently and each leak fails GREEN. npm lets a maintainer point `dist-tags.latest` at an rc; crates.io's `max_version` includes them; PyPI's legacy `info.version` includes yanked releases. Unit-tested with fixtures, since an end-to-end run cannot surface a wrong "up to date". * Offline, the gate serves an expired cache entry and PASSES with a DEGRADED banner (exit 3 only under --strict, which is CI). `--no-verify` is banned here, so a hook that hard-failed offline would leave no way to commit at all. * The allowlist has two entry classes. `blocked_by: transitive:<pkg>@<ver>` is a predicate that clears itself when upstream moves and must NOT carry a date; everything else is discretionary and requires `expires`, capped at 90 days. Exact pins plus latest-everywhere is provably unsatisfiable when a dependency internally constrains a shared transitive, and expiring the predicate class on a calendar would turn the gate red for a reason no commit could fix. An entry with nothing left to excuse is itself an error. One hook id, one shim, one shared implementation -- always delegating, so it cannot fork the way the 250-line cap forked into four ids, two of which were independent reimplementations. 256 tests, 100% branch coverage on every module of the gate. Also adds the workflow that runs them, which incidentally gives md_naming's 71 tests their first CI run. Not yet installed in any repo: a repo that gets the gate before its deps are bumped is instantly and permanently red, so the gate and the upgrade land together, per repo. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CRykabMwPgDzFHcARoqpaK		2026-08-28 13:00:35 +02:00
..
__init__.py	Add the shared dependency-freshness gate	2026-08-28 13:00:35 +02:00
conftest.py	Add the shared dependency-freshness gate	2026-08-28 13:00:35 +02:00
test_allowlist.py	Add the shared dependency-freshness gate	2026-08-28 13:00:35 +02:00
test_check.py	Add the shared dependency-freshness gate	2026-08-28 13:00:35 +02:00
test_constraints.py	Add the shared dependency-freshness gate	2026-08-28 13:00:35 +02:00
test_discover.py	Add the shared dependency-freshness gate	2026-08-28 13:00:35 +02:00
test_edges.py	Add the shared dependency-freshness gate	2026-08-28 13:00:35 +02:00
test_evaluate.py	Add the shared dependency-freshness gate	2026-08-28 13:00:35 +02:00
test_golang.py	Add the shared dependency-freshness gate	2026-08-28 13:00:35 +02:00
test_http.py	Add the shared dependency-freshness gate	2026-08-28 13:00:35 +02:00
test_parsers_edges.py	Add the shared dependency-freshness gate	2026-08-28 13:00:35 +02:00
test_parsers.py	Add the shared dependency-freshness gate	2026-08-28 13:00:35 +02:00
test_registries.py	Add the shared dependency-freshness gate	2026-08-28 13:00:35 +02:00
test_report.py	Add the shared dependency-freshness gate	2026-08-28 13:00:35 +02:00
test_resolve.py	Add the shared dependency-freshness gate	2026-08-28 13:00:35 +02:00
test_toolchain_registry.py	Add the shared dependency-freshness gate	2026-08-28 13:00:35 +02:00
test_versions.py	Add the shared dependency-freshness gate	2026-08-28 13:00:35 +02:00