solverpilot 0.1.0rc2__tar.gz

solverpilot-0.1.0rc2/BACKEND-CONTRACT-V0_1_0RC2.json

@@ -0,0 +1,38 @@
+{
+  "milestone": "PRE_PUBLIC_0_1_0_RC2",
+  "notes": [
+    "Backend IDs remain stable across the SolverPilot pre-GitHub cleanup.",
+    "Verification-only adapters are never admitted to the default solving registry.",
+    "Availability of optional public backends remains environment-dependent.",
+    "The legacy optimind Python package is not shipped in SolverPilot 0.1.0rc2."
+  ],
+  "package_version": "0.1.0rc2",
+  "production_baseline_policy": {
+    "convex_qp": "osqp-native when available; otherwise scipy-slsqp-qp-bridge for non-proof intents",
+    "learned_lp_performance_routing": false,
+    "lp": "scipy-highs-ds",
+    "milp": "scipy-highs-bridge"
+  },
+  "schema": "solverpilot.backend_contract.v1",
+  "stable_backend_ids": {
+    "base_runtime": [
+      "scipy-highs-ds",
+      "scipy-highs-ipm",
+      "scipy-highs-bridge",
+      "scipy-slsqp-qp-bridge"
+    ],
+    "optional_public": [
+      "highspy-native",
+      "osqp-native",
+      "pyscipopt-native",
+      "nlopt-slsqp-native"
+    ],
+    "verification_only": [
+      "casadi-osqp-bridge",
+      "casadi-highs-bridge",
+      "casadi-cbc-bridge",
+      "bundled-osqp-capi",
+      "bundled-highs-capi"
+    ]
+  }
+}

solverpilot-0.1.0rc2/CHANGELOG.md

