Summary
The docs introduction still listed persistent trust as future work, and the Pi setup sequence made an ArduPilot installation look mandatory. Name the shipped enrolled trust, verified metadata journal and owned candidate preparation, then give owned runtime development its own path before optional receive-only flight-controller telemetry.
- persistent trust is future work; continue Pi setup by installing ArduPilot
+ enrolled trust and owned candidates are available; develop our runtime or choose optional telemetryPhysical board installation, camera acquisition and boot recovery retain their separate qualification gates.
Evidence
- Before: the introduction contradicted main's update implementation; the Pi steps did not identify the optional driver boundary.
- After: the combined local docs worktree builds; its 87 rendered pages and 6,354 local links have no missing targets or fragments. This local rendered set also includes unpublished host-slot documentation. The clean PR head separately passes its native documentation build in CI. Open Farming also passes 50 live routes, 11 live assets and 55 rebuilt documentation pages.
- Buddy lint, application/runtime type checks, roadmap and parity structure checks pass. Parity remains incomplete. Adjacent current runtime suite: 149 tests, 0 failures.
- These two commits change only
docs/index.mdanddocs/raspberry-pi.md; the unpublished host-slot implementation is outside this PR. Exact-head CI 39702949709 passes all five jobs. Published both documentation commits to origin/main by normal fast-forward as Chris, without coauthors. The host-slot implementation is not part of this publication.
Merge Danger
Door: two-way. Revert the documentation edits.
Blast Radius: documentation.