Pull request #82 · stacks/drone

Summary

Expose the existing owned VTOL nominal front/cruise/back/vertical-landing route through native vtol:simulate. Buddy discovers the typed command; the standalone binary registers the same definition. Existing vtol:hover behavior and all physics, controls, reserve and authority logic remain unchanged.

vtol:simulate [--seconds 160] [--electrical]
  existing experimental transition profile and shared runtime
  qualified initial hover -> cruise -> back hover
  contact-gated landing and neutral output lease

The condensed JSON retains the actual status, mission, navigation, authority, board and optional energy observation. Exit 0 requires all ordered mode confirmations, estimated flight, modeled landing contact, completed landing without a runtime fault, neutral outputs and no active lease. Partial routes retain their evidence and exit 1. README and guides distinguish nominal CLI access from library-only fault/operator/recovery scenarios and the absent workspace selection.

Evidence

Before: Actual native command test failed because vtol:simulate did not exist. After: Nominal and electrical routes complete; short duration preserves duration-exhausted, and invalid duration refuses before a report.
Native Buddy/Pickier, application/runtime types, 151 VTOL tests / 9,401 assertions across nine files, 90-page docs, roadmap/parity and official compiled CLI build pass on unchanged functional inputs.
Copied standalone binary outside the checkout exactly matches Buddy reports and exits for nominal, electrical, short and invalid cases. Three existing hover outputs are byte-identical to the actual parent compiled binary: default, electrical and host-loss.
Both independent review axes passed. The final roadmap wording correction passed native lint and docs again; functional/compiler inputs are unchanged. Two parsed-YAML assertions preserve outside-checkout ownership for the new commands; removing their whole step blocks restores the parent workflow exactly.
Exact full Linux qualification passed all five jobs: 1,717 passes, 41 skips, zero failures, 499,425 assertions across 210 files. All four hover reports and both full-route reports qualify; nominal and electrical routes retain all three ordered mode confirmations, estimated flight, landing contact and neutral output. Original single log archive verified without refetch. No full macOS pass is claimed.
Published cd66516f732cf91b14b9a6d320bcc6bc2b835b2b to main using a normal fast-forward as Chris, without coauthors. The automatic main publication CI is separate. Parent electrical #81 was independently qualified and published first.

Merge Danger

Door: Two-way. Additive simulation CLI, no schema or physical endpoint change.

Blast Radius: Simulation. This exposes only the nominal fictional transition route. CLI fault/operator/recovery selection, common workspace integration, fresh-process recovery, broader wind/envelope campaigns, measured cell/motor models and board/HIL/physical qualification remain open in #12. No full VTOL, measured endurance or autopilot parity claim.