@@ -0,0 +1,121 @@
+# Changelog
+
+## 0.1.0rc2 — Correctness and trust hardening
+
+- canonicalizes every accepted QP Hessian to one symmetric matrix before hashing, validation, or backend translation; pairwise symmetry checks can no longer be relaxed by an unrelated large coefficient;
+- replaces raw-scale convexity tolerance with PSD-preserving local congruence scaling so a huge positive coefficient cannot hide material negative curvature;
+- makes conic bound/row feasibility componentwise and hardens PSD validation against the same global-scale masking failure;
+- rejects non-finite semantic/NLP candidates, objective coefficients, invalid infinity directions in bounds, and non-finite validation tolerances;
+- makes runtime and CP result payloads immutable snapshots so post-solve mutation cannot manufacture stronger proof claims or desynchronize a validated candidate from its report;
+- makes reference-free benchmark/oracle success proof-aware, requires protocol/environment/instance identity, and rejects non-finite timing costs;
+- records solver-reported objective values for native HiGHS/OSQP paths instead of validating a value recomputed from the same candidate;
+- hardens final pre-public release engineering by replacing production `assert` invariants with explicit exceptions, adding destructive CP/MPS/proof regressions, expanding optional-integration qualification across macOS/Windows Python 3.12–3.14, and gating release qualification on static correctness, dependency audit, SBOM generation, and least-privilege artifact/SBOM attestation;
+- supersedes the locally audited `0.1.0rc1` source artifact; public publication remains fail-closed pending exact-artifact external qualification.
+
+## 0.1.0rc1 — Integrated trust/application release candidate
+
+- promotes the locally verified S2–S10 additive layers into a distinct prerelease version rather than overwriting the historical `0.0.40rc2` artifact;
+- adds strict JSON/CSV ingestion and provenance, oracle/regret evaluation, versioned feature/OOD diagnostics, claim-safe reporting, explicit extension staging, TSP and CVRP/VRPTW application packs, and opt-in SQLite history;
+- preserves the frozen 78-symbol top-level API by keeping new capabilities under explicit submodules;
+- hardens cross-system trust boundaries around oracle comparability, report immutability, and independent optimality-proof issuance;
+- retains learned LP performance routing as disabled and keeps public publication fail-closed pending exact-artifact external qualification.
+
+## 0.0.40rc2 — Trust and numerical hardening after Track P merge
+
+- fail closed for unverified/unknown quadratic convexity at capability, inspection, planning, runtime, and guarded backend boundaries;
+- use scale-aware PSD/symmetry checks and primal feasibility validation while continuing to report raw residuals;
+- separate backend-reported optimality from independent primal/dual/gap/certificate evidence through `SolveResult.optimality_evidence`;
+- strengthen CP IR referential/type invariants and make parent revalidation capable of revoking an isolated worker's proof flag;
+- add an independent CP controller timeout;
+- record NLP `log`/`sqrt`/division domain hazards and use deterministic finite initial-point search;
+- distinguish solver-certified MINLP global proof scope from `independently_verified_global`;
+- reject ambiguous multiple MPS RHS/RANGES/BOUNDS vectors instead of silently selecting one;
+- constrain declared Python/runtime dependency ranges to the qualification line;
+- isolate OR-Tools CP-SAT native solving in a subprocess and revalidate results in the parent process to avoid a verified HiGHS shared-library ABI collision.
+
+- forward-ports the frozen Track P P0–P9 feature line onto the hardened SolverPilot rc8 codebase instead of overwriting M27–M33/release-hardening changes;
+- adds the semantic modeling kernel, parameter compiler/cache, Capability Protocol 2.0, bridge/transformation-tape engine, persistent sessions, conic layer, smooth NLP/AD, certified convex binary MINLP orchestration, and CP/CP-SAT core;
+- renames all live Track P Python modules/schema identifiers/metadata to the `solverpilot` namespace while preserving original OptiMind naming only in frozen history;
+- keeps the M30-frozen 78-symbol top-level API unchanged; Track P APIs are canonical under explicit submodules;
+- adds `conic`, `nlp`, `minlp`, and `cp` optional extras and the `solverpilot-capabilities` CLI;
+- expands README, examples, API docs, and limitations around the exact guarantee boundaries of the merged functionality;
+- retains the rejected learned LP performance selector as disabled; no new performance-ranking claim is introduced by this merge.
+
+## 0.0.36rc7 — Final pre-GitHub release cleanup
+
+- removes the pre-public `optimind` compatibility package to eliminate nested-import class identity duplication;
+- removes the internal `OptiMindError` compatibility alias from live source;
+- makes release manifest/smoke validation derive current name/version/Python floor from `pyproject.toml`;
+- derives RC API/backend snapshot filenames from the current prerelease version;
+- makes release smoke fail if a legacy `optimind` namespace is shipped;
+- moves historical M31/M32/M33 release helper scripts out of live `tools/`;
+- refreshes pre-GitHub hardening/verification documentation.
+
+## 0.0.36rc6 — SolverPilot brand and package migration
+
+- renames the public brand, distribution, CLI entry points, and canonical Python namespace to SolverPilot / `solverpilot`;
+- records author/maintainer metadata;
+- creates SolverPilot API/backend contract snapshots while preserving historical backend IDs;
+- retains the old OptiMind naming only as historical research provenance.
+
+## 0.0.36rc5 — Apache-2.0 license decision
+
+- adopts Apache License 2.0 (`Apache-2.0`);
+- adds the root `LICENSE` and PEP 639 license metadata;
+- keeps publication fail-closed pending final repository/service configuration.
+
+## 0.0.36rc4 — Pre-GitHub hardening
+
+- fixes atomic benchmark reacquisition, download verification semantics, and relative verification paths;
+- separates lightweight PR CI from manual exact-artifact release qualification;
+- binds disabled publishing to an exact successful qualification run/commit;
+- removes release binaries from the source tree and adds repository security/contribution policy files.
+
+## 0.0.36rc3 — M33 External CI & Publication Decision
+
+- narrows intended 1.0 support to CPython 3.12–3.14 and adds Python 3.14 to the exact-artifact matrix;
+- raises runtime floors to NumPy 2.2 and SciPy 1.15, with a dedicated minimum-dependency regression;
+- runs compatibility cells inside isolated virtual environments;
+- adds PyPA pip-audit runtime dependency checks and CycloneDX evidence;
+- documents the release process per current Scientific Python/GitHub/PyPI security guidance;
+- adds Dependabot for reviewed GitHub Action SHA updates and a disabled OIDC-only PyPI publication template;
+- adds same-source reproducibility diagnostics;
+- keeps public RC/1.0 authorization fail-closed until external execution and owner metadata complete.
+
+
+## 0.0.36rc2 — M32 External Compatibility & Supply-Chain Hardening
+
+- preserves the M30/M31 frozen 78-symbol public API and backend IDs;
+- changes CI to build-once/test-many using the exact release wheel;
+- records resolver NumPy/SciPy versions and requires `pip check` in every compatibility cell;
+- pins all external GitHub Actions to immutable full commit SHAs;
+- adds build-provenance attestation support while leaving publication disabled;
+- keeps public RC/1.0 fail-closed until the complete external matrix and owner publication metadata are available.
+
+
+## 0.0.36rc1 — M31 Technical Release Candidate Compatibility Checkpoint
+
+- froze M30 public API/backend contract into M31 snapshots;
+- added a fail-closed 3-OS x 4-Python compatibility workflow;
+- added Python-3.10 grammar audit and current Linux/Python-3.13 execution evidence;
+- separated upstream dependency-wheel availability from SolverPilot compatibility claims;
+- recorded unresolved license/name/maintainer/URL owner decisions and public-brand collision risk;
+- public 1.0 compatibility remains unauthorized until CI matrix execution.
+
+
+## 0.0.35 — M30 Release Consolidation
+
+- Freeze a stable top-level public API for the 1.0 release line.
+- Move milestone-specific evidence translators and the rejected selective-LP evaluator to `solverpilot.experimental`.
+- Add a stable public exception hierarchy for backend availability, capability mismatch, and planner routing failures.
+- Replace stale research-oriented README content with a product-facing scope/claim boundary.
+- Add explicit release/provenance/API documentation and public-API manifest tests.
+- Remove generated `egg-info`, bytecode caches, and stale root-level milestone clutter from the release source tree.
+- Keep learned LP performance routing disabled after M24–M29 negative generalization evidence.
+
+## 0.0.34 — M29
+
+- Value-of-information/feature-representation audit for LP DS/IPM selection.
+- No feature family passed cross-cohort authorization; learned LP routing closed for the 1.0 line.
+
+Earlier milestone detail is preserved under `docs/history/` and in the complete benchmark archive.

