mutantlens 0.0.1__tar.gz

mutantlens-0.0.1/.github/workflows/ci.yml

@@ -0,0 +1,21 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+jobs:
+  check:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: ["3.12", "3.13"]
+    steps:
+      - uses: actions/checkout@v7
+      - uses: astral-sh/setup-uv@v10
+      - run: uv sync --locked --python ${{ matrix.python-version }}
+      - run: uv run ruff check .
+      - run: uv run ruff format --check .
+      - run: uv run pyright
+      - run: uv run pytest -q

mutantlens-0.0.1/.gitignore

@@ -0,0 +1,220 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[codz]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#   Usually these files are written by a python script from a template
+#   before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py.cover
+*.lcov
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+# Pipfile.lock
+
+# uv
+#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+# uv.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+# poetry.lock
+# poetry.toml
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#   pdm recommends including project-wide configuration in pdm.toml, but excluding .pdm-python.
+#   https://pdm-project.org/en/latest/usage/project/#working-with-version-control
+# pdm.lock
+# pdm.toml
+.pdm-python
+.pdm-build/
+
+# pixi
+#   Similar to Pipfile.lock, it is generally recommended to include pixi.lock in version control.
+# pixi.lock
+#   Pixi creates a virtual environment in the .pixi directory, just like venv module creates one
+#   in the .venv directory. It is recommended not to include this directory in version control.
+.pixi/*
+!.pixi/config.toml
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule*
+celerybeat.pid
+
+# Redis
+*.rdb
+*.aof
+*.pid
+
+# RabbitMQ
+mnesia/
+rabbitmq/
+rabbitmq-data/
+
+# ActiveMQ
+activemq-data/
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.envrc
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs/Zensical documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#   JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#   be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#   and can be added to the global gitignore or merged into this file.  For a more nuclear
+#   option (not recommended) you can uncomment the following to ignore the entire idea folder.
+# .idea/
+
+# Abstra
+#   Abstra is an AI-powered process automation framework.
+#   Ignore directories containing user credentials, local state, and settings.
+#   Learn more at https://abstra.io/docs
+.abstra/
+
+# Visual Studio Code
+#   Visual Studio Code specific template is maintained in a separate VisualStudioCode.gitignore that
+#   can be found at https://github.com/github/gitignore/blob/main/Global/VisualStudioCode.gitignore
+#   and can be added to the global gitignore or merged into this file. However, if you prefer, you
+#   could uncomment the following to ignore the entire vscode folder
+# .vscode/
+# Temporary file for partial code execution
+tempCodeRunnerFile.py
+
+# Ruff stuff:
+.ruff_cache/
+
+# PyPI configuration file
+.pypirc
+
+# Marimo
+marimo/_static/
+marimo/_lsp/
+__marimo__/
+
+# Streamlit
+.streamlit/secrets.toml

mutantlens-0.0.1/CLAUDE.md

@@ -0,0 +1,58 @@
+# mutantlens: instructions for Claude Code
+
+mutantlens measures whether a test suite actually catches bugs. It seeds small faults (mutants) into source code and counts how many the tests notice. An LLM loop then proposes tests for the faults nobody caught, and every proposed test must earn its place by killing a fault that previously survived.
+
+> **Name:** the project, package and CLI are `mutantlens`. Do not introduce another name.
+
+Read this file fully, then read ONLY the task row you were given and the component note it names, if one exists. Do not read the whole repo.
+
+## Where things are
+- Task list: `mutantlens-tasks.xlsx` (Tasks sheet), kept outside the repo. The row is pasted into your prompt. Tasks are identified by ID, e.g. `1.5`.
+- Component notes: `docs/components/Cxx-*.md`, written only when a task needs one. Architecture: `docs/architecture.md`. Decisions: `docs/decisions/`.
+- Stages and the current stage's gate: `docs/roadmap.md`. Workflow: `docs/development-workflow.md`. Testing: `docs/testing.md`.
+- What every run must record: `docs/metrics.md`. Index of all docs: `docs/index.md`.
+
+## Hard rules (a violation means stop and ask)
+
+1. **One stage at a time, one task at a time.** A stage is a small set of tasks that ends in something runnable you can see; each task is one component or one measurement. Work only on the task ID you were given and touch only the files it needs. Do not plan or build tasks for a later stage. If you notice other work, write it in the PR description and move on.
+2. **Interface before implementation.** Propose the types and signatures first and stop for approval. No implementation in the same turn as a new interface.
+3. **Measure before you generate.** No LLM code, no prompts and no model dependencies before Stage 3 (task 3.1 is the first). If an earlier task seems to need a model, the task is wrong: stop and say so.
+4. **The verifier decides, never the model and never you.** A test is accepted only when the mutation runner reports it killed a mutant that previously survived. Never accept a test because it looks correct, raises coverage, or the model said it was good.
+5. **Coverage is reported, never enforced.** No code path may gate on coverage delta.
+6. **All generated or mutated code runs in the sandbox** (`mutantlens/sandbox/`, built in task 1.6): never execute a model-written test or a mutated module outside it. Until 1.6 is done, mutated code may run unsandboxed ONLY on fixtures under `tests/fixtures/` or `toy/` in this repo, never on external code. The sandbox has no network, a read-only source mount, memory and CPU caps and a hard timeout.
+7. **One LLM gateway.** Only `mutantlens/llm/` imports a provider SDK. Everything else takes a client interface. Pin model snapshots, set temperature explicitly, validate every response against a Pydantic model. The one exception is the throwaway `spike/ask.py` in task 3.1.
+8. **Determinism is a feature.** Every run records its seed. Every model call goes through cassette record/replay. Tests never touch the live network and never need an API key.
+9. **Types grow with the task that first needs them.** Add only the fields the current task uses; no up-front contracts. Types live in `mutantlens/contracts/`, one small module each. After the first tagged release they are frozen: a change then needs a decision-log entry, a schema-snapshot update and its own task.
+10. **Never spend money without being asked.** Do not run paid model calls, corpus runs or evaluations. Print the exact command for the human to run, with an estimate of what it will cost.
+11. **No new dependency** without stating why, checking its licence is permissive, and checking it is maintained.
+12. **No scope creep.** No speculative abstraction, no refactor, no rename, no "while I'm here" cleanup, no code for a future task.
+
+**`spike/` is throwaway** (Stage 0 and task 3.1): exempt from rules 2, 14 and 15 and from ruff and pyright, never imported by `mutantlens/`. Stage 0 code is deleted at task 1.10; `spike/ask.py` is deleted once the gateway (3.2) replaces it. Keep it small and ugly; the point is to see the idea run and see where it hurts.
+13. **Record provenance on every run once the run store exists.** Config hash, tool git SHA, target repo SHA, model snapshot, seed, budgets. A result that cannot be traced to these did not happen.
+14. **Tests ship with the code,** including the edge case the task's concept brief warned about. Never delete or skip a test to get green.
+15. **Docs stay in sync** in the same pull request: the component note if there is one, `docs/architecture.md` if an interface moved, an ADR if a decision changed.
+16. **When a mistake repeats, add a rule here** rather than fixing it again.
+
+## Commands
+
+```bash
+uv sync                      # install
+uv run ruff check . && uv run ruff format --check .
+uv run pyright
+uv run pytest                # must pass with no network and no API key
+uv run mutantlens assess <path>    # the tool
+uv run mutantlens report <run-id>  # render a run
+```
+
+## Conventions
+- Python 3.12+, full type annotations, Pydantic v2 at every module boundary.
+- Pure functions in the core; IO at the edges. The mutation core does not touch the network or the clock.
+- Errors are values at boundaries: no uncaught exception escapes the CLI. Every failure becomes a typed outcome that lands in the run store.
+- Structured logging only. Never log an API key, never log full source files.
+- Mutants are identified by content hash, never by index or line number alone.
+
+## Out of scope unless the task says so
+Multi-language support, a web UI, a hosted service, multi-agent orchestration, fine-tuning, and anything in a later stage than the task you were given. Python only until the Python numbers are published.
+
+## What does NOT belong in this file
+Component details, API shapes, long examples, the task list, history. Those live in `docs/` and are read on demand.

mutantlens-0.0.1/CONTRIBUTING.md

@@ -0,0 +1,27 @@
+# Contributing
+
+Thanks for looking. This project is built in public, one task at a time, from a roadmap in `docs/roadmap.md`.
+
+## Before you open a PR
+
+- **One task per PR.** If there is no task for what you want to do, open an issue first and we will add one.
+- **Tests ship with code.** No live network, no API key required to run the suite.
+- **Generated or mutated code runs only in the sandbox.** This is a hard rule, including in tests and examples.
+- **Dependencies** need a permissive licence and a reason. No AGPL code enters this repository.
+
+## Setup
+
+```bash
+uv sync --all-extras --dev
+uv run pytest
+```
+
+The suite must pass with no network access and no provider key.
+
+## What makes a good contribution here
+
+The project's value is that its measurements are trustworthy. A change that makes the tool faster but could cause a killing test to be missed is a bad trade. If you are touching mutant identity, test selection or outcome classification, say in the PR how you convinced yourself it is still correct.
+
+## Reporting a result
+
+If you run mutantlens on a repository and the numbers look wrong, that is the most useful issue you can file. Include the config hash, the tool version, the target repository and commit, and the run record if you can share it.

mutantlens-0.0.1/LICENSE

@@ -0,0 +1,201 @@
+                                 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.

mutantlens-0.0.1/PKG-INFO

@@ -0,0 +1,35 @@
+Metadata-Version: 2.5
+Name: mutantlens
+Version: 0.0.1
+Summary: Measures whether a test suite actually catches bugs, by seeding small faults and counting how many the tests notice.
+License-Expression: Apache-2.0
+License-File: LICENSE
+Requires-Python: >=3.12
+Description-Content-Type: text/markdown
+
+# mutantlens
+
+**Does your test suite actually catch bugs?**
+
+mutantlens seeds small faults into your code and counts how many your tests notice. Line coverage tells you which lines ran; mutation score tells you which bugs would have been caught. They are not the same number, and the gap is usually large.
+
+> Status: **pre-alpha**, building in public.
+
+## Two things in one repository
+
+1. **The tool.** A CLI and GitHub Action that assesses the code in a pull request, fast enough to run on every PR. Scoped to the diff, with per-mutant test selection and caching.
+2. **The experiment.** A corpus harness that runs the same engine across many repositories and variants to answer one question: *does feeding surviving mutants back to an LLM actually produce better tests than asking once?* Existing evidence disagrees with itself, and the answer is reported either way.
+
+## How it works
+
+Scope the diff, seed faults, run only the tests whose coverage touches each fault, and report what survived. Where tests are missing, a model proposes new ones — and a proposed test is accepted only if it kills a fault that survived before. Coverage is reported and never enforced.
+
+See [docs/architecture.md](docs/architecture.md) and [docs/roadmap.md](docs/roadmap.md).
+
+## Quickstart
+
+Not yet. The first release comes once the tool is useful without an LLM.
+
+## Licence
+
+Apache-2.0 (add the standard text to `LICENSE` before the first public commit). Deliberately permissive: the previous leading tool in this space was AGPL-3.0 and unmaintained, which blocked the teams most likely to want it.

mutantlens-0.0.1/README.md

@@ -0,0 +1,26 @@
+# mutantlens
+
+**Does your test suite actually catch bugs?**
+
+mutantlens seeds small faults into your code and counts how many your tests notice. Line coverage tells you which lines ran; mutation score tells you which bugs would have been caught. They are not the same number, and the gap is usually large.
+
+> Status: **pre-alpha**, building in public.
+
+## Two things in one repository
+
+1. **The tool.** A CLI and GitHub Action that assesses the code in a pull request, fast enough to run on every PR. Scoped to the diff, with per-mutant test selection and caching.
+2. **The experiment.** A corpus harness that runs the same engine across many repositories and variants to answer one question: *does feeding surviving mutants back to an LLM actually produce better tests than asking once?* Existing evidence disagrees with itself, and the answer is reported either way.
+
+## How it works
+
+Scope the diff, seed faults, run only the tests whose coverage touches each fault, and report what survived. Where tests are missing, a model proposes new ones — and a proposed test is accepted only if it kills a fault that survived before. Coverage is reported and never enforced.
+
+See [docs/architecture.md](docs/architecture.md) and [docs/roadmap.md](docs/roadmap.md).
+
+## Quickstart
+
+Not yet. The first release comes once the tool is useful without an LLM.
+
+## Licence
+
+Apache-2.0 (add the standard text to `LICENSE` before the first public commit). Deliberately permissive: the previous leading tool in this space was AGPL-3.0 and unmaintained, which blocked the teams most likely to want it.