Improve orbitalMotion robustness and preserve API compatibility

[schaubh]

• Tickets addressed: Improve numerical robustness, API consistency, and validation of the orbitalMotion libraries #1629
• Review: By commit
• Merge strategy: Merge (no squash)

Description

Improve numerical accuracy and robustness across the orbitalMotion libraries and related modules while preserving existing APIs, NumPy scalar outputs, and legacy conventions without deprecations. Add optional checked APIs and enforce inclinations between 0 and 180 degrees.

The six commits cover Kepler solvers, orbital conversions and KeplerianOrbit, mean-element and Hill transformations, environmental helpers and bindings, eclipse calculations, and documentation.

Verification

• 12,182 CI-selected Python tests passed, with no skips.
• 544 native and 97 Rust tests passed.
• Build, standalone-header checks, and focused Sphinx/Doxygen validation passed.
• Additional randomized C/Python reconstruction checks passed.

Added numerical, compatibility, and downstream regression tests. Updated partial-eclipse references using independent high-precision calculations and removed AVS test selectors that performed no checks.

Validation was performed locally on macOS. The external-renderer OpNav Monte Carlo example was reviewed but not executed.

Documentation

Updated API documentation, affected module documentation, the AVS library manual, known issues, and release notes. Added an orbital-motion compatibility guide documenting preserved conventions, validation behavior, and supported domains.

Future work

Further near-parabolic improvements using universal-variable formulations remain outside this PR.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-19T00:27:06.417311Z	8be8804	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.