pilot

# From a site to a field kit Read [the project contract](references/project.md). Start with what the person needs to document and the measurements they can supply. Translate ground-sampling or overlap requirements into camera geometry. Preserve their boundary and approved exclusions. Explain missing inputs in plain language; do not fabricate a georeferenced site, aircraft specifications or flight records. ## Author and revise 1. Read `flight/project.json` and `flight/DESIGN.md`. Distinguish supplied measurements, user decisions and explicit draft assumptions. The agent can create original polygon geometry; the starter orchard is only an example. Importing a GeoJSON file can replace or extend a site. 2. Author named boundary/exclusion layers and takeoff in local east/north meters. Keep the WGS 84 origin and locked geometry stable during targeted edits. Camera sensor width is across a run; sensor height is along it. Line angles are counterclockwise from east. 3. Run `node tools/build.mjs`. `DRONE_DSH_DIR` resolves tools for materialized workspaces. The HTML embeds its runtime; no CDN, map key or cloud service is needed to use or share the planner. 4. Resolve infeasibility explicitly: cadence, narrow geometry, disconnected paths or an inadequate return budget. Do not silently relax requested height, speed, overlap, margin or reserve. 5. Compare directions with the UI when useful. It samples 12 angles in 15-degree steps plus the current direction and repor...