test(rtx-fsi): closure schedule by tip speed (CRESCUE_SPEED=<f>), default off

Route 1 of omni-cortex docs/coupling_rescue_campaign.md §12, registered in docs/closure_scheduling_campaign.md: whenever the last committed tip jump exceeds f x its trailing-2000 peak, open a coarse episode (the s=2 interpolated closure, CRESCUE_COARSE=<M> steps, re-evaluated at each end) BEFORE the step — preventive, because the s=1 closure incubates the crossing instability inside the healthy envelope and no signature-triggered rescue acts early enough (rungs A, C, A' refuted). Speed episodes are expected twice per period: not counted against the runaway-episode cap; the coarse fraction is printed at the end of the march. Verified: FSI2 committed default digit-identical knob-off vs the same-day baseline; fmt + clippy clean. Co-Authored-By: Claude Fable 5.1 <[email protected]> Claude-Session: https://claude.ai/code/session_01X2GmJXeQ2njUecEKiJZ1G2
2026-09-03 09:57:40 -07:00
parent b66f73aeef
commit 19d8307ae4
3 changed files with 65 additions and 1 deletions
@@ -137,6 +137,7 @@ fn fsi3_added_mass_flag() {
            coarse_episode: 0,
            inc_trace: None,
            increment_factor: 0.0,
+            speed_fraction: 0.0,
            // Continuous interface velocity across step boundaries: the
            // constant-velocity closure's jump at each step start drew an
            // impulsive added-mass load the unit-ratio flag could not