fixfirst 0.1.0__tar.gz

fixfirst-0.1.0/.gitignore

@@ -0,0 +1,5 @@
+.venv/
+__pycache__/
+dist/
+.ruff_cache/
+uv.lock

fixfirst-0.1.0/.ruff.toml

@@ -0,0 +1,2 @@
+line-length = 120
+target-version = "py311"

fixfirst-0.1.0/AGENTS.md

@@ -0,0 +1,48 @@
+# CLAUDE.md — working on fixfirst
+
+Read first: `IDEA.md` (intention), `ROADMAP.md` (what to build next), `docs/adr/` (why).
+Current target: **MVP-1** in `ROADMAP.md`.
+
+## Ground rules
+- Python only. No TypeScript, no Node adapters (ADR-0010, ADR-0015).
+- Every decision that changes an ADR gets a new or updated ADR in MADR format, with the facts it
+  rests on (test output, cited docs). Do not silently deviate.
+- Claims about tool behaviour (ruff, ty, pytest, harnesses) are tested before they are written down.
+- Output contract (ADR-0009): one line per problem, silent on success. Keep the gate quiet.
+- Never gate the human; never delete user files; never rewrite files outside the agent's changes.
+
+## Repository layout (target)
+```
+src/fixfirst/cli.py        # check / verify / hook / install / env / doctor
+src/fixfirst/policy.py     # pytest plugin; copied + injected by the gate as fixfirst_gate (ADR-0020), no entry point
+src/fixfirst/data/         # git-shim.sh, hooks.json
+src/fixfirst/policy.py is never imported by the CLI (pytest lives in the project venv, not the CLI's)
+docs/adr/                  # decisions
+reference/                 # NOT shipped: prototype + originals for porting
+```
+
+## Reference material (`reference/`, do not ship)
+- `pyguard-0.2/` — working prototype (tested). Port from here; rename `pyguard` → `fixfirst`.
+  Its `opencode.ts`, `pi.ts`, Hermes plugin are superseded by ADR-0010 — do not port them.
+- `conftest-original.py` — the maintainer's original policy conftest (source of policy semantics).
+- `fixfirst-setup/` — `release.yml` (Trusted Publishing) and `pyproject.toml` template.
+- `scripts/attack-scenarios.sh [cli]` — regression: agent shortcuts against `<cli> verify`, plus a
+  PASS controls (clean, legacy, zero-config), every ADR-0007 suppression form, shim and hooks.
+  63/63 with fixfirst 0.1.0. Must keep passing. Use errors ruff cannot autofix (`verify` autofixes).
+
+## Commands
+```bash
+uv tool install --force .          # install CLI from checkout
+reference/scripts/attack-scenarios.sh fixfirst
+uvx ruff check src && uvx ruff format --check src
+```
+
+## Git (public repo, pseudonymous)
+- Commit messages carry no session trailers: no `Co-Authored-By`, no `Claude-Session` link.
+- Commit identity: the pseudonym with its GitHub noreply address (set in `git config`), never a real
+  name. Check with `git log --format='%an <%ae>'` before pushing.
+- Never write the employer, internal hosts or group names into the repo.
+
+## Maintainer preferences
+- One concrete recommendation, not a menu. Research first, then decide, then full instructions.
+- Plain, direct writing. State reasons and evidence; do not just agree.

fixfirst-0.1.0/IDEA.md

