ReviewOS

also looking at this

stacks/drone

fix: resolve source links through native drone docs

#40
Merged chris wants to merge codex/native-doc-links into main
56 files +179 -159
docs/hardware.mdmodified+4-4
Changes to docs/hardware.md
@@ -9,8 +9,8 @@ Do not buy a second Pi. These are off-the-shelf hardware parts assembled at home
99
1010For your own runtime, start with the Pi accessories and AI Camera below, then this separate
1111Pico 2 bench kit. The firmware currently produces neutral diagnostic outputs. The
12[runtime guide](https://github.com/stacksjs/drone/blob/main/docs/runtime.md) defines its wiring and measurements; add the
13[sensor profile](https://github.com/stacksjs/drone/blob/main/docs/sensors.md) as a later bench stage. No airframe or external autopilot firmware
12[runtime guide](runtime.md) defines its wiring and measurements; add the
13[sensor profile](sensors.md) as a later bench stage. No airframe or external autopilot firmware
1414is needed to begin that work.
1515
1616Bench prices checked October 20, 2026. These are additional to the airframe table, before tax,
@@ -32,7 +32,7 @@ possible to preserve the aircraft budget.
3232
3333For the later sensor stage, the implemented profile requires an **ICM-42688-P SPI breakout**,
3434**BMP280 at I2C address 0x76**, and **u-blox M10-class UART NAV-PVT**. Match the exact part,
35exposed signals and voltage to the [sensor bench guide](https://github.com/stacksjs/drone/blob/main/docs/sensors.md). The
35exposed signals and voltage to the [sensor bench guide](sensors.md). The
3636[Adafruit BMP280, product 2651](https://www.adafruit.com/product/2651) lists at $9.95.
3737Use its [pinout guide](https://learn.adafruit.com/adafruit-bmp280-barometric-pressure-plus-temperature-sensor-breakout/pinouts)
3838for breakout connections. [Bosch's datasheet, section 5.2](https://www.bosch-sensortec.com/media/boschsensortec/downloads/datasheets/bst-bmp280-ds001.pdf#page=28)
@@ -57,7 +57,7 @@ local quadcopter SITL; physical telemetry is receive-only and physical flight co
5757Choose flight-controller firmware independently of the owned mission and camera logic. No firmware
5858flash or physical-flight qualification follows from this shopping list.
5959
60The separate [owned board runtime](https://github.com/stacksjs/drone/blob/main/docs/runtime.md) uses a Pico 2 for bench development. Pixhawk 6C flight
60The separate [owned board runtime](runtime.md) uses a Pico 2 for bench development. Pixhawk 6C flight
6161firmware, physical control and measured aircraft validation remain separate roadmap work. Keep the
6262Pi 5 for Stacks mission and camera logic.
6363