feat: run configured modeled cargo delivery and phase failures

README.mdmodified+13-3

Changes to README.md

		⋯113 linesShow the 113 lines above this hunk@@ -114,9 +114,19 @@ our existing multirotor sensor, estimator, control and authority loop.
114	114	./buddy cargo:load-bench --scenario link-loss
115	115	```
116	116
117		-Link loss is deliberately unqualified and exits 1. This is a [bounded physics prerequisite](docs/cargo-load.md)
118		-for [#25](https://github.com/stacksjs/drone/issues/25); delivery, physical release, custody and endurance
119		-qualification remain open.
	117	+Link loss in this [bounded load characterization](docs/cargo-load.md) is deliberately unqualified
	118	+and exits 1. Its capability flags remain separate from the modeled delivery mission:
	119	+
	120	+```sh
	121	+./buddy cargo:mission examples/cargo-delivery.json
	122	+./buddy cargo:mission examples/cargo-delivery.json --scenario after-release-host-loss
	123	+```
	124	+
	125	+The [cargo delivery guide](docs/cargo-delivery.md) covers explicit mass/CG, receiver, alternate
	126	+and power declarations, captured release/custody, redundant links and post-release failures.
	127	+Exit 2 retains a configured mission that did not complete a matched delivery and carrier landing.
	128	+Distinct-vehicle fleet handover, electrical/measured endurance and physical/operational
	129	+qualification remain open in [#25](https://github.com/stacksjs/drone/issues/25).
120	130
121	131	## Agriculture sensing
122	132