deterministic-scenario-engine 2.1.0__tar.gz → 2.1.2__tar.gz

{deterministic_scenario_engine-2.1.0/src/deterministic_scenario_engine.egg-info → deterministic_scenario_engine-2.1.2}/PKG-INFO

@@ -1,8 +1,13 @@
 Metadata-Version: 2.4
 Name: deterministic-scenario-engine
-Version: 2.1.0
+Version: 2.1.2
 Summary: Reproducible, state-consistent business scenarios with deterministic ground truth
 License-Expression: Apache-2.0
+Project-URL: Homepage, https://github.com/imshahinul/deterministic-scenario-engine
+Project-URL: Documentation, https://github.com/imshahinul/deterministic-scenario-engine/tree/main/docs
+Project-URL: Source, https://github.com/imshahinul/deterministic-scenario-engine
+Project-URL: Issues, https://github.com/imshahinul/deterministic-scenario-engine/issues
+Project-URL: Release Notes, https://github.com/imshahinul/deterministic-scenario-engine/releases
 Keywords: deterministic,scenario,testing,fixtures,replay
 Classifier: Development Status :: 5 - Production/Stable
 Classifier: Intended Audience :: Developers
@@ -20,6 +25,7 @@ License-File: LICENSE
 Requires-Dist: PyYAML==6.0.3
 Provides-Extra: pytest
 Requires-Dist: pytest<10,>=9.1; extra == "pytest"
+Requires-Dist: build<2,>=1; extra == "pytest"
 Provides-Extra: sqlalchemy
 Requires-Dist: SQLAlchemy<3,>=2.0; extra == "sqlalchemy"
 Provides-Extra: hypothesis
@@ -35,11 +41,10 @@ Dynamic: license-file
 
 Deterministic Scenario Engine (DSE) creates reproducible, state-consistent
 business histories and deterministic scenario suites with ground truth for
-testing. The published distribution is `deterministic-scenario-engine` 2.0.0.
-Phase 3 evidence-interchange capabilities are implemented on `main` and the
-current source release candidate reports distribution version 2.1.0, while 2.1.0
-is not published. Its deterministic compatibility version remains
-`ENGINE_VERSION == "1.0.0"`, and its DSL version remains integer 1.
+testing. The source-tree distribution version is 2.1.2. Distribution release
+identity and deterministic compatibility identity are separate:
+`ENGINE_VERSION` remains 1.0.0 and DSL version remains 1. For authoritative
+public-release availability and history, see PyPI and GitHub Releases.
 
 ## Why it exists
 
@@ -74,11 +79,11 @@ make expected behavior explicit.
   explicit adapters, closed lossless migrations, and fixture-directory export
 
 Core execution does not require a database, network service, plugin, or property
