code-linting

# Code linting Check or fix Python with Ruff and JavaScript/TypeScript with Biome. Use repository commands and configuration before these defaults. Read project instructions, `pyproject.toml`, and `biome.json`; preserve configured rules and line width. ## Check and fix Use the project virtual environment (`./venv/bin/ruff` or `./env/bin/ruff`) and installed JavaScript tooling. For mixed projects, check both languages unless the task selects one. Adapt `src/` to the actual source directory. | Task | Python | JavaScript/TypeScript | |---|---|---| | Check | `ruff check .` | `npx @biomejs/biome check src/` | | Format check | `ruff format --check .` | Included in Biome check | | Fix lint | `ruff check --fix .` | `npx @biomejs/biome check --write src/` | | Format | `ruff format .` | `npx @biomejs/biome format --write src/` | If configured, use `make lint` or `make lint-fix`. Check first; apply fixes only within the requested work. Review `git diff`, undo incorrect fixes, then rerun lint and format checks. Do not change rules, install new tooling, or expand cleanup scope merely to get a pass. For remaining issues: F401 means remove or use the import; I001 needs import sorting; E501 needs shorter lines within existing settings. Biome `noVar` uses `let`/`const`, `useConst` marks unchanged bindings, and `noDoubleEquals` uses strict equality where semantics allow. Report commands, exit status, and actionable rule/file:line diagnostics. Keep full logs available; summarize passing ...