@@ -0,0 +1,123 @@
+# fixfirst — Idea and Intention
+
+> One gate that only the agent hits: in any harness it has to fix what it broke instead of
+> cheating around ruff and the checks you switch on. Configured only by your existing rules,
+> installed in one command, fast, offline, and so quiet the model only ever sees the bug.
+
+Status: 2026-11-14, pre-MVP-1. Working name `pyguard` (taken on PyPI) → final name `fixfirst`.
+
+## 1. Starting point
+
+The maintainer runs Python repos (12+, growing) with coding agents (OpenCode server with
+long-lived sessions, Hermes, pi, Claude Code, Codex; mostly local models).
+
+Current setup per repo:
+
+- `tests/conftest.py` holds the policy: ruff with `--ignore-noqa` (superseded: flags committed
+  suppressions in legacy files; fixfirst judges suppressions against the base instead, ADR-0007), ty, per-file coverage on
+  touched files, Hypothesis evidence for numerical code (boundary = TID251 per-file-ignores in
+  the ruff config), no code in `.tmp/`.
+- `chattr +i` on `conftest.py`, `ruff.toml`, `ty.toml`.
+
+It works, but: maintaining one conftest per repo across 12+ repos is a mess, and the agent
+still finds ways around it.
+
+## 2. The real problem
+
+The agent takes the path of least effort. Instead of fixing code it:
+
+- writes alternative configs (`.ruff.toml`, nested `ruff.toml`, `[tool.ruff]`, `pytest.ini`),
+- builds its own conftest (observed: a root `conftest.py` to circumvent the one in `tests/`),
+- adds suppression comments (`noqa`, `ty: ignore`, `ruff: ignore`, `--add-ignore` …),
+- writes a lot without running ruff in between,
+- does not commit or does not run pytest, so the conftest-based checks never run.
+
+Holes we reproduced against the conftest + chattr setup (all closed by the v0.2 prototype):
+
+| Shortcut | Why it worked |
+|---|---|
+| root `.ruff.toml` with `select = []` | ruff prefers `.ruff.toml` over `ruff.toml` |
+| nested `src/pkg/ruff.toml` | ruff uses the nearest config per directory |
+| `# ty: ignore[...]`, `ty check --add-ignore` | ty has no `--ignore-noqa`; `respect-type-ignore-comments=false` only covers `type: ignore` |
+| new module without any test | never imported → never measured → "untouched" |
+| `pytest other/`, `pytest file.py` outside `tests/` | `tests/conftest.py` is not loaded |
+| `--noconftest`, `PYTEST_ADDOPTS`, `addopts`, new `pytest.ini` | policy silently disabled |
+| agent conftest with hooks / overriding fixtures | runs in the same test process |
+| staged config change via `git hash-object` + `update-index` | `chattr` protects the file, not the index |
+
+## 3. Intention (agreed, latest)
+
+1. **Enforced on the agent only.** Checks apply to everything the agent does — while it works
+   and before its work counts as done or is committed. The human is never gated: no shim in the
+   human's shell or IDE git; the human runs pytest voluntarily. CI only confirms, it does not
+   correct late.
+2. **No pre-commit hook.** It would gate the human and is easy for the agent to skip.
+3. **Harness-agnostic.** Same behaviour in OpenCode (server, long-lived sessions), Hermes, pi,
+   Claude Code and Codex, without a separate solution per tool. Covered harness versions are
+   tested and documented.
+4. **Ruff always on, everything else opt-in** through the committed config: ty, coverage,
+   Hypothesis evidence, bandit (ruff `S`). **Suppression comments the agent adds never count**
+   (noqa, `ruff: ignore`/`disable`/`file-ignore`, type/ty/pyright ignore, nosec,
+   `pragma: no cover`, `fmt: off/skip`) — always, in every repo. Suppressions already committed
+   stay valid. Exclusions for false positives live in the committed config.
+5. **Judge only what the agent changed.** Existing problems in an old repo never block; only new
+   problems vs. the base count. Autofix touches only files the agent changed, never the whole
+   repo, never mid-edit.
+6. **Native configs as single source of truth**, read from git: `.ruff.toml`, `ty.toml`,
+   coverage and pytest config. No own config format, no renaming/"fixing" of user files, no
+   silent deletions — report, don't clean up.
+7. **Minimal manual setup.** The only manual work is writing your rules. Install + harness
+   wiring is one command with dry-run, uninstall, idempotent. Lint/type checks run everywhere;
+   tests (they execute repo code) run only in trusted repos, trust defined once by pattern.
+8. **Minimal output.** One line per problem (`file:line: rule message`), nothing on success;
+   `-v` for raw output, `--format json` for tools.
+9. **Fast and bounded.** Per-edit check < 100 ms when nothing changed; stop/retry loops capped.
+10. **Local and deterministic.** No network at runtime, no telemetry, no LLM calls; installed once
+    from a pinned, signed release; works air-gapped.
+11. **Honest about limits.** Stops lazy agents, not hostile ones. Root agents, direct
+    `/usr/bin/git`, and sabotage from inside test code are documented limits; the boundary there
+    is CODEOWNERS, protected branches and CI.
+12. **Release-ready.** Public PyPI project `fixfirst`, installable through Artifactory/Xray and in
+    public projects; Apache-2.0; changelog; semver; 60-second demo.
+
+Underneath: the maintainer tests whether arguments are evaluated or just conceded. Docs and
+decisions must state reasons and facts, not agreement.
+
+## 4. Value over conftest + chattr
+
+| | conftest + chattr | fixfirst |
+|---|---|---|
+| Feedback to the agent | only when it runs pytest | after every tool call, changed files |
+| "Done" enforced | only if the agent runs pytest | at Stop and at every commit |
+| Tested holes (section 2) | open | closed |
+| Setup per repo | copy conftest, chattr (sudo), unlock/relock per change | nothing beyond ruff/ty config |
+| Policy change | in every repo | one version bump |
+| Cloud/containers | chattr unavailable | works (config from git) |
+| Output to the model | conftest logs, coverage tables | one line per problem |
+
+Not gained: smarter checks (same policy logic), protection against hostile agents.
+Cost: several weekends to build; ongoing upkeep for ruff/ty suppression forms and harness changes.
+
+## 5. Competition (researched 2026-11-14)
+
+No tool covers the intention. Closest:
+
+| Tool | Covers | Missing |
+|---|---|---|
+| **cagr** (KrtinShet/cagr, TS/Bun, 0 stars) | suppression guard, changed-files lint, stop gate (max 2 blocks), time budgets, quiet output, honest framing, reviewer-agent PR gate | only Claude Code + Codex natively (others via git hooks only), shell edits invisible (`sed -i`, `cat >`), config read from disk and `ConfigError` fails open, git hooks gate humans too, no coverage/Hypothesis |
+| klasp | commit gate per agent | per-agent mechanisms, no OpenCode, no config protection |
+| oh-my-harness | commit/stop test gate, lint-on-save | Claude Code/Codex/Pi only, eslint-centric |
+| agent-guardrails | deterministic hooks, config tampering | Claude Code + Codex |
+| anti-slop-py | flags agents silencing type checkers | judges comments, not "new vs base"; coded suppressions allowed |
+| TDD Guard | pytest TDD enforcement | Claude Code only |
+| agentic-git | PATH shim for git | git safety only |
+
+Ideas adopted from cagr: stop cap, time budgets + `doctor`, every block says what to do instead,
+fail-open only for internal errors.
+
+## 6. Constraints
+
+- One-man show: maintenance must stay small. Pure Python, no TypeScript.
+- Private repo; code public through PyPI. Later a clean public repo, no public maintenance (ADR-0016, ADR-0017).
+- Pseudonymous publishing identity (GitHub org `fixfirst-sh`).
+- Must pass JFrog Artifactory + Xray (+ possibly Curation) in corporate environments.

