EscapistsReintroduced/docs/validation.md

Validation evidence

2026-09-19, local development environment. This remains a development prototype, not a release-qualified successor.

Repository checks

python3 tools/check.py passes: five-addon isolation, acyclic dependencies, twenty-two source resource identities, exact successor/vanilla GUID references, production mission-rule boundaries, physical radio paths and failure handling, settings conversion, helicopter availability policy and mortar salvo policy. The latter two are helper tests, not operational support-controller evidence.

The reference guard verified all 533 original workspace source/resource files against the pre-test snapshot. Existing missions were not edited or saved. Native tests use a separate profile and only the successor projects plus vanilla dependencies. Earlier successful visible runs were measured on the right display. A later launch restored an oversized main Workbench window despite placement rules; those tests were stopped. Automated tests now run on an isolated headless display and create no physical-desktop windows.

Native development sessions

Workbench version: 1.8.0.13. The initial September 18 source snapshots remain in native-initial-snapshot.json and native-followup-snapshot.json. They established script compilation, native world loading and initial spawning only.

Durable logs, screenshot captures, source hashes and a machine-readable report for logs_2026-09-19_00-28-24 are in native-2026-09-19-002824. That run completed two scripted rounds across an automatic restart, with 38 passing assertions. It exercised native prisoner spawn, the authored lock action, two real cache documents recovered into inventory, intel-driven identification, radio range rejection, interrupted and continuous defence, physical helicopter seating and the victory boundary.

The diagnostic deliberately teleports the player and helicopter and makes the test player invulnerable. It does not establish manual escape/piloting, combat balance, multiplayer lifecycle or FPS improvement. Engine screenshots capture the rendered scene and do not prove the HUD/end-screen presentation.

The original prison prototype had an unsuitable slope and a gate-opening mismatch. Read-only terrain and model-clearance scans selected an open site at 6090/7160. The gate now spans the three-metre opening. Walls have explicit hierarchy ownership, and equipment is placed on tables above vegetation. Final physical gate-passage and defeat checks are recorded separately below.

Remaining native issues

The run is not a clean runtime pass. The report preserves errors rather than suppressing them:

• Some restarts emit two catalog-manager errors associated with vanilla US and USSR medical-kit catalog objects. Read-only source inspection identified an inherited SCR_BaseItemSupportStationComponent.OnDelete validation path; the opt-in diagnostic now records the actual owner and manager state. The missing-manager teardown cause remains an inference until reproduced with that diagnostic.
• Vanilla vehicle resources emit unsupported fields: M151A2 SlidingTrackMaterial, and catalog-loaded BRDM2/BTR70 Parent entries. Validate the installed game/Tools resource compatibility before release.
• Vanilla UI slot/button warnings occur during end-screen setup, and inherited Everon initialization reports a radio-manager ordering warning. The successor creates its radio manager, but these warnings still need evaluation.

The shared-map destruction exception and unsupported runtime destructible-wall errors from earlier prototypes no longer occur in the archived repeated-round run.

No dedicated multiplayer, reconnect, spectator, twelve-player, operational support-controller, equivalent-workload performance or release-packaging acceptance has passed. The full acceptance ledger remains pending.

Final gate and victory regression

native-2026-09-19-003520 contains two completed rounds and 40 assertions, including BaseDoorComponent.CanCharacterPass(0.6) after unlocking. The actual result configuration returned "You escaped Everon" for the extracted player. The run had no script errors or virtual-machine exceptions. Seven inherited vehicle schema errors remain in the report, so its overall runtime result is deliberately nonzero. The source manifest matches the tested repository.

A Workbench-only diagnostic briefly replaced the reflected end-screen class and caused an unknown-class resource error in an intermediate run. That diagnostic override was removed; the archived final run resolves the class and the victory title successfully.

Extraction loss and defeat restart

native-2026-09-19-003902 completed two helicopter-loss rounds and recorded 45 passing assertions, including startup of a third round before the test process stopped. Removing the empty extraction helicopter during extraction caused DEFEAT through the normal server tick, then the mission restarted and completed the same test again. The defeat end-screen configuration resolved without missing-screen errors. This is not an all-players-dead, unconsciousness, reconnect or multiplayer test.

Four catalog-manager errors were recorded across the two restarts, alongside the inherited vehicle schema errors. The archive deliberately retains the failing overall native report. Both test processes were stopped; the user's pre-existing editor was left open.

Player death, identity roster and spectator restart

native-2026-09-19-011025 contains two completed death rounds with 20 passing assertions and no script/runtime exceptions. The fixture exercises native character death, transition into the local spectator camera, the all-dead grace interval, defeat and automatic restart. An isolated roster with a real living actor checks spent-life retention, disconnected survivor retention, duplicate identity rejection and reused connection IDs. It does not simulate an actual remote disconnect/reconnect. Seven inherited vehicle schema errors still fail the overall native report.

This test ran on headless Gamescope at 1280×720/30Hz using a cloned disposable Proton prefix. The physical desktop contained only the user's pre-existing editor. tools/headless_workbench.py provides a bounded version of this runner, stopping on failure, timeout or the requested number of completions and preserving engine errors in its exit status.

Physical radio equipment and routing

native-2026-09-19-011738 completed two bounded headless rounds with 30 assertions and no script/runtime exceptions. Each authored six-person patrol now includes one vanilla RTO with a physical manpack. The test runs production uplink and downlink routes, then removes a receiving carrier's actual radio during transmission and verifies delivery fails. It does not insert a synthetic contact into HQ. Strategic response to native visual perception remains a separate test. Seven inherited vehicle schema errors remain.

Both installed executable version resources report 1.8.0.13 (game Steam build 24903726; Tools build 24870687). The remaining schema errors are therefore not explained merely by different displayed version numbers.

Native sighting to HQ response

native-2026-09-19-012234 completed two headless rounds with 24 assertions. The real player was moved in front of a guard squad. Native perception generated a sighting; the production radio route delivered it to HQ; two different existing squads received downlinked orders and distinct search waypoints. The fixture did not inject HQ contacts or create response forces. Both rounds subsequently passed death, spectator and defeat. Two inherited catalog cleanup errors reappeared during restart; seven vehicle schema errors also remain. This is a scoped coordinator integration pass, not a clean native runtime pass.

Silent complete-loop regression

native-2026-09-19-013224 completed two headless escape rounds with 52 assertions and no script/runtime exceptions after the roster, spectator and radio-composition changes. Test audio was independently verified muted on the dedicated silent sink; other audio outputs were unchanged. Seven inherited vehicle schema errors remain. A preceding launch exited before gameplay with a host double free or corruption error; its raw diagnostics are retained in native-2026-09-19-012838-host-crash and are not counted as a successful run.

Physical mortar inventory checkpoint

native-2026-09-19-014052 completed two muted headless rounds with 30 assertions and no script/VM exceptions. Native inventories held exactly 27 HE shells across three crew plus a separate manpack operator. Deleting the shells did not replenish ammunition; deleting the gun and crew did not spawn replacements. Seven inherited vehicle schema errors remain. Firing, convoy rearming and multiplayer support acceptance are unverified. Further support migration is deferred while completing the base replacement.

Independent base escape

native-2026-09-19-015043 records two Core-only rounds and 26 assertions. The loaded-addon section contains engine core, vanilla Reforger and ERR_Core. Essential inventory-document recovery and discovered objective markers now belong to Core, with a separate base scenario identity. The scripted escape succeeds without AI, Intel, Chat or Map. Two catalog teardown errors and seven vehicle schema errors remain. This proves dependency separation and the exercised progression paths, not manual playability or multiplayer acceptance.

native-2026-09-19-015605 adds the native objective service: two Core-only rounds, 38 assertions, no script or VM exceptions. Tests verify prison task creation, previous-task completion, list-only search disclosure, changed instructions after radio discovery, countdown and reset after interrupted defence, physical extraction and restart. Seven inherited vehicle schema errors remain. These assertions inspect native task state; they do not establish the rendered UI quality or remote-client behavior.

native-2026-09-19-015947 checks the same Core changes with all companions loaded: one escape round, 26 assertions, no script/VM exceptions. Seven vehicle schema errors remain. The test retains physical document recovery, interrupted radio defence and actual helicopter occupancy while the core services own progression.

native-2026-09-19-020149 checks death/spectator/defeat with the new Core task lifecycle and companions loaded: one round, 10 assertions, no script/VM exceptions. Seven inherited vehicle schema errors remain.

Authored sites and finite scavenging

native-2026-09-19-022704 records two Core-only rounds with 62 assertions and no script/VM exceptions. The four configured sites prepare 52 physical stock entities; recursive inventory totals include native weapon attachments. The player transfers both targeted radio documents from the supply crate. Empty stock stays empty when preparation is queried again, and a destroyed crate remains absent. Radio progress, extraction and restart complete afterward. Both crate footprints pass bounded native model-clearance checks; the supply terrain sample spans 0.625 metres over six metres. Seven inherited vehicle schema errors remain.

