also looking at this
fix: resolve source links through native drone docs
#40
56 files
+179
-159
| @@ -53,10 +53,10 @@ wrong-pad identity, genuine stale feedback at call versus arm, regressed origina | ||
| 53 | 53 | pending and verified host silence, exact switch edges, and a blocked contact-enabled flight. |
| 54 | 54 | Legacy seven-scenario result bytes remain unchanged. The contact-only experiment keeps an |
| 55 | 55 | unmeasured nominal hover-load proxy without recharge credit. A separate optional |
| 56 | [partial-charge model](https://github.com/stacksjs/drone/blob/main/docs/patrol-charge.md) adds explicit permission, instrument verification | |
| 57 | and isolation. The separate [authenticated review ledger](https://github.com/stacksjs/drone/blob/main/docs/patrol-review.md) persists | |
| 56 | [partial-charge model](patrol-charge.md) adds explicit permission, instrument verification | |
| 57 | and isolation. The separate [authenticated review ledger](patrol-review.md) persists | |
| 58 | 58 | owner-only intent and review metadata without launch or charging authority. Measured |
| 59 | 59 | hardware current, a full weather system, production scheduling, runtime handoff/recovery, |
| 60 | 60 | a patrol workspace and physical docking remain open. |
| 61 | The [finite patrol command](https://github.com/stacksjs/drone/blob/main/docs/patrol-cli.md) composes this modeled contact verifier with | |
| 61 | The [finite patrol command](patrol-cli.md) composes this modeled contact verifier with | |
| 62 | 62 | explicit unsigned decisions; it adds no physical contact evidence. |