Retain aircraft through native landing and qualify bounded input diagnostics

docs/prison-approach-reliability.md

@@ -98,3 +98,25 @@ reserve, enlarge the target or extend the lifetime. Any future shorter-pulse
 strategy needs its own measured conservative stopping bound before it can safely
 address that remaining limitation. No such bound or improved runtime outcome is
 claimed here.
+
+
+## Implemented timing candidate, not yet native-qualified
+
+The candidate now performs the same full ownership guard immediately after W-down.
+If it finishes before50ms, the policy waits only the remaining time and then
+performs another full guard. W-up follows the latest successful full guard; no
+cached authority authorizes a later release. Bounded `release_timings` records
+retain guard entry/return and key-up attempt/return times. Failure still follows
+the independent guarded finally-release path. No safety or completion limit was
+changed. The input helper also waits for the native READY event before initially
+binding a game window; after binding, any replacement still refuses.
+
+The25 approach,11 independent evidence and79 helper checks pass, including the
+actual-main startup race. Shorter pulses can require more steps: the old synthetic
+180ms-guard scene now reaches the unchanged12-pulse limit and is explicitly tested
+as a safe refusal; a separate220ms-guard scene completes. This is neither evidence
+of native improvement nor a resolution of the stopping-reserve deadzone. A new
+source-bound native trial remains necessary; prior approach successes do not
+qualify the changed timing.
+
+The first [native timing candidate202949](evidence/approach-timing-review-2026-09-19-202949/review.json) passed camera calibration but failed its original approach deadline. It sent12 paired W pulses and14 yaw requests;11 full stops were completed before expiry. Actual holds were 195.1–236.3ms (median200.9ms), and largest completed stop was0.438m. Observed path was3.965m. All releases and owned cleanup were confirmed. The improved release latency therefore did not produce a completed route within the existing budget. No wheel/F was sent; the failure remains archived.