Earlier failed iterations are retained with their source hashes: attribute/callback compilation errors, unregistered storage, insufficient crate capacity, and use of a character-only inventory manager on a world container. The final controller uses the generic manager with explicit storage registration and an appropriately bounded weapon crate. These failures were corrected before the successful run; they are not hidden from the evidence archive.

native-2026-09-19-023120 repeats the new site flow with all companions loaded: two complete rounds and 52 assertions, including physical inventory transfers, interrupted radio defence and extraction. Templates now obtain location IDs entirely from definitions. The inherited catalog teardown pair and seven vehicle schema errors remain in the report, so this is not a clean runtime acceptance.

native-2026-09-19-023514 verifies radio integration after site ownership moved into Core: one muted headless round and 15 assertions, with no script/VM exceptions. All four authored six-person squads carry physical manpacks. Uplink and downlink work, and removing a receiving radio interrupts delivery. Native death, local spectator and all-dead defeat also pass. Seven inherited vehicle schema errors remain.

Injected base catalog and administration

native-2026-09-19-025539 completed two Core-only muted headless rounds and 92 assertions without script/VM exceptions. The physical prisoner and guard group match the injected catalog. Separate catalog mutations reject identical and unknown faction keys and a missing prisoner entry. Core's command service rejects unauthorized, malformed and out-of-range setting changes; valid commands save/read/restore the test duration. Escape, stock losses, objectives and restart still pass. Seven inherited vehicle schema errors remain.

The command tests call the native server service directly. They do not prove remote RPC identity enforcement, command-panel usability or pre-spawn presentation. Earlier command extension ordering and compact conditional-return compilation failures are retained in native-2026-09-19-025246-compile-failure and native-2026-09-19-025341-compile-failure; both were corrected before this successful run.

native-2026-09-19-030156-expected-startup-failure contains four passing assertions for deliberately invalid faction setup. No players, sites or stock spawn; services stop; administrators can retrieve the cause; even an otherwise legal transition from preparation into prison is rejected. The fixture modifies only its in-memory catalog. The expected startup ERROR and seven inherited vehicle schema errors remain in the report. The preceding scoped run is retained in native-2026-09-19-025951-expected-startup-failure. This is failure-handling evidence, not clean runtime or remote UI acceptance.

native-2026-09-19-030347 completed two Core-only escape rounds and 102 assertions without script/VM exceptions. A native controller transition keeps the actual player unconscious at the radio for 35 seconds. The player still prevents all-dead defeat, cannot progress transmission, retains the same body and camera, and resumes defence from zero after consciousness is restored. The one-life rule remains spent. These checks repeat after restart alongside the catalog/administration checks. Seven inherited vehicle schema errors remain. This does not validate medical item use, treatment animation, bleeding or remote revive actions.

native-2026-09-19-030903 completed two companion-loaded rounds with 96 assertions and no script/VM exceptions. Existing HQ interval/squad/radius and Intel carrying/reveal aliases resolve through the Core command service; unauthorized journal access is rejected; HQ status is preserved. Both rounds also pass the catalog, base administration, physical intel, radio defence, helicopter escape and restart checks. Seven inherited vehicle schema errors remain.

native-2026-09-19-031256 records one companion-loaded death round and 32 assertions without script/VM exceptions. Native death retains the spent life, activates the local spectator camera and reaches all-dead defeat after the Core command initialization changes. Catalog and companion command checks also pass. Seven inherited vehicle schema errors remain; remote spectators and reconnects are still unverified.

Expanded scavenging route and spatial survey

The read-only surveys in 031928 and 032144 inspected candidate terrain and obstacles. The initial 12-by-12-metre clearance requirement found no suitable candidates; using the actual 2.6-metre cache footprint found 19 western, 23 medical and 23 outpost candidates. Three low-slope sites were selected. No existing vanilla scenery or original missions were modified.

The first expanded-route native compile failed on Enforce's unsupported compound assignment to an indexed vector value. 033036-failed retains that failure and its cascading compiler diagnostics. An explicit assignment fixed it.

033110 completed one Core-only cache-loss escape with 65 assertions and no script/VM exceptions. All seven sites and 117 authored stock items prepared successfully; deleting the southern crate before recovery left the western documents able to identify the radio and complete extraction. Named optional medical discovery rejected unconscious and distant players, then emitted one event after a conscious player approached. Both stock depletion and deleted containers stayed lost. Seven inherited vehicle schema errors remained. A later API check found two sandbag rotations used pitch instead of yaw; subsequent validation uses corrected upright barriers and actual collision traces.

033500-failed confirmed all three upright barriers had native collision, then failed the new blocked-discovery assertion. The fixture had placed the test wall by its end pivot, leaving the sight line at its edge. Existing native bounds showed the wall extends three metres from its origin; centering it across the sight line corrected the fixture. The failure is preserved rather than discarded.

033719 completed two Core-only cache-loss escape/restart rounds with 148 passing assertions. All 117 stock items prepared each round. The three corrected outpost barriers were upright and native traces hit their collision. A centered physical wall prevented medical-site discovery; removing it allowed the conscious nearby player to reveal the named stash and emit one event. The alternate radio documents completed both rounds after the primary cache had been removed. There were no VM exceptions or failed smoke assertions. Two inherited catalog-manager script errors occurred during restart, alongside seven inherited vehicle schema errors, so the overall native report remains failed. These scoped checks do not establish manual navigation, medical treatment or multiplayer behavior.

034344 completed one full-companion escape with 48 passing assertions and no script/VM exceptions. The expanded seven-site configuration prepares under HQ/Intel/Chat/Map; the southern cache's documents still complete the primary route with the existing command aliases, interrupted radio defence and physical extraction. Seven inherited vehicle schema errors remain.

034556 completed the expanded guard-radio regression and death/defeat sequence with 37 passing assertions and no script/VM exceptions. All six physical six-person squads had manpacks; the selected production uplink/downlink delivered and deleting the receiver's actual radio interrupted an in-flight HQ order. The fixture also checked native death, local spectator activation and all-dead defeat. This does not prove every multi-hop route. Seven inherited vehicle schema errors remain.

The three archives (033719, 034344 and 034556) match the 99 addon source/resource files at that historical checkpoint. All test processes were stopped. Source/resource checks pass for five isolated addons and 22 unique resources; the 533-file original-workspace reference guard remains unchanged. Manual gameplay, medical treatment, multiplayer, performance and clean-runtime release gates remain open.

Independent extraction and mission clock

040125 passed 60 capacity/partial-result assertions with twelve actual vanilla characters seated in separate positions in the authored Mi-8. The helicopter exposes seventeen pilot/passenger positions. The isolated roster distinguishes a dead occupant, a disembarked survivor, unconscious and reserved disconnected passengers, and a different identity reusing a connection ID. It freezes one outcome and does not replace lost transport. This fixture uses synthetic identities and explicitly requests its own test reset.

040443 and 040657 each passed three negative-startup assertions. An unsuitable vanilla transport and an invalid extraction boundary respectively prevent gameplay, retain an admin-readable reason, withhold player spawns and remove the already-authored content. Both expected startup errors are preserved alongside inherited vehicle errors.

040928 passed 100 assertions with the integrated extraction, controller result and mission clock implementations. Real hidden vanilla result widgets update from the server-derived identity result and ignore stale winner IDs through isolated rebinding. The clock probe checks legacy settings migration without rewriting on load, explicit save/reload, invalid-value rejection, authorization, next-round-only changes and actual native clock advancement. No script/VM exceptions occurred; seven inherited vehicle schema errors remain.

041233 passed six assertions across two natural defeat/restart rounds. Removing the extraction helicopter during prison ends the mission while the actual prisoner remains alive and presents the specific loss reason. Two inherited catalog cleanup script errors and seven vehicle schema errors remain.

These hidden, muted local tests establish the exercised service and native-object paths only. Remote delayed result replication, actual reconnects, twelve network clients, manual casualty loading/piloting, dedicated-server behavior and equivalent-workload performance remain unverified.

041445 completed two Core-only escape/restart rounds with 194 assertions and no script/VM exceptions. Both rounds applied the seeded 06:15 / 4x settings and verified actual native clock advancement. Existing catalog/admin, stock, discovery, unconsciousness, radio and extraction checks still pass. The seeded input is archived as test-settings.json; all three private-profile settings files were restored byte-for-byte after the stopped run. Seven inherited vehicle schema errors remain.

042046 completed one companion-loaded escape with 48 assertions and no script/VM exceptions. Core, HQ, Intel, Chat and Map compile together; existing command aliases, physical documents, interrupted defence, extraction and the personal winner title still work. Seven inherited vehicle schema errors remain.

Archives 040928, 041233, 041445 and 042046 match all 105 addon source/resource files at this checkpoint. Tests ran on the private hidden display with muted test audio and were stopped afterward. The original workspace's 533 tracked reference source/resource files remain unchanged. Repository policy/resource checks pass; clean-runtime, manual-play, multiplayer and performance release requirements remain open.

Base radio separation, native objective details and ground transport

