fix(deps): refresh package-lock.json talisman checksum

Scoping the overrides changed package-lock.json again, so the pinned checksum
from the earlier commit is stale. Same false-positive/allowlist convention as
before (Talisman reads npm's sha512- integrity fields as base64 secrets).

#claude_code#
🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

Author: dhruv-parekh-cs

.talismanrc

@@ -9,7 +9,7 @@ fileignoreconfig:
 - filename: test/unit/commands/rollback.test.ts
   checksum: d1f931f2d9a397131409399ad6463653e28b5a2224e870b641d9ba57c4418f18
 - filename: package-lock.json
-  checksum: 16446727efd8a16417343fe853d4c927d58a32f35907c019866fa428f454c83b
+  checksum: c9f4aca9f8f295736cad854305bd2b68b28cf320da92f925b1ccfd70f7224c19
 - filename: src/adapters/github.test.ts
   checksum: b3d3d3a3c14adde103152d2ac4e1c4b7121a5f7533a87c3cc600f6d25fb59d1b
 - filename: src/adapters/file-upload.test.ts