docs: clarify runtime status and the owned Pi setup path

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/index.mdmodified+3-2

Changes to docs/index.md

		⋯46 linesShow the 46 lines above this hunk@@ -47,8 +47,9 @@ profile remains neutral-only. The owned [sensor pipeline](sensors.md),
47	47	[navigation](navigation.md) have separate simulation and hardware acceptance gates.
48	48
49	49	[Diagnostics and replay](diagnostics.md) retain explicit loss and provenance.
50		-[Runtime trust and image staging](runtime-updates.md) preserves initial trust and authenticates offline candidates;
51		-persistent trust, boot selection and rollback remain required before installation.
	50	+[Runtime trust and image staging](runtime-updates.md) preserves enrolled trust,
	51	+journals verified metadata and prepares owned image candidates. Physical board
	52	+installation, persistent boot selection and recovery require separate qualification.
52	53	The [library API](api.md) describes behavior extensions. The
53	54	[shared vehicle contract](vehicles.md) covers quadcopter, fixed-wing, ground,
54	55	surface and subsea profiles. [Optional external drivers](drivers.md) have