042945 retained a real presentation failure: the native task description changed after radio discovery, while its already-open details widget remained stale. The list/details initialized correctly and showed no hidden task position. The successor now subscribes only its own open objective details to native display-data changes, with removal on task switch/detach. The later 044330 and 044608 runs pass the already-open detail update after discovery; their separate new radio fixture fails before completing the round, so whole-loop validation remains separate.

043410 rejected the first ground-transport parking position at 5960/7232 due to a native geometry obstruction. Preparation rolled back; the error was not suppressed. 043631 then surveyed 120 nearby positions with the transport temporarily omitted only in its fixture definition, finding 43 clear candidates without removing scenery. The selected southern position, 5960/7212, has a 0.625 m sampled terrain range over its six-metre square. This is placement evidence, not driving or navigation acceptance.

043806 retained a subsequent readiness failure after the parking point itself passed. The bounded diagnostic in 044028 showed native vehicle bounds extending 3.25 m from the surveyed center, exceeding the original 2.5 m allowance; actual origin displacement was only about 0.06 m. The configuration now requires an eight-metre cleared square and retains a 0.5 m margin around full native bounds.

044205 passes 23 native transport checks with no script/VM exceptions. Parking, five native driver/passenger positions, actual two-character occupancy, ordinary engine startup and finite fuel work. Native fuel starts at 58.5 L with 78 L capacity. Depleting fuel and deleting transport do not refill or recreate it, including repeated preparation/initialization queries. The fixture stops its site service and explicitly requests test reset. Seven inherited vehicle schema errors remain; this is not manual driving, road access or multiplayer acceptance.

044330 and 044608 preserve failures in a new radio-service fixture that immediately checked distance after moving its character. Switching to the native character teleport API alone did not resolve the check; the fixture is being made asynchronous so it observes applied native state before asserting it. These runs do not count as completed Core regressions.

044924 independently completes the established companion-loaded escape with 48 passing assertions and no script/VM exceptions. The production radio service accepts the identified nearby player, resets on departure, completes real-time continuous occupancy and advances to physical helicopter extraction. Existing command aliases, document recovery and personal results still work. Seven inherited vehicle schema errors remain.

The offline performance comparator passes fifteen synthetic regressions and does not produce real benchmark evidence. Release qualification passes 46 validation regressions and correctly refuses the current ledger: all first-release cases remain pending and clean native runtime remains failed. Neither tool changes acceptance or publishes a package.

045450 confirms that deferred native movement resolves the distance assertions: the measured out-of-range position is 6.005 m from the radio and unconscious tuning is rejected. The next assertion fails during recovery. The test is being corrected to separate its overlapping characters and await native consciousness; no production authorization rule was weakened.

050158 preserves a compiler rejection of two ticket member names that collide with native type names. The members were renamed before further testing.

050240 preserves the next integration failure: the WORKBENCH-only spawn-logic override needed to repeat its native container metadata. The corrected reflected class loads and starts an ordinary prisoner in 050403, which completes 54 lifecycle assertions without script/VM exceptions. Native geometry leaves 20 clear prison positions around the real prisoner; reserved slots remain distinct and inside the enclosure. A physical unowned body blocks its slot. Native finalization rejects spent-life and wrong-data requests, deletes only the owned unpossessed actor, preserves the actual prisoner, and rejects vertical displacement. The fixture explicitly ends its test; real remote preload, disconnect/reconnect and 12-client acceptance remain pending. Seven inherited vehicle schema errors remain.

050515 completes two Core escape/restart rounds with 340 assertions, no script/VM exceptions and seven inherited vehicle schema errors. The independent radio edge fixture now waits for real native recovery and passes physical defender handover, empty samples, hostile/unknown/dead actors, interrupted occupancy, live duration changes, cancellation and one-time completion. The ordinary real-time escape then succeeds twice through the new player-admission gate. Native task details update after discovery, advancing progress and interruption. Separate objective-close cleanup review follows; remote UI remains unverified.

The opt-in station diagnostic identifies US/USSR medical-kit prefabs during OnDelete/InitValidSetup at restart. Both cached and global catalog references remain available in this run despite no current game mode, so the intermittent missing-manager error is not reproduced or declared fixed.

Future native runs now snapshot addon files before process launch, compare sources after shutdown and seal the raw console log. Archival and release checks reject source/log mismatches. Older archives retain their original historical evidence; they cannot satisfy the new launch-provenance release requirement.

051249 preserves a companion compile failure from two WORKBENCH test helpers sharing a member name on the same extended game mode. The Core helper was renamed to avoid the pre-existing Chat radio-network probe. This is the first archive with mechanically verified pre-launch source, stopped source and raw-log hashes; the failed result remains failed.

051452 completes two Core escape/restart rounds with 374 assertions, no script/VM errors and seven inherited resource errors. Native objective close/rebind/reopen checks pass, including no retained task events or delayed overflow calls to the closed panel. The runner verifies identical pre-launch and stopped addon sources and seals the raw log. A subsequent ownership-flag change covers task deletion before panel closure and is checked separately by the short objective-ui fixture.

052140 preserves a remaining teardown failure: deleting an isolated native task clears its weak references and the panel detaches, but a delayed callback still reaches the retained test handler. The assertion remains failed while callback identity and queue state are investigated.

052352 completes the full companion escape with 48 assertions, no script/VM errors and verified launch/stopped-source/log hashes. The helper-name collision is fixed. Core admission, radio, physical intel, preserved admin aliases and extraction work with all companions. Seven inherited resource errors remain; the isolated task-deletion UI failure is separate and still open at this snapshot.

052621 identifies the surviving callback as UpdateAssignees, invoked immediately when the real objective assignment is restored. Installed vanilla source declares all five task-event getters static; guarding their removal by a live task left the closed panel subscribed after task deletion. Cleanup now removes the static invoker subscriptions using retained successor-binding ownership. The unchanged delayed callback assertion is rerun rather than weakened.

052811 reaches all 30 UI assertions and completion after the static-event fix, but remains a failed runtime result: the added name-based queue diagnostic tries to inspect protected CheckOverflow and emits three VM exceptions. The normal function-based cancellation does not emit them. The invalid diagnostic is removed before final UI validation; its exceptions are retained in this archive and the preceding diagnostic run.

052932 completes the companion-loaded death/spectator/defeat fixture with 32 assertions, no script/VM exceptions and verified source/log provenance. Native damage kills the actual prisoner, activates the spectator camera and retains the spent life through the revised delayed observer callback. Seven inherited resource errors remain; remote reconnect and spectator streaming are still unverified.

053124 completes all 30 isolated UI assertions with no script/VM exceptions after removing the temporary name-based diagnostic. Real close/rebind/reopen, native weak-reference clearing after isolated task deletion, global event unsubscribe, delayed callback cancellation and restoration of the actual objective assignment all pass. Seven inherited resource errors remain. Its pre-launch/stopped source manifests match all 116 final addon files, and the stopped raw-log hash verifies.

At this checkpoint, repository policy/resource checks, 15 synthetic performance-tool regressions and 46 release/provenance regressions pass. The actual release checker still refuses all 17 pending first-release cases plus failed clean native runtime. All private test runners are stopped. Manual equipment/medical/casualty gameplay, real multiplayer/preload/reconnect testing, operational support/logistics, equivalent-workload FPS measurements and release packaging remain unfinished. Historical archives describe their own source snapshots; they are not relabelled as final-source tests.

Native medicine and environment checkpoint

062406 passes 24 actual blood-loss and treatment assertions, including consumed dressing, one attached saline bag, duplicate rejection, native consciousness recovery and finite infusion completion. It retains the seven earlier inherited catalog errors.

063559 passes 67 environment and deliberately narrowed faction-catalog assertions, with zero script/VM or engine errors. The successor profiles preserve vanilla faction, item, medical and radio behavior but catalog only its UAZ and Mi8 vehicles. Clear/overcast/rain, leap dates and unchanged clock progression pass. Repeated-round teardown, current complete-loop regression, manual play and multiplayer remain separate checks.

063949 passes 155 combined assertions with zero engine errors. The revised 3m-spaced interior prison search accommodates one real controlled prisoner and eleven physical test characters. Each has the exact unique starting kit and can receive and return a real clue. Repeated inventory references are counted once by entity identity; distinct same-prefab objects remain distinct. This is physical placement and inventory evidence, not twelve-client multiplayer.

064406 passes 54 combined assertions with zero engine errors. Recovery status, stable event counts, survival beyond the all-dead grace, identity preservation and administrator authorization pass. Explicit abandonment while the all-incapacitated warning is active enters normal defeat and clears the warning during cleanup.

064716 retains an integration compile failure: a separate WORKBENCH modded layer could not expose its restart-probe field to the main fixture, and the patrol check passed an entity where a boolean was required. Both were corrected; 065233 compiles and reaches the patrol fixture, which stops on an unexpected repeated native queue reference. Its route interpretation remains under investigation rather than declaring traversal passed.

