pytest-quint-connect 0.1.0__tar.gz

pytest_quint_connect-0.1.0/.gitignore

@@ -0,0 +1,22 @@
+.venv*/
+__pycache__/
+*.py[cod]
+.pytest_cache/
+.ruff_cache/
+.test-impact/
+impact-audit/
+dist/
+*.egg-info/
+.coverage
+coverage.xml
+htmlcov/
+tutorial-report.json
+
+# Built documentation
+/site/
+/.venv-docs/
+
+# Local judge credentials
+.env
+.artifacts/
+.impact-audit/

pytest_quint_connect-0.1.0/CHANGELOG.md

@@ -0,0 +1,16 @@
+# Changelog
+
+## 0.1.0 (2026-11-08)
+
+
+### Features
+
+* **codegen:** generate typed driver bases from the Quint model ([#2](https://github.com/gigaverse-app/pytest-quint-connect/issues/2)) ([156a334](https://github.com/gigaverse-app/pytest-quint-connect/commit/156a334c8c9996f6f0acb6bc806788b9de6162d0))
+* replay Quint-generated histories against Python implementations under pytest ([7db6585](https://github.com/gigaverse-app/pytest-quint-connect/commit/7db65854a1f0ae4c5c4ad5503297d624cf2d3163))
+
+
+### Bug fixes
+
+* **replay:** accept unbranched steps in the mbt cross-check, found by dogfooding ([#3](https://github.com/gigaverse-app/pytest-quint-connect/issues/3)) ([4892ec6](https://github.com/gigaverse-app/pytest-quint-connect/commit/4892ec6ac39ae44fcc8f15c5812c50f5338e1565))
+
+## Changelog

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

pytest_quint_connect-0.1.0/PKG-INFO

@@ -0,0 +1,229 @@
+Metadata-Version: 2.5
+Name: pytest-quint-connect
+Version: 0.1.0
+Summary: Model-based testing for Python: replay Quint-generated histories against real implementations under pytest
+Project-URL: Homepage, https://github.com/gigaverse-app/pytest-quint-connect
+Project-URL: Repository, https://github.com/gigaverse-app/pytest-quint-connect
+Project-URL: Issues, https://github.com/gigaverse-app/pytest-quint-connect/issues
+Project-URL: Changelog, https://github.com/gigaverse-app/pytest-quint-connect/blob/main/CHANGELOG.md
+Author: Gigaverse
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: formal-methods,itf,model-based-testing,pytest,quint,specification,testing
+Classifier: Development Status :: 3 - Alpha
+Classifier: Framework :: Pytest
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: Software Development :: Quality Assurance
+Classifier: Topic :: Software Development :: Testing
+Classifier: Typing :: Typed
+Requires-Python: >=3.11
+Requires-Dist: pytest>=8
+Description-Content-Type: text/markdown
+
+# pytest-quint-connect
+
+[![CI](https://github.com/gigaverse-app/pytest-quint-connect/actions/workflows/ci.yml/badge.svg?branch=main)](https://github.com/gigaverse-app/pytest-quint-connect/actions/workflows/ci.yml)
+[![Python 3.11+](https://img.shields.io/badge/python-3.11%2B-3776AB?logo=python&logoColor=white)](pyproject.toml)
+[![Quint 0.33.1](https://img.shields.io/badge/Quint-0.33.1-6E56CF)](https://quint.sh)
+[![Typed](https://img.shields.io/badge/typing-py.typed-3776AB)](src/pytest_quint_connect/py.typed)
+[![Apache-2.0](https://img.shields.io/badge/license-Apache--2.0-blue)](LICENSE)
+[![Agent skill](https://img.shields.io/badge/Agent_Skill-ready-2563EB)](skills/pytest-quint-connect/SKILL.md)
+
+**Model-based testing for Python under pytest.** [Quint](https://quint.sh)
+generates histories from your specification; pytest-quint-connect replays every
+step against your real Python implementation and compares the state you read back
+with the state the model expects.
+
+This is a community Python integration in the spirit of
+[Quint Connect](https://github.com/quint-co/quint-connect) (Rust) and
+[Quint's model-based testing guide](https://quint.sh/docs/model-based-testing).
+It is not an official Quint project and is not endorsed by its maintainers.
+
+```text
+test_lru_contract.py::test_lru_cache[witness-evictsLeastRecentlyUsedTest] FAILED
+
+Quint contract 'lru-cache': implementation state differs from the model
+  trace:  .artifacts/quint-connect/lru-cache/witness-evictsLeastRecentlyUsedTest-0.itf.json
+  state:  3 after action fetch(key='a', value=0)
+  seed:   7
+  4 difference(s):
+  entries[0].key: values differ
+      expected: 'b'
+      actual:   'a'
+  ...
+  reproduce: pytest test_lru_contract.py::test_lru_cache --quint-replay .artifacts/quint-connect/lru-cache/witness-evictsLeastRecentlyUsedTest-0.itf.json
+```
+
+## Quick start
+
+Install the plugin, plus Node.js 22+ with npm. On first use the plugin installs its
+locked Quint 0.33.1 into a per-user cache. To use your own Quint, pass `--quint PATH`
+or set `QUINT`.
+
+```bash
+pip install "pytest-quint-connect @ git+https://github.com/gigaverse-app/pytest-quint-connect"
+```
+
+Generate a typed driver base from the model, then declare the contract:
+
+```bash
+pytest-quint-connect codegen quint-connect.json -o lru_cache_driver.py
+```
+
+```python
+# test_cache_contract.py
+from pytest_quint_connect import quint_contract
+
+test_cache = quint_contract("quint-connect.json", driver="cache_driver")
+```
+
+Subclass the generated base. It has one typed method per model action and an
+`observe()` typed as the model's observed state, so a type checker flags a driver
+that has drifted from the spec:
+
+```python
+# conftest.py
+import pytest
+from lru_cache_driver import LruCacheDriver, Read, View  # generated
+from my_cache import LRUCache
+
+
+class CacheDriver(LruCacheDriver):
+    def __init__(self) -> None:
+        self.cache, self.last = LRUCache(2), {"tag": "NoRead"}
+
+    def init(self) -> None: ...
+    def inspect(self) -> None: ...
+
+    def store(self, key: str, value: int) -> None:  # apply one model action to the real code
+        self.cache.put(key, value)
+
+    def fetch(self, key: str) -> None:
+        value = self.cache.get(key)
+        self.last: Read = {"tag": "Miss"} if value is None else {"tag": "Hit", "value": value}
+
+    def observe(self) -> View:  # read the real state back
+        return {"entries": [{"key": k, "value": v} for k, v in self.cache.items()], "lastRead": self.last}
+
+
+@pytest.fixture
+def cache_driver():
+    return lambda context: CacheDriver()  # called once per history: fresh state each time
+```
+
+```bash
+pytest --quint-require-complete
+```
+
+A hand-written driver that implements `step(step)` and `observe()` works too; see
+[drivers](docs/drivers.md).
+
+[examples/lru_cache](examples/lru_cache) is the complete version. It checks a
+list-based cache and an `OrderedDict` refactor against the same generated
+histories, catches a cache whose reads forget to refresh recency, and runs from
+the installed wheel in CI.
+
+## What a contract run does
+
+```text
+quint-connect.json ──► quint typecheck ──► quint test  (named witnesses)  ──► witness-*.itf.json ─┐
+                                      └──► quint run --mbt (seeded samples) ──► sample-*.itf.json  ─┤
+                                                                                                 ▼
+pytest: test_x[witness-…] test_x[sample-N] ──► fresh driver per history ──► step → observe → compare
+        test_x[mutant-…]   every trace through the mutant; only an observed mismatch counts
+        test_x[coverage]   every declared action reached
+                                                                                                 ▼
+                     .artifacts/quint-connect/results.json, traces, logs, mismatch-*.json
+```
+
+- **Real pytest cases.** Each witness, sample, mutant and the coverage check is a
+  parametrized case: selectable with `-k`, listed by `--collect-only`, reported in
+  JUnit (with `quint_trace`, `quint_seed` and `quint_detected_by` properties),
+  with ordinary fixture setup and teardown.
+- **Fresh Quint, every run.** Traces are regenerated from the model with the
+  manifest's seed and bounds; the output directory is emptied first. Collection
+  never runs Quint; a Quint failure is a setup error for every case of that contract.
+- **Mutation controls.** A mutant passes only when some generated history produces
+  an observed-state mismatch. An exception while building or running the mutant fails
+  the case: it is not detection.
+- **Complete or not.** With `--quint-require-complete`, the session fails unless every
+  contract in `quint_required_contracts` ran every case and passed. A `-k`-filtered run
+  is recorded as `partial`, a replay as `replay-only`; a crash leaves `running`, never
+  an earlier `passed`.
+- **Actionable failures.** A mismatch names the trace, state, action and arguments,
+  a field-level expected/actual difference, the seed and a command that replays that
+  exact trace (`--quint-replay`, optionally `--quint-mutant`).
+
+## To / Read
+
+| To | Read |
+| --- | --- |
+| Set it up with an agent | [skills/pytest-quint-connect/SKILL.md](skills/pytest-quint-connect/SKILL.md) |
+| Write a manifest | [docs/manifest.md](docs/manifest.md) |
+| Write a driver and choose a step convention | [docs/drivers.md](docs/drivers.md) |
+| Know what a passing run does and does not prove | [docs/limits.md](docs/limits.md) |
+| Configure options and read the receipt | [docs/reference.md](docs/reference.md) |
+| See it on a production integration | [pytest-obligation's report-merge contract](https://github.com/gigaverse-app/pytest-obligation/tree/main/docs/quint/report-merge) |
+
+## Measured
+
+| Contract | Histories | Cases | Mutants detected | Notes |
+| --- | --- | --- | --- | --- |
+| [LRU cache example](examples/lru_cache) | 15 (3 witnesses, 12 samples) | 17 per implementation | 1/1 | list and `OrderedDict` implementations pass; the stale-read cache fails 4 of 15 histories |
+| pytest-obligation `merge_reports` | 21 (5 witnesses, 16 samples) | 28 | 6/6 | same 21 histories, state for state, as the runner it replaced |
+| [This plugin's own receipts](dogfood) | 8 (4 witnesses, 4 samples) | 13 | 4/4 | each step is a real pytest session; the mutants break the plugin's completeness and receipt logic |
+
+Quint 0.33.1, TypeScript backend. See [PROVENANCE.md](PROVENANCE.md) for where the
+engine came from and how the baseline was reproduced.
+
+### Duplicates kept out
+
+Local hooks and the required PR check prevent new copies. The weekly audit
+records progress against the accepted backlog. [Setup and cleanup workflow](CONTRIBUTING.md#duplication).
+
+<!-- dry-lint-progress:start -->
+<a href="https://github.com/gigaverse-app/dry-lint"><picture><source media="(prefers-color-scheme: dark)" srcset="https://dry-lint-counter.gigaverse-oss.workers.dev/v1/sign.svg?theme=dark&amp;key=bc47fb5de1a72359c95c190667ac9a84218d2ce822909a59d7e114ff2779542f&amp;name=gigaverse-app%2Fpytest-quint-connect&amp;cleaned=0&amp;remaining=5&amp;dismissed=0"><img alt="dry-lint in gigaverse-app/pytest-quint-connect: new duplicates kept out of its pull requests, 0 old duplicates cleaned up, 5 remaining" src="https://dry-lint-counter.gigaverse-oss.workers.dev/v1/sign.svg?key=bc47fb5de1a72359c95c190667ac9a84218d2ce822909a59d7e114ff2779542f&amp;name=gigaverse-app%2Fpytest-quint-connect&amp;cleaned=0&amp;remaining=5&amp;dismissed=0" width="100%"></picture></a>
+
+**Reviewed duplication debt** · Counts from the committed baselines.
+
+| Accepted pairs | Remaining | Retired | Dismissed |
+| :-- | --: | --: | --: |
+| Functions | 5 | 0 | 0 |
+| Models | Not initialized | — | — |
+
+[Accepted backlog](.dry-lint/baseline.json) · [Weekly audit](https://github.com/gigaverse-app/pytest-quint-connect/actions/workflows/dry-lint-audit.yml)
+
+Retired means a side was removed, or (functions only) the judge now finds the pair separate. It is not a count of refactors. Dismissals stay separate; an uninitialized model baseline is unknown.
+<!-- dry-lint-progress:end -->
+
+## Related projects
+
+| Project | What it does |
+| --- | --- |
+| [pytest-obligation](https://github.com/gigaverse-app/pytest-obligation) | Conformance proofs for background work that must survive lost messages and dead workers |
+| [Due](https://github.com/gigaverse-app/due) | Durable obligations for Python: PostgreSQL remembers what is owed |
+| [pytest-selective](https://github.com/gigaverse-app/pytest-selective) | Explainable test impact analysis for pytest |
+| [CI-esta](https://github.com/gigaverse-app/ci-esta) | CI observability and honest merge gates |
+| [dry-lint](https://github.com/gigaverse-app/dry-lint) | Finds code that re-implements what the codebase already does |
+
+## License
+
+Apache 2.0. See [CONTRIBUTING.md](CONTRIBUTING.md) to work on pytest-quint-connect
+itself and [RELEASING.md](RELEASING.md) for publishing.
+
+---
+
+[![CI measured by CI-esta](https://img.shields.io/badge/CI_measured_by-CI--esta-EA580C?logo=data%3Aimage%2Fsvg%2Bxml%3Bbase64%2CPHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHZpZXdCb3g9IjAgMCA2NCA2NCI%2BPHJlY3Qgd2lkdGg9IjY0IiBoZWlnaHQ9IjY0IiByeD0iMTUiIGZpbGw9IiNFQTU4MEMiLz48cGF0aCBkPSJNMTUgMzRsMTEgMTEgMjAtMjIiIGZpbGw9Im5vbmUiIHN0cm9rZT0iI2ZmZiIgc3Ryb2tlLXdpZHRoPSI3IiBzdHJva2UtbGluZWNhcD0icm91bmQiIHN0cm9rZS1saW5lam9pbj0icm91bmQiLz48cGF0aCBkPSJNNDYgN2gxMGwtMTAgMTBoMTAiIGZpbGw9Im5vbmUiIHN0cm9rZT0iI2ZmZiIgc3Ryb2tlLXdpZHRoPSIzLjUiIHN0cm9rZS1saW5lY2FwPSJyb3VuZCIgc3Ryb2tlLWxpbmVqb2luPSJyb3VuZCIvPjwvc3ZnPg%3D%3D)](https://github.com/gigaverse-app/ci-esta)
+
+[![Tests selected by pytest-selective](https://img.shields.io/badge/tests_selected_by-pytest--selective-2563EB)](https://github.com/gigaverse-app/pytest-selective)
+
+<sub>Pull requests run only the [test lanes](.github/test-lanes.json) and test files a
+change can affect, chosen by [pytest-selective](https://github.com/gigaverse-app/pytest-selective).
+[CI-esta](https://github.com/gigaverse-app/ci-esta) reports this repository's CI timing,
+keeps its test durations and owns its required gate. Neither is a dependency of
+pytest-quint-connect. See [how CI runs here](docs/ci-toolkit.md).</sub>

pytest_quint_connect-0.1.0/PROVENANCE.md

@@ -0,0 +1,45 @@
+# Provenance
+
+pytest-quint-connect was extracted from two working, application-specific Quint
+replay runners at Gigaverse, with authorization to open-source them:
+
+| Source | Commit | Files |
+| --- | --- | --- |
+| [pytest-obligation](https://github.com/gigaverse-app/pytest-obligation) | `6c923bff2c7fd1220cb837d14fbbf565e1b5c0e5` | `scripts/quint/replay.py`, `scripts/quint/test_replay.py`, `scripts/quint/README.md`, `scripts/quint/package.json`, `scripts/quint/package-lock.json`, `docs/quint/report-merge/` |
+| [Due](https://github.com/gigaverse-app/due) | `3709d585ffc6dd391e823e81d8000304f3ff906f` | `scripts/ci/check_quint_report.py`, `docs/quint/report-provenance/` |
+
+Both sources are Apache-2.0 projects of the same copyright holder.
+
+## What changed in the extraction
+
+- The generation, ITF decoding and replay engine is separated from pytest and has no
+  knowledge of either source repository: their hardcoded repository layout,
+  `pytest_obligation` import check, `docs/quint` discovery and source-mutation helper
+  became manifest fields (`root`, `attest`, `sources`) and consumer-owned driver code.
+- The single opaque runner became pytest cases: one per witness, sampled history,
+  mutant and action-coverage check, with fixtures, JUnit, selection and saved-trace replay.
+- The ITF decoder was rewritten. The original stringified map keys and decoded sets
+  to sorted lists, which is correct only for its one contract. The new decoder keeps
+  every Quint type distinct. [itf-py](https://github.com/konnov/itf-py) 0.5.0 was
+  evaluated and not used: it decodes records to namedtuples (so `{a: 1, b: 2}`,
+  `{b: 1, a: 2}` and the tuple `(1, 2)` compare equal), and it raises on every Quint
+  0.33.1 trace that contains a unit variant (`{"#tup": []}` is not a valid field name).
+- `--mbt` metadata is supported alongside the original explicit `event`/`observed`
+  convention, and cross-checked against it when both are present.
+- Due's runner contributed the checks for required exit status and per-trace output
+  status. Its report-provenance contract replays a shell workflow and has not been
+  migrated.
+
+## Baseline reproduction
+
+On pytest-obligation `6c923bff`, with Quint 0.33.1 on Windows,
+`python scripts/quint/replay.py --topic report-merge` passed **21 generated
+histories** (5 witnesses, 16 samples) and **detected all six mutations**. The same
+contract under pytest-quint-connect, from an installed wheel, generated the same 21
+histories (every `event` and `observed` value identical, state for state), passed
+all 28 cases and detected all six mutations. The original runner's negative
+controls (altered observation, empty trace, missing generation, missing tool with a
+stale success receipt, setup error during a mutant, edited historical model) are
+covered by `tests/test_replay.py` and `tests/test_plugin.py`.
+
+Copyright Gigaverse. Licensed under Apache-2.0; see [LICENSE](LICENSE).