solverpilot-0.1.0rc2/CONTRIBUTING.md

@@ -0,0 +1,42 @@
+# Contributing
+
+SolverPilot is still pre-1.0. Changes should preserve the project's fail-closed evidence standard: do not promote an unexecuted compatibility cell, skipped optional integration, or historical benchmark result into a current pass.
+
+## Development setup
+
+```bash
+python -m pip install ".[test]"
+python -m pytest
+```
+
+For benchmark work:
+
+```bash
+python -m pip install ".[benchmark]"
+```
+
+For optional public solver integrations, install the relevant extra (`highs`, `osqp`, `scip`, `nlopt`, or `casadi`).
+
+## Pull requests
+
+A pull request should:
+
+- include regression tests for behavioral changes;
+- keep public-status and evidence claims scoped to what the tests actually establish;
+- preserve deterministic/provenance fields in benchmark artifacts;
+- avoid adding generated wheels, sdists, caches, benchmark corpora, or credentials to the repository;
+- update public API/release documentation when externally visible behavior changes.
+
+Normal PR CI is intentionally smaller than release qualification. Cross-platform release claims come only from the manual exact-artifact qualification workflow.
+
+## API changes
+
+The top-level public API was frozen before 1.0. Backward-compatible additions require explicit review; removals or semantic changes should not be slipped into cleanup work. `solverpilot.experimental` is not covered by the same compatibility promise.
+
+## Security
+
+Follow `SECURITY.md`. Do not disclose suspected vulnerabilities in public issues or pull requests.
+
+## Contribution licensing
+
+Unless explicitly stated otherwise, contributions intentionally submitted for inclusion in this project are provided under the Apache License 2.0, consistent with Section 5 of the license.

