fix(nix): resync npmDepsHash after upstream merge (#352)

The 182-commit upstream sync (PR #352) changed package-lock.json, so the pinned npmDepsHash in nix/lib.nix went stale and the nix flake-check failed (advisory, non-blocking, but breaks the nix build on main). Bumped to the hash fetchNpmDeps actually computes for the merged lockfile (the authoritative 'got:' from CI, which fix-lockfiles itself prefers over the prefetch-npm-deps guess). No package-lock.json change — this path only updates the hash.

Co-Authored-By: Hermes Evolution <<REDACTED:email:5484c254e0d8265e80a4c422e37c84ac>>

Author: Lexus2016

nix/lib.nix

@@ -21,7 +21,7 @@ let
 
   # Single npm deps fetch from the workspace root lockfile.
   # All workspace packages share this derivation.
-  npmDepsHash = "sha256-kbjJksq7limRIYqP3DwI+GNgCXkG96tXcsQqmuEedxo=";
+  npmDepsHash = "sha256-rcZA9b/e02qQOvurztSkpQWrGyS2QL8pn0Jc8wuGs2c=";
 
   npmDeps = pkgs.fetchNpmDeps {
     inherit src;