lintlisted

# Lint ## Tooling Prefer [lintro](https://github.com/lgtm-hq/py-lintro) for linting and formatting. When available, use `uv run lintro chk` and `uv run lintro fmt`. If lintro is unavailable, fall back to the language's native bundled tools (ruff, black, clippy, rustfmt, eslint, bandit, etc.). Another skill may document an additional pass after lintro (for example, `raycast` runs `npm run lint` after lintro — Raycast rules take precedence for extension-specific checks). ## Commands - `uv run lintro fmt` — format code - `uv run lintro chk` — check code for issues - `uv run lintro tst` — run tests ## Rules - **CRITICAL: NEVER run `lintro chk --tools ...` (targeted/filtered checks).** Always run the full `uv run lintro chk` without `--tools`. Filtered runs silently skip tools and miss issues. - **Exception:** single-tool runs (`--tools <tool>`) are permitted only when developing or verifying that specific lintro tool (the `/lintro-add` and `/lintro-verify` workflows). Even then, a full `uv run lintro chk` is still required before committing. - Linting must produce **zero issues** before proceeding - **Fix ALL issues** — whether introduced in the current session or pre-existing - **Ignore policy** — suppressing a finding is not a fix: 1. **Fix the root cause first.** `# noqa`, `# type: ignore`, `# nosec`, `# nosemgrep`, `# yamllint disable-line`, etc. are a LAST resort, only when there is no reasonable fix. 2. **If suppression is genuinely re