pnpm lint is broken: eslint is declared as a script but never installed

[so0k]

Problem

pnpm lint fails immediately — nothing in this repo is linted today.

$ pnpm lint
$ eslint .
sh: eslint: command not found
[ELIFECYCLE] Command failed.

Cause

package.json declares the script:

"lint": "eslint ."

but eslint was never actually wired up:

• not in dependencies or devDependencies
• not present in pnpm-lock.yaml
• no eslint binary in node_modules/.bin after a clean pnpm install --frozen-lockfile
• no flat config (eslint.config.*) or legacy config (.eslintrc.*) anywhere in the repo

git log -S '"lint"' -- package.json traces the script back to 1c7a7d3 ("Initial commit from v0") — it came in with the v0 scaffold and the tooling behind it was never added. Note that Next.js 16 also removed the built-in next lint command, so there is no fallback path.

Impact

CI and contributors get no lint feedback at all. Anyone running the documented pnpm lint hits a confusing command not found rather than a lint result.

Suggested fix

Either:

1. Wire it up — add eslint, eslint-config-next, and @eslint/eslintrc/typescript-eslint as devDependencies and add an eslint.config.mjs flat config; or
2. Remove the script if linting is intentionally out of scope, so the failure isn't misleading.

Option 1 seems right given the repo already ships TypeScript and a Next app.

Found while working on #(logo asset cleanup) — unrelated to that change, this is pre-existing on v3.