Complete v0.8.0 pre-release correctness and safety remediation

[IvanChernyshov]

Outcome

Complete the final v0.8.0 correctness and safety remediation before release qualification.

Workstreams

• R1 — Correct and freeze the separator inverse objective contract — R1 — Correct and freeze the separator inverse objective contract #36
• R2 — Replace the scalar proximal loop with a certified bounded solver — R2 — Replace the scalar proximal loop with a certified bounded solver #37
• R3 — Harden public inputs, immutable value objects, and native preconditions (closes after both stages and the integrated R3 gate)
  • R3-A — Add strict shared validators and guard every native container construction — v0.8 R3-A: add strict shared validators and guard every native container construction #38
  • R3-B — Complete package-wide adoption and immutable ownership — v0.8 R3-B: complete package-wide strict input adoption and immutable ownership #39
• R4 — Implement certified periodic nearest-image and minimum-image geometry — v0.8 R4: certify periodic nearest-image and minimum-image geometry #40
• R5 — Make forward generator containment and duplicate safety non-optional — v0.8 R5: centralize generator preparation and make native safety non-optional #41
• R6 — Bind observations, fits, realizations, and reports to canonical source data — v0.8 R6: bind separator observations, results, realizations, and reports to canonical source data #42
• R7 — Make the active-set final state atomic and self-consistent
• R8 — Make diagnostics and strict validation severity-complete
• R9 — Synchronize the public API, documentation, distribution, licensing, and release contract

Issue #33 is the final qualification and release workstream and depends on completion of this tracker.

Execution order

R1 -> R2 -> R3-A -> R3-B -> R4 -> R5 -> R6 -> R7 -> R8 -> R9 -> #33

Detailed contracts and implementation guidance will be maintained in source-controlled development documentation added by the associated repository patch.

Working rules

• Reproduce each confirmed defect before fixing it where practical.
• Use independent numerical or safety oracles rather than backend agreement alone.
• Approve public formulas, defaults, identity rules, schemas, and severity semantics before implementation.
• Keep each child issue focused and add regression coverage for every confirmed defect.
• Run focused tests, affected subsystem tests, and the full deterministic suite.
• Do not tag or publish from remediation workstreams.

Acceptance criteria

• Focused child issues exist for R1–R9.
• Every R1–R9 issue is closed or explicitly deferred by a maintainer decision compatible with a safe v0.8 release.
• Every confirmed correctness or native-safety defect has regression coverage or an independent release oracle.
• Source-controlled audit and remediation documentation is merged and synchronized with the issue graph.
• No unresolved release-blocking finding remains.
• Issue Qualify and release v0.8.0 #33 can begin from a clean checkout of the exact candidate commit.

Out of scope

New numerical features, broad performance work, and release publication itself.