also looking at this
fix: resolve source links through native drone docs
#40
56 files
+179
-159
| @@ -18,8 +18,8 @@ charging at 47 seconds, then reviews the second flight at 60 seconds. The fixed | ||
| 18 | 18 | is 2026-01-01T00:00:00.000Z. These are unsigned synthetic decisions, without authenticated |
| 19 | 19 | operator identity. The nominal model completes flights at 44.120 and 102.120 seconds, |
| 20 | 20 | verifies their own selected-pad contact, and proves modeled charge isolation at 55.400 seconds. |
| 21 | See the [recurrence](https://github.com/stacksjs/drone/blob/main/docs/patrol-recurrence.md), [contact](https://github.com/stacksjs/drone/blob/main/docs/patrol-contact.md) and | |
| 22 | [partial-charge](https://github.com/stacksjs/drone/blob/main/docs/patrol-charge.md) contracts for their fixed models and limits. | |
| 21 | See the [recurrence](patrol-recurrence.md), [contact](patrol-contact.md) and | |
| 22 | [partial-charge](patrol-charge.md) contracts for their fixed models and limits. | |
| 23 | 23 | |
| 24 | 24 | ## Decisions and native options |
| 25 | 25 | |
| @@ -65,7 +65,7 @@ It includes each decision's fulfillment, its own historical mission/contact evid | ||
| 65 | 65 | verification and measured modeled isolation, separate true and credited energy, host freshness |
| 66 | 66 | and actual request/acceptance counters. Optional `--output <directory>` publishes the same |
| 67 | 67 | summary with normalized input and a completion manifest before printing it. The directory must |
| 68 | not already exist. See the [recording and replay contract](https://github.com/stacksjs/drone/blob/main/docs/patrol-recording.md) for bounds, | |
| 68 | not already exist. See the [recording and replay contract](patrol-recording.md) for bounds, | |
| 69 | 69 | fresh replay consent and publication failure behavior. The command does not dump traces. |
| 70 | 70 | |
| 71 | 71 | `neutral-preview`, `reviewed-denials` and `completed` exit successfully. Any unfulfilled explicit |
| @@ -74,7 +74,7 @@ flight must actually complete with its own verified contact; approved charging m | ||
| 74 | 74 | isolate its own episode. A queued request or final relay-off value alone cannot establish success. |
| 75 | 75 | The retained model continues to the horizon without a fabricated final stop or revoke. |
| 76 | 76 | |
| 77 | The separate [authenticated review ledger](https://github.com/stacksjs/drone/blob/main/docs/patrol-review.md) persists owner-only intent, | |
| 77 | The separate [authenticated review ledger](patrol-review.md) persists owner-only intent, | |
| 78 | 78 | decisions and consumption metadata without invoking this command or handing off to a runtime. |
| 79 | 79 | Issue #24 remains open for a patrol workspace, production scheduling, runtime recovery, broader |
| 80 | 80 | weather behavior and physical qualification. This command adds no physical transport, unattended |