fixfirst-0.1.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

fixfirst-0.1.0/PKG-INFO

@@ -0,0 +1,63 @@
+Metadata-Version: 2.5
+Name: fixfirst
+Version: 0.1.0
+Summary: Makes coding agents fix their code instead of cheating around ruff, ty and your tests
+Author: fixfirst contributors
+License-Expression: Apache-2.0
+License-File: LICENSE
+Classifier: Development Status :: 3 - Alpha
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: Software Development :: Quality Assurance
+Requires-Python: >=3.11
+Requires-Dist: ruff==0.17.5
+Requires-Dist: ty==0.0.104
+Description-Content-Type: text/markdown
+
+# fixfirst
+
+Makes coding agents fix their code instead of cheating around ruff, ty and your tests.
+One gate that only the agent hits, configured only by your committed rules, one line per problem,
+silent on success. Status: alpha (0.1.0). Design: `IDEA.md`, `docs/adr/`.
+
+## Setup (once per machine)
+
+```bash
+uv tool install fixfirst
+fixfirst install                 # git shim + hooks for Claude Code (~/.claude) and Codex (~/.codex)
+```
+
+In each harness launcher or systemd unit — **not** in your own shell:
+
+```bash
+eval "$(fixfirst env)"                                    # git shim first on the agent's PATH
+export FIXFIRST_TRUST="gitlab.example.com/mygroup/*"      # repos whose tests may run (host/path)
+```
+
+Per repo: nothing. The project needs a `.venv` (`uv sync`) with pytest, plus pytest-cov / hypothesis
+if you switch those policies on. `fixfirst doctor` shows the wiring, the base and the trust status.
+
+## What runs
+
+| check | on when (committed config) |
+|---|---|
+| ruff | always; `.ruff.toml` / `ruff.toml` / `[tool.ruff]`, else ruff defaults |
+| bandit | ruff `S` rules selected |
+| ty | `ty.toml` exists |
+| coverage | coverage `fail_under` set; per touched/changed file |
+| Hypothesis evidence | TID251 per-file-ignores in the ruff config (numerical boundary) |
+| tests | `tests/` or a pytest config exists, and the origin matches `FIXFIRST_TRUST` |
+| suppressions | always: any `noqa`, `type/ty/pyright: ignore`, `nosec`, `pragma: no cover`, `fmt: off/skip` … not present at the base |
+
+Config is read from git (`HEAD`), never from disk: agent edits to config have no effect and block
+its commit. Only changed files are checked, so old problems in untouched files never block.
+
+When: after every agent tool call (changed files, report only), when the agent stops, and on every
+`git commit` through the shim (autofix of changed files, then everything). CI:
+`fixfirst verify --ci origin/<target>`.
+
+Limits: stops lazy agents, not hostile ones — root agents, `/usr/bin/git` and sabotage from test
+code are out of scope (ADR-0012). Protect `main` with CI and CODEOWNERS.
+
+## Source and contributions
+Apache-2.0. The source ships in the package on PyPI; development happens in a private repository,
+so there is no public issue tracker and no pull requests.

