inferlint 0.1.0__tar.gz

inferlint-0.1.0/.gitattributes

@@ -0,0 +1,3 @@
+# Store text with LF line endings so fixtures and scripts are identical on every OS.
+* text=auto eol=lf
+*.png binary

inferlint-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,22 @@
+name: ci
+
+on:
+  push:
+  pull_request:
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python: ["3.10", "3.11", "3.12"]
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python }}
+      - run: pip install -e ".[dev]"
+      - run: ruff check src tests
+      - run: ruff format --check src tests
+      - run: pyright
+      - run: pytest -q

inferlint-0.1.0/.gitignore

@@ -0,0 +1,13 @@
+# internal planning and tooling never ships
+*.internal.md
+_internal/
+
+__pycache__/
+*.pyc
+.venv/
+.pytest_cache/
+.ruff_cache/
+build/
+dist/
+*.egg-info/
+results/scratch/

inferlint-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.

inferlint-0.1.0/NOTICE

@@ -0,0 +1,4 @@
+inferlint
+Copyright 2026 RadianVector
+
+This product includes software developed by RadianVector (https://radianvector.com).

inferlint-0.1.0/PKG-INFO

@@ -0,0 +1,312 @@
+Metadata-Version: 2.5
+Name: inferlint
+Version: 0.1.0
+Summary: Things your inference server doesn't tell you, turned into checks.
+Project-URL: Homepage, https://github.com/radianvector/inferlint
+Project-URL: Source, https://github.com/radianvector/inferlint
+Project-URL: Issues, https://github.com/radianvector/inferlint/issues
+Project-URL: Documentation, https://github.com/radianvector/inferlint/blob/main/docs/tripwires.md
+Author-email: RadianVector <hello@radianvector.com>
+License-Expression: Apache-2.0
+License-File: LICENSE
+License-File: NOTICE
+Keywords: benchmark,gpu,inference,llm,prometheus,vllm
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Intended Audience :: Science/Research
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: System :: Benchmark
+Classifier: Typing :: Typed
+Requires-Python: >=3.10
+Provides-Extra: dev
+Requires-Dist: pyright>=1.1.390; extra == 'dev'
+Requires-Dist: pytest>=8; extra == 'dev'
+Requires-Dist: ruff>=0.9; extra == 'dev'
+Description-Content-Type: text/markdown
+
+# inferlint
+
+**Things your inference server doesn't tell you, turned into checks.**
+
+Serving benchmarks fail quietly. vLLM preempts requests and logs nothing. A config boots
+cleanly and dies on its first request. The KV pool you measured yesterday is not the one
+you got today. A cleanup script stops the API server and leaves the engine holding the
+GPU. None of these raise an error, and all of them change the numbers.
+
+`inferlint` turns each one into a check. You run it around a benchmark test: it reads
+the server's start-up log and counters, and tells you which of the test's numbers can be
+trusted. It does not start the server or send the load, so it works with the tools you
+already use.
+
+## One run, measured
+
+vLLM 0.28 on an RTX 4090, a 27B hybrid attention/Mamba model with 4-bit weights and
+CUDA graphs on. 32 concurrent requests, 1,000 output tokens each:
+
+```console
+$ inferlint preemption before.json after.json
+[ T1] FAIL  22 preemptions during the run
+$ grep -ci preempt boot.log
+0
+$ inferlint series run.series.jsonl --snapshot after.json --requested 32
+[T14] PASS  gauge denominator is 42 = num_gpu_blocks (43) - 1 null block
+[ T9] WARN  ceiling moved between 7 and 10 as requests grew (one request held 9.5% to 14.3% of the cache); concurrency was not a constant of this run
+[ T8] FAIL  requested 32 concurrent, server never ran more than 10
+```
+
+- The client held 32 requests in flight. The server never ran more than 10 at once.
+- A fresh request held 4 KV blocks, so 10 fit. As outputs crossed the 784-token block
+  boundary, running requests held up to 6 blocks each on average, and the number that
+  fit fell as low as 7. Each fall evicted running requests, 22 times in all, and the
+  server log says nothing about it.
+- The server exports 43 KV blocks, but the usage gauge counts in 42nds. One block is
+  reserved and never holds a request.
+
+Then the API server was killed with SIGKILL, as a crash or the OOM killer would:
+
+```console
+$ pkill -9 -f "vllm[ ]serve"; sleep 20
+$ ps -eo pid,ppid,rss,args | grep -E "[V]LLM::|[v]llm serve"
+   1030     423 2733144 VLLM::EngineCore
+$ inferlint gpu-inspect          # the GPU's model and memory lines are left out here
+[ T2] FAIL  card not clear; refusing to boot. ... 21768 MiB used, 1 server processes alive
+$ inferlint teardown
+target  pid=1030     VLLM::EngineCore
+(pkill -f 'vllm serve' would miss 1 and wrongly hit 0)
+[ T2] PASS  2 consecutive clear readings
+```
+
+The engine outlived its parent and kept 21.3 GiB of the card. The usual cleanup pattern
+cannot see it, and the next boot would have loaded a second copy into what was left.
+The raw files from this run are in
+[`tests/fixtures/vllm-0.28/live/`](https://github.com/radianvector/inferlint/tree/main/tests/fixtures/vllm-0.28/live),
+and `tests/test_live.py` pins every number above.
+
+## What it checks
+
+| id | trap | command |
+|---|---|---|
+| T1 | preemption is silent: a counter moves, no log line is written | `inferlint preemption BEFORE AFTER` |
+| T2 | `pkill -f "vllm serve"` misses the renamed `VLLM::EngineCore` | `inferlint teardown`, `inferlint gpu-inspect` |
+| T3 | `pkill -f` in a shell one-liner kills the shell | `inferlint teardown` |
+| T4 | the KV pool is drawn per boot, in discrete levels | `inferlint check-log BOOT...` |
+| T5 | hybrid models force a large attention block (the allocation unit) | `inferlint check-log` |
+| T6 | the requested attention backend is not applied to the speculative drafter | `inferlint check-log` |
+| T7 | a config boots, then dies on its first request | `inferlint probe URL` |
+| T8 | requested concurrency is not achieved concurrency | `inferlint series --requested N` |
+| T9 | the concurrency ceiling is `floor(1 / share)`, and it falls as requests grow | `inferlint series` |
+| T10 | integer-second timers are worth several percent | `inferlint rate BEFORE AFTER` |
+| T11 | KV memory differs between boots of one config | `inferlint check-log BOOT...` |
+| T12 | boot failures recorded without a reason | `inferlint check-log` |
+| T13 | a killed campaign's waiter adopts the next server | [docs/orchestration.md](https://github.com/radianvector/inferlint/blob/main/docs/orchestration.md) |
+| T14 | the KV usage gauge's denominator is `num_gpu_blocks - 1` | `inferlint series --snapshot` |
+
+Each is described in [docs/tripwires.md](https://github.com/radianvector/inferlint/blob/main/docs/tripwires.md)
+with its symptom, why it changes results, and a command that reproduces it from files in
+this repository.
+
+## Install
+
+```console
+pipx install inferlint
+inferlint --help
+```
+
+[pipx](https://pipx.pypa.io) gives `inferlint` an environment of its own and puts the
+command on your PATH, so it works in any terminal and from any folder, with nothing to
+activate. `uv tool install inferlint` does the same. To use it as a library, install it
+into your project's environment with `pip install inferlint` (see
+[Use it from Python](#use-it-from-python)).
+
+Python 3.10+, no dependencies. `teardown`, and the free-GPU check in `gpu-inspect`, find
+the server's processes through `/proc`, so they need Linux (or WSL), where vLLM runs.
+Everything else runs anywhere.
+
+## Use
+
+A test with inferlint takes as long as your benchmark. It checks one test at a time; it
+is not a monitor for a server that runs for days (Prometheus and Grafana do that job).
+
+Use two terminals on the GPU machine, in the same folder: **A** runs the server, **B**
+runs everything else.
+
+```bash
+# 1. Before the server starts (B)
+inferlint gpu-inspect                  # which GPU, its memory; fails if an old server still holds it
+
+# 2. Start the server (A): your usual command, saving its start-up output
+vllm serve MODEL 2>&1 | tee boot.log   # wait for "Application startup complete"
+
+#    then check it (B)
+inferlint check-log boot.log           # block size, attention backend, start-up failures
+inferlint probe http://127.0.0.1:8000  # sends 9 small requests: does it answer?
+
+# 3. The test (B)
+inferlint snapshot http://127.0.0.1:8000 -o before.json
+inferlint watch http://127.0.0.1:8000 -o run.series.jsonl --interval 0.25 &
+vllm bench serve --model MODEL --max-concurrency 32 ...   # your benchmark sends the load
+inferlint snapshot http://127.0.0.1:8000 -o after.json
+kill %1                                # stops the recording
+
+# 4. The verdict: one HTML page (any time later, on any computer)
+inferlint report -o run.html --requested 32 --boot-log boot.log \
+    --before before.json --after after.json --series run.series.jsonl
+
+# 5. Stop the server (B)
+inferlint teardown                     # stops every vLLM process, waits until the GPU is free
+```
+
+- **Your benchmark** sends the requests and reports speed and latency. inferlint reads
+  the server's side and says which of those numbers hold.
+- **`--requested`** is the concurrency your benchmark asked for (`--max-concurrency` in
+  `vllm bench serve`). Requests, tokens and preemptions come from the server's counters.
+- **Each command does one job and exits**, except `watch`. They only read, except
+  `probe` (9 small requests) and `teardown`, which stops the server: don't run it
+  against a server that is serving users.
+- **The same verdicts in the terminal:** `inferlint preemption before.json after.json`
+  (T1), `inferlint rate before.json after.json` (T10),
+  `inferlint series run.series.jsonl --snapshot after.json --requested 32` (T8, T9, T14).
+- **T4 and T11 compare start-ups:** keep the log of each start with the same settings and
+  pass them all (`--boot-log boot1.log --boot-log boot2.log`).
+- **In scripts,** `inferlint gpu-inspect || exit 1` and
+  `inferlint probe http://127.0.0.1:8000 || exit 1` stop a run before it produces bad
+  numbers. [docs/orchestration.md](https://github.com/radianvector/inferlint/blob/main/docs/orchestration.md)
+  covers scripts that run many tests.
+
+Exit status is 0 when every check passes (warnings allowed), 1 when one fails, and 2
+when one cannot decide because a series or a log line was missing. A missing series
+is never read as zero. `--json` gives machine-readable results; `--strict` fails on
+warnings.
+
+### The report
+
+`inferlint report` turns a run's files into one HTML page. It opens with a plain-English
+account of what happened (how long the test ran, requests finished and failed, tokens
+generated, time spent queued, which tripwires were checked and which need other
+files), then the verdicts, charts of what the server did over time, the boot facts, and
+a guide to every tripwire. Two collapsible glossaries explain the terms (token, KV
+pool, block, preemption) and what Pass, Warning, Fail and Can't tell mean: a Fail is a
+finding about the measurement, not a crash, except for T7 and T12.
+
+The page fetches nothing, so it opens offline and can be attached to a ticket as it is.
+It has a light/dark switch, every chart has a data table, and hovering (or the arrow
+keys) reads values at any moment.
+
+<picture>
+  <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/radianvector/inferlint/main/docs/report-dark.png">
+  <img alt="The report for the live run: what happened, the headline numbers, and 2 failures and 2 warnings" src="https://raw.githubusercontent.com/radianvector/inferlint/main/docs/report.png">
+</picture>
+
+**See a full example.**
+[`docs/example-report.html`](https://github.com/radianvector/inferlint/blob/main/docs/example-report.html)
+is the complete report for the run above: the charts, the findings and both glossaries.
+GitHub shows HTML files as source code, so open the file, choose **Download raw file**,
+and open it in any browser. It works offline.
+
+**Try it without a GPU.** The example is built from the recorded run in this repository.
+Download the repository for its files, and make the report yourself:
+
+```bash
+git clone https://github.com/radianvector/inferlint
+cd inferlint
+inferlint report -o example-report.html --title "vLLM 0.28 on an RTX 4090" --requested 32 \
+    --boot-log tests/fixtures/vllm-0.28/live/boot.log \
+    --before tests/fixtures/vllm-0.28/live/before.snapshot.json \
+    --after tests/fixtures/vllm-0.28/live/after.snapshot.json \
+    --series tests/fixtures/vllm-0.28/live/run.series.jsonl
+```
+
+`inferlint explain T9` prints the same plain-English explanation in the terminal.
+
+## Use it from Python
+
+Install it into your project's environment with `pip install inferlint`. Every check
+returns a `CheckResult` with a `status` (pass, warn, fail or unknown), a `message`, and
+the `evidence` behind it.
+
+```python
+import subprocess
+
+from inferlint import bootlog, checks, telemetry
+
+url = "http://127.0.0.1:8000"
+before = telemetry.scrape(url)
+subprocess.run(["vllm", "bench", "serve", "--model", "MODEL"], check=True)  # your benchmark
+after = telemetry.scrape(url)
+
+result = checks.check_no_preemption(before, after)
+print(result.status.value, result.message)  # fail 22 preemptions during the run
+result.raise_for_status()  # raises TripwireFailed on a Fail or a Can't tell
+
+facts = bootlog.parse_file("boot.log")
+print(facts.attention_block_size, facts.kv_pool_tokens)  # 784 26093
+record = {"boot": facts.result_block()}  # pool, block size, backend: keep with your results
+```
+
+`raise_for_status()` lets warnings through; `raise_for_status(allow_warn=False)` stops on
+them too.
+
+| module | what it gives you |
+|---|---|
+| `bootlog` | the facts in a start-up log (`parse_file`) |
+| `telemetry` | the server's counters (`scrape`, `load`) |
+| `series` | recordings made during a run (`watch`, `read`) |
+| `checks` | the checks, each returning a `CheckResult` |
+| `probe` | the first-request check (T7) |
+| `gpu` | which GPU, its family and memory (`read_gpus`) |
+| `teardown` | stopping the server and waiting for a free GPU (Linux) |
+| `report` | the HTML report (`build`, `render`) |
+
+## How it is tested
+
+- **Real evidence.** Fixtures are vLLM 0.28 boot logs and `/metrics` output from an
+  RTX 4090, with paths removed. Each check is tested against the case it exists for.
+- **Every check is watched failing.** `tests/test_mutations.py` changes one number or
+  line in real evidence and requires the verdict to flip.
+- **Instruments against ground truth.** The probe runs against a mock server with known
+  failure modes. Block-count inference (T14) is checked against the count the server
+  exports. The teardown's process matching runs on a synthetic `/proc` that includes the
+  shell one-liner and a bystander. GPU facts are parsed from real `nvidia-smi` output.
+- **Unknown formats are reported, not defaulted.** When a known log line changes format
+  in a new vLLM release, `boot-facts` lists it as unparsed instead of returning a value.
+
+## Develop
+
+To change the code, work from a clone in a virtual environment of its own, with the
+package installed in editable mode (edits take effect without reinstalling) and the test
+tools added:
+
+```bash
+git clone https://github.com/radianvector/inferlint
+cd inferlint
+python -m venv .venv
+source .venv/bin/activate          # Windows PowerShell: .venv\Scripts\Activate.ps1
+pip install -e ".[dev]"
+pytest -q                          # no GPU needed
+ruff check src tests && ruff format --check src tests && pyright
+```
+
+The last two lines are what CI runs on Python 3.10, 3.11 and 3.12.
+
+## Status
+
+Alpha. Every tripwire is tested against recorded vLLM 0.28 evidence. T1, T2, T5, T8, T9,
+T10 and T14 have also been re-measured by this code on a live vLLM 0.28 server. Next: one
+command that runs the whole sequence above, re-verification on the current vLLM release,
+and support for the llama.cpp `/metrics` subset.
+
+## About
+
+`inferlint` is made by [RadianVector](https://radianvector.com). RadianVector develops
+tools and research for evaluating and improving AI systems.
+
+## License
+
+Copyright 2026 RadianVector.
+
+This project, including the recorded evidence in `tests/fixtures/`, is licensed under the
+Apache License, Version 2.0. See [LICENSE](https://github.com/radianvector/inferlint/blob/main/LICENSE)
+for details.