also looking at this
fix: resolve source links through native drone docs
#40
56 files
+179
-159
| @@ -12,7 +12,7 @@ sensor-to-neutral-output bench target, with no arming, PWM, flight modes or actu | ||
| 12 | 12 | - `app/Commands/Runtime*.ts`: native `defineCommand()` commands, automatically discovered by Buddy. |
| 13 | 13 | - `bin/drone.ts`: the same Stacks command definitions in a standalone CLI. No separate argument parser. |
| 14 | 14 | |
| 15 | The [language and board decision](https://github.com/stacksjs/drone/blob/main/docs/adr/0002-bench-runtime.md) records the firmware exception. | |
| 15 | The [language and board decision](adr/0002-bench-runtime.md) records the firmware exception. | |
| 16 | 16 | The Pico 2 is an additional development board, not the existing Pi 5 and not yet an approved |
| 17 | 17 | flight controller. Existing ArduPilot and PX4 drivers continue independently. This bench protocol |
| 18 | 18 | cannot be adapted into flight `Telemetry` from a synthetic scalar; flight integration needs real |
| @@ -137,7 +137,7 @@ The watchdog is refreshed only after a healthy completed tick. Deadline/clock fa | ||
| 137 | 137 | reset and stop watchdog feeding. Invalid frames revoke diagnostic authority but keep sampling neutral. |
| 138 | 138 | |
| 139 | 139 | Boot/session identity, freshness, version mismatch, sequence exhaustion, lease expiry and invalid |
| 140 | capabilities are described in the [protocol specification](https://github.com/stacksjs/drone/blob/main/docs/runtime-protocol.md). There is no crypto | |
| 140 | capabilities are described in the [protocol specification](runtime-protocol.md). There is no crypto | |
| 141 | 141 | authentication: local UART is a trusted bench boundary. Network transport and physical flight authority |
| 142 | 142 | remain separate work. A diagnostic lease never changes GP15 from neutral. |
| 143 | 143 | |
| @@ -149,9 +149,9 @@ remain separate work. A diagnostic lease never changes GP15 from neutral. | ||
| 149 | 149 | - Board boot, UART capture, deadline timing, stack high-water and watchdog reset: **not measured**. |
| 150 | 150 | Issue #2 remains open for those acceptance gates. No physical flight capability is claimed. |
| 151 | 151 | |
| 152 | The [validation record](https://github.com/stacksjs/drone/blob/main/docs/validation.md) tracks the complete release checks, and the | |
| 152 | The [validation record](validation.md) tracks the complete release checks, and the | |
| 153 | 153 | [historical runtime build evidence snapshot](https://github.com/stacksjs/drone/blob/main/docs/runtime-evidence.json) records artifact hashes and static footprint. Add real bench captures, |
| 154 | 154 | logic-analyser measurements, exact board revision and stack/watchdog results before closing #2. |
| 155 | 155 | |
| 156 | The optional [sensor bench profile](https://github.com/stacksjs/drone/blob/main/docs/sensors.md) adds bounded IMU, barometer and GNSS acquisition. | |
| 156 | The optional [sensor bench profile](sensors.md) adds bounded IMU, barometer and GNSS acquisition. | |
| 157 | 157 | Its larger footprint must be checked separately from the historical synthetic-only snapshot. |