Bump `@typescript-eslint/eslint-plugin` & parser 5.51.0 → 8.65.0 (3 majors behind, compatible with locked eslint 8.57.1)

[pinecone-groundskeeper]

Problem

package.json:41-42 pins both @typescript-eslint/eslint-plugin and @typescript-eslint/parser at ^5.51.0 (resolved 5.62.0 per package-lock.json). Current published major on npm for both is 8.65.0 — three majors behind.

This is independently fixable from the separate ESLint-8-is-EOL tracking issue: @typescript-eslint/eslint-plugin@8.65.0's peer requirements are eslint: "^8.57.0 || ^9.0.0 || ^10.0.0" and typescript: ">=4.8.4 <6.1.0" (verified via npm view @typescript-eslint/eslint-plugin@8.65.0 peerDependencies). This repo's locked eslint is already 8.57.1 (the last 8.x release) and typescript is 5.9.3 — both satisfy the v8 peer range, so the bump does not require the eslint 9/10 migration.

Acceptance criteria

• @typescript-eslint/eslint-plugin and @typescript-eslint/parser in package.json devDependencies are bumped to ^8.65.0, with package-lock.json updated accordingly.
• .eslintrc.cjs and any rule names it references are updated if v8 renamed/removed a rule this repo uses (check npm run lint output for rule not found errors).
• npm run lint passes with zero errors (fixing any newly-surfaced violations from stricter v8 rules is in scope as part of this bump).
• npm run typecheck and npm test remain unaffected (this is lint-only tooling).

Scope

Only @typescript-eslint/eslint-plugin and @typescript-eslint/parser, and the minimal .eslintrc.cjs/source fixes required for lint to pass cleanly afterward. Do not touch eslint, eslint-config-airbnb-base, or migrate to flat config — those are tracked separately as a human-decision item.

Generated by GitHub Maintenance Audit · sonnet50 · 74.4 AIC · ⌖ 17.8 AIC · ⊞ 7.3K · ◷