Setup CI linter for code standards enforcement

[BowTiedRadone]

Setup a linter that runs in CI to enforce code quality, style, and consistency across the project. The linter should cover key aspects such as import organization, Node.js core module naming (e.g., node:util), general code style, and potential error patterns. This will help maintain a consistent codebase and reduce manual review overhead in future PRs.

[BowTiedRadone]

Thanks to @hugo-stacks for highlighting this — #193 (comment) shows why this issue has become necessary.

[moodmosaic]

Perhaps a zero-install CI run can be as simple as using https://github.com/biomejs/biome, e.g.

npx @biomejs/biome check .

I think that's thelowest-ceremony option. Single binary, no plugins, no config files, no prettier. Just works. ESLint always needs setup, even minimal.

[hugo-stacks]

I'm using oxlint on certain projects, which has good defaults.

Also using prettier form formatting (!= linting).

And I still recommend setting it in the package.json for consistency across different env (local, ci, etc)

[BowTiedRadone]

@moodmosaic @hugo-stacks Thanks for the suggestions! When the moment comes, I will explore both and document the decision. I think formatting is needed as well, I am using prettier to format JS/TS and it does a great job.