assay-engine 0.5.0.dev2__tar.gz → 0.5.0.dev3__tar.gz

{assay_engine-0.5.0.dev2 → assay_engine-0.5.0.dev3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: assay-engine
-Version: 0.5.0.dev2
+Version: 0.5.0.dev3
 Summary: Explainable composition of measurements recorded on heterogeneous scales.
 Project-URL: Homepage, https://github.com/hseshadr/assay
 Project-URL: Repository, https://github.com/hseshadr/assay
@@ -36,12 +36,13 @@ score and the arithmetic behind every row.
 
 ## Installation status
 
-> **Status:** `assay-engine` 0.5.0.dev2 and `@edgeproc/assay` 0.5.0-dev.2 are local split candidates. Neither package is published.
+> **Status:** `assay-engine` 0.5.0.dev3 and `@edgeproc/assay` 0.5.0-dev.3 are the authorized prerelease pair. Check both registries before installing.
 
-The future authorized registry commands are `pip install assay-engine` and
-`npm install @edgeproc/assay`. They are shown for identity only; do not run them until
-a release is explicitly authorized. The runnable candidate path builds from this
-checkout.
+The base registry commands are `pip install assay-engine` and
+`npm install @edgeproc/assay`. For this prerelease, pin them as
+`pip install assay-engine==0.5.0.dev3` and `npm install @edgeproc/assay@0.5.0-dev.3`,
+and use them only after both exact versions appear in their registries. The checkout
+path below remains runnable before, during, and after publication.
 
 ## Run the Northstar example
 
@@ -224,7 +225,7 @@ print(result.score, result.selected_component_id)
 ```
 
 The command line accepts typed JSON for `assay compose`, `assay measure`, and
-`assay explain`. Build and installation commands for the unpublished checkout are in
+`assay explain`. Build and installation commands for the source checkout are in
 the [quickstart](https://github.com/hseshadr/assay/blob/main/QUICKSTART.md).
 
 ## Optional calculators

{assay_engine-0.5.0.dev2 → assay_engine-0.5.0.dev3}/README.md

@@ -8,12 +8,13 @@ score and the arithmetic behind every row.
 
 ## Installation status
 
-> **Status:** `assay-engine` 0.5.0.dev2 and `@edgeproc/assay` 0.5.0-dev.2 are local split candidates. Neither package is published.
+> **Status:** `assay-engine` 0.5.0.dev3 and `@edgeproc/assay` 0.5.0-dev.3 are the authorized prerelease pair. Check both registries before installing.
 
-The future authorized registry commands are `pip install assay-engine` and
-`npm install @edgeproc/assay`. They are shown for identity only; do not run them until
-a release is explicitly authorized. The runnable candidate path builds from this
-checkout.
+The base registry commands are `pip install assay-engine` and
+`npm install @edgeproc/assay`. For this prerelease, pin them as
+`pip install assay-engine==0.5.0.dev3` and `npm install @edgeproc/assay@0.5.0-dev.3`,
+and use them only after both exact versions appear in their registries. The checkout
+path below remains runnable before, during, and after publication.
 
 ## Run the Northstar example
 
@@ -196,7 +197,7 @@ print(result.score, result.selected_component_id)
 ```
 
 The command line accepts typed JSON for `assay compose`, `assay measure`, and
-`assay explain`. Build and installation commands for the unpublished checkout are in
+`assay explain`. Build and installation commands for the source checkout are in
 the [quickstart](https://github.com/hseshadr/assay/blob/main/QUICKSTART.md).
 
 ## Optional calculators

{assay_engine-0.5.0.dev2 → assay_engine-0.5.0.dev3}/pyproject.toml

@@ -40,6 +40,7 @@ cli = [
 
 [dependency-groups]
 dev = [
+    "dagger-io==0.21.8",
     "hatchling==1.27.0",
     "pytest>=9.1.1",
     "pytest-cov>=6.0",
@@ -92,6 +93,7 @@ ignore = ["S101", "PLR0913"]
 "tests/test_cli_privacy.py" = ["S603", "S607"]
 "tests/test_measurement.py" = ["S603", "S607"]
 "tests/test_release_contract.py" = ["S603", "S607"]
+"tests/test_dagger_contract.py" = ["S603"]
 "tests/test_workflow_contract.py" = ["S603", "S607"]
 # Domain errors use semantic names such as InvalidRankingRequest. They are the stable,
 # coded interface consumed across Assay's calculators, CLI, and tests.
@@ -150,10 +152,10 @@ fail_under = 90.0
 [tool.poe.tasks]
 # scripts/ is held to the same bar as src/ and tests/: the mutation harness is the thing
 # that proves the guards can fail, so it is not exempt from the gate that guards them.
-lint = "ruff check src/ tests/ scripts/ benchmarks/"
-fmt-check = "ruff format --check src/ tests/ scripts/ benchmarks/"
-fmt = "ruff format src/ tests/ scripts/ benchmarks/"
-complexity = "xenon --max-absolute A --max-modules A --max-average A src/assay scripts benchmarks"
+lint = "ruff check .dagger/src src/ tests/ scripts/ benchmarks/"
+fmt-check = "ruff format --check .dagger/src src/ tests/ scripts/ benchmarks/"
+fmt = "ruff format .dagger/src src/ tests/ scripts/ benchmarks/"
+complexity = "xenon --max-absolute A --max-modules A --max-average A .dagger/src src/assay scripts benchmarks"
 test = "pytest --cov=assay --cov-branch --cov-report=term-missing --cov-fail-under=90"
 gate = ["lint", "fmt-check", "typecheck", "complexity", "test"]
 
@@ -170,4 +172,4 @@ artifacts = "bash scripts/build_release_artifacts.sh dist/release"
 release-candidate = "bash scripts/verify_release_candidate.sh"
 
 [tool.poe.tasks.typecheck]
-cmd = "mypy --strict src/assay scripts benchmarks"
+cmd = "mypy --strict .dagger/src src/assay scripts benchmarks"

{assay_engine-0.5.0.dev2 → assay_engine-0.5.0.dev3}/src/assay/_version.py

@@ -2,4 +2,4 @@
 
 from __future__ import annotations
 
-__version__ = "0.5.0.dev2"
+__version__ = "0.5.0.dev3"