-testing framework. See [security assumptions and non-goals](docs/security-and-non-goals.md).
+testing framework. See [security assumptions and non-goals](https://github.com/imshahinul/deterministic-scenario-engine/blob/main/docs/security-and-non-goals.md).
 Neither Phase 2 nor Phase 3 adds hidden discovery, network, randomness,
 wall-clock, or ambient environment semantics. The historical Phase 2 contract
-is frozen in the [Phase 2 public contract](docs/phase2-public-contract.md); the
-additive evidence surface is frozen in the [Phase 3 public contract](docs/phase3-public-contract.md).
+is frozen in the [Phase 2 public contract](https://github.com/imshahinul/deterministic-scenario-engine/blob/main/docs/phase2-public-contract.md); the
+additive evidence surface is frozen in the [Phase 3 public contract](https://github.com/imshahinul/deterministic-scenario-engine/blob/main/docs/phase3-public-contract.md).
 
 ## Installation
 
@@ -98,13 +103,13 @@ Install only the named optional integrations you need:
 /tmp/scenario-engine-docs-venv/bin/python -m pip install '.[schemathesis]'
 ```
 
-The published distribution is `deterministic-scenario-engine` 2.0.0. Install the package
-with `pip install deterministic-scenario-engine`, or select an optional integration
-with a command such as `pip install 'deterministic-scenario-engine[pytest]'`.
+Install the package with `pip install deterministic-scenario-engine`, or select
+an optional integration with a command such as
+`pip install 'deterministic-scenario-engine[pytest]'`.
 
 ## Minimal quickstart
 
-The public [cart scenario](examples/cart.yaml) is an executable DSL 1 document.
+The public [cart scenario](https://github.com/imshahinul/deterministic-scenario-engine/blob/main/examples/cart.yaml) is an executable DSL 1 document.
 Run it from the repository root:
 
 ```python
@@ -139,32 +144,31 @@ normalized result contains the same data under its `state` field.
 Generation derives from semantic `ExecutionAddress` values, not consumption of
 a mutable global random stream. Exact replay requires the same canonical
 scenario, explicit inputs, algorithms/plugins, and recorded execution context.
-Unsupported cross-version replay fails explicitly. See the [determinism model](docs/determinism.md),
-[reproducibility guide](docs/reproducibility.md), and normative
-[compatibility contract](docs/compatibility.md).
+Unsupported cross-version replay fails explicitly. See the [determinism model](https://github.com/imshahinul/deterministic-scenario-engine/blob/main/docs/determinism.md),
+[reproducibility guide](https://github.com/imshahinul/deterministic-scenario-engine/blob/main/docs/reproducibility.md), and normative
+[compatibility contract](https://github.com/imshahinul/deterministic-scenario-engine/blob/main/docs/compatibility.md).
 
 ## Documentation
 
-- [Quickstart](docs/quickstart.md)
-- [DSL 1 reference](docs/dsl-reference.md)
-- [Determinism model](docs/determinism.md)
-- [Reproducibility and replay](docs/reproducibility.md)
-- [Testing, faults, and oracle](docs/testing-oracle.md)
-- [Plugins](docs/plugins.md)
-- [SQLAlchemy adapter](docs/sqlalchemy.md)
-- [Hypothesis integration](docs/hypothesis.md)
-- [Schemathesis integration](docs/schemathesis.md)
-- [Public Python API](docs/api.md)
-- [Security assumptions and non-goals](docs/security-and-non-goals.md)
-- [Compatibility contract](docs/compatibility.md)
-- [Phase 2 public contract, CLI, and hard bounds](docs/phase2-public-contract.md)
-- [Phase 3 public contract and evidence interchange](docs/phase3-public-contract.md)
+- [Quickstart](https://github.com/imshahinul/deterministic-scenario-engine/blob/main/docs/quickstart.md)
+- [DSL 1 reference](https://github.com/imshahinul/deterministic-scenario-engine/blob/main/docs/dsl-reference.md)
+- [Determinism model](https://github.com/imshahinul/deterministic-scenario-engine/blob/main/docs/determinism.md)
+- [Reproducibility and replay](https://github.com/imshahinul/deterministic-scenario-engine/blob/main/docs/reproducibility.md)
+- [Testing, faults, and oracle](https://github.com/imshahinul/deterministic-scenario-engine/blob/main/docs/testing-oracle.md)
+- [Plugins](https://github.com/imshahinul/deterministic-scenario-engine/blob/main/docs/plugins.md)
+- [SQLAlchemy adapter](https://github.com/imshahinul/deterministic-scenario-engine/blob/main/docs/sqlalchemy.md)
+- [Hypothesis integration](https://github.com/imshahinul/deterministic-scenario-engine/blob/main/docs/hypothesis.md)
+- [Schemathesis integration](https://github.com/imshahinul/deterministic-scenario-engine/blob/main/docs/schemathesis.md)
+- [Public Python API](https://github.com/imshahinul/deterministic-scenario-engine/blob/main/docs/api.md)
+- [Security assumptions and non-goals](https://github.com/imshahinul/deterministic-scenario-engine/blob/main/docs/security-and-non-goals.md)
+- [Compatibility contract](https://github.com/imshahinul/deterministic-scenario-engine/blob/main/docs/compatibility.md)
+- [Phase 2 public contract, CLI, and hard bounds](https://github.com/imshahinul/deterministic-scenario-engine/blob/main/docs/phase2-public-contract.md)
+- [Phase 3 public contract and evidence interchange](https://github.com/imshahinul/deterministic-scenario-engine/blob/main/docs/phase3-public-contract.md)
 
 ## Status
 
 Distribution release identity and deterministic engine compatibility are
-separate contracts. Version 2.0.0 has been published to PyPI and as a GitHub
-Release. This source tree reports the unpublished 2.1.0 release candidate;
-generated core manifests retain `ENGINE_VERSION` 1.0.0 and DSL 1. No 2.1.0 tag,
-GitHub Release, or package-index publication exists. The project is licensed
-under Apache-2.0.
+separate contracts. This source tree reports distribution version 2.1.2;
+generated core manifests retain `ENGINE_VERSION` 1.0.0 and DSL 1. PyPI and
+GitHub Releases are the authoritative sources for public-release availability
+and history. The project is licensed under Apache-2.0.

{deterministic_scenario_engine-2.1.0 → deterministic_scenario_engine-2.1.2}/README.md

@@ -4,11 +4,10 @@
 
 Deterministic Scenario Engine (DSE) creates reproducible, state-consistent
 business histories and deterministic scenario suites with ground truth for
-testing. The published distribution is `deterministic-scenario-engine` 2.0.0.
-Phase 3 evidence-interchange capabilities are implemented on `main` and the
-current source release candidate reports distribution version 2.1.0, while 2.1.0
-is not published. Its deterministic compatibility version remains
-`ENGINE_VERSION == "1.0.0"`, and its DSL version remains integer 1.
+testing. The source-tree distribution version is 2.1.2. Distribution release
+identity and deterministic compatibility identity are separate:
+`ENGINE_VERSION` remains 1.0.0 and DSL version remains 1. For authoritative
+public-release availability and history, see PyPI and GitHub Releases.
 
 ## Why it exists
 
@@ -43,11 +42,11 @@ make expected behavior explicit.
   explicit adapters, closed lossless migrations, and fixture-directory export
 
 Core execution does not require a database, network service, plugin, or property
-testing framework. See [security assumptions and non-goals](docs/security-and-non-goals.md).
+testing framework. See [security assumptions and non-goals](https://github.com/imshahinul/deterministic-scenario-engine/blob/main/docs/security-and-non-goals.md).
 Neither Phase 2 nor Phase 3 adds hidden discovery, network, randomness,
 wall-clock, or ambient environment semantics. The historical Phase 2 contract
-is frozen in the [Phase 2 public contract](docs/phase2-public-contract.md); the
-additive evidence surface is frozen in the [Phase 3 public contract](docs/phase3-public-contract.md).
+is frozen in the [Phase 2 public contract](https://github.com/imshahinul/deterministic-scenario-engine/blob/main/docs/phase2-public-contract.md); the
+additive evidence surface is frozen in the [Phase 3 public contract](https://github.com/imshahinul/deterministic-scenario-engine/blob/main/docs/phase3-public-contract.md).
 
 ## Installation
 
@@ -67,13 +66,13 @@ Install only the named optional integrations you need:
 /tmp/scenario-engine-docs-venv/bin/python -m pip install '.[schemathesis]'
 ```
 
-The published distribution is `deterministic-scenario-engine` 2.0.0. Install the package
-with `pip install deterministic-scenario-engine`, or select an optional integration
-with a command such as `pip install 'deterministic-scenario-engine[pytest]'`.
+Install the package with `pip install deterministic-scenario-engine`, or select
+an optional integration with a command such as
+`pip install 'deterministic-scenario-engine[pytest]'`.
 
 ## Minimal quickstart
 
-The public [cart scenario](examples/cart.yaml) is an executable DSL 1 document.
+The public [cart scenario](https://github.com/imshahinul/deterministic-scenario-engine/blob/main/examples/cart.yaml) is an executable DSL 1 document.
 Run it from the repository root:
 
 ```python
@@ -108,32 +107,31 @@ normalized result contains the same data under its `state` field.
 Generation derives from semantic `ExecutionAddress` values, not consumption of
 a mutable global random stream. Exact replay requires the same canonical
 scenario, explicit inputs, algorithms/plugins, and recorded execution context.
-Unsupported cross-version replay fails explicitly. See the [determinism model](docs/determinism.md),
-[reproducibility guide](docs/reproducibility.md), and normative
-[compatibility contract](docs/compatibility.md).
+Unsupported cross-version replay fails explicitly. See the [determinism model](https://github.com/imshahinul/deterministic-scenario-engine/blob/main/docs/determinism.md),
+[reproducibility guide](https://github.com/imshahinul/deterministic-scenario-engine/blob/main/docs/reproducibility.md), and normative
+[compatibility contract](https://github.com/imshahinul/deterministic-scenario-engine/blob/main/docs/compatibility.md).
 
 ## Documentation
 
-- [Quickstart](docs/quickstart.md)
-- [DSL 1 reference](docs/dsl-reference.md)
-- [Determinism model](docs/determinism.md)
-- [Reproducibility and replay](docs/reproducibility.md)
-- [Testing, faults, and oracle](docs/testing-oracle.md)
-- [Plugins](docs/plugins.md)
-- [SQLAlchemy adapter](docs/sqlalchemy.md)
-- [Hypothesis integration](docs/hypothesis.md)
-- [Schemathesis integration](docs/schemathesis.md)
-- [Public Python API](docs/api.md)
-- [Security assumptions and non-goals](docs/security-and-non-goals.md)
-- [Compatibility contract](docs/compatibility.md)
-- [Phase 2 public contract, CLI, and hard bounds](docs/phase2-public-contract.md)
-- [Phase 3 public contract and evidence interchange](docs/phase3-public-contract.md)
+- [Quickstart](https://github.com/imshahinul/deterministic-scenario-engine/blob/main/docs/quickstart.md)
+- [DSL 1 reference](https://github.com/imshahinul/deterministic-scenario-engine/blob/main/docs/dsl-reference.md)
+- [Determinism model](https://github.com/imshahinul/deterministic-scenario-engine/blob/main/docs/determinism.md)
+- [Reproducibility and replay](https://github.com/imshahinul/deterministic-scenario-engine/blob/main/docs/reproducibility.md)
+- [Testing, faults, and oracle](https://github.com/imshahinul/deterministic-scenario-engine/blob/main/docs/testing-oracle.md)
+- [Plugins](https://github.com/imshahinul/deterministic-scenario-engine/blob/main/docs/plugins.md)
+- [SQLAlchemy adapter](https://github.com/imshahinul/deterministic-scenario-engine/blob/main/docs/sqlalchemy.md)
+- [Hypothesis integration](https://github.com/imshahinul/deterministic-scenario-engine/blob/main/docs/hypothesis.md)
+- [Schemathesis integration](https://github.com/imshahinul/deterministic-scenario-engine/blob/main/docs/schemathesis.md)
+- [Public Python API](https://github.com/imshahinul/deterministic-scenario-engine/blob/main/docs/api.md)
+- [Security assumptions and non-goals](https://github.com/imshahinul/deterministic-scenario-engine/blob/main/docs/security-and-non-goals.md)
+- [Compatibility contract](https://github.com/imshahinul/deterministic-scenario-engine/blob/main/docs/compatibility.md)
+- [Phase 2 public contract, CLI, and hard bounds](https://github.com/imshahinul/deterministic-scenario-engine/blob/main/docs/phase2-public-contract.md)
+- [Phase 3 public contract and evidence interchange](https://github.com/imshahinul/deterministic-scenario-engine/blob/main/docs/phase3-public-contract.md)
 
 ## Status
 
 Distribution release identity and deterministic engine compatibility are
-separate contracts. Version 2.0.0 has been published to PyPI and as a GitHub
-Release. This source tree reports the unpublished 2.1.0 release candidate;
-generated core manifests retain `ENGINE_VERSION` 1.0.0 and DSL 1. No 2.1.0 tag,
-GitHub Release, or package-index publication exists. The project is licensed
-under Apache-2.0.
+separate contracts. This source tree reports distribution version 2.1.2;
+generated core manifests retain `ENGINE_VERSION` 1.0.0 and DSL 1. PyPI and
+GitHub Releases are the authoritative sources for public-release availability
+and history. The project is licensed under Apache-2.0.

{deterministic_scenario_engine-2.1.0 → deterministic_scenario_engine-2.1.2}/docs/phase2-architecture.md

@@ -275,7 +275,7 @@ From the 2026-09-03 freeze, the likely range is roughly late October through lat
 
 ## V1 Contract Validation
 
-Pre-mutation validation ran from repository root `/Users/smshahinulislam/Developer/scenario-engine` on branch `main`. HEAD/main/origin-main were `ee29f52f714e84f17e1048ce24192fcf1c69345a`, tree `2a61915d578dcb1c4ec94049350a24d2cabdf721`, divergence `0/0`, with zero staged, unstaged, or untracked paths. The sole remote was `origin`, resolving to public `imshahinul/deterministic-scenario-engine`; tag `1.0.0` peeled to the baseline and its tree.
+Pre-mutation validation ran from `<repository-root>` on branch `main`. HEAD/main/origin-main were `ee29f52f714e84f17e1048ce24192fcf1c69345a`, tree `2a61915d578dcb1c4ec94049350a24d2cabdf721`, divergence `0/0`, with zero staged, unstaged, or untracked paths. The sole remote was `origin`, resolving to public `imshahinul/deterministic-scenario-engine`; tag `1.0.0` peeled to the baseline and its tree.
 
 Validation used CPython 3.14.6 in isolated environment `/tmp/dse-phase2-0a-venv`, pytest 9.1.1, PyYAML 6.0.3, SQLAlchemy 2.0.52, Hypothesis 6.167.1, and Schemathesis 4.25.2, with repository `src` on `PYTHONPATH`. Canonical validation is `python -m pytest -q`; collection is `python -m pytest --collect-only -q`. It collected 280 tests and the full run passed: `280 passed, 136 subtests passed` in 41.94 seconds. Focused golden enforcement passed 4 tests and 3 subtests.
 

deterministic_scenario_engine-2.1.2/docs/product-evidence-gate.md

@@ -0,0 +1,65 @@
+# Product evidence gate
+
+A successfully shipped phase does not automatically authorize design or
+implementation of the next feature phase.
+
+## Demand evidence requirement
+
+Before Phase 4 product scope can be frozen, every proposed substantial
+capability must trace to credible evidence of an actual problem. Acceptable
+evidence includes:
+
+- an external user report or request;
+- a public issue or discussion describing real friction;
+- observed integration failure or friction;
+- a repeated support question;
+- a real downstream implementation needing the capability;
+- credible usage or adoption evidence combined with a specific observed
+  problem.
+
+The following is insufficient by itself: ability to build something,
+architectural fit or elegance, previous deferral, download counts, GitHub stars,
+benchmark opportunities, or feature parity with another tool.
+
+## Maintenance exceptions
+
+Product-demand evidence is not required before addressing a confirmed bug,
+security vulnerability, compatibility regression, release-integrity defect,
+dependency or platform breakage, data-loss or correctness issue, or maintenance
+needed to preserve an existing public contract. Such work instead requires
+evidence of the defect or risk.
+
+## Phase 4 evidence packet
+
+No Phase 4 architecture freeze or implementation prompt is authorized until an
+evidence packet exists. For every candidate substantial feature, it must record:
+
+- problem statement;
+- evidence source and date;
+- affected user or workflow;
+- observed current workaround or failure;
+- why DSE itself should solve the problem;
+- why external tooling is insufficient;
+- minimum useful outcome;
+- evidence strength.
+
+Classify each candidate as `SUPPORTED_BY_EVIDENCE`, `WEAK_EVIDENCE`, or
+`NO_EVIDENCE`. Only supported items may enter MUST or SHOULD scope. Weak items
+remain observational; unsupported items go to the parking lot or are deferred.
+This policy does not itself create a Phase 4 feature list.
+
+## Adoption observation
+
+Downloads, stars, forks, clones, and traffic may be recorded as context but do
+not prove a feature need. Preferred evidence combines a specific observed
+problem, credible user/workflow context, and repeatability or consequence.
+Quantitative adoption data is supporting evidence, not the product requirement.
+
+Until qualifying external problem evidence and the required packet exist:
+
+```text
+PHASE4_AUTHORIZED=NO
+PHASE4_ARCHITECTURE_STARTED=NO
+PHASE4_IMPLEMENTATION_STARTED=NO
+NEXT_ACTIVITY=ADOPTION_AND_PROBLEM_OBSERVATION
+```

deterministic_scenario_engine-2.1.2/docs/release-process.md

@@ -0,0 +1,63 @@
+# Release process
+
+The package README is the PyPI long description. It must describe durable
+product and version semantics, not transient publication state. Statements such
+as "unpublished", "no current-version tag", "no GitHub Release", or "no
+package-index publication" belong only in checkpoint evidence, release audits,
+or temporary release-candidate reports.
+
+## Pre-RC
+
+Before building artifacts:
+
+- run the README release-state-neutrality test;
+- require `PRE_RC_PYPI_LINK_PORTABILITY=PASS` by rejecting repository-relative
+  file links in the package README and checking internal anchors separately;
+- confirm the configured package long-description material passes the same
+  neutrality test.
+
+## RC
+
+Release-candidate evidence may record that publication, a tag, or a release is
+absent. Package long-description material may not encode those transient facts.
+
+## Pre-upload
+
+Immediately before `twine upload`, rerun the source README neutrality test and
+inspect the accepted wheel and sdist metadata to confirm their packaged
+README/long description is release-state neutral. Require
+`PREUPLOAD_PYPI_LINK_PORTABILITY=PASS` for both artifact descriptions, run
+`twine check` and record `TWINE_RENDER_CHECK=PASS`, and resolve every important
+absolute documentation target to record `PYPI_LINK_TARGET_CHECK=PASS`.
+
+## Publication
+
+Publish the exact accepted artifacts. Do not rebuild between acceptance and
+publication.
+
+## Post-publication completion gate
+
+Using fresh public observations rather than pre-upload text, verify:
+
+- the PyPI version exists and its hashes exactly match the accepted artifacts;
+- a production installation passes;
+- the release tag targets the exact accepted commit;
+- the GitHub Release exists and its asset hashes exactly match;
+- the canonical README remains consistent with durable version semantics;
+- package documentation still satisfies the release-state policy;
+- fresh inspection of the rendered PyPI project page proves that documentation,
+  examples, security, compatibility, license, and repository links resolve to
+  their intended destinations, recording `POSTPUBLICATION_PYPI_LINK_SMOKE=PASS`.
+
+`twine check` alone is not sufficient for link portability. The post-publication
+gate must inspect the live PyPI description and its rendered link targets.
+
+Only after every post-publication check passes may checkpoint evidence record
+`PHASE_COMPLETE=YES`. A post-publication check must never rely solely on text
+prepared before upload.
+
+Published wheel and sdist metadata is immutable. If stale long-description text
+has already shipped, record it as a known published-artifact limitation; do not
+rewrite, rebuild, republish, or yank an otherwise accepted release merely to
+alter that text. The durable correction applies to canonical `main` and future
+artifacts.

{deterministic_scenario_engine-2.1.0 → deterministic_scenario_engine-2.1.2}/pyproject.toml

@@ -25,11 +25,18 @@ classifiers = [
 ]
 dependencies = ["PyYAML==6.0.3"]
 
+[project.urls]
+Homepage = "https://github.com/imshahinul/deterministic-scenario-engine"
+Documentation = "https://github.com/imshahinul/deterministic-scenario-engine/tree/main/docs"
+Source = "https://github.com/imshahinul/deterministic-scenario-engine"
+Issues = "https://github.com/imshahinul/deterministic-scenario-engine/issues"
+"Release Notes" = "https://github.com/imshahinul/deterministic-scenario-engine/releases"
+
 [project.scripts]
 scenario = "scenario_engine.cli:main"
 
 [project.optional-dependencies]
-pytest = ["pytest>=9.1,<10"]
+pytest = ["pytest>=9.1,<10", "build>=1,<2"]
 sqlalchemy = ["SQLAlchemy>=2.0,<3"]
 hypothesis = ["hypothesis>=6,<7"]
 schemathesis = ["hypothesis>=6,<7", "schemathesis>=4,<5"]

{deterministic_scenario_engine-2.1.0 → deterministic_scenario_engine-2.1.2/src/deterministic_scenario_engine.egg-info}/PKG-INFO

@@ -1,8 +1,13 @@
 Metadata-Version: 2.4
 Name: deterministic-scenario-engine
-Version: 2.1.0
+Version: 2.1.2
 Summary: Reproducible, state-consistent business scenarios with deterministic ground truth
 License-Expression: Apache-2.0
+Project-URL: Homepage, https://github.com/imshahinul/deterministic-scenario-engine
+Project-URL: Documentation, https://github.com/imshahinul/deterministic-scenario-engine/tree/main/docs
+Project-URL: Source, https://github.com/imshahinul/deterministic-scenario-engine
+Project-URL: Issues, https://github.com/imshahinul/deterministic-scenario-engine/issues
+Project-URL: Release Notes, https://github.com/imshahinul/deterministic-scenario-engine/releases
 Keywords: deterministic,scenario,testing,fixtures,replay
 Classifier: Development Status :: 5 - Production/Stable
 Classifier: Intended Audience :: Developers
@@ -20,6 +25,7 @@ License-File: LICENSE
 Requires-Dist: PyYAML==6.0.3
 Provides-Extra: pytest
 Requires-Dist: pytest<10,>=9.1; extra == "pytest"
+Requires-Dist: build<2,>=1; extra == "pytest"
 Provides-Extra: sqlalchemy
 Requires-Dist: SQLAlchemy<3,>=2.0; extra == "sqlalchemy"
 Provides-Extra: hypothesis
@@ -35,11 +41,10 @@ Dynamic: license-file
 
 Deterministic Scenario Engine (DSE) creates reproducible, state-consistent
 business histories and deterministic scenario suites with ground truth for
-testing. The published distribution is `deterministic-scenario-engine` 2.0.0.
-Phase 3 evidence-interchange capabilities are implemented on `main` and the
-current source release candidate reports distribution version 2.1.0, while 2.1.0
-is not published. Its deterministic compatibility version remains
-`ENGINE_VERSION == "1.0.0"`, and its DSL version remains integer 1.
+testing. The source-tree distribution version is 2.1.2. Distribution release
+identity and deterministic compatibility identity are separate:
+`ENGINE_VERSION` remains 1.0.0 and DSL version remains 1. For authoritative
+public-release availability and history, see PyPI and GitHub Releases.
 
 ## Why it exists
 
@@ -74,11 +79,11 @@ make expected behavior explicit.
   explicit adapters, closed lossless migrations, and fixture-directory export
 
 Core execution does not require a database, network service, plugin, or property
-testing framework. See [security assumptions and non-goals](docs/security-and-non-goals.md).
+testing framework. See [security assumptions and non-goals](https://github.com/imshahinul/deterministic-scenario-engine/blob/main/docs/security-and-non-goals.md).
 Neither Phase 2 nor Phase 3 adds hidden discovery, network, randomness,
 wall-clock, or ambient environment semantics. The historical Phase 2 contract
-is frozen in the [Phase 2 public contract](docs/phase2-public-contract.md); the
-additive evidence surface is frozen in the [Phase 3 public contract](docs/phase3-public-contract.md).
+is frozen in the [Phase 2 public contract](https://github.com/imshahinul/deterministic-scenario-engine/blob/main/docs/phase2-public-contract.md); the
+additive evidence surface is frozen in the [Phase 3 public contract](https://github.com/imshahinul/deterministic-scenario-engine/blob/main/docs/phase3-public-contract.md).
 
 ## Installation
 
@@ -98,13 +103,13 @@ Install only the named optional integrations you need:
 /tmp/scenario-engine-docs-venv/bin/python -m pip install '.[schemathesis]'
 ```
 
-The published distribution is `deterministic-scenario-engine` 2.0.0. Install the package
-with `pip install deterministic-scenario-engine`, or select an optional integration
-with a command such as `pip install 'deterministic-scenario-engine[pytest]'`.
+Install the package with `pip install deterministic-scenario-engine`, or select
+an optional integration with a command such as
+`pip install 'deterministic-scenario-engine[pytest]'`.
 
 ## Minimal quickstart
 
-The public [cart scenario](examples/cart.yaml) is an executable DSL 1 document.
+The public [cart scenario](https://github.com/imshahinul/deterministic-scenario-engine/blob/main/examples/cart.yaml) is an executable DSL 1 document.
 Run it from the repository root:
 
 ```python
@@ -139,32 +144,31 @@ normalized result contains the same data under its `state` field.
 Generation derives from semantic `ExecutionAddress` values, not consumption of
 a mutable global random stream. Exact replay requires the same canonical
 scenario, explicit inputs, algorithms/plugins, and recorded execution context.
-Unsupported cross-version replay fails explicitly. See the [determinism model](docs/determinism.md),
-[reproducibility guide](docs/reproducibility.md), and normative
-[compatibility contract](docs/compatibility.md).
+Unsupported cross-version replay fails explicitly. See the [determinism model](https://github.com/imshahinul/deterministic-scenario-engine/blob/main/docs/determinism.md),
+[reproducibility guide](https://github.com/imshahinul/deterministic-scenario-engine/blob/main/docs/reproducibility.md), and normative
+[compatibility contract](https://github.com/imshahinul/deterministic-scenario-engine/blob/main/docs/compatibility.md).
 
 ## Documentation
 
-- [Quickstart](docs/quickstart.md)
-- [DSL 1 reference](docs/dsl-reference.md)
-- [Determinism model](docs/determinism.md)
-- [Reproducibility and replay](docs/reproducibility.md)
-- [Testing, faults, and oracle](docs/testing-oracle.md)
-- [Plugins](docs/plugins.md)
-- [SQLAlchemy adapter](docs/sqlalchemy.md)
-- [Hypothesis integration](docs/hypothesis.md)
-- [Schemathesis integration](docs/schemathesis.md)
-- [Public Python API](docs/api.md)
-- [Security assumptions and non-goals](docs/security-and-non-goals.md)
-- [Compatibility contract](docs/compatibility.md)
-- [Phase 2 public contract, CLI, and hard bounds](docs/phase2-public-contract.md)
-- [Phase 3 public contract and evidence interchange](docs/phase3-public-contract.md)
+- [Quickstart](https://github.com/imshahinul/deterministic-scenario-engine/blob/main/docs/quickstart.md)
+- [DSL 1 reference](https://github.com/imshahinul/deterministic-scenario-engine/blob/main/docs/dsl-reference.md)
+- [Determinism model](https://github.com/imshahinul/deterministic-scenario-engine/blob/main/docs/determinism.md)
+- [Reproducibility and replay](https://github.com/imshahinul/deterministic-scenario-engine/blob/main/docs/reproducibility.md)
+- [Testing, faults, and oracle](https://github.com/imshahinul/deterministic-scenario-engine/blob/main/docs/testing-oracle.md)
+- [Plugins](https://github.com/imshahinul/deterministic-scenario-engine/blob/main/docs/plugins.md)
+- [SQLAlchemy adapter](https://github.com/imshahinul/deterministic-scenario-engine/blob/main/docs/sqlalchemy.md)
+- [Hypothesis integration](https://github.com/imshahinul/deterministic-scenario-engine/blob/main/docs/hypothesis.md)
+- [Schemathesis integration](https://github.com/imshahinul/deterministic-scenario-engine/blob/main/docs/schemathesis.md)
+- [Public Python API](https://github.com/imshahinul/deterministic-scenario-engine/blob/main/docs/api.md)
+- [Security assumptions and non-goals](https://github.com/imshahinul/deterministic-scenario-engine/blob/main/docs/security-and-non-goals.md)
+- [Compatibility contract](https://github.com/imshahinul/deterministic-scenario-engine/blob/main/docs/compatibility.md)
+- [Phase 2 public contract, CLI, and hard bounds](https://github.com/imshahinul/deterministic-scenario-engine/blob/main/docs/phase2-public-contract.md)
+- [Phase 3 public contract and evidence interchange](https://github.com/imshahinul/deterministic-scenario-engine/blob/main/docs/phase3-public-contract.md)
 
 ## Status
 
 Distribution release identity and deterministic engine compatibility are
-separate contracts. Version 2.0.0 has been published to PyPI and as a GitHub
-Release. This source tree reports the unpublished 2.1.0 release candidate;
-generated core manifests retain `ENGINE_VERSION` 1.0.0 and DSL 1. No 2.1.0 tag,
-GitHub Release, or package-index publication exists. The project is licensed
-under Apache-2.0.
+separate contracts. This source tree reports distribution version 2.1.2;
+generated core manifests retain `ENGINE_VERSION` 1.0.0 and DSL 1. PyPI and
+GitHub Releases are the authoritative sources for public-release availability
+and history. The project is licensed under Apache-2.0.

{deterministic_scenario_engine-2.1.0 → deterministic_scenario_engine-2.1.2}/src/deterministic_scenario_engine.egg-info/SOURCES.txt

@@ -12,7 +12,9 @@ docs/phase2-public-contract.md
 docs/phase3-architecture.md
 docs/phase3-public-contract.md
 docs/plugins.md
+docs/product-evidence-gate.md
 docs/quickstart.md
+docs/release-process.md
 docs/reproducibility.md
 docs/schemathesis.md
 docs/security-and-non-goals.md
@@ -182,4 +184,6 @@ tests/test_phase_3_4_evidence_adapter_contract.py
 tests/test_phase_3_5_compatibility_migration_planner.py
 tests/test_phase_3_6_lossless_migrations_fixture_export.py
 tests/test_phase_3_7_cli_interchange_surface.py
-tests/test_phase_3_8_ecommerce_evidence_workflow.py
+tests/test_phase_3_8_ecommerce_evidence_workflow.py
+tests/test_readme_pypi_portability.py
+tests/test_test_portability.py

{deterministic_scenario_engine-2.1.0 → deterministic_scenario_engine-2.1.2}/src/deterministic_scenario_engine.egg-info/requires.txt

@@ -5,6 +5,7 @@ hypothesis<7,>=6
 
 [pytest]
 pytest<10,>=9.1
+build<2,>=1
 
 [schemathesis]
 hypothesis<7,>=6

{deterministic_scenario_engine-2.1.0 → deterministic_scenario_engine-2.1.2}/src/scenario_engine/_version.py

@@ -1,4 +1,4 @@
 """Authoritative distribution and deterministic compatibility versions."""
 
-VERSION = "2.1.0"
+VERSION = "2.1.2"
 ENGINE_VERSION = "1.0.0"

{deterministic_scenario_engine-2.1.0 → deterministic_scenario_engine-2.1.2}/tests/test_phase_0_2b_json_pytest_integration.py

@@ -17,9 +17,6 @@ from scenario_engine.result import ScenarioResult
 
 ROOT = Path(__file__).parents[1]
 SRC = ROOT / "src"
-AUDIT_PYTHON = Path(
-    "/Users/smshahinulislam/Developer/scenario-engine-audit/runtime-venv/bin/python"
-)
 SCENARIO = """
 dsl_version: 1
 scenario: phase02b
@@ -47,11 +44,12 @@ def run_result(seed: str = "seed", run_index: int = 0) -> ScenarioResult:
     )
 
 
-def subprocess_environment() -> dict[str, str]:
-    environment = os.environ.copy()
-    existing = environment.get("PYTHONPATH")
-    environment["PYTHONPATH"] = str(SRC) + (os.pathsep + existing if existing else "")
-    return environment
+def pytest_command(test_file: Path) -> list[str]:
+    command = [sys.executable, "-m", "pytest", "-q"]
+    if os.environ.get("PYTEST_DISABLE_PLUGIN_AUTOLOAD"):
+        command.extend(("-p", "scenario_engine"))
+    command.append(str(test_file))
+    return command
 
 
 class Phase02BJsonPytestIntegrationTests(unittest.TestCase):
@@ -161,7 +159,7 @@ class Phase02BJsonPytestIntegrationTests(unittest.TestCase):
         document = tomllib.loads((ROOT / "pyproject.toml").read_text(encoding="utf-8"))
         self.assertEqual(document["project"]["dependencies"], ["PyYAML==6.0.3"])
         self.assertEqual(document["project"]["optional-dependencies"]["pytest"],
-                         ["pytest>=9.1,<10"])
+                         ["pytest>=9.1,<10", "build>=1,<2"])
         self.assertEqual(document["project"]["entry-points"]["pytest11"]["scenario_engine"],
                          "scenario_engine.pytest_plugin")
 
@@ -169,7 +167,6 @@ class Phase02BJsonPytestIntegrationTests(unittest.TestCase):
         with tempfile.TemporaryDirectory() as directory:
             test_file = Path(directory) / "test_fixture.py"
             test_file.write_text(textwrap.dedent(f'''\
-                pytest_plugins = ["scenario_engine.pytest_plugin"]
                 from scenario_engine.result import ScenarioResult
                 SCENARIO = {SCENARIO!r}
                 def test_fixture(scenario_engine):
@@ -180,8 +177,7 @@ class Phase02BJsonPytestIntegrationTests(unittest.TestCase):
                     assert first.manifest.run_index == 4
             '''), encoding="utf-8")
             completed = subprocess.run(
-                [str(AUDIT_PYTHON), "-m", "pytest", "-q", str(test_file)],
-                cwd=directory, env=subprocess_environment(), capture_output=True, text=True,
+                pytest_command(test_file), cwd=directory, capture_output=True, text=True,
             )
         self.assertEqual(completed.returncode, 0, completed.stdout + completed.stderr)
 
@@ -191,7 +187,6 @@ class Phase02BJsonPytestIntegrationTests(unittest.TestCase):
             source.write_text(SCENARIO, encoding="utf-8")
             test_file = Path(directory) / "test_file_fixture.py"
             test_file.write_text(textwrap.dedent(f'''\
-                pytest_plugins = ["scenario_engine.pytest_plugin"]
                 from pathlib import Path
                 from scenario_engine.result import ScenarioResult
                 def test_file_fixture(scenario_engine):
@@ -201,8 +196,7 @@ class Phase02BJsonPytestIntegrationTests(unittest.TestCase):
                     assert result.final_state["money"].as_tuple().exponent == -2
             '''), encoding="utf-8")
             completed = subprocess.run(
-                [str(AUDIT_PYTHON), "-m", "pytest", "-q", str(test_file)],
-                cwd=directory, env=subprocess_environment(), capture_output=True, text=True,
+                pytest_command(test_file), cwd=directory, capture_output=True, text=True,
             )
         self.assertEqual(completed.returncode, 0, completed.stdout + completed.stderr)