[Done] Review the package.json

[YiweiShen]

/codex

[github-actions]

• High: The manifest has moved the GitHub Actions SDK to ESM-only majors without moving the test stack with it. package.json:22 and package.json:23 pull in @actions/core@^3 and @actions/github@^9; both installed packages are type: "module" and export only an import entry (node_modules/@actions/core/package.json:12, node_modules/@actions/github/package.json:11). The test toolchain is still split across Jest 29 and 30 (package.json:34, package.json:35, package.json:47, package.json:50) with a ts-jest ESM config (jest.config.js:1). On a clean npm ci, npm test -- --runInBand fails immediately with Cannot find module '@actions/core'. As written, package.json points at dependency majors the current test harness cannot execute.

• Medium: The lint-staged setup declared in package.json:48 and package.json:53 is inert, because the pre-commit hook does not run it. pre-commit:4 comments out npx lint-staged, so the manifest advertises local checks that contributors never actually get.

• Medium: If that hook is re-enabled, the current lint-staged commands will rewrite unrelated files. package.json:7 defines format as prettier --write ., and package.json:55 invokes that script from lint-staged. That means staging one TS/JS file can format the entire repo, creating noisy diffs and accidental commits. package.json:58 also keeps a manual git add, which is unnecessary with modern lint-staged.

I verified this by running npm ci, npm run build, npm test -- --runInBand, and npm run lint. build passed; test and lint are currently red.