fixfirst-0.1.0/README.md

@@ -0,0 +1,48 @@
+# fixfirst
+
+Makes coding agents fix their code instead of cheating around ruff, ty and your tests.
+One gate that only the agent hits, configured only by your committed rules, one line per problem,
+silent on success. Status: alpha (0.1.0). Design: `IDEA.md`, `docs/adr/`.
+
+## Setup (once per machine)
+
+```bash
+uv tool install fixfirst
+fixfirst install                 # git shim + hooks for Claude Code (~/.claude) and Codex (~/.codex)
+```
+
+In each harness launcher or systemd unit — **not** in your own shell:
+
+```bash
+eval "$(fixfirst env)"                                    # git shim first on the agent's PATH
+export FIXFIRST_TRUST="gitlab.example.com/mygroup/*"      # repos whose tests may run (host/path)
+```
+
+Per repo: nothing. The project needs a `.venv` (`uv sync`) with pytest, plus pytest-cov / hypothesis
+if you switch those policies on. `fixfirst doctor` shows the wiring, the base and the trust status.
+
+## What runs
+
+| check | on when (committed config) |
+|---|---|
+| ruff | always; `.ruff.toml` / `ruff.toml` / `[tool.ruff]`, else ruff defaults |
+| bandit | ruff `S` rules selected |
+| ty | `ty.toml` exists |
+| coverage | coverage `fail_under` set; per touched/changed file |
+| Hypothesis evidence | TID251 per-file-ignores in the ruff config (numerical boundary) |
+| tests | `tests/` or a pytest config exists, and the origin matches `FIXFIRST_TRUST` |
+| suppressions | always: any `noqa`, `type/ty/pyright: ignore`, `nosec`, `pragma: no cover`, `fmt: off/skip` … not present at the base |
+
+Config is read from git (`HEAD`), never from disk: agent edits to config have no effect and block
+its commit. Only changed files are checked, so old problems in untouched files never block.
+
+When: after every agent tool call (changed files, report only), when the agent stops, and on every
+`git commit` through the shim (autofix of changed files, then everything). CI:
+`fixfirst verify --ci origin/<target>`.
+
+Limits: stops lazy agents, not hostile ones — root agents, `/usr/bin/git` and sabotage from test
+code are out of scope (ADR-0012). Protect `main` with CI and CODEOWNERS.
+
+## Source and contributions
+Apache-2.0. The source ships in the package on PyPI; development happens in a private repository,
+so there is no public issue tracker and no pull requests.