test(spring): [#230] boundary fuzz + round-trip сетка — добить RED-список

[lemone112]

Что

Реализация #230 (springFromPeak/springFromOscillation) влита с PR #280; этот PR добивает недостающие пункты RED-списка issue:

• Boundary fuzz: сетка краёв overshoot M→0/M→1 × timeToPeak 1e-9..1e9 (и period × halfLife) — каждый вход либо конечные валидные параметры, либо MotionParamError; NaN/Infinity в результате невозможны.
• Round-trip через (ω₀, ζ): прямые наблюдаемые (t_peak=π/ωd, overshoot=exp(−ζπ/√(1−ζ²))) восстанавливаются из параметров с точностью 1e-10 на сетке домена.
• Sabotage-proof: мутант знака в L=−ln(mp) краснит 4 теста (диверсия выполнена и откатана).
• Контрольный пример тела issue сверен исполняемо: k=335.7212724332, c=22.9611694937 — точное совпадение.

Уже покрыто ранее (#280): точные биекции без коэрсии, mass-инвариантность, dampingRatio-координата, LM092/LM093 домены, tree-shake субпутя (size-гейт spring 1.63KB OK).

Гейты локально

Тесты 3971 passed; size PASS; typecheck PASS.

Контекст плана

Закрывает узел PHYS-02 трека lab-motion-production.

Rollback

Revert-PR (docs/test-only, поведенческого дрейфа нет).

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your current included review allowance is based on your included PR review attempts over the past 7 days.

Next review available in: 53 minutes

Limit details: You’ve used the included review currently available. Your 105 included PR review attempts over the past 7 days set your current allowance at 1 review per hour.

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits within each organization.

For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 7da03a9e-81ae-46af-96a5-117270ed0019

📥 Commits

Reviewing files that changed from the base of the PR and between 5003f1c and 38b4451.

📒 Files selected for processing (1)

• test/spring-observable-constructors.test.ts

---

_{Comment @coderabbitai help to get the list of available commands.}