feat: expose owned VTOL transition simulation through native CLI

docs/vehicles.mdmodified+4-3

Changes to docs/vehicles.md

		⋯60 linesShow the 60 lines above this hunk@@ -61,11 +61,12 @@ recompute mission replay, reject altered traces and exercise payload uncertainty
61	61	All evidence is owned physics simulation. The Pico neutral-only board image does not run these
62	62	TypeScript controllers. Native board execution, external firmware SITL, HIL and measured physical
63	63	vehicle acceptance remain separate gates. A separate [VTOL development guide](vehicles-vtol.md)
64		-covers the hover-only command and an experimental lift-and-cruise library profile. The latter
	64	+covers the hover-only command and an experimental lift-and-cruise library profile with a native
	65	+`vtol:simulate` nominal-route command. The latter
65	66	executes a bounded modeled front/cruise/back/vertical-landing route with stable-phase pause and
66	67	resume, plus explicitly declared hover-and-land transition recovery. Complete recovery/abort
67		-envelopes, hybrid energy qualification,
68		-a native transition command and a VTOL selection in the common workspace remain open. Helicopter,
	68	+envelopes, measured hybrid energy qualification,
	69	+CLI fault/operator scenarios and a VTOL selection in the common workspace remain open. Helicopter,
69	70	soaring, blimp and other airframe families remain explicit roadmap work.
70	71
71	72	Read [air](vehicles-air.md), [ground](vehicles-ground.md), [surface](vehicles-surface.md), [subsea](vehicles-subsea.md),