also looking at this
fix: resolve source links through native drone docs
#40
56 files
+179
-159
| @@ -5,7 +5,7 @@ The private `createNavigationOccurrenceSession` in | ||
| 5 | 5 | `contact` is also selected. Profiles are `nominal`, `no-current`, `current-stuck`, |
| 6 | 6 | `stuck-relay`, `feedback-loss`, `feedback-replay` and `mains-loss`. Issue #24 remains open |
| 7 | 7 | for production scheduling, runtime recovery, a full weather system and physical qualification. |
| 8 | The separate [authenticated review ledger](https://github.com/stacksjs/drone/blob/main/docs/patrol-review.md) persists owner-only intent and | |
| 8 | The separate [authenticated review ledger](patrol-review.md) persists owner-only intent and | |
| 9 | 9 | review metadata without granting charge or launch authority. This experiment has no charger hardware transport. |
| 10 | 10 | |
| 11 | 11 | Only the charge-enabled adapter exposes `requestCharge()` and `stopCharge()`. A request is |
| @@ -96,5 +96,5 @@ orders, finite capacity and exact refusal behavior. Seven full legacy navigation | ||
| 96 | 96 | remain byte-identical. Physical charging, unattended operation, HIL and endurance evidence |
| 97 | 97 | are outside this modeled checkpoint. |
| 98 | 98 | |
| 99 | A separate [finite recurrence ledger](https://github.com/stacksjs/drone/blob/main/docs/patrol-recurrence.md) records due slots and explicit | |
| 99 | A separate [finite recurrence ledger](patrol-recurrence.md) records due slots and explicit | |
| 100 | 100 | local reviews. Neither due slots nor flight reviews supply charge approval. |