Capture current mission, AI, map and administration development

Include the current addon, terrain integrations, tools, regression tests and recorded development evidence.

docs/performance-comparison.md

@@ -111,3 +111,12 @@ at 30 Hz/FPS; their records cannot demonstrate ordinary-client improvement. No
 new collector, benchmark or performance acceptance resulted from this audit.
 
 The [native server statistics exporter](native-server-statistics.md) now extracts real coarse `-logStats` records from existing console logs, preserving source hashes and raw lines. It explicitly leaves unavailable AI-only duration and raw-frame percentiles unknown. Its output is useful for native monitoring, but cannot substitute for the matched frame/tick datasets required above.
+
+
+## HQ planning scan budget (2 October 2026)
+
+The final pursuit selection pass now counts global active/pending commitments once after cleanup, retasking and missing-patrol investigation, then increments that local count only when a previously idle unit receives a pending order. Hunting occupancy remains separate from global occupancy; investigations and other existing orders still consume the global limit. Nothing is cached across ticks, and scheduling, radio delivery, reservations and force eligibility are unchanged.
+
+An actual-method regression executes the entire final selection/commit loop across 360 deterministic scenarios. It compares selected orders, roles, destinations, bearings, deadlines, home reservations and hunt cooldowns against the previous repeated-count implementation. A 64-belief/128-unit no-dispatch case reduces the repeated `Assigned()` scans inside that selection pass from over 10,000 unit visits to 128. Earlier cleanup scans, eligibility checks and candidate scoring are outside that count. The old source fails the scan-budget assertion; an independently compiled mutation removing the increment fails behavior equivalence.
+
+These are operation counts with controlled policy/native doubles, **not measured frame time or FPS**. Equivalent-workload engine performance acceptance remains pending. Current native integration and full-suite results are recorded in [the change review](evidence/hq-planner-budget-2026-10-02/review.json).