aussie/EscapistsReintroduced
1
0
Fork 0
forked from escapists/EscapistsReintroduced
Code Pull Requests Activity

Integrate startup optics and supply vehicle lock picking

Browse Source
This commit is contained in:
jakub
2026-09-20 05:34:30 +02:00
parent 9205e2129a
commit 963cab50c0
104 changed files with 16171 additions and 25 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/convoy-migration.md
+10
View File
@@ -156,3 +156,13 @@ still need a direct native scenario. Source and six external dependencies stayed
unchanged, and hidden/muted process cleanup was confirmed. Four external
localization errors keep strict native qualification failed. Full-route,
dismount/flank/reboard, unloading, multiplayer and FPS work remain outstanding.
## Cover test and seat-retention diagnostic
The opt-in `--smoke convoy --convoy-cover --rounds 1 --timeout 900` test first requires the existing physical driving/crew/cargo proof, then moves only the canonical local prisoner beside the original lead vehicle. It observes genuine perception, completed uplink, HQ HOLD, completed downlink and owned-waypoint removal, conceals that same prisoner at a distant authored site, and waits for ordinary evidence expiry and delivered RESUME followed by 20 m of physical travel. Temporary player damage protection is restored on success, refusal or shutdown. No AI, ammunition, reports, radio routes or production timers are created or altered by the cover arrangement. The cover-only smoke timeout is 840 seconds; ordinary convoy timing remains unchanged.
[05:09:06 diagnostic](evidence/native-2026-09-20-050906-convoy-seat-diagnostic/report.json) compiled the current addon sources and passed 170 assertions, but failed the final driving-stage population check: original crew member 18, the final UAZ gunner, failed the combined conscious/original-seat/identity assertion. Exact group membership still matched the six-vehicle plan. That combined failure alone cannot distinguish unconsciousness, a seat switch, dismount or another predicate; failure-only diagnostics now record each condition without changing the assertion. The cover arrangement never started; this run does not validate HOLD/RESUME. The failure is retained without weakening the seat check. Four installed RHS/WCS localization errors also remain; private cleanup and unchanged launch sources were confirmed.
`test_native_convoy_cover_probe.py` executes the fixture's observation, snapshot, delivery and cleanup methods against native doubles, including rejected/failed radio routes, unapplied orders, unchanged HOLD refresh measurement, exact resumed route index, quiet age and damage restoration. Runner refusals occur before launch for an incompatible smoke mode or insufficient cover timeout. These policy tests do not replace the still-pending native cover sequence.
The [20 September 05:15:05 convoy cover run](evidence/native-2026-09-20-051505-convoy-cover-diagnostic/report.json) passed the baseline six-vehicle driving, original crew/seat and cargo assertions. After arranging the existing prisoner beside the lead vehicle, it captured no qualifying visual reports and failed the combined physical-force/player invariant about 34 seconds later. It therefore does not establish native HOLD/RESUME behavior, nor identify a production defect. The retained logs do not distinguish an ordinary completed route from a released vehicle, crew-state change, controller change or physical-force-list difference. The lead route advanced from index14 to18, but that alone does not establish task completion: production ends the task only when all six orders have arrived or been released, and the fixture allows an individual arrived vehicle. Failure-only diagnostics are now included for a future run; no additional convoy test was launched at this checkpoint.