solverforge 0.6.2__tar.gz → 0.6.3__tar.gz

{solverforge-0.6.2 → solverforge-0.6.3}/Cargo.lock

@@ -560,9 +560,9 @@ checksum = "8ed6a63f02c8539c91a8685a86f4099661ba3da017932f6ebbea6de3f0fa7c90"
 
 [[package]]
 name = "solverforge-bridge"
-version = "0.19.0"
+version = "0.19.1"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "f47d5b1bc4e9ea86acf24e3e71f971161bc5c1eba09d4b7105a25542045ed59a"
+checksum = "6bc1bbd14aa7b23a845359b408747b6b783ed31529f1b2cfa12512d425e305f5"
 dependencies = [
  "solverforge-config",
  "solverforge-core",
@@ -572,9 +572,9 @@ dependencies = [
 
 [[package]]
 name = "solverforge-config"
-version = "0.19.0"
+version = "0.19.1"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "a94f2ff36fc3513dd17473fea8402a7908470b0d18132862e938b402d4cc3dce"
+checksum = "3251fc0471e05f2c05f9148f648618aa8d021fa4dff9af626ac7f05843f114f8"
 dependencies = [
  "serde",
  "serde_yaml",
@@ -585,9 +585,9 @@ dependencies = [
 
 [[package]]
 name = "solverforge-console"
-version = "0.19.0"
+version = "0.19.1"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "5ecece452a5533bda0f129188cf5284b06b5f0f4b32b6334521e5dbcefa2a318"
+checksum = "42794d46f6685a00e9387a67b0037d49321f7e34796cd5a97b8fd99a72e20377"
 dependencies = [
  "num-format",
  "owo-colors",
@@ -597,18 +597,18 @@ dependencies = [
 
 [[package]]
 name = "solverforge-core"
-version = "0.19.0"
+version = "0.19.1"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "75396bba5cd24cd16c77477e7ef93dac5643026998904aa862c1bd3f70a5a04f"
+checksum = "32858c2be2505640f60a0bcee902a29e7b9dd136aec49928601ca8764920cb79"
 dependencies = [
  "thiserror",
 ]
 
 [[package]]
 name = "solverforge-scoring"
-version = "0.19.0"
+version = "0.19.1"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "85df4f001bed630512b2205334113c1766d80ac8b7f4a5da1c2c63f680db1494"
+checksum = "50bd20153f578099fe768873f8d5c07f8e4a56e79bb3da4611776ca5f65941e4"
 dependencies = [
  "solverforge-core",
  "thiserror",
@@ -616,9 +616,9 @@ dependencies = [
 
 [[package]]
 name = "solverforge-solver"
-version = "0.19.0"
+version = "0.19.1"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "606d50e70307c448f09370028d7ec02172066899896fd8142dd59886b0cb555e"
+checksum = "ae2870ba2c94f03150870d84224fc009936071f9e9313161979473735e059988"
 dependencies = [
  "rand",
  "rand_chacha",
@@ -644,7 +644,7 @@ dependencies = [
 
 [[package]]
 name = "solverforge_py"
-version = "0.6.2"
+version = "0.6.3"
 dependencies = [
  "indexmap",
  "once_cell",

{solverforge-0.6.2 → solverforge-0.6.3}/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "solverforge_py"
-version = "0.6.2"
+version = "0.6.3"
 edition = "2021"
 license = "Apache-2.0"
 rust-version = "1.95"
@@ -26,7 +26,7 @@ name = "solverforge_py"
 crate-type = ["cdylib", "rlib"]
 
 [package.metadata.solverforge]
-version = "0.19.0"
+version = "0.19.1"
 
 [dependencies]
 indexmap = "2.12.1"
@@ -42,12 +42,12 @@ toml = "0.9.8"
 tracing = "0.1.44"
 tracing-subscriber = { version = "0.3.23", features = ["env-filter"] }
 
-solverforge-config = { version = "=0.19.0" }
-solverforge-bridge = { version = "=0.19.0" }
-solverforge-console = { version = "=0.19.0", features = ["verbose-logging"] }
-solverforge-core = { version = "=0.19.0" }
-solverforge-scoring = { version = "=0.19.0" }
-solverforge-solver = { version = "=0.19.0" }
+solverforge-config = { version = "=0.19.1" }
+solverforge-bridge = { version = "=0.19.1" }
+solverforge-console = { version = "=0.19.1", features = ["verbose-logging"] }
+solverforge-core = { version = "=0.19.1" }
+solverforge-scoring = { version = "=0.19.1" }
+solverforge-solver = { version = "=0.19.1" }
 solverforge-ui = { version = "=0.7.0", default-features = false }
 
 [dev-dependencies]

{solverforge-0.6.2 → solverforge-0.6.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: solverforge
-Version: 0.6.2
+Version: 0.6.3
 Classifier: Development Status :: 3 - Alpha
 Classifier: Intended Audience :: Developers
 Classifier: Intended Audience :: Science/Research
@@ -39,10 +39,10 @@ The native extension owns the working solution state in Rust so SolverForge can
 clone, mutate, and snapshot solutions safely. Python callbacks are the single
 constraint authoring surface.
 
-The package targets CPython 3.14 and Rust 1.95.0. This checkout consumes the
-published SolverForge Rust crates `0.19.0` and pins `solverforge-ui` to `0.7.0`
-through exact crates.io versions in `Cargo.toml` and registry checksums in
-`Cargo.lock`; it has no local path or Git dependency override. The `solverforge`
+The package targets CPython 3.14 and Rust 1.95.0. This checkout targets the
+SolverForge Rust crates `0.19.1` and pins `solverforge-ui` to `0.7.0` through
+exact crates.io versions in `Cargo.toml` and registry checksums in `Cargo.lock`.
+There is no local path or Git dependency override. The `solverforge`
 `0.6.x` line is the current dynamic binding architecture and intentionally
 supersedes the older incompatible `0.2.x` and `0.3.0` artifacts in the same PyPI
 namespace. Those older artifacts exposed `SolverFactory`, `PlanningVariable`,
@@ -50,12 +50,12 @@ Java service requirements, and other APIs that are not part of this package.
 
 ## Installation
 
-The package version prepared by this checkout is `solverforge` `0.6.2`, built
-on the exact published and locked SolverForge Rust `0.19.0` registry dependency
-base. Install the matching package after publication with:
+The package version prepared by this checkout is `solverforge` `0.6.3`, targeting
+the published and locked SolverForge Rust `0.19.1` registry dependency base.
+Install the matching package after its Python release with:
 
 ```sh
-python3.14 -m pip install "solverforge==0.6.2"
+python3.14 -m pip install "solverforge==0.6.3"
 ```
 
 The installable wheel contains the core `solverforge` package, native extension,
@@ -80,7 +80,7 @@ installed package without `PYTHONPATH` or an editable checkout:
 ```sh
 python3.14 -m venv .venv-examples
 . .venv-examples/bin/activate
-python -m pip install "solverforge[examples]==0.6.2"
+python -m pip install "solverforge[examples]==0.6.3"
 python examples/nqueens.py
 python -m examples.solverforge_hospital
 python -m examples.solverforge_deliveries
@@ -187,9 +187,13 @@ Run `make help` for focused targets such as `make test-hospital`,
   `list_cheapest_insertion`, `list_regret_insertion`, `list_clarke_wright`, and
   `list_k_opt`, with the final two requiring their respective savings and route
   metadata bundles. These are core graph nodes over the immutable runtime
-  model. An explicit `group_name` phase obeys its configured obligation and
-  termination; required-only completion belongs solely to upstream omitted
-  defaults. Default local search is assembled only when the top-level
+  model. All configured limits remain binding during construction. A solve
+  publishes a best or completed solution only after every list element,
+  required assignment row, and non-optional scalar variable is assigned; if a
+  limit is reached first, a direct solve raises and a retained job enters
+  `FAILED` without exposing a partial snapshot. Omitted construction still
+  resolves required and optional stages in core, but required work never
+  bypasses a configured limit. Default local search is assembled only when the top-level
   termination has an effective finite limit, so an empty or invalid termination
   cannot accidentally create an unbounded solve. There is no wrapper assignment
   placer, required stream, phase tree, TLS slot state, synthetic metric, or
@@ -197,6 +201,8 @@ Run `make help` for focused targets such as `make test-hospital`,
 - `SolverManager` is backed by upstream retained jobs, statuses, events, and
   snapshots. `SolverManager.solve(...)` returns `JobHandle(job_id=...)`; the
   manager supports pause, resume, cancel, delete, and exact snapshot reads.
+  A pause before mandatory construction completes remains resumable internal
+  state and does not expose an incomplete solution snapshot.
   Retained event payloads read current score from the attached solution snapshot
   when present. Long-running phases publish progress at the shared upstream
   cadence, and telemetry includes the current phase type, index, counters, and

{solverforge-0.6.2 → solverforge-0.6.3}/README.md

@@ -8,10 +8,10 @@ The native extension owns the working solution state in Rust so SolverForge can
 clone, mutate, and snapshot solutions safely. Python callbacks are the single
 constraint authoring surface.
 
-The package targets CPython 3.14 and Rust 1.95.0. This checkout consumes the
-published SolverForge Rust crates `0.19.0` and pins `solverforge-ui` to `0.7.0`
-through exact crates.io versions in `Cargo.toml` and registry checksums in
-`Cargo.lock`; it has no local path or Git dependency override. The `solverforge`
+The package targets CPython 3.14 and Rust 1.95.0. This checkout targets the
+SolverForge Rust crates `0.19.1` and pins `solverforge-ui` to `0.7.0` through
+exact crates.io versions in `Cargo.toml` and registry checksums in `Cargo.lock`.
+There is no local path or Git dependency override. The `solverforge`
 `0.6.x` line is the current dynamic binding architecture and intentionally
 supersedes the older incompatible `0.2.x` and `0.3.0` artifacts in the same PyPI
 namespace. Those older artifacts exposed `SolverFactory`, `PlanningVariable`,
@@ -19,12 +19,12 @@ Java service requirements, and other APIs that are not part of this package.
 
 ## Installation
 
-The package version prepared by this checkout is `solverforge` `0.6.2`, built
-on the exact published and locked SolverForge Rust `0.19.0` registry dependency
-base. Install the matching package after publication with:
+The package version prepared by this checkout is `solverforge` `0.6.3`, targeting
+the published and locked SolverForge Rust `0.19.1` registry dependency base.
+Install the matching package after its Python release with:
 
 ```sh
-python3.14 -m pip install "solverforge==0.6.2"
+python3.14 -m pip install "solverforge==0.6.3"
 ```
 
 The installable wheel contains the core `solverforge` package, native extension,
@@ -49,7 +49,7 @@ installed package without `PYTHONPATH` or an editable checkout:
 ```sh
 python3.14 -m venv .venv-examples
 . .venv-examples/bin/activate
-python -m pip install "solverforge[examples]==0.6.2"
+python -m pip install "solverforge[examples]==0.6.3"
 python examples/nqueens.py
 python -m examples.solverforge_hospital
 python -m examples.solverforge_deliveries
@@ -156,9 +156,13 @@ Run `make help` for focused targets such as `make test-hospital`,
   `list_cheapest_insertion`, `list_regret_insertion`, `list_clarke_wright`, and
   `list_k_opt`, with the final two requiring their respective savings and route
   metadata bundles. These are core graph nodes over the immutable runtime
-  model. An explicit `group_name` phase obeys its configured obligation and
-  termination; required-only completion belongs solely to upstream omitted
-  defaults. Default local search is assembled only when the top-level
+  model. All configured limits remain binding during construction. A solve
+  publishes a best or completed solution only after every list element,
+  required assignment row, and non-optional scalar variable is assigned; if a
+  limit is reached first, a direct solve raises and a retained job enters
+  `FAILED` without exposing a partial snapshot. Omitted construction still
+  resolves required and optional stages in core, but required work never
+  bypasses a configured limit. Default local search is assembled only when the top-level
   termination has an effective finite limit, so an empty or invalid termination
   cannot accidentally create an unbounded solve. There is no wrapper assignment
   placer, required stream, phase tree, TLS slot state, synthetic metric, or
@@ -166,6 +170,8 @@ Run `make help` for focused targets such as `make test-hospital`,
 - `SolverManager` is backed by upstream retained jobs, statuses, events, and
   snapshots. `SolverManager.solve(...)` returns `JobHandle(job_id=...)`; the
   manager supports pause, resume, cancel, delete, and exact snapshot reads.
+  A pause before mandatory construction completes remains resumable internal
+  state and does not expose an incomplete solution snapshot.
   Retained event payloads read current score from the attached solution snapshot
   when present. Long-running phases publish progress at the shared upstream
   cadence, and telemetry includes the current phase type, index, counters, and

{solverforge-0.6.2 → solverforge-0.6.3}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "maturin"
 
 [project]
 name = "solverforge"
-version = "0.6.2"
+version = "0.6.3"
 description = "Dynamic Python bindings for the SolverForge constraint solver."
 readme = "README.md"
 license = { text = "Apache-2.0" }

{solverforge-0.6.2 → solverforge-0.6.3}/python/solverforge/__init__.py

@@ -40,7 +40,7 @@ from .manager import JobHandle, SolverManager
 from .score import HardMediumSoftScore, HardSoftDecimalScore, HardSoftScore, SoftScore
 from .solver import Solver
 
-__version__ = "0.6.2"
+__version__ = "0.6.3"
 
 __all__ = [
     "CallbackError",