065351 passes two real environment/restart rounds, 107 assertions and zero engine or script/VM errors. Real mode settings save 2000-02-29 and Overcast, leave the current round untouched, and load/apply them in the next mode instance. Native clock progression remains unchanged; successful round two removes the private fixture files. Bounded station diagnostics show medical kits in backpack inventories outside the main world, consistent with catalog preview content; neither successor site ownership nor a teardown failure was observed in this run. Complete-loop regression and remote testing remain separate.

070733 passes 58 assertions with zero native errors after canonical participant validation is shared by discovery and radio authorization. The lost-document path deletes all four original clues, rejects distant/NPC/obstructed observers, and identifies the station once by actual close approach before authorized tuning. No replacement documents are created.

070919 passes 295 assertions with zero native errors. Preparation observes complete six-person membership of every original guard squad. Both existing patrol groups move and complete five ordered native Move events, crossing a cycle boundary, before route-only cleanup preserves a foreign Search. Startup queue enumeration repeats references that clear as waypoints complete; no production queue normalization was introduced. HQ preemption, manual gameplay and remote clients remain separate checks.

071654 passes 60 assertions with zero native errors. The partial-knowledge case transfers one real clue before losing all four documents, then verifies that close physical discovery still identifies the radio station and permits tuning. It does not duplicate documents or require zero prior knowledge.

072014 retains a casualty-loading readiness failure. Over ten seconds, the untouched parked Mi8 remains alive, upright and motionless, but its native helicopter simulation reports no ground contact. The real participant, helper, distance and visibility checks pass. Casualty loading is not yet qualified; physical landing-gear support is being investigated without accepting a stationary hover.

072609 ordinary game preserves a failed private ArmaReforgerSteamDiag.exe launch. Its vanilla intro splash reports unknown SCR_WidgetExportRuleRoot before Game module compilation completes. GameLib reports ENF_WB; this run does not establish ordinary production compilation or mission startup. The runner stops only its own process group/prefix and confirms cleanup and unchanged addon bytes.

072700 retains an actual guard-cancellation failure: an initially empty fixture-owned automatic squad receives a late native dispatch after repeated preparation Stop. The ordinary six mission groups remain separate. This identifies an incomplete cancellation path; a one-time purge alone has not proved sufficient while the incomplete group remains alive.

072838 passes the companion HQ/patrol fixture: 272 assertions and zero native errors. The original outpost squad physically completes a route cycle, receives a real HQ Search through the delivered-order method, retains its patrol queue, and resumes physical cyclic movement after actual HQ release. No additional response force is created. This deliberately bypasses report radio transit and is not multiplayer proof.

073231 ordinary game confirms that the regular executable omits editor/diagnostic GameLib defines, but reproduces the same vanilla intro-splash unknown-class error before Game compilation finishes. The failure remains fatal; further diagnostic collection must not turn it into a clean startup pass.

073313 preserves a compile failure in the new wheel-support helper: the native method is Math3D.MatrixIdentity4, not MatrixIdentity. After correction, 073423 compiles and proves that the sleeping, engine-off helicopter fails all three short wheel-support traces. Its wheel pivots resolve distinctly, but no supporting collision is found within the tight tolerance. This may be an initially unsettled vehicle on sloping ground; neither a stale contact flag nor a safely parked aircraft is assumed. Native placement/settling is being investigated.

073601 passes 68 native assertions with zero errors after retiring each cancelled instance's spawn intent before purging. The empty squad receives no dispatch/member; the partial squad keeps its one existing member and two prior dispatches unchanged for fifteen seconds while the independent control reaches six. Normal rollback deletes the seven captured actors and all three groups; another six seconds shows no delayed dispatch. Actual mission groups remain intact.

073806 passes two complete Core escape/restart rounds with 564 assertions and zero engine or script/VM errors. Both rounds exercise Core administration, canonical player admission, independent clue routes, real radio service boundaries, repeated unconsciousness/recovery, replicated-feedback source values and player-guide copy, native objective widgets, helicopter extraction and restart. New radio feedback moves through inactive/waiting/transmitting/interrupted/resumed/cleared states. Station teardown diagnostics remain enabled and no catalog error occurs. These are source-bound local scripted rounds; subsequent initial-helicopter placement changes, ordinary game, real clients and FPS remain separate.

074505 ordinary game captures completed production Game compilation with no WORKBENCH/ENF_WB defines and no successor script compilation error. It remains a failed startup: the vanilla splash error persists, and the native executable crashes in SpawnEntityPrefabEx while expanding its first guard squad. The raw log reports no configuration for world-system initialization; the authored scenario header specifies vanilla MissionSystems. Launch/system configuration is therefore being investigated before another ordinary-game attempt. The private processes were stopped and source/log provenance verified; this is not a playable-startup pass.

074655 confirms the production one-shot placement wake: the original helicopter settles naturally, all three tire bottoms meet terrain within millimetres, native contact becomes true, fuel remains present, and only one wake occurs before prisoner spawning. Separate raised, tilted and moving aircraft are rejected. The complete run remains failed: its later casualty step stays conscious because the fixture disabled damage handling before its own resilience-damage request. The fixture is corrected to admit only that synchronous native request while retaining surrounding protection; no production health changes are made.

075014 preserves a native-removal fixture parse failure at a local variable named reference; it was renamed before further compilation. 075324 ordinary game preserves a separate launcher compile failure: native ArmaReforgerScripted cannot own queued callbacks because it is not Managed. The queued transition is being moved into a managed helper; identity and mission admission are unchanged.

075514 passes 87 casualty-service assertions with zero engine or script/VM errors. The original helicopter naturally settles after its one-shot initial wake, and separate unsafe-aircraft checks pass. The fixture's single admitted native damage operation incapacitates the actual controlled player; strict membership rejects the separate helper until the explicit helper-only adapter is enabled. External bench reservations and a physical wall prevent loading. Invoking the real action completion boundary then runs the local owner handshake, seats the living incapacitated player exactly once, releases the selected reservation and preserves identity. Duplicate completion and repeated Stop do not load or resolve again. The real controller takes the local fast path; helper identity is synthetic, action input is not held, legal phases are deliberately advanced, and the fixture requests reset. Remote RPC transit, pending-load deletion, manual play and multiplayer remain unverified.

080004 ordinary game compiles production Game with neither WORKBENCH nor ENF_WB, requests the Core scenario header once, initializes vanilla MissionSystems, verifies the selected header and reaches phase 0 -> 1. No repeat of the earlier guard-spawn crash is captured. The run is still failed: two vanilla splash unknown-class errors remain and the local player cannot bind an identity, so spawn admission correctly stays closed. Header transition and mission preparation are observed, not clean startup, a controllable player or a completed escape. The runner confirms private-process cleanup and identical launch/stopped addon bytes; raw errors remain in the source-bound archive. This does not establish ordinary input, remote authentication, multiplayer or performance.

080058 passes 66 native casualty-removal assertions with zero engine or script/VM errors. The existing SCR_RemoveCasualtyUserAction resolves the occupied Mi8 child bench, exterior door_l01_door context and native authored exit. The actual conscious caller passes action visibility/permission, then one direct completion call uses the stock KickFromVehicle path. A native exit event clears vehicle and seat occupancy; the still-living incapacitated test body settles within the unchanged observation bounds beside the exit, and the bench is accessible. Root horizontal error is 0.710329m and terrain clearance is 0.862961m after an earlier observation correctly fails the clearance bound. No post-boarding teleport, recovery or retry is introduced. Pre-removal isolated extraction occupancy passes; post-removal evidence concerns physical vacancy, not recalculating a frozen outcome. This fixture ends through its own reset and does not exercise held input, remote action transit or multiplayer.

080226 passes 37 companion-loaded native assertions with zero engine or script/VM errors. The actual mortar initializes four physical crew, a manpack operator and exactly 27 unique HE shells. Deleting that stock leaves it empty with zero confirmed shots; deleting the gun and crew leaves support permanently unavailable. This qualifies inventory identity deduplication and loss retention at the recorded source, not firing or later readiness/transfer changes.

game080528 verifies the narrowly gated diagnostic no-splash path, ordinary Game compilation, matching Core mission header/MissionSystems and preparation reaching PRISON without the earlier GUI errors or a captured crash. It remains failed on native offline identity binding: server, mode and local controller exist, but the returned identity is null. No identity bypass is applied. Normal visible splash UI and player input are not exercised.

080656 passes two complete Core escape/restart rounds, 564 assertions and zero engine or script/VM errors. This source includes the one-shot physical extraction-aircraft settling and the casualty service; normal base progression, inventory/discovery, radio interruption/recovery feedback, objective UI, boarding and result cleanup pass. It does not exercise held-input rescue, later ordinary admission diagnostics, later mortar changes or remote clients.

game081359 confirms the ordinary admission blocker precisely: native backend data is the well-formed 36-character all-zero UUID sentinel, which vanilla returns unchanged because it checks only string emptiness before its fallback. Mode is standalone None, a real local controller exists, and the unchanged strict roster rejects the null identity. The strengthened local-participant observer compiles without Workbench but correctly produces no pass marker. No authentication, identifier contents or name contents are logged.