solverpilot-0.1.0rc2/KNOWN-LIMITATIONS.md

@@ -0,0 +1,70 @@
+# Known Limitations — 0.1.0rc2
+
+This file records real limitations and guarantee boundaries for the merged SolverPilot + Track P prerelease.
+
+
+## 0.1.0rc2 release-candidate boundaries
+
+The S2–S10 migration layers are part of this prerelease source line, but the 78-symbol top-level API remains frozen. The new layers are intentionally submodule-scoped. Public release qualification still requires the exact-artifact GitHub matrix, including optional native integrations and artifact attestation before publication.
+
+The learned solver selector remains disabled. OOD diagnostics are conservative shift indicators rather than calibrated probabilities. History persistence is opt-in plaintext SQLite and intentionally excludes raw solution vectors/problem arrays, but caller-provided metadata can still be sensitive. TSP/VRP exact reference solvers are exponential and intended only for small validation/oracle cases. Extension activation assumes caller-owned canonical registries are not mutated concurrently outside the manager during activation.
+
+## Validation tolerances
+
+Candidate validation uses `ValidationTolerances` defaults with an absolute feasibility floor of `1e-7` plus an internal scale-aware relative term. Raw absolute residuals are still reported, and a warning records when a candidate is accepted only by the scale-aware criterion. High-level `solve()` / `solve_production()` does not yet expose a per-call validation-tolerance parameter, so users with domain-specific numerical requirements should still validate against their own tolerances.
+
+## Infeasible / unbounded status evidence
+
+Candidate-bearing statuses are independently checked against canonical constraints, integrality, and objective consistency. `INFEASIBLE`, `UNBOUNDED`, and `INFEASIBLE_OR_UNBOUNDED` normally reflect backend termination unless independent certificate/diagnostic evidence is explicitly recorded.
+
+## Learned LP routing
+
+Learned LP performance routing remains disabled. Track P does not change or override the M24–M29 negative generalization decision.
+
+## Conic boundary
+
+SOC and RSOC representation/validation are supported, with a restricted verified linear-objective solve path. PSD representation/validation is supported, but generic PSD solving is not promoted as verified. Quadratic-objective conic solving also remains fail-closed without the necessary conformance evidence. Exponential/power/generalized-power cones are not implemented.
+
+## NLP boundary
+
+Smooth continuous NLP is optional and uses the pinned CasADi verification path. Generic NLP results are local-optimal candidates only after independent primal/objective validation and KKT stationarity checks. SolverPilot does not claim global optimality for generic NLPs. Nonsmooth generic atoms such as arbitrary `abs/max/min` are not part of the current verified surface.
+
+## MINLP boundary
+
+The current proof-aware MINLP layer supports a certified convex **binary-discrete** scope. General integer MINLP, nonconvex/global MINLP, nonlinear equalities, two-sided nonlinear constraints, and indicator+MINLP composition remain unsupported/fail-closed.
+
+## Constraint-programming boundary
+
+OR-Tools CP-SAT is executed in a Python isolated-mode subprocess rather than loaded after the core HiGHS path in the same process. This is intentional: the verified Linux OR-Tools 9.15.6755 wheel and the SciPy/HiGHS path can expose incompatible HiGHS shared-library ABIs when loaded in the wrong order. The worker protocol binds the request/response to the SolverPilot version, exact OR-Tools version, request nonce, structural hash, and data hash. Worker results cross a strict JSON boundary and primal/objective data are revalidated in the parent process; backend optimality is preserved only when the worker status/proof metadata and parent checks are mutually consistent.
+
+The reference CP backend is exhaustive and can return `unknown_state_limit` when its configured state budget would be exceeded. OR-Tools CP-SAT is optional and locked to version `9.15.6755` for the frozen P9 integration evidence; public cross-platform support still depends on the release qualification matrix.
+
+## Persistence / reoptimization
+
+`PersistentSession` can select native patching only when exact granular capability evidence is runtime verified. Reuse is not guaranteed to be faster; Track P retained negative timing cases where a persistent solve was slower than a cold rebuild.
+
+## Cross-platform release status
+
+Local Linux validation is not equivalent to public support. Linux/macOS/Windows support for Python 3.12–3.14 is promoted only after the manual exact-artifact release qualification workflow passes.
+
+## Optional integrations
+
+Availability depends on third-party binary packages, bundled plugins, and platform support. An upstream wheel existing is not by itself SolverPilot integration evidence.
+
+## Historical 0.0.40rc2 core hardening semantics
+
+- A `QuadraticProblem` may still be constructed with `convexity_status=UNKNOWN` for compatibility, but it is not eligible for convex-QP capability classification, planning, inspection, runtime execution, or guarded direct QP backend solving until convexity is confirmed.
+- `PublicStatus.VALID_OPTIMAL` remains a compatibility status: it means the backend reported optimality and the canonical primal candidate validated. Inspect `SolveResult.optimality_evidence` for whether dual/gap/certificate evidence was independently verified.
+- Linear/QP primal feasibility now uses an absolute numerical floor plus a scale-aware relative term internally. Large absolute residuals accepted only by the scale-aware criterion are surfaced as validation warnings.
+- NLP IR records domain hazards for `log`, `sqrt`, and symbolic division when safety cannot be proved from declared bounds. Compilation remains compatible; the Ipopt bridge uses deterministic finite starting-point search, and final original-space validation remains authoritative.
+- MINLP `globally_proven=True` is solver-certified within the compiler's convexity assumptions. `independently_verified_global` is a separate field and is currently false for the P8 orchestration path because SolverPilot does not reconstruct the complete end-to-end KKT/MILP proof chain independently.
+
+
+## Research benchmark cache security
+
+Some scripts under `benchmarks/` consume locally generated Python pickle caches. These are trusted-development artifacts, not safe interchange files. Loading a pickle from an untrusted source can execute code. Public dataset acquisition and scientific evidence must use the hash/provenance-controlled acquisition path rather than accepting third-party pickle caches.
+
+
+## Local build reproducibility boundary
+
+With a fixed `SOURCE_DATE_EPOCH`, the current local diagnostic wheel was byte-reproducible across two independent builds, while the sdist had identical member names and semantic file contents but not identical archive bytes. This local environment also does not provide the exact build-system versions pinned by `pyproject.toml`. Public-release reproducibility and exact build-backend qualification therefore remain GitHub release-qualification gates rather than locally certified properties.

