feat: add VTOL scenario playback to the mission workspace

docs/index.mdmodified+6-4

Changes to docs/index.md

		⋯50 linesShow the 50 lines above this hunk@@ -51,16 +51,18 @@ profile remains neutral-only. The owned [sensor pipeline](sensors.md),
51	51	journals verified metadata and prepares owned image candidates. Physical board
52	52	installation, persistent boot selection and recovery require separate qualification.
53	53	The [library API](api.md) describes behavior extensions. The
54		-[shared vehicle contract](vehicles.md) covers quadcopter, fixed-wing, ground,
	54	+[shared vehicle contract](vehicles.md) covers quadcopter, fixed-wing, VTOL, ground,
55	55	surface and subsea profiles. [Optional external drivers](drivers.md) have
56	56	[acknowledged protocol services](driver-protocols.md); scripted peers are distinct
57	57	from [firmware SITL](sitl.md) and physical testing.
58	58
59		-The separate [VTOL development guide](vehicles-vtol.md) covers the hover-only command and an
	59	+The separate [VTOL development guide](vehicles-vtol.md) covers the hover-only and full-route commands,
	60	+named fault/operator scenarios, and an
60	61	experimental TypeScript library profile for modeled front transition, cruise, back transition and
61	62	vertical landing, with stable-phase pause/resume and explicitly declared hover-and-land recovery
62		-routes. Complete recovery/abort envelopes, hybrid energy qualification and the common VTOL mission
63		-workspace remain open.
	63	+routes. The common `/missions` workspace selects the same named cases and displays captured mode
	64	+observations and optional battery readings. Complete recovery/abort envelopes and measured hybrid
	65	+energy qualification remain open.
64	66
65	67	## Explore a workflow
66	68