feat(rate-of-closure): adapt wind trials to scalar ensembles

[d-sorgcodexagent]

Outcome

Adds the first UI-neutral #4199 integration slice without changing the existing flight physics:

• exact Python/React scalar-ensemble/v1 wire contract;
• structured provenance, labeled stages/categories/cohorts, unit-bearing variables, RFC3986 composite row IDs, immutable nullable trials, and exact scatter availability;
• pure wind-strategy adapters retaining completed, nonconverged, and invalid outcomes;
• true/estimated wind, launch/aim, target, actual/perfect-information landing, miss, cost, and information-delta scalars;
• fail-closed request/analysis agreement and deterministic scenario-provenance validation;
• explicit test that React adaptation never calls the flight integrator.

This does not complete #4199. Background execution, cancellation/progress, client workflow, strategy/scatter views, persistence, and export wiring remain follow-up work.

Ground and parity tracking

Revalidates existing epics #4267 and #4260 rather than creating duplicates. Exact reuse, physical prerequisite, product-identity, and acceptance refinements are recorded in their 2026-08-07 comments and both Rate handoffs.

Verification

• Python/PyQt/shared swing: 906 passed, 1 expected optional-Rust skip, 15 existing warnings
• React: 91 files / 555 tests passed
• Ruff check + format, Black, focused mypy: pass
• TypeScript and zero-warning ESLint: pass
• Vite production build: pass (166 modules)
• git diff --check: pass
• production Python files <400 lines; changed functions <=50 lines

Refs #4199
Refs #4144
Refs #4260
Refs #4267

[github-actions]

⚠️ SPEC.md Update Required

Source files were modified in this PR but SPEC.md was not updated.

Per the Specification-Driven Development Policy:

• Any PR that adds, removes, or changes functionality must update SPEC.md
• Update the relevant sections (features, architecture, tests, dependencies, etc.)
• Bump the Spec Version if making substantive changes

To resolve:

1. Update SPEC.md to reflect your changes, OR
2. Add the spec-exempt label if this PR genuinely doesn't affect the spec (e.g., pure refactor with no behavior change)

This check is enforced by the spec-check CI workflow.