feat: integrate ball-flight and launch-monitor campaign

[dieterolson]

Purpose

Draft integration checkpoint for the Rate of Closure ball-flight and launch-monitor campaign. This aggregates the reviewed source branches without rewriting them and provides one exact head for combined CI and browser/package hardening.

Included work

• convention registry with fail-closed unknown signs
• Launch Direction selector and visible unavailable Foresight sign
• canonical result metric catalog
• desired-flight inverse solver and impact solution families
• capability optimizer including variability and downside/CVaR objectives
• wind physics and responsive locked-aspect plots
• wind uncertainty v2 with perfect-information counterfactual, target-hold, CVaR, and directional risk
• physical-time interactive 3D playback with Launch/Apex/Landing events
• versioned 3D spatial targets
• PyQt/React Launch Monitor Analytics with modules under 400 lines

Local evidence

• combined Python campaign suite: 740 passed, 4 expected Rust-wheel skips
• combined React suite: 439 tests across 70 files passed
• Vite production build, TypeScript type-check, ESLint passed
• Ruff, Black, production mypy, module-size and diff checks passed
• final wind-v2 delta: 25 focused Python and 11 focused React tests plus all type/lint/build gates passed
• manual browser QA at http://127.0.0.1:5270/ confirmed the analytics tab and disabled Foresight sign choice

Release status

This PR is intentionally draft. It does not close #4201 or #4191. Remaining blockers include protected CI/reviews, complete end-user UI workflows for the contract-only cores, worker/thread progress and cancellation, persistence/export, Rust/WASM and installed-package parity, UpstreamDrift pin verification, scientific benchmarks, and browser visual/accessibility coverage.

The exact stack, commands, evidence, and next safe steps are maintained in docs/development/RATE_OF_CLOSURE_CAMPAIGN_HANDOFF.md.

Tracks #4191
Tracks #4201

[d-sorgcodexagent]

Exact-head continuation update (6a6ae47ee158e43a8b6c93de1afc26bd99b06e18):

• Corrected the final SpatialTargetPanel frame literal boundary found by pinned mypy 1.13 on the preceding head.
• Clean-cache pinned mypy 1.13 now passes all 64 changed production files.
• Focused spatial-target GUI suite: 25 passed.
• Ruff check and ruff-format check pass for the corrected file.
• CI Standard quality-gate job 92851958106 on run 31174032957 passed, including lint, format, pinned type check, security audit, and module-size budget.
• The normal auto backend now falls back to the Python swing integrator without emitting a crash-like missing-wheel warning; explicit Rust requests remain fail-closed.
• Responsive PyQt layout and React target-label/control layout were verified at the recorded compact/full viewport sizes; the exact evidence is in docs/development/RATE_OF_CLOSURE_CAMPAIGN_HANDOFF.md.

Other protected jobs are still queued on the shared runners. This PR remains draft and will not be merged by bypassing checks or review.

[d-sorgcodexagent]

Themed-launcher follow-up is published at exact head 280b58622bbfedb686777173fb3b22397d3495ee.

The live screenshot defect was reproduced through the real setup_themed_app path: the nested group reserved only its inner layout height and omitted themed title/frame chrome. Commit d813d652fc76d90582a20928820d1aa306ab8a91 now reserves the complete widget height-for-width and recalculates after style/font changes.

Verification on this head:

• Live standalone window at 1296 x 759: all Ball Setup rows contained and 7 px clearance before Contact Policy.
• Complete Rate of Closure Python/PyQt suite: 630 passed (2 documented non-failing warnings).
• Clean-cache pinned mypy 1.13: 64 changed production files passed.
• Ruff check/format and diff checks passed.
• Exact-head CI quality-gate job 92861112620: passed, including lint, format, type check, security audit, and module-size budget.
• Handoff updated with the exact commit and evidence path.

Other protected workflows remain queued on the shared runner pool; the draft/review state remains unchanged and no merge protections have been bypassed.