[BUG]: npm run lint triggers interactive setup instead of running checks

[arunabha003]

Bug Description

The repo does not have a committed ESLint configuration, so running npm run lint does not execute lint checks directly.

Instead, Next.js opens the interactive ESLint setup prompt, which makes lint unusable in CI and inconvenient for normal local verification.

Steps to Reproduce

1. Clone the repo.
2. Install dependencies with npm install.
3. Run npm run lint.
4. Observe that the command opens the interactive Next.js ESLint setup prompt instead of running lint checks normally.

Logs and Screenshots

Environment Details

No response

Impact

High - Major feature is broken

Code of Conduct

• I have joined the Discord server and will post updates there
• I have searched existing issues to avoid duplicates