081601 passes 89 native Core lifecycle assertions with zero engine or script/VM errors against revised prison placement and canonical participant checks. It remains a local fixture, not real remote preload/reconnect evidence.

081837 compiles the revised finite mortar readiness/transaction/firing code and new native firing probe with all companions. All 37 inventory/loss assertions pass with zero engine or script/VM errors. The journal confirms four original physical members and 27 completed shell requests before readiness; depletion and permanent loss remain correct. Actual transfer and projectile tests remain separate.

082123 proves real test uplink, HQ scheduling, downlink, native artillery activity and ballistic solution, but no physical shot. The native gun takes about24s to finish aiming, exceeding the ten-second solution lease; final authorization correctly withholds. A later retry of the same still-fresh report triggers the probe's single-order assertion. This remains failed and motivates equivalent-solution revalidation, not relaxed report freshness or fabricated firing.

game082733 is the first clean ordinary Core startup: regular Game compiles without Workbench, the correct header and MissionSystems load, actual guards/stock prepare, and the real local controller receives a living canonical roster participant in PRISON through native admission. A native-generated standalone round key handles the confirmed backend null sentinel without changing network identity or permissions. Fifteen seconds of continuous ready state pass with no captured engine/script failures and confirmed process cleanup. Diagnostic no-splash is active; held input, full escape, normal splash UI and multiplayer remain untested.

082938 ordinary Chat passes regular-game startup with all five successor addons. Native audit/finalization binds the actual sole local controller to a living canonical prisoner; the fifteen-second ready interval and owned cleanup complete without captured errors. This shares the standalone-admission source snapshot with the clean Core startup. No held input, full route, normal splash or multiplayer claim.

083352 mortar firing passes 48 native assertions with zero errors. The earlier aiming timeout is resolved by recomputing native ballistics against the immutable original command and delivered report, renewing only an equivalent aiming solution. The real gun fires one physical projectile through the actual report uplink/HQ/downlink/native activity path; exactly one of the original 27 HE shells is consumed. Explicit Stop closes the order, followed by twelve seconds without another order, projectile or ammunition replacement. Synthetic observation and unmeasured impact remain explicit limits; full salvos and multiplayer are separate.

083213 dedicated diagnostic compiles the native Linux regular-server Game module, loads the authored Core header/MissionSystems and reaches prison phase with zero players and 36 physical AI. Mandatory no-route network isolation and owned cleanup are verified. Four raw installed editor-helper resource errors remain, so this is partial dedicated startup, not clean runtime or multiplayer acceptance. The frozen source and binary/command/log records are retained separately from Workbench archives.

083810 exact mortar transfer passes 119 native assertions with zero errors. A disclosed scheduler/radio-bypass fixture moves existing shell entities between the actual crew inventories, requires callback plus exact physical ownership, cancels a second accepted operation without permitting another request/readiness, conserves all 27 shells and restores each original owner before deleting empty fixture boxes. The observed callback completed synchronously before cancellation; this does not qualify late callback timing. No ammunition is minted or discarded.

084040 vanilla-only dedicated control loads only the installed core and ArmaReforger addons and reproduces all four resource errors from the successor dedicated run. The installed Game Master Everon header and its GameMasterSystems reach GAME with zero players. Twenty-one total vanilla errors remain preserved, including the four matching errors; this is a control, not a clean successor or multiplayer pass. Source diagnosis identifies missing Workbench assets referenced by installed Calvary and blast-trigger prefabs. No successor gameplay/resource patch is justified by this result.

084026 companion restart reaches two scripted victories and 96 passing assertions on the standalone-admission/mortar-readiness source snapshot. It is a failed runtime result: two native support-station missing-catalog errors occur between rounds. The clean first-shot and transfer mechanism runs do not erase this restart failure.

084543 admission probe integration preserves an unknown spawn-container class and consequent native respawn failures. The WORKBENCH modded test layer needed the original BaseContainerProps metadata. 084919 then preserves an unrelated powered-flight probe compile failure: LockInVehicle was an extension-added method, not a native character method. Those calls were removed; actual seat ownership is checked instead.

085048 local admission passes 54 native assertions without errors. Replayed callbacks preserve the actual local prisoner, key, roster object and spent life without new spawn work. Disposable helper fault inputs latch failure, and a deliberate invalid-controller method argument makes the real production context guard end the round while preserving the original body/life. This is method injection and callback replay in a standalone native session, not a genuine network disconnect or authentication test.

085302 discovery probe integration retains missing native map-marker serializer methods caused by modding the replicated vanilla base class for test access. The probe now uses separate owned plain/objective subclasses and preserves the native RPC type. The production discovery-marker fix is separate from this test access correction; native widget verification remains pending.

085442 Core restart and discovery widgets passes two complete Core-only escape/restart rounds with 586 assertions and zero engine or script/VM errors. The snapshot includes the standalone admission helper and successor discovery-marker fix. Each round's eleven marker assertions instantiate real hidden native marker layouts, reproduce the vanilla stale-label/annotation-ownership behavior, verify successor immediate label refresh and protected ownership, recreate the widget with its latest label and remove only owned probe widgets/markers. Existing physical clue, radio defence/feedback, objective UI, extraction and restart checks complete. This is local scripted evidence for the archived source; real map input, remote clients, flight and FPS remain outside scope. The separate 085048 admission result remains 54 clean assertions with method-fault injection and callback replay, not new network authentication. Neither pass resolves the earlier companion-only restart catalog error.

090203 powered-flight pad refusal compiles and passes 51 preliminary assertions, then fails to find a separate clear flat pad among its twelve initial candidates. Both fixture failure messages and zero completions are retained. No fixture aircraft/pilot, engine start, flight-input hook observation or powered flight is established; the extraction vehicle remains untouched. The refusal motivates a bounded candidate-search revision without reducing physical-clearance requirements.

090443 HQ proof compile failure stops before runtime, first reporting Formula too complex at ERR_NativeHQResponseProof.c:236. 090705 pad-search compile failure stops first at ERR_NativePoweredFlightProbe.c:36 with Unknown operator '%'. Each report preserves all subsequent compiler errors and has zero assertions/completions. Corrections require a fresh archived native run; earlier clean Core and ordinary startup snapshots do not qualify this later source.

For these five 085048–090705 archives, console SHA-256 values were checked against runner metadata, and launch/stopped source-manifest bytes and their recorded hashes match. All seventeen release cases and current-source clean runtime remain pending. No actual multiplayer, powered flight, matched-workload FPS improvement or released package is established.

091306 mortar expiry passes 48 native assertions with zero captured errors. The corrected HQ proof and pad helper compile in this source. A single unchanged synthetic observation traverses the actual radio/HQ/native firing path; two physical shells are committed while its original age is below sixty seconds. A subsequent firing attempt is explicitly withheld for report expiry at 61.004 seconds. HQ continues operating beyond the deadline and through an additional twelve-second stable interval without a new order, new projectile or further ammunition consumption. Commitment is observed before native inventory transfer and linked to the actual emitted projectile, preserving legitimate completion of already authorized operations. This is expiry/deduplication evidence, not real perception, a complete salvo, measured impacts, multiplayer or the later station-cleanup source.

091641 medical-kit teardown passes 76 native assertions with zero captured errors. Two fixture-owned stock kits initialize in separate owned preview worlds, then only each station's cached catalog reference is deliberately cleared. Actual native resource callbacks stop reaching the station after the scoped production teardown, duplicate teardown does not repeat work, and queued delayed initialization remains cancelled after 500 ms. The global catalog remains unchanged. Both stock kits report zero installed damage-callback sources, so runtime damage-listener removal is not established. This is explicit catalog-expiry injection, not spontaneous expiry or reproduction of the earlier companion restart error; a later complete companion restart is still required.

091819 expanded flight-pad survey compiles but refuses all 128 candidates before aircraft creation. Three have low terrain and 125 exceed the unchanged 0.8 m cardinal height-difference limit; the best is 0.803917 m. Cylinder and swept-box checks are not reached. A later bounded local refinement is intended to find nearby suitable geometry without relaxing this limit; no powered flight is established.

092026 prison breach registration compiles but fails its first gate-registration assertion before any gate damage or boundary crossing. The registration's actual scenario ownership/hierarchy is being investigated; no native destroyed-gate progression pass is claimed.

092237 genuine HQ response passes 35 native assertions with zero captured errors. A native visual sample from an original source-group soldier becomes report M1, travels through its original physical RTO/uplink to HQ, and is delivered through downlink M5 to a different original squad. The original recipient physically moves toward the current native Search waypoint; the original force/group/actor sets are unchanged. No target, report, radio event or order is seeded by the observer. The real prisoner is deliberately positioned near the source and temporarily protected for this arranged local test. The established death/spectator/defeat ending also passes. This does not establish multiplayer, unrestricted perception quality or later logistics changes.

