fix: remove obsolete ESLint 10 --ext option

[Cherry7593]

What changed

Remove the obsolete ESLint 10 --ext option from the repository lint script.

Why

This repository uses ESLint 10 flat config, where --ext is no longer accepted. The flat config already defines TypeScript/React handling and ignores, so linting src/ preserves the same owned source scope.

Validation

• repository lint passed with the existing warnings and zero errors
• TypeScript 6 typecheck passed
• 8/8 suites and 80/80 existing tests passed
• Father ESM/CJS/declaration build and Less compile passed
• package output contained the expected 82 files

Development-script only; no runtime API changes.

[vercel]

@Cherry7593 is attempting to deploy a commit to the afc163's projects Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 3a471f45-e095-4515-a370-df602f6986e0

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[nrps9909]

Verified exact head 889c86e01396764fb7aa256b8a44736a9c386773 with the ESLint 10.6 flat config in this repository. npm run lint exits successfully with 0 errors (12 existing hook/disable warnings), and npm run tsc passes. I also compared JSON lint output from eslint src/ against the previous eslint src/ --ext .ts,.tsx,.jsx,.js,.md: both discover the same 19 source files and report the same result, so removing the obsolete discovery flag does not reduce current lint coverage. No blocking issues found.