agenttwin 0.1.1__tar.gz

agenttwin-0.1.1/CHANGELOG.md

@@ -0,0 +1,45 @@
+# Changelog
+
+Every release is tagged in git and published on PyPI.  The tape format is
+`schema 0.1` for all of them, so a tape recorded by an older release still
+replays on a newer one: the package version in the fingerprint is compared
+major.minor, so a patch release never invalidates a tape.
+
+## 0.1.1 — 2026-11-05
+
+Documentation, one viewer fix and one change of meaning; the tape format is
+untouched.
+
+### Added
+
+- `examples/hero.py` and `assets/hero.gif`: one committed tape replayed twice —
+  faithful first (exit 1), then with a single policy key changed (exit 0).  Both
+  README editions embed the animation and quote the same transcript, and
+  `tests/test_hero.py` keeps that transcript equal to a real run.
+- A `Changelog` link in the package metadata.
+
+### Fixed
+
+- The offline viewer's state-diff panel drew eighteen rows as ten-pixel slivers:
+  the list is a flex column with `overflow: auto`, so every row was shrinking to
+  fit instead of scrolling.  Rows keep their height now.
+- `README` installation instructions now lead with `pip install agenttwin`;
+  the `-e .` path is mentioned only for working on a checkout.
+
+### Changed
+
+- A replay that carries a patch or an explicit `policy=` now reports
+  `mode: counterfactual`, and its divergence no longer forces exit code 2 — the
+  assertions decide.  A faithful replay (neither supplied) still treats any
+  divergence as exit 2, which is the check that catches a controller that stopped
+  reproducing the recorded run.
+- `fingerprint._DEFAULT_VERSION` no longer repeats the package version; the
+  single source of truth is `agenttwin.__version__`.
+
+## 0.1.0 — 2026-11-05
+
+First public release: record / replay / counterfactual, the four drift classes,
+nine assertion factories plus combinators and YAML loading, seq-aligned
+`TraceDiff`, the single-file HTML viewer and report, the five `agenttwin`
+commands, the openai-compatible adapter, and ten bundled fixtures in five
+before/after pairs.

agenttwin-0.1.1/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.

agenttwin-0.1.1/MANIFEST.in

@@ -0,0 +1,2 @@
+include CHANGELOG.md
+include README.zh-CN.md

agenttwin-0.1.1/PKG-INFO