solverpilot-0.1.0rc2/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.

solverpilot-0.1.0rc2/MANIFEST.in

@@ -0,0 +1,30 @@
+include README.md
+include LICENSE
+include CHANGELOG.md
+include SECURITY.md
+include CONTRIBUTING.md
+include KNOWN-LIMITATIONS.md
+include RELEASING.md
+include PUBLIC-API-V0_1_0RC2.json
+include BACKEND-CONTRACT-V0_1_0RC2.json
+include PRE-PUBLIC-RELEASE-AUDIT-0.1.0rc2.json
+include PRE-PUBLIC-RELEASE-VERIFICATION-0.1.0rc2.md
+include TRACK-P-MERGE-PROVENANCE.json
+include docs/api/PUBLIC-API-v1.md
+include docs/api/EXTENDED-MODELING-API.md
+include docs/release/PRE-GITHUB-HARDENING.md
+include docs/release/SOLVERPILOT-PUBLIC-DOCS-0.1.0RC2.md
+include docs/release/README-CHECKLIST-0.1.0RC2.md
+include docs/release/PRE-GITHUB-LICENSE-DECISION.md
+include docs/release/OWNER-PUBLICATION-DECISIONS.md
+prune docs/history
+prune docs/research
+prune docs/benchmarking
+prune benchmarks
+prune evidence
+prune verification
+prune tests
+prune .github
+prune tools
+global-exclude __pycache__ *.py[cod] *.egg-info *.whl *.tar.gz *.zip
+recursive-include examples *.py *.md