rustedscithe 0.1.1__tar.gz → 0.1.2__tar.gz

{rustedscithe-0.1.1 → rustedscithe-0.1.2}/Cargo.lock

@@ -4,7 +4,7 @@ version = 4
 
 [[package]]
 name = "RustedSciThe"
-version = "0.4.23"
+version = "0.4.24"
 dependencies = [
  "ahash",
  "append-only-vec",

{rustedscithe-0.1.1 → rustedscithe-0.1.2}/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "RustedSciThe"
-version = "0.4.23"
+version = "0.4.24"
 edition = "2024"
 description = "Rust framework for symbolic and numerical computing:BVP ( Newton-Raphson frozen/damped/with collocations ), IVP( BDF, Radau, Backward Euler, LSODE, LSODA, RK45, DoPri), nonlinear equations ( Levenberg, Gavin) and more"
 author = "Gleb Zaslavsky"
@@ -8,10 +8,10 @@ license = "MIT"
 keywords = [ "mathematics", "science", "ODE", "symbolic"]
 repository = "https://github.com/Gleb-Zaslavsky/RustedSciThe"
 include = [
-    "Cargo.toml",
-    "Cargo.lock",
-    "./LICENSE.txt",
-    "README.md",
+    "/Cargo.toml",
+    "/Cargo.lock",
+    "/LICENSE.txt",
+    "/README.md",
     "src/**/*.rs",
     "src/**/*.cu",
     # Public guides are package documentation; internal TODO/story/test files
@@ -28,6 +28,62 @@ include = [
     "examples/**/*.rs",
     "examples/task_docs/reference/**/*.txt",
     "benches/**/*.rs",
+    # Repository-only material. Cargo include patterns support gitignore-style
+    # negation, so keep these exclusions explicit instead of relying on a
+    # broad source allowlist to remain correct forever.
+    "!/.kilo",
+    "!/.kilo/**/*",
+    "!/Cargo.toml.orig",
+    "!src/numerical/optimization/gavin_reference/**",
+    "!src/numerical/ivp_scipy_reference/**",
+    "!src/numerical/BVP_sci/scipy_reference/**",
+    "!src/somelinalg/sparse_lu_reference/**",
+    "!src/**/*[tT][eE][sS][tT]*.md",
+    "!src/**/*[sS][tT][oO][rR][yY]*.md",
+    "!src/**/tests/**/*.md",
+    "!scripts/**/*[tT][eE][sS][tT]*.md",
+    "!scripts/**/*[sS][tT][oO][rR][yY]*.md",
+    "!benches/**/*[tT][eE][sS][tT]*.md",
+    "!benches/**/*[sS][tT][oO][rR][yY]*.md",
+    "!examples/**/*[tT][eE][sS][tT]*.md",
+    "!examples/**/*[sS][tT][oO][rR][yY]*.md",
+    "!examples/**/tests/**/*.md",
+    "!src/**/*[tT][oO][dD][oO]*",
+    "!scripts/**/*[tT][oO][dD][oO]*",
+    "!benches/**/*[tT][oO][dD][oO]*",
+    "!examples/**/*[tT][oO][dD][oO]*",
+    "!src/command_interpreter/task_shell_cli_contract.rs",
+    "!src/**/aot/**/*",
+    "!src/**/generated/**/*",
+    "!scripts/**/aot/**/*",
+    "!scripts/**/generated/**/*",
+    "!benches/**/aot/**/*",
+    "!benches/**/generated/**/*",
+    "!examples/**/aot/**/*",
+    "!examples/**/generated/**/*",
+    # Non-Rust reference/build artifacts are not crate inputs. The maintained
+    # task-document fixtures below are re-added after this global filter.
+    "!**/*.txt",
+    "!**/*.log",
+    "!**/*.py",
+    "!**/*.f",
+    "!**/*.c",
+    "!**/*.cpp",
+    "!**/*.h",
+    "!**/*.dll",
+    "!**/*.so",
+    "!**/*.dylib",
+    "!**/*.a",
+    "!**/*.doc",
+    "!**/*.docx",
+    "!**/*.[pP][nN][gG]",
+    "!**/*.[jJ][pP][gG]",
+    "!**/*.[jJ][pP][eE][gG]",
+    "!**/*.[gG][iI][fF]",
+    "!**/*.[bB][mM][pP]",
+    "!**/*.[sS][vV][gG]",
+    # These are intentional public package inputs.
+    "examples/task_docs/reference/**/*.txt",
     # Required source for the optional, separately built native SuperLU bridge.
     "src/somelinalg/sparse_lu_reference/superlu_bridge.c",
 ]
@@ -479,7 +535,3 @@ path = "examples/rus/universal_fitting_guide.rs"
 [[example]]
 name = "rus_gavin_fitting_guide"
 path = "examples/rus/gavin_fitting_guide.rs"
-
-[[test]]
-name = "task_shell_cli_contract_tracked"
-path = "src/command_interpreter/task_shell_cli_contract.rs"

rustedscithe-0.1.2/PKG-INFO

@@ -0,0 +1,193 @@
+Metadata-Version: 2.4
+Name: rustedscithe
+Version: 0.1.2
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Science/Research
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Programming Language :: Rust
+Classifier: Topic :: Scientific/Engineering :: Mathematics
+Requires-Dist: numpy>=2.0
+Requires-Dist: mypy==2.4.0 ; extra == 'dev'
+Provides-Extra: dev
+License-File: LICENSE.txt
+Summary: Python bindings for RustedSciThe symbolic and numerical computing
+Keywords: numerical,ode,bvp,symbolic,rust
+Author: RustedSciThe contributors
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown; charset=UTF-8; variant=GFM
+Project-URL: Homepage, https://github.com/Gleb-Zaslavsky/RustedSciThe
+Project-URL: Repository, https://github.com/Gleb-Zaslavsky/RustedSciThe
+
+# RustedSciThe for Python
+
+RustedSciThe brings a symbolic engine and a family of stiff ODE, boundary-value,
+nonlinear-system and fitting solvers to Python. The Python package is a thin,
+idiomatic interface over a compiled Rust numerical core: expressions are parsed
+and differentiated in Rust, solver workspaces and algorithms stay in Rust, and
+Python receives ordinary typed objects and detached NumPy results.
+
+This project is for problems where a trustworthy derivative, a stiff or
+strongly nonlinear method, and visibility into numerical behavior matter more
+than hiding every solver choice behind one universal interface.
+
+## Why RustedSciThe
+
+- **Symbolic derivatives without a Python CAS dependency.** Build expressions,
+  simplify and substitute them, and derive exact Jacobians with RustedSciThe's
+  own symbolic engine. Prepared residual and Jacobian callbacks are reused
+  instead of being rebuilt during every numerical iteration.
+- **Native stiff IVP and BVP solvers.** Use Rust implementations inspired by
+  SciPy's Radau, variable-order BDF and collocation methods, alongside LSODE2,
+  Backward Euler and the damped BVP solver. The numerical solve runs in Rust,
+  not in a Python loop around a native linear algebra call.
+- **More than ODE integration.** Solve square nonlinear systems, rectangular
+  least-squares problems, observation-based fitting and separable models with
+  VarPro. These are first-class numerical workflows, not just helper routines
+  attached to an IVP API.
+- **Algorithms beyond the SciPy-like IVP/BVP set.** Native nonlinear methods,
+  a dedicated rectangular Levenberg-Marquardt solver, Gavin fitting and
+  variable projection cover workflows that are not merely wrappers around
+  SciPy's ODE interfaces.
+- **Choose the linear algebra layout when the solver supports it.** Dense,
+  Sparse and Banded routes are available across most solver families. Their
+  performance depends on the equation structure and problem size; there is no
+  universally fastest layout. BVP_sci additionally offers opt-in SuperLU.
+- **Lambdify and AOT execution.** Use prepared in-process callbacks for a fast
+  development cycle, or generated compiled callbacks where supported. The
+  symbolic frontend (`expr_legacy` or `atom_native`) is a separate choice from
+  the execution route (`lambdify` or `aot`).
+- **Prepared models and parameter series.** Reuse symbolic preparation across
+  continuation and restart workflows where the solver exposes that lifecycle.
+- **Diagnostics designed for numerical work.** Typed exceptions, route
+  provenance, optional counters and stage timings help explain what happened
+  without parsing console output or error messages.
+
+Performance is workload-dependent. A Rust implementation is not automatically
+the fastest choice for every equation, frontend, layout or lifecycle. Compare
+the same workload and inspect preparation, callback and full-solve timings
+before choosing a route.
+
+## Architecture
+
+```text
+Python model and NumPy inputs
+             |
+       PyO3 boundary
+             |
+Rust symbolic preparation -> exact derivatives -> Lambdify or AOT callbacks
+             |
+Rust solver -> Dense / Sparse / Banded linear algebra where supported
+             |
+typed result, telemetry and owned NumPy arrays
+```
+
+Python is the user-facing layer, not a second implementation of the algorithms.
+NumPy arrays returned by result objects own their data; they do not borrow a
+mutable solver workspace. The package does not require SymPy.
+
+## Quick Start
+
+This small stiff IVP uses Radau with its default symbolic and numerical
+configuration:
+
+```python
+from rustedscithe import Expr, RadauSolver
+
+y = Expr.variable("y")
+solver = RadauSolver([-y], ["y"], "t", 0.0, 1.0, 0.1)
+solution = solver.solve([1.0])
+print(f"y(1) = {solution.final_state[0]:.8f}")
+```
+
+Install the published package with `python -m pip install rustedscithe`. For a
+checkout-based editable build, install `maturin` and run:
+
+```powershell
+python -m maturin develop --manifest-path bindings/python/Cargo.toml
+```
+
+The extension uses the stable `abi3` Python 3.10+ ABI and NumPy 2.x. Import the
+public API from `rustedscithe`; `_native` is an implementation module.
+
+## Solver Families
+
+| Problem | Python entry points | Useful distinction |
+| --- | --- | --- |
+| Stiff initial-value problems | `RadauSolver`, `BdfSolver`, `BackwardEulerSolver`, `Lsode2Solver` | Radau and LSODE2 expose structured layouts where supported; standalone BDF and Backward Euler are Dense. LSODE2 separates its solver family from its Adams/BDF/Auto controller. |
+| Boundary-value problems | `BvpSciSolver`, `BvpDampSolver` | BVP_sci uses symbolic boundary residuals and collocation; BVP_Damp uses observed state/boundary data and damped Newton. Their boundary contracts intentionally differ. |
+| Nonlinear systems | `NonlinearSolver` | Prepared square systems with Newton, LM and trust-region method families. |
+| Least squares and fitting | `FittingSolver`, `GavinFittingSolver`, `VarProSolver` | Rectangular symbolic least squares, observation-based fitting and separable-model fitting have distinct contracts. |
+| Text task documents | `TaskDocument`, `task`, `run_task_batch` | Parse and execute reusable IVP/BVP documents through the native task infrastructure. |
+
+Use `capabilities("solver_name")` to inspect the Python-supported routes.
+Native features that are not exposed by this package are not implied by a
+shared option name; unsupported combinations raise a typed error instead of
+silently selecting a different backend.
+
+## Configuration Choices
+
+Several independent axes shape a solve, and a given solver supports only a
+documented subset of their combinations:
+
+| Axis | Examples | What it selects |
+| --- | --- | --- |
+| Symbolic frontend | `expr_legacy`, `atom_native` | Representation used for symbolic preparation and differentiation. |
+| Callback execution | `lambdify`, `aot` | In-process prepared closures or generated compiled artifacts. |
+| Matrix layout | `dense`, `sparse`, `banded` | Storage and linear-system route. |
+| Callback policy | `sequential`, `parallel`, `auto` | Scheduling where the native solver supports it. |
+| Lifecycle | fresh solve, `prepare`, continuation, restart | Whether prepared model or previous state is reused. |
+
+Check the relevant guide and `capabilities()` before combining options. A
+structured layout is useful only when the problem has exploitable structure;
+parallel callback evaluation and AOT compilation also have workload-dependent
+break-even points. For continuation, distinguish cold preparation from warm
+solve time.
+
+## Guides and Examples
+
+The overview guides explain shared Python conventions. Solver-specific guides
+preserve each native solver's option breadth, supported routes, limitations and
+recommended workflows.
+
+| Family | English | Русский |
+| --- | --- | --- |
+| Python API overview | [Python solvers](https://github.com/Gleb-Zaslavsky/RustedSciThe/blob/master/bindings/python/guides/PYTHON_SOLVERS_GUIDE_EN.md) | [Обзор Python API](https://github.com/Gleb-Zaslavsky/RustedSciThe/blob/master/bindings/python/guides/PYTHON_SOLVERS_GUIDE_RU.md) |
+| Radau | [Guide](https://github.com/Gleb-Zaslavsky/RustedSciThe/blob/master/bindings/python/guides/RADAU_GUIDE_EN.md) | [Руководство](https://github.com/Gleb-Zaslavsky/RustedSciThe/blob/master/bindings/python/guides/RADAU_GUIDE_RU.md) |
+| BDF | [Guide](https://github.com/Gleb-Zaslavsky/RustedSciThe/blob/master/bindings/python/guides/BDF_GUIDE_EN.md) | [Руководство](https://github.com/Gleb-Zaslavsky/RustedSciThe/blob/master/bindings/python/guides/BDF_GUIDE_RU.md) |
+| Backward Euler | [Guide](https://github.com/Gleb-Zaslavsky/RustedSciThe/blob/master/bindings/python/guides/BACKWARD_EULER_GUIDE_EN.md) | [Руководство](https://github.com/Gleb-Zaslavsky/RustedSciThe/blob/master/bindings/python/guides/BACKWARD_EULER_GUIDE_RU.md) |
+| LSODE2 | [Guide](https://github.com/Gleb-Zaslavsky/RustedSciThe/blob/master/bindings/python/guides/LSODE2_GUIDE_EN.md) | [Руководство](https://github.com/Gleb-Zaslavsky/RustedSciThe/blob/master/bindings/python/guides/LSODE2_GUIDE_RU.md) |
+| BVP_sci | [Guide](https://github.com/Gleb-Zaslavsky/RustedSciThe/blob/master/bindings/python/guides/BVP_SCI_GUIDE_EN.md) | [Руководство](https://github.com/Gleb-Zaslavsky/RustedSciThe/blob/master/bindings/python/guides/BVP_SCI_GUIDE_RU.md) |
+| BVP_Damp | [Guide](https://github.com/Gleb-Zaslavsky/RustedSciThe/blob/master/bindings/python/guides/BVP_DAMP_GUIDE_EN.md) | [Руководство](https://github.com/Gleb-Zaslavsky/RustedSciThe/blob/master/bindings/python/guides/BVP_DAMP_GUIDE_RU.md) |
+| Nonlinear systems and fitting | [Guide](https://github.com/Gleb-Zaslavsky/RustedSciThe/blob/master/bindings/python/guides/NONLINEAR_FITTING_GUIDE_EN.md) | [Руководство](https://github.com/Gleb-Zaslavsky/RustedSciThe/blob/master/bindings/python/guides/NONLINEAR_FITTING_GUIDE_RU.md) |
+
+Runnable, commented Python examples include Robertson kinetics, Lorenz and
+three-body systems, frontend/layout comparisons, continuation, AOT and task
+documents. See the [Python example index](https://github.com/Gleb-Zaslavsky/RustedSciThe/blob/master/bindings/python/examples/README.md);
+the repository's Rust examples are collected separately in the root
+[examples directory](https://github.com/Gleb-Zaslavsky/RustedSciThe/tree/master/examples/).
+
+## Text Tasks and Executable
+
+Python users can parse and run text task documents with `TaskDocument` or
+`task(...)`, and batch independent documents with `run_task_batch(...)`. The
+batch API preserves typed per-task failures and can write a compact table. The
+Windows console executable is part of the main Rust project, not this Python
+package; see the [task parser documentation](https://github.com/Gleb-Zaslavsky/RustedSciThe/tree/master/src/command_interpreter/).
+
+## Diagnostics and Development
+
+Native exceptions preserve their Python class and expose machine-readable
+`stage`, `solver` and `route` attributes. Telemetry is opt-in and solutions
+provide detached counters, timings and report writers where supported. Prefer
+these fields over parsing exception text or redirecting build output into a
+performance report.
+
+For development and contribution checks, see the [Python contract tests](https://github.com/Gleb-Zaslavsky/RustedSciThe/tree/master/bindings/python/tests/),
+the [strict typing consumer](https://github.com/Gleb-Zaslavsky/RustedSciThe/blob/master/bindings/python/tests/typing_consumer.py),
+and the [Python binding roadmap](https://github.com/Gleb-Zaslavsky/RustedSciThe/blob/master/bindings/python/TODO.md).
+The core crate's broader algorithm documentation and release evidence remain
+in the [main README](https://github.com/Gleb-Zaslavsky/RustedSciThe/blob/master/README.md)
+and solver guides.
+

rustedscithe-0.1.2/README.md

@@ -0,0 +1,170 @@
+# RustedSciThe for Python
+
+RustedSciThe brings a symbolic engine and a family of stiff ODE, boundary-value,
+nonlinear-system and fitting solvers to Python. The Python package is a thin,
+idiomatic interface over a compiled Rust numerical core: expressions are parsed
+and differentiated in Rust, solver workspaces and algorithms stay in Rust, and
+Python receives ordinary typed objects and detached NumPy results.
+
+This project is for problems where a trustworthy derivative, a stiff or
+strongly nonlinear method, and visibility into numerical behavior matter more
+than hiding every solver choice behind one universal interface.
+
+## Why RustedSciThe
+
+- **Symbolic derivatives without a Python CAS dependency.** Build expressions,
+  simplify and substitute them, and derive exact Jacobians with RustedSciThe's
+  own symbolic engine. Prepared residual and Jacobian callbacks are reused
+  instead of being rebuilt during every numerical iteration.
+- **Native stiff IVP and BVP solvers.** Use Rust implementations inspired by
+  SciPy's Radau, variable-order BDF and collocation methods, alongside LSODE2,
+  Backward Euler and the damped BVP solver. The numerical solve runs in Rust,
+  not in a Python loop around a native linear algebra call.
+- **More than ODE integration.** Solve square nonlinear systems, rectangular
+  least-squares problems, observation-based fitting and separable models with
+  VarPro. These are first-class numerical workflows, not just helper routines
+  attached to an IVP API.
+- **Algorithms beyond the SciPy-like IVP/BVP set.** Native nonlinear methods,
+  a dedicated rectangular Levenberg-Marquardt solver, Gavin fitting and
+  variable projection cover workflows that are not merely wrappers around
+  SciPy's ODE interfaces.
+- **Choose the linear algebra layout when the solver supports it.** Dense,
+  Sparse and Banded routes are available across most solver families. Their
+  performance depends on the equation structure and problem size; there is no
+  universally fastest layout. BVP_sci additionally offers opt-in SuperLU.
+- **Lambdify and AOT execution.** Use prepared in-process callbacks for a fast
+  development cycle, or generated compiled callbacks where supported. The
+  symbolic frontend (`expr_legacy` or `atom_native`) is a separate choice from
+  the execution route (`lambdify` or `aot`).
+- **Prepared models and parameter series.** Reuse symbolic preparation across
+  continuation and restart workflows where the solver exposes that lifecycle.
+- **Diagnostics designed for numerical work.** Typed exceptions, route
+  provenance, optional counters and stage timings help explain what happened
+  without parsing console output or error messages.
+
+Performance is workload-dependent. A Rust implementation is not automatically
+the fastest choice for every equation, frontend, layout or lifecycle. Compare
+the same workload and inspect preparation, callback and full-solve timings
+before choosing a route.
+
+## Architecture
+
+```text
+Python model and NumPy inputs
+             |
+       PyO3 boundary
+             |
+Rust symbolic preparation -> exact derivatives -> Lambdify or AOT callbacks
+             |
+Rust solver -> Dense / Sparse / Banded linear algebra where supported
+             |
+typed result, telemetry and owned NumPy arrays
+```
+
+Python is the user-facing layer, not a second implementation of the algorithms.
+NumPy arrays returned by result objects own their data; they do not borrow a
+mutable solver workspace. The package does not require SymPy.
+
+## Quick Start
+
+This small stiff IVP uses Radau with its default symbolic and numerical
+configuration:
+
+```python
+from rustedscithe import Expr, RadauSolver
+
+y = Expr.variable("y")
+solver = RadauSolver([-y], ["y"], "t", 0.0, 1.0, 0.1)
+solution = solver.solve([1.0])
+print(f"y(1) = {solution.final_state[0]:.8f}")
+```
+
+Install the published package with `python -m pip install rustedscithe`. For a
+checkout-based editable build, install `maturin` and run:
+
+```powershell
+python -m maturin develop --manifest-path bindings/python/Cargo.toml
+```
+
+The extension uses the stable `abi3` Python 3.10+ ABI and NumPy 2.x. Import the
+public API from `rustedscithe`; `_native` is an implementation module.
+
+## Solver Families
+
+| Problem | Python entry points | Useful distinction |
+| --- | --- | --- |
+| Stiff initial-value problems | `RadauSolver`, `BdfSolver`, `BackwardEulerSolver`, `Lsode2Solver` | Radau and LSODE2 expose structured layouts where supported; standalone BDF and Backward Euler are Dense. LSODE2 separates its solver family from its Adams/BDF/Auto controller. |
+| Boundary-value problems | `BvpSciSolver`, `BvpDampSolver` | BVP_sci uses symbolic boundary residuals and collocation; BVP_Damp uses observed state/boundary data and damped Newton. Their boundary contracts intentionally differ. |
+| Nonlinear systems | `NonlinearSolver` | Prepared square systems with Newton, LM and trust-region method families. |
+| Least squares and fitting | `FittingSolver`, `GavinFittingSolver`, `VarProSolver` | Rectangular symbolic least squares, observation-based fitting and separable-model fitting have distinct contracts. |
+| Text task documents | `TaskDocument`, `task`, `run_task_batch` | Parse and execute reusable IVP/BVP documents through the native task infrastructure. |
+
+Use `capabilities("solver_name")` to inspect the Python-supported routes.
+Native features that are not exposed by this package are not implied by a
+shared option name; unsupported combinations raise a typed error instead of
+silently selecting a different backend.
+
+## Configuration Choices
+
+Several independent axes shape a solve, and a given solver supports only a
+documented subset of their combinations:
+
+| Axis | Examples | What it selects |
+| --- | --- | --- |
+| Symbolic frontend | `expr_legacy`, `atom_native` | Representation used for symbolic preparation and differentiation. |
+| Callback execution | `lambdify`, `aot` | In-process prepared closures or generated compiled artifacts. |
+| Matrix layout | `dense`, `sparse`, `banded` | Storage and linear-system route. |
+| Callback policy | `sequential`, `parallel`, `auto` | Scheduling where the native solver supports it. |
+| Lifecycle | fresh solve, `prepare`, continuation, restart | Whether prepared model or previous state is reused. |
+
+Check the relevant guide and `capabilities()` before combining options. A
+structured layout is useful only when the problem has exploitable structure;
+parallel callback evaluation and AOT compilation also have workload-dependent
+break-even points. For continuation, distinguish cold preparation from warm
+solve time.
+
+## Guides and Examples
+
+The overview guides explain shared Python conventions. Solver-specific guides
+preserve each native solver's option breadth, supported routes, limitations and
+recommended workflows.
+
+| Family | English | Русский |
+| --- | --- | --- |
+| Python API overview | [Python solvers](https://github.com/Gleb-Zaslavsky/RustedSciThe/blob/master/bindings/python/guides/PYTHON_SOLVERS_GUIDE_EN.md) | [Обзор Python API](https://github.com/Gleb-Zaslavsky/RustedSciThe/blob/master/bindings/python/guides/PYTHON_SOLVERS_GUIDE_RU.md) |
+| Radau | [Guide](https://github.com/Gleb-Zaslavsky/RustedSciThe/blob/master/bindings/python/guides/RADAU_GUIDE_EN.md) | [Руководство](https://github.com/Gleb-Zaslavsky/RustedSciThe/blob/master/bindings/python/guides/RADAU_GUIDE_RU.md) |
+| BDF | [Guide](https://github.com/Gleb-Zaslavsky/RustedSciThe/blob/master/bindings/python/guides/BDF_GUIDE_EN.md) | [Руководство](https://github.com/Gleb-Zaslavsky/RustedSciThe/blob/master/bindings/python/guides/BDF_GUIDE_RU.md) |
+| Backward Euler | [Guide](https://github.com/Gleb-Zaslavsky/RustedSciThe/blob/master/bindings/python/guides/BACKWARD_EULER_GUIDE_EN.md) | [Руководство](https://github.com/Gleb-Zaslavsky/RustedSciThe/blob/master/bindings/python/guides/BACKWARD_EULER_GUIDE_RU.md) |
+| LSODE2 | [Guide](https://github.com/Gleb-Zaslavsky/RustedSciThe/blob/master/bindings/python/guides/LSODE2_GUIDE_EN.md) | [Руководство](https://github.com/Gleb-Zaslavsky/RustedSciThe/blob/master/bindings/python/guides/LSODE2_GUIDE_RU.md) |
+| BVP_sci | [Guide](https://github.com/Gleb-Zaslavsky/RustedSciThe/blob/master/bindings/python/guides/BVP_SCI_GUIDE_EN.md) | [Руководство](https://github.com/Gleb-Zaslavsky/RustedSciThe/blob/master/bindings/python/guides/BVP_SCI_GUIDE_RU.md) |
+| BVP_Damp | [Guide](https://github.com/Gleb-Zaslavsky/RustedSciThe/blob/master/bindings/python/guides/BVP_DAMP_GUIDE_EN.md) | [Руководство](https://github.com/Gleb-Zaslavsky/RustedSciThe/blob/master/bindings/python/guides/BVP_DAMP_GUIDE_RU.md) |
+| Nonlinear systems and fitting | [Guide](https://github.com/Gleb-Zaslavsky/RustedSciThe/blob/master/bindings/python/guides/NONLINEAR_FITTING_GUIDE_EN.md) | [Руководство](https://github.com/Gleb-Zaslavsky/RustedSciThe/blob/master/bindings/python/guides/NONLINEAR_FITTING_GUIDE_RU.md) |
+
+Runnable, commented Python examples include Robertson kinetics, Lorenz and
+three-body systems, frontend/layout comparisons, continuation, AOT and task
+documents. See the [Python example index](https://github.com/Gleb-Zaslavsky/RustedSciThe/blob/master/bindings/python/examples/README.md);
+the repository's Rust examples are collected separately in the root
+[examples directory](https://github.com/Gleb-Zaslavsky/RustedSciThe/tree/master/examples/).
+
+## Text Tasks and Executable
+
+Python users can parse and run text task documents with `TaskDocument` or
+`task(...)`, and batch independent documents with `run_task_batch(...)`. The
+batch API preserves typed per-task failures and can write a compact table. The
+Windows console executable is part of the main Rust project, not this Python
+package; see the [task parser documentation](https://github.com/Gleb-Zaslavsky/RustedSciThe/tree/master/src/command_interpreter/).
+
+## Diagnostics and Development
+
+Native exceptions preserve their Python class and expose machine-readable
+`stage`, `solver` and `route` attributes. Telemetry is opt-in and solutions
+provide detached counters, timings and report writers where supported. Prefer
+these fields over parsing exception text or redirecting build output into a
+performance report.
+
+For development and contribution checks, see the [Python contract tests](https://github.com/Gleb-Zaslavsky/RustedSciThe/tree/master/bindings/python/tests/),
+the [strict typing consumer](https://github.com/Gleb-Zaslavsky/RustedSciThe/blob/master/bindings/python/tests/typing_consumer.py),
+and the [Python binding roadmap](https://github.com/Gleb-Zaslavsky/RustedSciThe/blob/master/bindings/python/TODO.md).
+The core crate's broader algorithm documentation and release evidence remain
+in the [main README](https://github.com/Gleb-Zaslavsky/RustedSciThe/blob/master/README.md)
+and solver guides.

{rustedscithe-0.1.1 → rustedscithe-0.1.2}/bindings/python/Cargo.lock

@@ -4,7 +4,7 @@ version = 4
 
 [[package]]
 name = "RustedSciThe"
-version = "0.4.23"
+version = "0.4.24"
 dependencies = [
  "ahash",
  "append-only-vec",
@@ -7178,7 +7178,7 @@ dependencies = [
 
 [[package]]
 name = "rustedscithe-python"
-version = "0.1.1"
+version = "0.1.2"
 dependencies = [
  "RustedSciThe",
  "nalgebra",

{rustedscithe-0.1.1 → rustedscithe-0.1.2}/bindings/python/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "rustedscithe-python"
-version = "0.1.1"
+version = "0.1.2"
 edition = "2024"
 publish = false
 description = "PyO3 bindings for the RustedSciThe symbolic and numerical APIs"
@@ -18,6 +18,8 @@ extension-module = ["pyo3/extension-module"]
 abi3 = ["pyo3/abi3-py310"]
 # Opt-in only: forwards the core crate's runtime-loaded SuperLU bridge support.
 superlu = ["rustedscithe-core/superlu"]
+# Test-only Python boundary probe; never enabled in published wheels.
+test-panic-probe = []
 
 [dependencies]
 pyo3 = { version = "0.27" }

{rustedscithe-0.1.1 → rustedscithe-0.1.2}/bindings/python/PUBLICATION_GUIDE.md

@@ -95,12 +95,40 @@ when the test harness requires it.
 - [x] installed-wheel NumPy and `Expr` import smoke test passed.
 - [x] Python contract suite passed: `87 passed`.
 - [ ] Rust unit-test link gate with the installed Python development library.
-- [x] Windows TestPyPI upload and clean install from TestPyPI passed.
-- [ ] Production PyPI upload.
+- [x] Initial Windows TestPyPI `0.1.0` upload and clean install passed; it is
+  staging-only because its PyPI description used the core README.
+- [x] Corrected Windows `0.1.1` artifacts uploaded to TestPyPI and clean
+  installed successfully with the Python-specific README.
+- [x] Windows-first `0.1.1` sdist and wheel uploaded to production PyPI and
+  clean installed from the public index.
+
+### Windows candidate 0.1.2
+
+Local candidate evidence (2026-10-15): the sdist was rebuilt, the Windows
+`cp310-abi3-win_amd64` wheel was rebuilt from that sdist, and both artifacts
+passed `twine check`. The wheel was installed in a clean CPython 3.14 / NumPy
+2.5.4 environment outside the checkout; its full Python suite passed with
+`99 passed, 2 skipped`. The two skips are the intentionally absent
+test-only panic probe. The README metadata check confirms the Python README,
+not the core Rust README, is embedded.
+The build used binding version `0.1.2` with the current core version `0.4.24`.
+
+Candidate artifact hashes:
+
+| Artifact | SHA-256 |
+| --- | --- |
+| `rustedscithe-0.1.2.tar.gz` | `f923d1eadf167e904f2bed1f095a672f7362941ff01098330ba94bb221ae6d9c` |
+| `rustedscithe-0.1.2-cp310-abi3-win_amd64.whl` | `fdb528784e59d9a8e8a9ebb71576920bc4aab5ed69de432bfc70dd68cdd8db9f` |
+
+These are local candidate files and have not been uploaded. Do not rebuild
+between the TestPyPI smoke and production upload; publish the same immutable
+sdist and wheel only after TestPyPI validation.
 
 Recorded Windows toolchain for this evidence: Rust/Cargo `1.98.1`, Python
 `3.14.6`, NumPy `2.5.4`, PyO3 `0.27.2`, maturin `1.15.0`, twine `7.0.0`,
 binding/core version `0.1.1`/`0.4.23`.
+The published Windows `0.1.1` artifact hashes are recorded in the binding
+TODO and should be retained with the release report.
 
 ## Linux
 
@@ -190,7 +218,7 @@ if necessary:
 ```powershell
 $ErrorActionPreference = "Stop"
 $python = (Resolve-Path .\.venv-gavin-win\Scripts\python.exe).Path
-$dist = (Resolve-Path .\bindings\python\target\publication-20261015).Path
+$dist = (Resolve-Path .\bindings\python\target\publication-0.1.2).Path
 $sdist = (Get-ChildItem $dist -Filter "*.tar.gz").FullName
 $wheel = (Get-ChildItem (Join-Path $dist "wheels-from-sdist") -Filter "*.whl").FullName
 
@@ -210,7 +238,7 @@ $smokePython = Join-Path $smoke "Scripts/python.exe"
 & $smokePython -m pip install --no-cache-dir `
   --index-url https://test.pypi.org/simple/ `
   --extra-index-url https://pypi.org/simple/ `
-  rustedscithe==0.1.1
+  rustedscithe==0.1.2
 & $smokePython -c "import numpy, rustedscithe; from rustedscithe import Expr; print(rustedscithe.__file__); print(numpy.__version__); print(Expr.parse('x^2 + 1'))"
 ```
 
@@ -224,7 +252,7 @@ production:
 PyPI release files cannot be replaced under the same version. If an upload or
 metadata mistake is found after publication, increment the package version,
 rebuild both artifacts, rerun the gates and publish a new release instead of
-reusing `0.1.1`.
+reusing an already-published version.
 
 For later CI publication, prefer Trusted Publishing or a short-lived scoped
 credential; never commit a long-lived upload token.