@@ -0,0 +1,347 @@
+Metadata-Version: 2.1
+Name: agenttwin
+Version: 0.1.1
+Summary: Frozen-replay for LLM agents: record one JSONL tape, replay it deterministically, diff what changed.
+Author: ravenkernel
+License: Apache-2.0
+Project-URL: Homepage, https://github.com/ravenkernel/agenttwin
+Project-URL: Source, https://github.com/ravenkernel/agenttwin
+Project-URL: Issues, https://github.com/ravenkernel/agenttwin/issues
+Project-URL: Changelog, https://github.com/ravenkernel/agenttwin/blob/main/CHANGELOG.md
+Keywords: llm,agents,replay,record,determinism,testing
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Software Development :: Testing
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Provides-Extra: yaml
+Requires-Dist: pyyaml; extra == "yaml"
+Provides-Extra: dev
+Requires-Dist: pytest>=7; extra == "dev"
+
+[English](README.md) · [中文](README.zh-CN.md)
+
+# AgentTwin
+
+**The VCR for agents.** Record one agent run to a tape, replay it offline afterwards, and you have a unit test you can commit to CI.
+
+Not a trace dashboard, not a monitoring platform: no service, no database, no dashboard, just one JSONL file and one ordinary assertion.
+
+![One failing tape, one policy change: the offline viewer, before and after](https://raw.githubusercontent.com/ravenkernel/agenttwin/main/assets/hero.gif)
+
+*One committed tape, replayed twice with no model call: two assertions fail, one policy key changes, all three pass. What you are looking at is a single HTML file, opened from `file://`.*
+
+The 30-second version:
+
+1. Recording calls the model and writes the request hash and the response into the tape;
+2. Replay calls no model and executes no real tool; it walks the tape event by event;
+3. A mismatch is a failure (not "run it again and see"); the assertion result ends up as a process exit code.
+
+Every code block below was actually run against this repository. The Python and YAML blocks run in order on the tape recorded by the first one; the shell blocks only need the fixtures that ship inside the package. The output under a block is the output of that run.
+
+## 1. Record one run
+
+`record_demo.py`
+
+```python
+"""Record one agent run to a JSONL tape.  Run: python record_demo.py"""
+import json
+
+from agenttwin import Twin
+
+
+def fake_llm(request):                    # stands in for your model client
+    return {"text": f"order {request['prompt']} is on its way"}
+
+
+def lookup_order(order_id):               # stands in for a real, side-effecting tool
+    return {"order_id": order_id, "status": "paid"}
+
+
+def agent(llm, tools):                    # your agent: identical when replaying
+    reply = llm({"prompt": "A-1"})
+    order = tools["lookup_order"]("A-1")
+    return {"answer": reply["text"], "status": order["status"]}
+
+
+with Twin.record("checkout", out="checkout.jsonl",
+                 llm=fake_llm, tools={"lookup_order": lookup_order}) as rec:
+    rec.returned(agent(rec.llm, rec.tools()))     # leaving the block writes the tape
+
+lines = open("checkout.jsonl", encoding="utf-8").read().splitlines()
+header = json.loads(lines[0])
+print("header:", header["schema_version"], header["trace_id"], "seed=" + str(header["seed"]))
+print("events:", " -> ".join(json.loads(line)["kind"] for line in lines[1:]))
+print("line 2:", lines[1][:96] + " ...")
+```
+
+Output:
+
+```text
+header: 0.1 checkout seed=0
+events: llm_call -> tool_call -> tool_result -> terminal
+line 2: {"actor":"llm","kind":"llm_call","payload":{"prompt_hash":"1d783fcd9d8b565fc5b19532a4538139c2ab6 ...
+```
+
+Only the last three lines do the recording: run the agent once inside `with Twin.record(...) as rec:`, keep the return value with `rec.returned(...)`, and the tape is written when the `with` block exits.
+
+`checkout.jsonl` is plain JSONL: the first line is the header (`schema_version` / `trace_id` / `seed` / `env_fingerprint` / `redaction`), then one event per line; there are exactly 8 `kind`s: `llm_call`, `tool_call`, `tool_result`, `state_patch`, `decision`, `human_input`, `error`, `terminal`. Any text tool can read it.
+
+## 2. Replay offline, then assert
+
+Keep going in the same directory:
+
+`replay_demo.py`
+
+```python
+"""Replay the tape offline and assert on it.  Run after record_demo.py, same dir."""
+import sys
+
+from agenttwin import Twin, asserts
+
+
+def agent(llm, tools):                    # the same agent, character for character
+    reply = llm({"prompt": "A-1"})
+    order = tools["lookup_order"]("A-1")
+    return {"answer": reply["text"], "status": order["status"]}
+
+
+report = Twin.load("checkout.jsonl").replay(agent)   # note: no llm=, no tools=
+report.assert_(
+    asserts.max_repeats("lookup_order", n=1),
+    asserts.never_calls("refund"),
+    asserts.terminates_within(10),
+)
+
+for result in report.results:
+    status = "SKIP" if result.passed is None else ("PASS" if result.passed else "FAIL")
+    print(f"{status}  {result.name}")
+page = report.html("report.html")         # one self-contained file, opens from file://
+print(f"html: {page.name} ({page.stat().st_size} bytes)")
+print(f"divergent: {report.divergent}")
+print(f"exit code: {report.exit_code}")
+sys.exit(report.exit_code)
+```
+
+Output:
+
+```text
+PASS  max_repeats(lookup_order, n=1)
+PASS  never_calls(refund)
+PASS  terminates_within(n=10)
+html: report.html (56546 bytes)
+divergent: False
+exit code: 0
+```
+
+Two things that are easy to miss:
+
+- `Twin.load("checkout.jsonl").replay(agent)` takes no `llm=` and no `tools=`: both the model and the tools come from the tape. `llm(...)` returns the response as recorded, `tools["lookup_order"](...)` returns the result as recorded, and the real functions are never called.
+- `sys.exit(report.exit_code)` turns the assertion result into an ordinary exit code that `pytest` or any CI consumes directly.
+
+The same result in three shapes: `report.markdown()` (a table for humans), `report.json()` (for machines, with fixed top-level keys `schema_version` / `trace_id` / `mode` / `divergent` / `exit_code` / `results` / `misses` / `drifts` / `diff` / `header`), and `report.html("report.html")` (a single-file report, no external references, opens straight from `file://`; the byte count above varies a little with the tape and the environment). The viewer carries an English/Chinese switch in its header (the choice is remembered in `localStorage`); the recorded tape text itself is never translated.
+
+### The whole loop in one command
+
+`examples/hero.py` is the animation at the top of this page: one tape from the fixtures that ship with the package, replayed twice, with one policy key changed between the two runs.
+
+```bash
+PYTHONPATH=src python examples/hero.py
+```
+
+Output:
+
+```text
+tape: deathloop.jsonl  (21 events)
+no model call, no network, no API key: the tape is the whole environment
+
+before  mode=replay  recorded (no policy passed)
+  exit code 1
+  FAIL  max_repeats(shell, n=3)  -- 6 calls of shell exceeds the limit of 3; first excess at seq 12  (seq 12)
+  FAIL  budget_within(calls<=8)  -- calls 13 > 8 (first excess at seq 12)  (seq 12)
+  PASS  never_calls(shell, args_contains='rm -rf')  -- no call of shell matches
+
+after   mode=counterfactual  policy={'max_attempts': 6, 'stop_on_failure': True}
+  exit code 0
+  PASS  max_repeats(shell, n=3)  -- 0 call(s) of shell (limit 3)
+  PASS  budget_within(calls<=8)  -- calls 2/8
+  PASS  never_calls(shell, args_contains='rm -rf')  -- no call of shell matches
+
+first divergence: seq 3  (same tape, different trajectory)
+reports: build/hero/before.html  build/hero/after.html
+```
+
+The word `counterfactual` in that banner is the point. A replay that carries a patch or its own policy is asking "what if", so the viewer labels it as one and its divergence is not a failure. A replay that carries neither has to reproduce the tape event for event, and divergence there is still exit code 2.
+
+## 3. A changed request is a hard failure
+
+```python
+"""A changed request is a hard failure, not a flaky test.  Run after record_demo.py."""
+from agenttwin import DriftError, Twin
+
+
+def changed_agent(llm, tools):
+    llm({"prompt": "A-2"})                # one value changed in the request
+    tools["lookup_order"]("A-1")
+
+
+try:
+    Twin.load("checkout.jsonl").replay(changed_agent)
+except DriftError as exc:                 # PromptDrift / ArgsDrift / FingerprintDrift
+    detail = exc.message.replace(exc.expected, exc.expected[:8] + "...").replace(exc.actual, exc.actual[:8] + "...")
+    print(f"{type(exc).__name__}: {detail}")
+    raise SystemExit(2)
+```
+
+Output:
+
+```text
+PromptDrift: prompt_hash mismatch at seq 0: tape expects 1d783fcd..., controller sent 4250ccd5...
+```
+
+Note that it raises instead of noting the mismatch and carrying on: the replay stops right there, and `SystemExit(2)` turns it into a red job in CI.
+
+## 4. Assertions can be data too (optional `[yaml]`)
+
+`asserts.yaml`:
+
+```yaml
+# The same three checks as replay_demo.py, kept as data.
+- {spec: max_repeats, args: {tool: lookup_order, n: 1}}
+- {spec: never_calls, args: {tool: refund}}
+- {spec: terminates_within, args: {n: 10}}
+```
+
+`yaml_demo.py`:
+
+```python
+"""The same three checks as data.  Run after record_demo.py."""
+from agenttwin import Twin, asserts
+
+
+def agent(llm, tools):
+    reply = llm({"prompt": "A-1"})
+    order = tools["lookup_order"]("A-1")
+    return {"answer": reply["text"], "status": order["status"]}
+
+
+report = Twin.load("checkout.jsonl").replay(agent)
+report.assert_(*asserts.load_yaml("asserts.yaml"))   # needs the [yaml] extra
+
+for result in report.results:
+    print(f"{'PASS' if result.passed else 'FAIL'}  {result.name}")
+print("exit code:", report.exit_code)
+```
+
+Output:
+
+```text
+PASS  max_repeats(lookup_order, n=1)
+PASS  never_calls(refund)
+PASS  terminates_within(n=10)
+exit code: 0
+```
+
+## What this tape does not promise
+
+This section sits on the second screen because the most common question is "why did nothing change when I changed the temperature".
+
+- **What is frozen is the request and the response as recorded, not an inference pass you can run again.** The model is not called a second time during replay, so sampling parameters (temperature / top_p / seed) do not participate and do not affect the result. Conversely, if your agent puts temperature into the request dict, it is part of the request, it changes the `prompt_hash`, and it raises `PromptDrift`: a changed request is supposed to fail.
+- **No real side effects.** A tool call during replay returns the `result` from the tape and the real function does not execute; there is no "call it for real while we are here" either, `Twin.load(..., allow_real=True)` raises `ValueError` outright.
+- **No second model call.** No network requests, no token bill; as many `llm_call`s as the tape holds is as many replays as you get, and not one more appears out of nowhere.
+- **All four drift kinds are hard failures.** `DriftError` and its three subclasses `PromptDrift` / `ArgsDrift` / `FingerprintDrift` are raised and stop the replay; `TapeMiss` (nothing recorded for that call) is not a drift and is not raised, but it also turns `exit_code` into 2.
+- **Replay is not "run the agent again".** A tape hit does not re-execute the model or the tool, and a tape miss does not degrade into a real call.
+
+## What it does not do
+
+| Not doing | Why |
+| --- | --- |
+| Calling the LLM again | Replay is worth exactly its determinism and its zero cost; for new results, record a new tape |
+| Producing real side effects | Replay has to run in CI, on a machine with no network |
+| Promising zero-config support for every framework | You write the agent as `agent(llm, tools)`, or as an object with `run(llm, tools)`; the tape knows nothing about your framework |
+| SaaS / dashboard / database | The tape is a file and the report is a file; there is no backend to host |
+| LLM-as-judge for pass or fail | The verdict has to be a deterministic assertion; asking a model to grade brings the uncertainty right back |
+
+## Install
+
+```bash
+python -m pip install agenttwin
+```
+
+Working on a clone of this repository instead, `python -m pip install -e .`.
+
+An extra dependency is needed only to read and write YAML assertion files (`pyyaml` is imported lazily, inside `load_yaml()` only):
+
+```bash
+python -m pip install "agenttwin[yaml]"
+```
+
+Python 3.10+, zero third-party dependencies at runtime: `pyproject.toml` declares `dependencies = []`, and `import agenttwin` does not pull in `pyyaml`.
+
+### Exit codes
+
+| code | meaning |
+| --- | --- |
+| 0 | everything PASSes (SKIP is not a failure) |
+| 1 | an assertion FAILed |
+| 2 | Drift / TapeMiss / SchemaError / incompatible schema |
+| 3 | configuration or install error (missing tape, broken assertion file, missing dependency) |
+
+`--strict` turns SKIP into 1, with precedence 3 > 2 > 1 > 0. `Report.exit_code` only ever produces 0 / 1 / 2; 3 comes from the CLI's usage and configuration layer (`EXIT_USAGE = 3` in `agenttwin.cli`: the tape does not exist, `--agent` is malformed, the assertion file cannot be read).
+
+### Command line
+
+Once installed, `agenttwin` and `python -m agenttwin` are the same entry point (`agenttwin.cli:main`), with five subcommands: `record` / `replay` / `diff` / `doctor` / `gallery`. To see the ten fixtures shipped with the repo (five before/after pairs, one per assertion family), without recording a tape first:
+
+```bash
+python -m agenttwin gallery list
+python -m agenttwin gallery run deathloop
+```
+
+Output (the second command prints the head of a report and its assertion table; the Diff / Fingerprint / Redaction sections in between are elided, `...` marks the gap):
+
+```text
+deathloop  Checkout retry loop
+repaired  Checkout that stops on the failed observation
+cleanup  Cleanup that deletes build/ with rm -rf
+cleanup_guarded  Cleanup that leaves the tree alone
+write_first  Release note written before the search
+search_first  Release note that cites what it found
+partial_receipt  Receipt without the charged total
+full_receipt  Receipt that carries the total it charged
+double_shipping  Order that pays shipping twice
+correct_shipping  Order priced once
+
+# AgentTwin report: gallery-deathloop
+
+verdict: FAIL (exit code 1)
+mode: replay
+divergent: no
+strict: no
+...
+| name | status | detail | first_offense_seq |
+| --- | --- | --- | --- |
+| max_repeats(shell, n=3) | FAIL | 6 calls of shell exceeds the limit of 3; first excess at seq 12 | 12 |
+| budget_within(calls<=8) | FAIL | calls 13 > 8 (first excess at seq 12) | 12 |
+| never_calls(shell, args_contains='rm -rf') | PASS | no call of shell matches | - |
+```
+
+`gallery run deathloop` exits 1 and `gallery run repaired` exits 0: same assertion set, and the only difference is whether that agent repeats the same tool call a thirteenth time. The other four pairs are the same shape: `cleanup` / `cleanup_guarded` (`never_calls`), `write_first` / `search_first` (`call_order`), `partial_receipt` / `full_receipt` (`output_schema`), `double_shipping` / `correct_shipping` (`state_invariant`). `python -m agenttwin <command> --help` shows the arguments of each command.
+
+## Status
+
+0.1.1 is published: [agenttwin on PyPI](https://pypi.org/project/agenttwin/0.1.1/), Apache-2.0, Python 3.10+. What changed in each release: [CHANGELOG.md](CHANGELOG.md).
+
+- Done and tested: the record/replay core (`Twin.record` / `Twin.load`), drift detection, 9 assertion factories plus the combinators and YAML loading, `TraceDiff`, `Report` (JSON / Markdown / single-file HTML), the five `agenttwin` subcommands, the openai-compatible adapter (duck-typed, no SDK import), and the ten bundled fixtures (five before/after pairs).
+- Verified on GitHub: [CI](https://github.com/ravenkernel/agenttwin/actions) runs on every push to `main` — eight jobs: Python 3.10–3.13 on Ubuntu, 3.12 on macOS and Windows, and two stdlib-only import checks that uninstall PyYAML first, plus a console-script step in each. The first run failed on a fixture that used `platform: linux` and therefore matched the real `sys.platform` on the Ubuntu runners; that was a test bug, fixed in `6c5dae7`, and the suite has been green since.
+- Verified from a clean install: `python -m pip install agenttwin` into an empty venv from the public index gives `agenttwin --version` → `agenttwin 0.1.1`, all ten fixtures from `agenttwin gallery list`, the bundled single-file HTML replayer, `gallery run repaired` → 0 and `gallery run deathloop` → 1. A record → offline replay → `.html()` loop run from an empty directory outside the repository produced a report with no unfilled placeholder and no external resource in it.
+- Not done yet: a coverage gate, any hosted service or dashboard. The examples above run with `PYTHONPATH=src` so they work without installing anything.