Publish a frozen installed-wheel BayesianPhysTwin release after the paper claim freeze

[FlorianPfaff]

Purpose

Turn the current 0.4.1.dev0 development package into an immutable installed distribution once the release-facing BayesianPhysTwin claim and its evidence bindings are frozen. This is software/retrieval reproducibility only; it must not consume a sealed target or change a scientific result.

Preconditions

• The full-22 point result, last_residual comparator, raw-covariance failure, exact-mean covariance mechanism, DLO2-to-DLO3 transfer, and independent-validation boundary are synchronized across the public claim snapshot, paper evidence ledger, manuscript, figures, and release wording.
• Every claim-bearing result names its exact code revision, protocol, run/evidence identity, and information boundary.
• The separate Deform360 covariance source/confirmation gate remains accurately open, negative, or complete; release preparation must not open confirmation data.
• Causal4D and Prob4D compatibility ranges are frozen from installed-wheel tests rather than editable checkouts.

Release construction

• Choose the final version and remove the .dev0 suffix only in a dedicated release PR.
• Build wheel and source distribution in the pinned release environment.
• Run the isolated installed-wheel and installed-sdist smoke suites, public API manifest checks, CLI checks, PEP 561 checks, provider-contract corpus, and three-repository installed-wheel capsule.
• Verify the stable distribution member/byte budgets and generate SHA-256 manifests.
• Generate an SBOM, public API manifest, observation/provider schema compatibility manifest, dependency resolver input, and build provenance/attestation.
• Confirm Python support metadata against the actually tested matrix. Add 3.11/3.13 classifiers only if the corresponding isolated release tests pass; otherwise document the narrower support matrix explicitly.
• Create a signed annotated tag at the exact verified release commit and publish a GitHub release containing the wheel, sdist, manifests, SBOM, compatibility record, and release notes.
• Record the archival DOI when available and update CITATION.cff without rewriting historical evidence identities.

Governance

• Require a pull request and independent review for the release boundary.
• Require authoritative quality, security, packaging, provider-contract, and installed-ecosystem checks on the exact release head.
• Prevent force pushes/deletion of the release tag and preserve administrator bypass for documented incident recovery only.

Completion evidence

Close only after the published assets install in clean environments, match their declared digests, expose the documented public API/CLI, pass the released-wheel ecosystem capsule, and resolve to the exact signed tag.

Scientific boundary

A release establishes distribution identity, retrieval, packaging, and compatibility. It does not establish unseen-object transfer, real-provider competence, raw-posterior calibration, Causal4D physical benefit, deployment safety, or general deformable-object state of the art.