shiplisted

```! git status --short --branch git diff --stat HEAD ``` Run the gate below in order. **Stop at the first failure** and fix it — do not proceed to the commit with a red gate, and do not skip a step because it "looks fine". ## Gate 1. **Format** — the project's formatter over the changed files (`black` + `isort`, `prettier`). 2. **Lint** — `ruff` / `eslint`. Fix warnings; do not silence them with ignore comments. 3. **Types** — `mypy` / `pyright` / `tsc --noEmit`. No new errors, no `any`, no `# type: ignore` added to get through. 4. **Tests** — the full suite, not just the files you touched. Report the actual pass/fail counts. 5. **Coverage** — ≥80%. Report the number and the command that produced it. 6. **Security scan** — `bandit -r <package>/` for Python, `npm audit` for Node. Address high and critical advisories. 7. **Secret sweep** — read the diff and confirm no API keys, passwords, tokens, connection strings, or `.env` contents are being committed. If something was exposed, say so and recommend rotating it before anything else. If a tool is not installed in this project, say which step you could not run rather than reporting the gate as passed. ## Commit Only after the gate is green: - Stage deliberately — `git add` the files that belong to this change, never `git add -A` over a dirty tree you have not inspected. - Message format: `<type>: <description>` where type is one of `feat` `fix` `refactor` `docs` `test` `chore` `perf` `ci`. Imperative moo