also looking at this
fix: resolve source links through native drone docs
#40
56 files
+179
-159
| @@ -18,7 +18,7 @@ | ||
| 18 | 18 | Desktop and phone layouts were visually inspected against the existing operator workspace design. |
| 19 | 19 | - Evidence is owned physics simulation. Physical mission execution, hardware payload dispatch, |
| 20 | 20 | whole-runtime durable restart, terrain following and external driver compilation remain open in |
| 21 | [#10](https://github.com/stacksjs/drone/issues/10). See [the mission guide](https://github.com/stacksjs/drone/blob/main/docs/missions.md). | |
| 21 | [#10](https://github.com/stacksjs/drone/issues/10). See [the mission guide](missions.md). | |
| 22 | 22 | |
| 23 | 23 | ## External-driver protocol software slice |
| 24 | 24 | |
| @@ -65,7 +65,7 @@ | ||
| 65 | 65 | - Physical kill/RC/disarm, board supervisor port, measured HIL failures and recovery controllers |
| 66 | 66 | remain open in [#6](https://github.com/stacksjs/drone/issues/6). Zero modeled thrust is not a |
| 67 | 67 | landing controller. Parachute, rally/emergency landing and redundant links are explicitly deferred |
| 68 | in [the authority contract](https://github.com/stacksjs/drone/blob/main/docs/authority.md). Physical outputs remain inhibited. | |
| 68 | in [the authority contract](authority.md). Physical outputs remain inhibited. | |
| 69 | 69 | |
| 70 | 70 | ## Simulated multirotor control slice |
| 71 | 71 | |
| @@ -200,7 +200,7 @@ are not applicable. Newly authored visible copy uses no em-dash or separator en- | ||
| 200 | 200 | - Firmware flashing, sensor calibration, RC link, actuator outputs or physical airworthiness tests. |
| 201 | 201 | - Authenticated paired GNSS transport or calibrated metric visual-position fusion. |
| 202 | 202 | - Board-validated runtime, estimation/controls and the domain workflows listed in the |
| 203 | [replacement matrix](https://github.com/stacksjs/drone/blob/main/docs/roadmap/feature-coverage.md). They remain planned work. | |
| 203 | [replacement matrix](roadmap/feature-coverage.md). They remain planned work. | |
| 204 | 204 | |
| 205 | 205 | The scaffold warns that feature-stripped defaults differ from the installed full defaults. Build |
| 206 | 206 | output can warn about inherited unused image assets and an unset deployed sitemap domain. No cloud |