Problem

biome check . currently scans too much of the repository and is not useful as a CI/review gate.

Observed during a Metareview run on PR #5491 / commit 62462fe1:

Checked 1243 files.
Found 24894 errors.
Found 25034 warnings.
Found 1565 infos.

The first diagnostics are formatting changes for .greptile/config.json and .greptile/files.json, and the scan also reaches large generated/bundled assets. There is no biome.json / biome.jsonc in the repo root, so a plain Biome invocation has no project-specific include/ignore policy.

Why it matters

A check with 50k+ diagnostics cannot serve as an actionable gate. It also hides real web/JS regressions inside generated assets and tool configuration formatting churn.

Suggested fix

• Add a root biome.json / biome.jsonc with explicit includes for source files Biome should own.
• Ignore generated/bundled/vendor outputs and tool metadata that should not be formatted by Biome.
• Document the intended command, for example biome check <configured paths>.
• Optionally add a CI job only after the baseline is clean or intentionally scoped.

Verification

Run the intended Biome command and confirm diagnostics are actionable and bounded to maintained source files.