Allow off-airport extraction across terrains; record Workshop 0.0.124

docs/terrain-takeover.md

@@ -117,19 +117,15 @@ Everon. The menu screenshot uses a labeled offline presentation fixture.
 
 ## Placement and requirements
 
-Escape prefers detected airfields. If there are no airport markers, standard
-runways or control towers, it surveys a clear helicopter landing zone instead.
-Nogova's painted runway therefore needs no administrator coordinates. Every
-candidate still passes terrain, navigation, slope and aircraft-clearance checks;
-a missing airport does not allow an unsafe spawn. Searches have finite time and
-attempt budgets and never fall back to coordinates from another map.
+Escape surveys clear helicopter landing zones across the entire terrain from the
+first candidate, whether airports exist or not. There is no airport-first search
+or dedicated airport-discovery wait. Every candidate still passes terrain,
+navigation, slope, aircraft-clearance and rescue-fleet space checks. Searches
+have finite time and attempt budgets and never fall back to coordinates from
+another map.
 
 Terrain-generated placement allows up to 48,000 candidates or 120 seconds per
 site, whichever comes first, keeping the existing cooperative 8 ms work slices.
-Airport-only extraction searches broaden after 12,000 candidates or 30 seconds
-without resetting that total budget. The fallback surveys the terrain for a
-helicopter landing zone and retains the normal primary/secondary aircraft
-clearance and navigation checks.
 
 Extraction pads do not use the camp-only 12 m road exclusion, and their initial
 ground survey uses the same 0.8 m height variation limit as the landing-zone
@@ -158,7 +154,7 @@ Search diagnostics use the `Reintroduced [placement search]` log prefix. Each
 summary identifies the site, attempts and elapsed milliseconds, with counts for
 failed or deferred checks: water, uneven ground, obstacles, road/airport distance,
 site spacing, navigation and aircraft clearance. Summaries appear on completion,
-exhaustion and airport fallback, plus every 30 seconds during a long search.
+exhaustion, plus every 30 seconds during a long search.
 Counts describe checks rather than unique candidates: a candidate awaiting a
 navigation tile can be checked repeatedly. Mandatory placement failures also
 include the site and rejection summary directly on the loading screen, so no