re(flight): short bursts confirm the rate-vs-speed SHAPE, without needing the clock

The design the sweep could not provide: settle the throttle, measure the settled
speed, pitch for ONE second so speed barely moves inside the burst. Three
throttles, two repeats, row pin CONFIDENT, fresh flight.

    LT min      burst speed ~105    rate 113.6, 109.5 deg/wall-s
    cruise                  ~383         100.2,  88.4
    RT max                 ~1483          52.2,  70.5

Rate falls monotonically with speed -- 111.5 -> 94.3 -> 61.4 -- at three KNOWN,
SETTLED speeds instead of smeared across a bleeding one.

The decisive comparison needs no clock. Absolute rates depend on the run's clock
ratio, but the min:max RATIO cancels it:

    measured min:max            = 1.82
    AV_PitchMinus_Min/Max 75/40 = 1.88   ->  3.0% apart
    AV_PitchPlus_Min/Max 150/70 = 2.14   -> 15.1% apart

Two conclusions, neither resting on a clock measurement:
 - _Min/_Max really do mean "at minimum / at maximum speed", with the rate
   interpolating between them: shape confirmed to 3%.
 - ly+ drives pitch-MINUS, not plus. The craft has asymmetric pitch authority
   (75/40 down vs 150/70 up) and the ratio picks the pair cleanly.

Absolute magnitudes remain open: this run did not bracket the HUD clock, so
deg/GAME-second cannot be computed from it, and picking a ratio that makes the
numbers fit would be circular. The probe now screenshots the clock at both ends.

Also: fly_stage.sh now waits for the TAKE-OFF load too. Guarding only the stage
load left a run pressing A into a black screen and then reporting "player entity
not found" from a game that never reached flight.

docs/re/captures/pitch-burst-settled-speeds.csv

@@ -0,0 +1,7 @@
+throttle,rep,settled_speed,burst_speed,rate_deg_per_wall_s
+min,0,121.3,102.6,113.64
+min,1,152.0,108.8,109.46
+cruise,0,428.5,374.7,100.19
+cruise,1,361.6,391.4,88.39
+max,0,1564.4,1352.0,52.22
+max,1,1249.3,1614.6,70.52

docs/re/flight-speed-law.md

@@ -620,3 +620,41 @@ inside a 1 s burst, so each burst yields one honest `(speed, rate)` point. Repea
 `LT` / neutral / `RT` for three clean points at known speeds, instead of one smeared
 sweep. Data:
 [`captures/pitch-rate-curve-clean.csv`](captures/pitch-rate-curve-clean.csv).
+
+
+## ✅ Short bursts at settled speeds: the law's SHAPE is confirmed, clock-free
+
+The design the sweep could not provide: settle the throttle, measure the settled
+speed, then pitch for **one second** so the speed barely moves inside the burst.
+Three throttle settings, two repeats each, row pin **CONFIDENT**, fresh flight.
+
+| throttle | burst speed (wall) | rate (°/wall-s) |
+|---|---|---|
+| `LT` min | ~105 | 113.6, 109.5 |
+| none, cruise | ~383 | 100.2, 88.4 |
+| `RT` max | ~1 483 | 52.2, 70.5 |
+
+**Rate falls monotonically with speed** — 111.5 → 94.3 → 61.4 — measured at three
+*known, settled* speeds rather than smeared across a bleeding one.
+
+**And the decisive comparison needs no clock at all.** Absolute rates depend on the
+run's clock ratio, but the **min:max ratio cancels it**:
+
+```
+measured min:max            = 1.82
+AV_PitchMinus_Min/Max 75/40 = 1.88   ->  3.0 % apart
+AV_PitchPlus_Min/Max 150/70 = 2.14   -> 15.1 % apart
+```
+
+So two things follow, neither resting on a clock measurement:
+
+1. **`_Min` / `_Max` really do mean "at minimum / at maximum speed"**, with the rate
+   interpolating between them — the shape is confirmed to 3 %.
+2. **`ly+` drives pitch-MINUS**, not pitch-plus. The craft has asymmetric pitch
+   authority (75/40 down versus 150/70 up), and the ratio picks the pair cleanly.
+
+🟡 **Absolute magnitudes are still open** — this run did not bracket the HUD clock, so
+deg/*game*-second cannot be computed from it, and choosing a ratio that makes the
+numbers fit would be circular. The probe now takes clock screenshots at both ends so
+the next run closes it. Data:
+[`captures/pitch-burst-settled-speeds.csv`](captures/pitch-burst-settled-speeds.csv).