092512 companion restart passes two complete companion-loaded escape/restart rounds with 96 assertions and zero captured errors. Teardown diagnostics are disabled. This snapshot includes the scoped medical-kit cleanup, report deduplication and strengthened native proof sources. The prior 084026 failure remains archived; a clean pair is regression evidence, not proof that intermittent catalog expiry was reproduced or cannot recur. The subsequent prison-registration correction and flight-footprint changes need separate native runs.

092923 prison breach passes 62 native assertions with zero captured errors. The owned prison root resolves normally; its gate child's raw prefab name is empty while the installed resource-name resolver identifies the exact successor door. The corrected owner/action lookup registers the actual gate with health 1000. Native HandleDamage deletes that gate; the weak reference becomes null, while a fresh unsubscribed helper refuses zero candidates and cannot grant escape. Destruction alone, a distant jump and outside-only arrival do not progress. A deliberately repositioned bounded inside-to-outside crossing then enters RADIO_SEARCH once, reveals both supply sites and stays free of duplicate completion. This is actual native destruction plus scripted movement, not walking through damaged geometry, held input or multiplayer.

093115 ordinary Chat regression runs the regular game with all five successor addons, no WORKBENCH define or smoke fixture. The matching Chat header initializes MissionSystems, normal preparation reaches PRISON, and the real sole local controller receives a living canonical prisoner. Ready-state observation and owned cleanup complete with zero captured errors and matching launch/stopped addon bytes. The diagnostic noSplash path and standalone round-local identity are explicit. This production-source startup includes the prison correction, but excludes WORKBENCH flight probes; it does not qualify full ordinary escape, normal splash/input, remote identities, multiplayer or FPS.

For the six newly checked 091306/091641/092237/092512/092923/game093115 archives, console hashes match runner metadata and launch/stopped source-manifest bytes and recorded digests match. Existing mortar-expiry, scoped-station, genuine-perception HQ and companion-restart entries above are retained rather than duplicated. All seventeen release cases and current-source clean runtime remain pending. The active 208-candidate/whole-aircraft-footprint flight experiment and private courier draft have no runtime qualification in this checkpoint. The deterministic source handoff tool produces labelled editable development ZIPs only; it is not native packaging or publication.

093319 enlarged flight-clearance refusal compiles the 208-point refinement with enlarged clearance, but stops before creating a fixture aircraft: three candidates fail minimum terrain, 182 fail slope and 23 fail the entity-clear cylinder. The best terrain delta is 0.0999985 m; no candidate reaches the swept-box or measured aircraft-footprint check. The archive retains 51 preceding assertions, two explicit fixture failures and zero completions. Console and launch/stopped source-manifest hashes match runner metadata, and both source manifests have identical bytes. A subsequent draft adds 169 airport-grid candidates after the local 208, for 377 total, and adds native-input diagnostics; its runtime result remains pending. This updates the preceding active-draft description without relabelling that earlier checkpoint. No powered flight, native control callback, real fuel use, multiplayer or FPS result is established.

093749 flight initialization finds airport candidate 213 in the bounded 377-point survey, with all terrain/clearance requirements retained, then creates one fixture aircraft and its empty group. It fails the immediate compound native simulation/seat/fuel check after 53 preceding assertions. The later bounded native-component polling correction is separate; no engine start or flight is established.

094021 courier compile failure identifies the reserved Enforce parameter name owned; 094317 courier compile failure identifies incompatible reference-array specialization in Batteries.Copy. The parameter is renamed and enumeration uses explicit clear/insert. Cascading errors remain in both original archives rather than being filtered. Neither run reaches gameplay.

094436 courier setup compiles the finite courier production implementation and verifies 27 original crew shells plus twelve distinct physical cache shells. It creates three empty fixture stores, then refuses the fourth obstructed fixed point before moving any original ammunition. The 51 preceding assertions are retained with both fixture failures and zero completions. A later bounded search for five clear stores is a fixture correction; this archive proves neither collection nor delivery.

094843 flight seating again finds the safe airport candidate, creates one aircraft/group, and observes its native controller, valid simulation, fuel manager, 1938.75 fuel and seventeen compartment slots after initialization. It selects the empty primary PilotCompartment and accepts one pilot allocation. The subsequent combined ownership/seating/ground-settling gate does not complete within thirty seconds, retaining 55 preceding assertions and two failures. Individual predicate diagnostics are required before changing behavior. Measured footprint, input callbacks, engine start and powered flight remain unproved.

095513 finite mortar courier passes 154 native assertions with zero captured errors. The bounded fixture survey finds five native stores after fourteen candidates and physically sequesters all 27 original crew shells, retaining their identities. The production low-ammunition observation traverses actual uplink/HQ/downlink; the original western patrol collects existing cache shells, its original bearer walks more than 100 m, and the empty battery receives exact original depot entities. The same immutable status remains fresh at delivery. Completion releases the HQ reservation and resumes the original patrol; all original forces and all twelve finite cache shells retain exactly one physical owner. No artillery firing, synthetic target report, force spawning or ammunition replacement is used. This is a local arranged depletion fixture, not ordinary player play, full stock exhaustion, interrupted courier loss or multiplayer acceptance.

095950 flight occupancy diagnostics retains the seating failure while identifying its predicates: the owned living pilot belongs to the expected group, the active primary seat matches, and the aircraft is settled/ready, but that seat is empty and the pilot has no vehicle. The group unexpectedly contains six agents after queued native initialization. Installed source reveals the supposed empty USSR base group authors six default members and queues their creation, so the immediate zero-agent snapshot was insufficient. A memberless vanilla group and explicit owned pilot activity correction require a fresh run; no powered flight is claimed.

100148 prison action boundary passes 67 native assertions with zero captured errors. Direct PerformAction calls with the original guard and canonical prisoner cannot open the locked native gate or advance progression. Actual native gate destruction, missing initial registration refusal, far-displacement/outside-only rejection and the bounded physical crossing then pass. The same run checks rough/exact coordinate storage on one native discovery marker. It precedes the disabled-marker cleanup and later identity fault-injection/casualty maintenance changes. Body movement is scripted; no walking, held input or multiplayer claim.

100422 one-pilot/input diagnostic establishes one living native AI pilot physically occupying the single owned fueled helicopter, with both native preparation hooks and later control-application observations. The group correction avoids queued default soldiers. Stage 2 refuses the assumed signed collective minimum: a written -1 reads back as 0 while Direct mode is active. The simulation's documented internal-physics transform remains identity and is unsuitable for world-space altitude/drift. The next fixture revision maps its bounded signed feedback demand into native [0,1] and reads the actual aircraft entity world transform, retaining all envelope, drift, altitude, contact and landing limits. No engine start, takeoff or powered flight is established by this failure.

100619 integrated Core regression passes two complete escape/restart rounds with 612 native assertions and zero captured errors. Each round proves canonical-actor fault rejection at normal unlock, held targeted-document rejection without spending/discovery, immediate successful recovery after exact restoration, coarse-to-precise native marker coordinates, actual disabled-list cleanup and duplicate deletion safety. The existing finite stock, objective presentation, unconsciousness/recovery, radio interruption, extraction/result and restart sequence remains successful. The roster mismatch is synchronous explicit fault injection, while travel/extraction are scripted; this is not ordinary manual play or remote identity/reconnect qualification. Casualty pending maintenance compiles here but its empty-server timing remains covered by the actual-method harness rather than a real disconnect session. The subsequent flight-only world-pose/collective revision requires its own compilation evidence.

101342 native engine and rotor test passes the complete measured airframe/rotor envelope (110 entities, 93 meshes, 74 zones; radius 27.6823 m) inside the unchanged cleared pad. One occupied native pilot starts the engine through one normal request; actual rotor speed reaches 196 and fuel falls from 1938.75 to 1937.33. The run then fails when horizontal displacement reaches 9.223 m, beyond its unchanged 8 m limit. Crucially, matched-sequence input diagnostics show positive collective/cyclic demands overwritten to zero before native application; rotor signals agree. The earlier negative-input finding was therefore not proof of a complete numeric-domain diagnosis. This source proves engine/rotor/fuel operation, not controlled takeoff, hover, landing or an HQ aircraft driver. A final-callback correction and independent positive rotor-signal check require fresh native evidence.

101611 integrated companion regression passes two complete companion-loaded escape/restart rounds with 96 native assertions and zero captured errors, with station teardown diagnostics disabled. It includes finite courier production, prison direct-action/crossing corrections, canonical unlock/discovery guards, coarse discovery markers with culled-list cleanup, and casualty pending-ticket maintenance. The separate flight experiment is opt-in and unused. The subsequent OnApply flight callback revision and later ordinary-game controls need their own source-bound qualification. This is scripted local integration, not manual gameplay or multiplayer acceptance; the historical catalog failure remains retained.

102037 casualty-service regression passes 101 native assertions with zero captured errors. The actual incapacitated local player remains canonical; an explicitly disclosed helper-only membership adapter permits the arranged NPC rescuer. Real seat contention, a spawned line-of-sight obstacle, completion-time rejection, the native owner handshake, one physical loading operation, released reservation and idempotent Stop all pass with the new pending-maintenance callback installed. The unadapted helper is rejected both before and after entering extraction. This does not simulate a real remote rescuer or last-client disconnect. Empty-population lease expiry remains qualified by the actual-method regression harness, while the live normal loading/cleanup path is covered here.

