Qualify route gain and observe native gate context through ordinary input

docs/aircraft-route.md

@@ -1,6 +1,6 @@
 # Experimental two-pad aircraft route
 
-The isolated twenty-metre route now has a successful native mechanism run: the [155909 archive](evidence/native-2026-09-19-155909-aircraft-route/report.json) records **38 passing assertions, one completion and zero script/runtime or engine errors** against its captured 192-file addon source snapshot. It reached the immutable destination, held position, landed with actual contact and shut down the original aircraft. This is **not operational HQ dispatch**, a general route capability or multiplayer acceptance. The earlier ninety-second timeout remains archived; the successful run uses the bounded 160-second translation stage within the unchanged 240-second overall lease. Earlier normal, cancellation and four-metre translation archives retain their separate scopes.
+The isolated twenty-metre route has successful baseline and route-gain native mechanism runs. The [192238 gain run](evidence/native-2026-09-19-192238-aircraft-route-gain/report.json) also passed 38 assertions with one completion and zero errors; its measured comparison and single-run limits appear below. For the earlier baseline, the [155909 archive](evidence/native-2026-09-19-155909-aircraft-route/report.json) records **38 passing assertions, one completion and zero script/runtime or engine errors** against its captured 192-file addon source snapshot. It reached the immutable destination, held position, landed with actual contact and shut down the original aircraft. This is **not operational HQ dispatch**, a general route capability or multiplayer acceptance. The earlier ninety-second timeout remains archived; the successful run uses the bounded 160-second translation stage within the unchanged 240-second overall lease. Earlier normal, cancellation and four-metre translation archives retain their separate scopes.
 
 ## Bound and ownership
 
