Migrate the lint script off the deprecated next lint command

[nanaf6203-bit]

Labels / Complexity: DX, good first issue · Trivial — 2 points

Summary

package.json defines "lint": "next lint", which is deprecated and will be removed in Next.js 16; the warning prints on every run. The project's actual ESLint config is the flat config eslint.config.mjs, so the script should invoke the ESLint CLI directly.

Proposal

• Change the lint script to eslint . (or eslint src) so it reads eslint.config.mjs.
• Keep the same lint surface (no new rules) and confirm the existing @typescript-eslint and no-console rules still apply.
• Update README.md if it documents the lint command.

Acceptance criteria

• npm run lint runs the ESLint CLI and exits 0 on a clean tree.
• A deliberately introduced lint error is reported by npm run lint.
• The next lint deprecation warning no longer appears.
• npm run typecheck still passes.

Getting started

Files: package.json, eslint.config.mjs, README.md. Verify with npm run lint.

Good first files to read: package.json and eslint.config.mjs.

[zubairz4far]

I'd like to work on this issue. I've implemented the ESLint CLI migration and the branch is ready for CI verification.