102235 final-callback flight refusal compiles the sole OnApply input writer and repeats the physical footprint, occupied pilot, normal engine/RPM and fuel observations. Its mandatory positive-input stage refuses to begin climb: five fresh observations over 2.5 seconds show requested collective 0.05 and 15/30/45/60/75 real apply callbacks, while the native main-rotor collective signal remains zero. Immediate context write/readback is insufficient evidence of consumption. No height/drift/tilt guard is relaxed and no flight success is claimed. Further work must use an evidenced native input interface rather than tuning gains around unconsumed commands.

102533 vanilla-only ordinary startup loads exactly the two installed engine/ArmaReforger addons with the regular executable, a fresh separate disposable profile, no successor path/GUID/helper and no noSplash option. It reproduces the initial IntroSplashScreen unknown SCR_WidgetExportRuleRoot error, then reaches the vanilla main menu. The failure remains latched despite menu initialization; hidden/muted process cleanup is confirmed. This isolates that initial splash error from successor mission code in the installed environment. It does not reproduce the separate scenario-reload splash, prove normal visible input, or qualify any successor mission/release requirement. The retained successor manifest is explicitly unused provenance bookkeeping.

102737 ordinary companion startup runs the regular executable with all five successor addons and no Workbench defines or smoke fixture. The expected Chat header/MissionSystems initializes, preparation reaches PRISON, and the real sole local controller receives a living canonical prisoner. Fifteen seconds of stable readiness, zero captured errors, unchanged addon source bytes and owned cleanup are verified. The scoped diagnostic noSplash workaround and standalone round-local identity remain explicit; the separately archived vanilla control reproduces the initial splash error without this mod. No normal visible splash, input, full ordinary escape or multiplayer acceptance is inferred.

103025 checkpoint companion regression repeats two complete companion-loaded escape/restart rounds, 96 native assertions and zero captured errors on the exact source shared with casualty regression 102037 and ordinary Chat startup 102737. Teardown diagnostics remain disabled, and the opt-in failed flight experiment is inactive. This source qualifies the development clean-runtime checkpoint; all seventeen release acceptance cases remain pending. A subsequent experimental actor-local flight-input branch must invalidate current-source qualification until separately tested.

104048 actor-local flight refusal compiles the optional upstream action path and proves the supplied manager is the exact pilot agent manager, distinct from the global manager, with HelicopterContext active. It fails before engine start with zero virtual writes. 104256 context diagnostics then records four callbacks where ActivateContext returns false while IsContextActive is true, with valid timestep/input/simulation. The fixture incorrectly required both activation return and active state; no meaning for that return was documented. The correction queries existing active state first, activates only when inactive, and requires observed active state before any writes. Native action consumption and physical flight remain separate mandatory gates. Both failures remain retained.

104438 consumed-input takeoff proves the corrected actor-local action path reaches native collective/cyclic inputs and existing rotor signals. The mandatory0.05 collective gate agrees on distinct ticks; the same aircraft takes off using real thrust, reaches5.318m above its settled origin and consumes finite fuel. It then fails the unchanged8m horizontal-drift bound before stable hover or landing. This is meaningful native input/takeoff evidence, not a flight-controller acceptance or production HQ aircraft integration. Further work requires motion telemetry and controlled stabilization under the same physical bounds.

105226 flight motion diagnostic repeats real input consumption and takeoff with read-only velocity, acceleration, angular-rate, basis and native rotor-axis observations. The same airframe reaches6.8385m and fails at8.00134m horizontal displacement; lateral velocity has already begun reversing. The native rotor-axis API is documented in local space but is not itself a measured thrust direction. No hardcoded rotor trim or safety-bound increase follows from this trace. Spectator guidance compiles in this Core run; ordinary hint rendering and input remain unqualified.

104634 first private native packaging attempt copies validated authored Core source into a fresh private session. Workbench prints Packaging project successful and naturally returns0, producing data.pak, addon.gproj and resourceDatabase.rdb. However, native shutdown reports UI resource leaks and Gamescope remains alive until the original runner's300s deadline. Cleanup is confirmed and both captured repository/copied authored bytes remain unchanged; the attempt is a failure, not a release build. Independent read-only inventory finds107 packed entries byte-identical to all107 captured Core source files after metadata/project exclusion; this validates content correspondence, not packed-only engine loading or the noisy build.

105441 full-salvo refusal compiles the complete eight-round observer and preserves the original27 physical HE shells. A single explicit inert-target observation travels through real uplink, HQ and downlink; the same battery commits and launches two distinct physical projectiles. Its immutable report then reaches60s age and firing correctly closes without a third launch. The strict full-salvo case fails, while the refusal remains consistent with stale-report policy. Audit confirms fresh later HQ contacts currently have no downlink path into an already active battery; implementing an explicit fresh-report update path is separate from weakening timestamps or inventing observations.

105709 flight damping experiment increases only velocity damping0.3→0.6. It again consumes actual controls and fuel, and reaches roughly9m altitude. It later oscillates horizontally and exceeds the unchanged flight envelope; no stable5s hover or landing passes. Higher outer-loop damping alone is insufficient with the observed native attitude response. This remains opt-in WORKBENCH investigation, never a production aircraft controller.

105949 silent packaging attempt repeats native Core packing with documented-wbSilent, retaining actual successful packing messages and natural native exit0. The corrected runner now distinguishes native completion from its remaining owned display wrapper and confirms cleanup without a timeout. Native UI resource-leak errors still occur, so the attempt remains failed; silent initialization does not solve that environment issue. All captured source bytes remain unchanged.

110404 empty-addon packaging control contains only the five owned project descriptors, with no successor scripts, worlds, compositions or UI resources. The same installed native packer naturally exits0 and repeats the UI resource-leak shutdown errors. Its private input repository remains unchanged and cleanup is confirmed. This isolates the shutdown symptom from successor payload content in this environment; it neither clears the earlier errors nor qualifies a build, mission, package consumption or release.

110127 first packed-only startup mounts only the expected packed successor/vanilla inputs with no native errors, but the runner rejects the engine's exact $profile:../addons/ search alias and stops before readiness. The corrected verifier resolves only that literal alias to the captured private profile's addon directory and rejects traversal/other aliases; the failed run remains latched in its archive.

110729 packed-only ordinary Core startup passes after the verifier correction. The regular executable loads exactly engine Core, vanilla ArmaReforger and packed successor Core, with exact package/database paths, normal non-Workbench modules and no loose successor or original addon. The actual Core scenario/MissionSystems reaches PRISON, equips the real local canonical prisoner, and remains ready for15s with zero captured errors. All3runtimeartifact bytes and sealed console hashes are preserved in the independent archive; ownedcleanup isconfirmed. This proves consumption of that specific native package despite its separately retained packaging shutdown errors. It does not qualify current later source, manual gameplay, full escape, multiplayer or release.

19 September — packaged closure and mortar completion

The five-addon packaging archive retains all authored inputs and fifteen runtime artifacts. All147 PAK entries match captured source, but all five native packer invocations retain the same UI shutdown errors as the empty control and remain unqualified. Packed Core ordinary startup110729 is a separate successful artifact-bound check.

The fresh-report salvo initially fired all eight rounds but failed natural completion at 111915. Native activity terminal events can be followed by a reset polled state; the exact-activity/order event latch now preserves the terminal event and detaches before cancellation cleanup. The 112900 rerun passes 55 assertions with zero captured errors, three delivered refreshes, eight actual launches, nineteen original shells remaining and 25 seconds without replay. The expiry classification failure110955 and immutable-report expiry105441 remain retained.

Powered flight112320 refused before engine start because native autohover also changed collective. Manual angular damping112502 held horizontal drift below 8 metres but still exceeded the unchanged 18 metre height limit. Both failures are retained; hover/landing and operational HQ aircraft remain unqualified.

The 113315 packed Chat ordinary startup succeeds with all five 111731 PAKs, exact seven loaded addons including engine/vanilla, fifteen unchanged artifact files, canonical prisoner and 15 seconds ready; zero captured errors and owned cleanup confirmed. Its separate packed provenance does not qualify later loose-source edits or waive packaging shutdown errors.

Powered flight114504 passes81 assertions with zero captured errors using proven signed actor-local collective plus native autohover. Same physical aircraft/pilot, native fuel use, five-second hover, two-second ground-contact landing and engine-off check; rotors still coasting. Translation, full HQ aircraft service and multiplayer remain separate.

Current mortar expiry and Intel registration

114751 passes 48 assertions and zero captured errors, preserving fresh native commitments and withholding after report expiry with the correct journal reason. 115232 passes 46 assertions and zero errors: all four original mortar crew have undergone the existing Intel carrying roll after readiness, before the fixture exercises physical inventory depletion/loss. No document is forced and no carrying probability is changed. These remain scripted local checks, not multiplayer acceptance.