@@ -16,7 +16,7 @@ The allocating owner must retain it and call the existing exact-actor `PrepareAc
 
 ## Flight and cancellation
 
-The native startup and five-second hover sequence is preserved. The route then uses the already proven native autohover/capped 0.03 actor-local cyclic demand and 0.5m/s requested horizontal speed toward its fixed endpoint. Movement and settling now have an experimental 160-second stage bound, clamped to the unchanged absolute overall maximum of 240 seconds. The first ninety-second attempt timed out; the 160-second stage completed in the isolated 155909 run. That result does not establish timing reliability on other routes or workloads. The destination must be held within 0.75 metres, below 0.25m/s horizontal speed and within the original hover constraints for five continuous seconds.
+The native startup and five-second hover sequence is preserved. The route uses native autohover, a 0.03 actor-local cyclic magnitude cap and 0.5m/s requested horizontal speed toward its fixed endpoint. The archived run used velocity-error gain 0.05; the current candidate uses route-only gain 0.10 while translating, with the isolated [192238 native comparison](evidence/native-2026-09-19-192238-aircraft-route-gain/report.json) now passed; its limits are detailed below. Landing and the original short-translation controller retain gain 0.05. Movement and settling now have an experimental 160-second stage bound, clamped to the unchanged absolute overall maximum of 240 seconds. The first ninety-second attempt timed out; the 160-second stage completed in the isolated 155909 run. That result does not establish timing reliability on other routes or workloads. The destination must be held within 0.75 metres, below 0.25m/s horizontal speed and within the original hover constraints for five continuous seconds.
 
 Unlike the original radial-eight-metre mode, the separate route mode limits the aircraft origin to less than eight metres from the **fixed, endpoint-clamped segment**, including its endpoint caps. The pre-translation stages retain the original start-pad eight-metre radius. Relative height remains -3 through 18 metres, with uprightness at least 0.85; both native input callbacks and Tick enforce this envelope and the original deadlines. The original home is never rebased to manufacture progress.
 
@@ -47,3 +47,31 @@ The follow-up changes only the route stage bound to `Math.Min(originalDeadline,
 The timeout run's recorded final twenty seconds gained approximately 2.56 metres in radial distance over 20.2 seconds, while reported physical speed was approximately 0.15–0.18m/s. From 8.14 metres remaining, reaching the 0.75-metre acceptance radius at roughly 0.13m/s plus a five-second hold would need about another 62 seconds, before extra proportional braking near the endpoint. Thus 150 seconds would be marginal; 160 seconds leaves only a small route margin. The observed approximately 45-second startup/hover plus a full 160-second leg and an estimated 25-second landing totals approximately 230 seconds, only ten seconds below the unchanged absolute lease. This was the pre-run timing estimate, not the later landing evidence. Further slowdown or longer startup may still legitimately fail; the source does not extend or renew that lease to make the fixture pass.
 
 The [155909 console](evidence/native-2026-09-19-155909-aircraft-route/console.log.txt) records a requested distance of 20.2214 metres from the actual post-hover origin. The destination hold completed at 0.546151 metres error after 2,716 translation updates. Final physical displacement was 20.1261 metres with 0.129942 metres target error. The controller reached COMPLETE with one initial wake, one engine start, one controller start and the original pilot/seat; native assertions required ground contact, engine off and finite fuel consumption. The [runner record](evidence/native-2026-09-19-155909-aircraft-route/runner.json.txt) retains `smoke-completed` and unchanged source across the run. These observations qualify this one newly authored experimental leg only. They do not establish radio-authorized HQ routing, transport loading, repeated sorties, dynamic obstacle avoidance, remote ownership or human piloting.
+
+## Route-only gain candidate and native comparison
+
+The captured 155909 source remains the accepted baseline, not evidence for this candidate. In that console, translation began at approximately native time 58,559ms and the destination hold completed at 213,917ms: approximately 155.36 seconds of the 160-second stage. The first logged sample within two metres was at 195,709ms, so approximately 137.15 seconds were spent reaching the final two metres. Across sixty cruise samples with more than two metres remaining, progress along the fixed segment was 15.6404 metres over 119.4608 seconds (0.131m/s). Computed demand magnitude never exceeded 0.01919, below the existing 0.03 cap. Thus the five-second hold was not the principal delay. Native simulator velocity and finite-difference position progress are separate observations; these figures use the logged world positions and clock.
+
+The candidate changes only TRANSLATING velocity-error gain from 0.05 to 0.10 through `ERR_AircraftRouteRules.Demand`. Desired velocity remains horizontal `error * 0.25`, capped at 0.5m/s; demand remains capped at magnitude 0.03. Landing—including cancellation descent—uses the unchanged shared demand. The read-only fixture diagnostic selects the same equation as the controller. No deadline, terrain/obstacle qualification, speed/arrival criterion, input ownership, rotor proof or native asset is changed. The single native comparison below demonstrates faster completion in that run, not repeatable stability across conditions; the exposed native autohover API does not document its internal response law.
+
+The [192238 run](evidence/native-2026-09-19-192238-aircraft-route-gain/console.log.txt) repeated the existing twenty-metre native route and passed 38 assertions, one completion and zero recorded script/runtime or engine errors. It preserves the original hold, physical landing and shutdown criteria. Preserve any failed run and its original errors. The existing cancellation regression must still preserve the captured landing point, original lease and shared landing gain. Longer field routes and HQ dispatch remain unimplemented; changing this gain does not qualify either.
+
+`python tests/test_aircraft_route_demand.py` executes the actual demand methods and route native-control callback with fake native boundaries. It checks horizontal speed/magnitude caps, opposing-velocity braking, zero vertical output, TRANSLATING-only selection, unchanged landing demand after cancellation and grounded zero cyclic. These are source-local policy checks, not native flight evidence.
+
+### Measured 155909 → 192238 comparison
+
+The [machine-readable comparison](evidence/route-comparison-2026-09-19-192238/comparison.json) records exact input archive paths, every archive file hash, console/launch/end-manifest binding checks, source-snapshot differences, console event lines and calculation methods. It adds no acceptance verdict beyond the original archived reports.
+
+| Measurement | Baseline gain 0.05 | Route gain 0.10 |
+|---|---:|---:|
+| Translation start → completed destination hold |155.365s|69.293s|
+| Sampled cruise progress along the fixed route |0.131m/s|0.322m/s|
+| Translation start → successful shutdown/result |170.542s|84.984s|
+| Completed hold → first logged ground contact |12.150s|11.640s|
+| Completed hold → COMPLETE |15.177s|15.691s|
+| Error at completed hold |0.546m|0.398m|
+| Final target error |0.130m|0.099m|
+
+The measured translation duration decreased by 55.4% (86.072 seconds), while cruise progress increased by 2.46 times. Landing duration remained approximately unchanged. The candidate's recorded translation height stayed 7.996–8.024 metres; maximum sampled cross-track distance was 3.044 metres, including the initial post-hover offset. No endpoint crossing appears in the two-second telemetry: the largest logged along-route position during translation/landing was 19.912 metres for the nominal 20 metre endpoint. This is sampled evidence, not proof of zero inter-sample oscillation. Both native runs completed on the original aircraft/pilot with actual contact, engine off and finite fuel consumption.
+
+These are one run per gain, not a matched-load performance/FPS benchmark. Initial requested distances differed slightly (20.2214 m versus 20.2311 m), and the complete source snapshots contain 192 versus 195 files with nine differing paths recorded in the comparison. The baseline used gain 0.05 and the candidate route uses 0.10; the unchanged shared flight controller hash is retained in both source manifests. The result supports this isolated candidate mechanism only. It does not establish repeatability, longer terrain routes, operational HQ dispatch, multiplayer/remote ownership or cancellation under the new gain. No qualification, deadline or arrival requirement was widened for this comparison.