fix: stabilize VTOL lateral flow and hover control

Review threads live on the whole diff, not on one commit, so none are shown here - a thread's line means something in the branch's final form, and painting it into an intermediate step would put it on code it is not about.

docs/vehicles-vtol.mdmodified+4-2

Changes to docs/vehicles-vtol.md

		⋯433 linesShow the 433 lines above this hunk@@ -434,8 +434,10 @@ reconstruct the electrical plant from a mission trace alone.
434	434
435	435	Actual model campaigns cover combined front demand, all nominal phases, open-circuit pusher timeout, initial/front/back abort
436	436	landing, held recovery/resume, global endurance during pause, supply cutoff, bad battery observations,
437		-reserve, host loss and independent sessions. The nominal example's front peak is 347.313 W; its
438		-last captured use is about 4.62 Wh. Neither value predicts aircraft endurance. Motor/propeller advance
	437	+reserve, host loss and independent sessions. With `projected-incidence-v3`,
	438	+`./buddy vtol:simulate --scenario nominal --electrical` reports a last captured use of 4.238631 Wh
	439	+at `capturedAtMs: 75680` in the retained native campaign. This fictional example does not predict
	440	+aircraft endurance. Motor/propeller advance
439	441	ratio, voltage-dependent thrust, cell temperature/degradation, current-sensor calibration and measured
440	442	capacity remain unmodeled or unqualified. The open-circuit fixture removes pusher demand and thrust;
441	443	it does not model a seized motor's electrical current.