Bounded physical translation

120245 passes 85 assertions with zero captured errors. The same finite aircraft and AI pilot take off using consumed actor-local actions and native autohover, approach a frozen target four metres from the initial hover, remain within 0.75m for five seconds, then land and stop the engine. Actual final displacement is about 3.62m, within the declared target tolerance. The original home, 8m drift bound, 18m ceiling, tilt limits and cleared column remain unchanged. No position/velocity override or replenishment is used. This is an isolated mechanism; route support, fully stopped rotors and real multiplayer remain unproved.

Shared map replacement ownership and deletion

120633 passes 58 assertions with zero captured errors. Real delayed callbacks, distinct/reused native configurations and root widgets, ModeClear and spare/interrupted deletion preserve the replacement native map. The earlier 115646 refusal assumed component references disappeared in the deletion call. Actual diagnostics show both post-super callbacks and entity invalidation occur immediately, while component references clear on the next tick. The corrected bounded observation retains all cleanup requirements and the late-callback window. Native camera render state and multiplayer are not measured.

120808 companion loops passes two complete scripted rounds, 96 assertions and zero captured errors after the canonical participant, shared-map ownership, Intel readiness and bounded translation changes. This remains local scripted integration, not ordinary player input or multiplayer.

121730 ordinary prisoner view and 122353 yard candidate load all five addons in the regular game, admit the genuine canonical local prisoner and observe a clean readiness interval. Opt-in read-only screenshots show the actual authored prison and correct escape objective. Native BMPs plus lossless viewing PNGs and conversion hashes are retained. The single scale-three vanilla dirt decal clears a small central patch; most wheat remains. 123226 bounds diagnostic confirms native DecalEntity bounds collapse to its origin, so those values cannot qualify its projected surface extent.

122118 map/controller compile passes the 58-assertion map ownership regression with the new aircraft mechanism compiled. 123439 actual controller then exercises that actual production controller and post-spawn qualifier: 37 clean assertions, original finite Mi-8 and pilot, one engine start, sustained physical hover, settled contact landing and engine-off COMPLETE. This is distinct from the earlier Core-only experimental implementation.

124154 editor-camera attempt passes its underlying 48-assertion companion round, but does not obtain the requested overhead frame. The flag and branch marker are present; the screenshot remains a horizontal editor/game viewport. The ineffective diagnostic option was removed; neither its screenshot nor the zero decal bounds establishes yard coverage.

124915 actual airborne cancellation passes 39 assertions with zero captured errors. Cancel is issued once at 5.09m without ground contact. The same controller keeps its input callbacks, token and exact deadline through 13.15 seconds of landing; the fixture independently observes two stable grounded seconds before shutdown. Both native callback counts reach 908, with one original aircraft/pilot and finite fuel use. The terminal state is CANCELLED with engine off. No HQ dispatch, aircraft replacement, transform/velocity write, deadline extension, manual piloting or multiplayer is claimed.

125906 integrated ordinary startup compiles the new fixed-target controller, bounded active admission and action-denial feedback in the regular game. All five successor addons load, the real local canonical prisoner is admitted, the 15-second ready interval and private cleanup pass with zero captured errors. The unaltered player capture shows the correct objective and a larger irregular stock-scale dirt patch; some wheat remains. Actual-method tests cover the thirty-attempt admission boundary and unchanged interaction permissions, but the image does not prove those denial messages, held actions or remote UI.

130038 actual fixed-target flight passes 38 assertions with zero captured errors. The production StartTranslation freezes its target before takeoff; after native hover the requested horizontal displacement is 3.3096m. The original helicopter physically moves 2.91183m, holds near the target for five observed seconds, lands and shuts down 0.399235m from the target. One engine/controller/wake, finite fuel and 1,572 paired native callbacks are retained; 484 translation updates perform the movement. The original qualification home, token and absolute deadline never change. This does not qualify longer navigation, HQ dispatch or multiplayer.

130347 current Core completes two full scripted escape/restart rounds, 612 assertions and zero captured errors. 131041 current companion completes two rounds with 96 assertions and zero captured errors. Both source manifests are exactly equal to ordinary Chat 125906 and actual fixed-target flight130038. The clean-runtime development gate is passed for this source snapshot; all seventeen release cases, including player-input escape and real multiplayer, remain pending. Repository checks and the new native-statistics/dedicated-runner tests pass separately.

Current artifact closure and Linux preparation

The 1317 five-addon package audit verifies all 151 PAK entries against the 183 authored source files and all fifteen runtime artifacts against their reports. Every packaging runner remains failed with the same 25 UI shutdown errors as the empty control. Ordinary packed Chat 131942 then passes canonical prisoner startup and its fifteen-second ready interval with zero captured errors from only those artifacts and vanilla.

The authored-only Linux failure 131458 is retained: missing all five resource databases meant the listed addon identities did not establish script/resource loading. New runner preflight rejects that incomplete input before launching. The complete packed retry 132456 loads all five PAK/RDB pairs, compiles 5780 Game files and 11202 classes, loads Chat/MissionSystems and prepares seven sites, 117 stock entities and prison phase. All fifteen inputs remain unchanged. Four native errors remain, each also present in the older vanilla control; there are no script/VM-pattern failures. The isolated 90-second timeout and owned cleanup are recorded. No client joined; no clean Linux build, graceful shutdown, multiplayer or performance acceptance follows from this result.

Native game-over lifecycle correction

Vanilla administration could end the native round without traversing successor Transition, leaving services active until reload. The correction now cancels preparation/server/binding callbacks, closes services once before native restart, and preserves terminal escape identities. Unknown personal results use neutral wording. Preparing and active each pass two actual native-ended rounds with 21 assertions and zero captured errors. Core, companions and ordinary Chat then pass their normal regressions on the same 184-file addon snapshot. Native preparation/active tests do not arrange an in-flight preload or remote client. Packaging and all 17 release requirements remain separate.

Guidance, preparation feedback and fixed aircraft route

The preparation adapter now uses the native respawn loading-placeholder callback. 153525 retains the initial compile failure; 153905 compiles the correction and observes the actual failure title/body/parent/size and hidden spinner continuously for 17 seconds. Its deliberate setup error remains a failure. The Workbench screenshot is blank blue, so this does not prove ordinary-player readability. Guidance caches only hints accepted by native ShowCustom; rough radio intel now explains its 500 m search square and remaining discovery options.

Aircraft route 155909 passes 38 assertions / one completion with zero captured errors. The original helicopter and AI pilot physically travel 20.1261 m toward a frozen 20.2214 m destination, hold, land in contact and stop the engine with finite fuel; final error 0.129942 m. The 160 s route stage finishes with 4.64 s margin and the unchanged 240 s operation with 23.4 s margin. This is one unloaded experimental airport leg, not operational HQ support, repeated reliability or multiplayer. Initial compile 154851 and 90 s timeout 155105 failures remain retained.

Core 160849 passes two escape/restart rounds and 612 assertions with zero captured errors on the 192-file addon snapshot. Ordinary observer 160522 compiles that same snapshot and admits the canonical prisoner; the opt-in read-only sampler reaches READY and completes 391 samples over 45.014 s. No input is sent and inventory transitions are not observed. The overall run remains failed because the independent display-ownership check rejected Proton’s trailing-slash WINEPREFIX.

The corrected prefix comparison also detects old private-test device helpers previously missed by exact byte equality. Active-prefix refusal proves the strengthened check refuses a live Workbench. Historical cleanup claims based on the earlier comparison do not establish that the entire disposable prefix was empty; the native logs and source snapshots remain unchanged. Current cleanup qualification is recorded separately.

Companion regression passes two rounds / 96 assertions on the same 192-file snapshot as Core 160849 and aircraft 155909. Ordinary Chat passes actual canonical-prisoner startup, read-only sampler completion and private game-window ownership with zero captured native errors. No external input is sent. The new cleanup path confirms the disposable prefix is idle after both runs; the earlier 19 orphan device helpers were separately cleared under the prefix lock using verified process identities and pidfds. Current source/local runtime qualification does not promote any of the 17 release cases.

First ordinary input and inventory failure

The explicit private keyboard helper sends only a brief W pair and two Tab pairs after fresh native READY, with ownership/focus checks before every event, confirmed releases, independent worker supervision and parent cleanup. 164944 retains the initial release-state refusal and lost original error; later helper changes preserve separate supervisor diagnostics. 165512 proves real inventory opening before two GUI slot errors trigger cleanup.

165832 keeps the same errors under an explicit 10-second diagnostic grace. All six events complete, native movement reaches 2.62 m, inventory opens/closes, and later native forward/movement inputs are neutral. The 45-second sampler is truncated, so the full exercise remains failed. The open-labelled screenshot shows the prior world frame; inventory presentation is not proved. The source trace identifies two incompatible vanilla LayoutSlot calls against the GridWidgetSlot child; a standalone vanilla control remains pending. The clean-runtime development gate is returned to pending, while prior Core/companion/startup checkpoints remain intact. All 17 release cases remain pending.