EscapistsReintroduced/docs/evidence/playtest-refresh-2026-10-02-transfer-fixes/package-helpers/proposed-docs-source-only/current-status.md

Current development status

Pending transfer-fixes source checkpoint: The sealed snapshot at .build/playtest-source-2026-10-02-transfer-fixes contains 420 authored files.

This snapshot includes the radio-hop interruption checks, cancellation guards for finite supply transactions, and the deleted-mortar-shell settlement fix. Earlier terrain/admin integration and bounded HQ travel-history planning remain included.

Verification is pending. This preview makes no passing-suite, native-route or packaged-startup claim.

Packaging did not complete; the explicit refusal/block evidence is preserved in the finalization record. The previous runtime handoff remains the latest candidate. No native process is left waiting to launch; continuation must recheck host-visible idle state.

Qualification covers this frozen snapshot, not later live edits. Physical resupply/interception, manual UI behavior, complete human escape, real multiplayer/JIP/reconnect/twelve-player play, comparative FPS and a clean release remain unverified. Existing packages and original missions remain unchanged.

2 October 2026 — deleted mortar shells no longer block the battery: a shell deleted during an accepted transfer now settles as a failed loss. The battery can consider its remaining physical shells; surviving items with uncertain custody remain quarantined, with no refund or retry. Four focused regression programs pass, including actual transfer and battery pending methods. Independent testing reproduces the baseline failure. No native or multiplayer run was made for this change, and existing packaged/source checkpoints predate it. Fix and verification.

2 October 2026 — interrupted radio hops and cancelled supply transactions stay stopped: HQ radio routes now validate both carriers and the existing range rule on each observed sending tick. A carrier losing its radio, consciousness or ownership, or a receiver leaving the link, cannot recover before the deadline and complete that interrupted hop. Delivery and route advancement still wait for the original deadline; radio capability caching remains unchanged.

Mine resupply, mounted-ammunition pickup and mounted-magazine exchange now preserve cancellation and recheck authority after native submission. An inline callback can no longer turn a stopped or captured transaction into a successful delivery. Committed stock remains spent, and late exact movement can settle uncertainty without a retry or refund. Existing physical-access checks and trace budgets remain intact.

Eleven focused regression programs pass on the changed source. Independent actual-method tests reproduce the old failures and pass with the fixes. Native boundaries are doubled in those tests; no engine session was launched for this increment after detecting an existing Reforger session, which was left untouched. Physical supply, real multiplayer and performance remain unverified. The prior runtime package and sealed source checkpoint are preserved and predate these fixes; refresh the source snapshot before packaging the latest implementation. Changes, tests and preservation.

2 October 2026 — gameplay-fixes source verified; new runtime package deferred: the sealed editable source contains 420 authored files and passes 290 registered regression programs. The confirmed normal Everon route completes 63 assertions and one round, with zero script/runtime failures and 13 retained engine errors.

The snapshot includes the rifle-supply callback cancellation guard, bounded HQ road-survey fairness, and inherited terrain/admin-item integration. These are source inclusions; manual UI behavior, physical resupply/interception, complete human escape, multiplayer and comparative FPS remain unqualified.

Packaging was refused before creating its session because an existing Reforger session was detected. It was left untouched, and no new runtime candidate was produced. No native process was left waiting to launch; continuation will recheck host idleness before packaging. The latest existing playtest package remains unchanged. The first normal-route cleanup refusal (a transient compiler process could not be classified), successful retry and package refusal are all retained with source bindings and review. Strict failures are not waived.

2 October 2026 — cancelled rifle resupply stays cancelled: a synchronous native inventory callback could move the magazine while cancelling the transfer, capturing its donor or changing ownership. Rifle transfers then skipped the guards used by launcher transfers and could record a successful delivery. Both modes now recheck terminal state and authority after submission. Submitted items remain spent; late physical arrival can settle uncertainty without counting a delivery or permitting another attempt.

Four focused regression programs pass for the current source, including the actual transfer and coordinator, shared finite reservations and convoy budget admission. Independent tests reproduce the old failure and pass with the correction; a mutation also demonstrates the ownership guard. No new engine or multiplayer run was made for this two-line correction. Fix, tests and preservation.

The earlier 415-file frozen source now completes 288 registered programs across resumed verification: 233 unchanged passing records plus 55 freshly passing programs. Preserving an inactive task-owned temporary snapshot elsewhere, with every file verified and its old path retained, freed the required temporary quota. Earlier failed attempts remain archived. This finishes that snapshot's checks; it is not a full-suite result for the current 417-file source. Existing missions, inherited work and the previous development package are unchanged. Physical interception, manual escape, real multiplayer, comparative FPS and release qualification remain open.

2 October 2026 — fair bounded HQ road surveying and an opt-in physical interception witness: HQ road surveying now rotates through delivered tracks while retaining the existing two-survey limit. Previously, the first two eligible tracks with blocked road candidates could consume every pass and permanently starve a later usable track. The actual-method regression fails before the change and passes afterward; independent review confirms the bounded cursor and unchanged radio, force-claim and expiry policy.

Resumed verification retains 233 passing programs against identical frozen input hashes and attempts 1 fresh suffix program; the current resumed result exits 1 after 234 total recorded programs. Complete passing verification remains unestablished. The initial deadline-test adapter failure, later /tmp quota failure and rejected alternate-directory attempt remain archived. Resumed temporary files use /tmp; no production/native source changed for this resumption. The final canonical /tmp retry stops in test_native_package.py with disk-quota errors (Errno 122); the remaining suffix is unverified. No full-suite pass is claimed. The bounded native run records 33 assertions, 0 completions, 2 script/runtime failures and 15 retained engine errors; runner result: test-failed. It does not establish the complete physical interception sequence; preserve the failed or incomplete result and its raw logs. The canonical convoy admission assertion failed before the interception stage; no physical interception was exercised and no admission policy was weakened. Cleanup confirmed: True. Strict engine errors are retained. A separate normal-route run of the same source records 63 assertions, 1 completion, 0 script/runtime failures and 13 retained engine errors; runner result: smoke-completed and cleanup confirmed: True. This ordinary route does not validate physical interception.

The opt-in Workbench witness uses two synthetic observation positions in an original soldier’s local inbox. Radio hops, HQ memory/planning, the original escort and physical AI movement remain production paths. It is not natural detection, a human escape, multiplayer, interception effectiveness, FPS or release qualification. No vehicles, crew or stock are created by the new interception stage. The separate HQ-memory/menu-fix development package is unchanged and predates this survey correction and opt-in witness. Concurrent terrain work and older evidence remain preserved. Source, regression, native and independent-review evidence.

2 October 2026 — corrected HQ-memory/menu-startup development handoff: separate package and editable source. 409 authored files, 351 exact PAK payloads and three runtime files match editable source and handoff.json.

A startup guard now skips automatic terrain takeover in mode-less menu worlds; ordinary supported scenarios and unsupported-mode diagnostics keep their existing behavior. This snapshot includes observer recovery/defeat guidance, finite resupply of supported reloadable launchers, and one original armed convoy escort receiving a radio interception order ahead of delivered player travel history. Earlier finite logistics, controller ownership and authored discovery/mine-warning map presentation remain included. The frozen snapshot includes the earlier parallel task’s automatic terrain takeover behavior; newer concurrent terrain-name/presentation edits remain in the live workspace and are not in this package; this handoff’s fresh scripted route targets Everon.

The exact source passes 285 registered regression programs and the fresh normal escape fixture completes 63 assertions and one round, with zero script/runtime failures and thirteen retained engine errors. Fresh ordinary startup of this exact package verifies the normal mission and local prisoner with zero script/runtime failures and 17 retained engine errors. Strict packaging/startup failures remain recorded.

The initial HQ-memory candidate and its one script/eighteen engine errors remain retained; this corrected package includes the demonstrated menu-world guard. This is an unqualified development candidate. Physical launcher delivery, native interception movement/holding/rejoining, a complete human escape, real multiplayer/JIP/reconnect/twelve-player play, comparative FPS and a clean release remain unverified. Historical standard-map visual checks do not prove physical held-map rendering or current remote UI behavior. No new native flight or prison-input experiments are included. Previous packages, original missions and inherited work remain preserved; nothing was committed or published. Package hashes.

2 October 2026 — HQ motorized interception implemented in source: one original armed UAZ convoy escort can receive a radio command to hold a road ahead of remembered player travel, then rejoin its convoy. Orders use delivered history and complete original-formation status, share force limits, expire on a fixed deadline and cannot spawn replacements or compete with logistics. Behavior and limits.

All 285 registered regression programs pass. The hidden/muted final-source normal escape passes 63 assertions and one round, with zero script/runtime failures and thirteen retained engine errors. The initial missing-hook compilation failure and test default-path failure are preserved with their fixes. Implementation, review and preservation.

Native driving to the intercept, physical holding/rejoining and interception effectiveness remain unverified; the normal escape run proves compilation and base-loop integration only. Human play, real multiplayer, comparative FPS and clean release remain pending. The existing 416-file playtest package is unchanged and predates this increment. Original missions and inherited work are preserved; nothing was committed or published.

2 October 2026 — recovery warnings and finite launcher resupply: unconscious spectators now receive the already-replicated recovery, reconnection or thirty-second defeat warning. Hints refresh when that information changes and clear on awakening. HQ can also arrange supply for a reported empty, supported reloadable launcher using original compatible truck stock, after rifle and mounted demand. Disposable launchers remain excluded. Implementation and review.

All 283 registered regression programs pass. The hidden/muted observer fixture passes 29 assertions, including accepted recovery text and clearing on wake; the final-source normal escape passes 63 assertions and one round. Both have zero script/runtime failures and thirteen retained engine errors, with confirmed cleanup. The observer run predates the four AI changes but uses exactly the final observer/probe code; the normal route binds all 407 final authored files.

Actual launcher transfer/reloading, full human play, multiplayer and comparative FPS remain unverified; no release qualification is claimed. The existing 416-file playtest package predates these changes and is unchanged. Original missions and inherited work are preserved; nothing was committed or published. A separate motorized-interception proposal remains design-only.

2 October 2026 — current package checked on an isolated Linux dedicated server: the unchanged objective-map playtest loads its exact ten-addon closure, compiles Game scripts and reaches the normal Everon prison phase. The empty server stays under observation for fifteen seconds afterward; there are zero script/runtime failures and eleven retained engine errors. Raw evidence and independent review.

This is packaged dedicated startup, not connected-client, multiplayer, complete-escape, performance or release qualification. The private supervisor stops its own server with SIGTERM after 72 seconds; graceful shutdown is unproved. Network/PID isolation, no display/audio, cleanup and unchanged package/external inputs are recorded. Three bounded gameplay reviews found no demonstrated defect; no production code changed. All 407 authored files, 416 candidate files, 533 original reference files and 70 inherited unstaged paths remain unchanged. The prior 283-program pass still covers identical source. Preservation.

2 October 2026 — objective-map playtest package refreshed: the new separate development handoff contains the authored discovery/mine-warning UI alongside the earlier controller ownership, HQ and logistics work. 407 authored files, 349 exact PAK payloads and three runtime files match editable source. Artifact hashes.

The unchanged source retains its 283-program regression pass, 101 map-fixture assertions and 63-assertion normal escape route. Fresh ordinary startup of the exact package verifies the normal mission and local prisoner, with zero script/runtime failures and seventeen retained engine errors. Strict packaging/startup failures remain; this is not a qualified release. Shared-map evidence remains geometry-only, with physical held-map capture unverified.

Three bounded parallel reviews of base radio/extraction/guidance, map lifecycle and intel/loot ownership found no demonstrated new defect; no production code changed for this packaging increment. All native work stayed hidden/muted with confirmed cleanup and unchanged inputs. Original missions, existing working changes and the previous 412-file candidate are preserved; nothing was committed or published. Review and preservation. Human play, real multiplayer, physical logistics, comparative FPS and clean release remain unfinished.

2 October 2026 — independent objective map UI integrated: discovered sites and recovered mine warnings now use authored UI outside the native player-annotation lists. Stable rough positions, exact identification, pan/zoom culling and close/reopen cleanup remain intact. Supported standard-map and shared-map containers replace the rejected Canvas parent. Player annotations and their restrictions are unchanged. Implementation and limits.

All 283 registered regression programs pass. The final hidden/muted map fixture completes 101 assertions and one completion, and the normal escape route completes 63 assertions and one round. Both record zero script/runtime failures; 16/13 engine errors and strict failed verdicts remain. Earlier compile, Canvas-parent and asynchronous-close fixture failures are retained.

Read-only private-window captures show the standard question/radio glyphs, reopened marker and long-warning text at the small Workbench viewport. Shared-map checks establish widget geometry/lifecycle only: its disabled render target does not appear in screenshots, and physical held-map capture remains unverified. Review, raw captures and preservation.

Source contains 407 authored files. The existing owner-fixes playtest is unchanged and predates this increment. Original missions and inherited work are preserved; nothing was committed or published. Human play, manual map interaction, real multiplayer, physical logistics, comparative FPS and clean release remain unfinished.

2 October 2026 — development package refreshed with controller ownership fixes: the separate owner-fixes handoff now includes the tested observer/rebinding and chat-menu cleanup corrections alongside the earlier ground-depot/guide features. 403 authored files, 346 exact PAK payloads and three runtime files match editable source. Artifact hashes.

The unchanged source retains its 280-program regression pass and 63-assertion normal escape. Fresh ordinary startup of the exact package verifies the normal mission and local prisoner, with zero script/runtime failures and seventeen retained installed-resource errors. Strict packaging/startup failures remain; this is not a qualified release. The earlier route retains thirteen installed-resource errors.

All native work stayed hidden/muted with confirmed cleanup and unchanged inputs. Original missions, 61 inherited unstaged paths and the previous 412-file candidate are preserved. No production code changed for this packaging increment. A separate authored map-overlay proposal is not included. Human play, real multiplayer, native controller replacement, physical logistics, comparative FPS and clean release remain unfinished. Independent review and preservation.

2 October 2026 — old chat callbacks preserve the current administration menu: a retained former local controller now removes only its own chat listener and timers; it cannot close a replacement controller's newly opened panel. Current-owner shutdown and mission-change cleanup remain intact. Independent actual-method tests compile and reproduce the old failure, then pass with the ownership check; all 280 registered regression programs pass.

The hidden/muted normal escape completes 63 assertions and one round, with zero script/runtime failures, thirteen retained installed-resource errors, confirmed cleanup and unchanged source/external inputs. This is compilation and ordinary scripted-route evidence, not native controller-replacement or multiplayer qualification. Review and preservation. Original missions, inherited changes and the existing 412-file playtest are unchanged; that package predates the observer and chat ownership fixes. Human play, real multiplayer, physical logistics, comparative FPS and clean release remain unfinished.

2 October 2026 — partial-clue loss recovery checked on current source: the hidden/muted fixed-site fixture passes 76 assertions and one completion. After ordinary partial discovery and deliberate loss of all four targeted documents, distant, unauthorized and obstructed observations remain rejected; a clear close approach identifies the radio once and permits entry into radio defence without replacement clues. This uses the existing LegacySites test catalog, teleports, damage protection and direct mission interfaces, then explicitly ends the round. It does not prove generated-site coverage, held interactions, defence completion or a full escape.

Zero script/runtime failures, thirteen retained installed-resource errors and confirmed cleanup; source and external inputs remain unchanged. Three bounded parallel gameplay reviews found no demonstrated new defect. No production changes or package refresh were made; the previous 279-program pass covers identical addon source. Original missions, 61 inherited unstaged paths and the existing playtest are preserved. Review and exact limitations. Human play, real multiplayer, physical logistics, comparative FPS and clean release remain unfinished.

2 October 2026 — spectator callbacks respect local controller ownership: a retained old controller can no longer restore its old body camera, close the current editor or create a new spectator view after replacement. It stops only its own monitor and releases its owned presentation state. The existing binder keeps watching for a replacement controller and starts its monitor once, retaining normal stop/end cleanup. Independent actual-method tests reproduce the old fault and verify the corrected behavior; all 279 registered regression programs pass.

The hidden/muted unconscious-camera run completes 27 assertions and one round, preserving ordinary unconsciousness, both spectator views, tracking, pose-gap fallback, healing and repeated knockout. It records zero script/runtime failures and thirteen retained installed-resource errors, with confirmed cleanup and unchanged inputs. The first attempt used the wrong Chat fixture selector and failed because the general smoke also ran; that evidence is retained, and the runner now refuses that selector combination before native setup. This is normal camera integration evidence; native controller replacement and real multiplayer remain unverified. Review and exact limits.

Playtest instructions now open the actual combined Core project and point to the latest retained build. Original missions and inherited changes are preserved. The existing 412-file packaged candidate is unchanged and does not yet contain this observer fix. Human play, multiplayer, physical logistics, comparative FPS and clean release remain unfinished.

2 October 2026 — updated development playtest and objective-hint ownership fix: the separate ground-depot/guide handoff now includes recent finite camp loading, zero-stock engineer resupply, HQ count optimization and a correction preventing a retained old controller from displaying hints after local ownership changes. It contains 403 authored files, 346 exact PAK payloads and three runtime files, with matching editable source. Artifact hashes and strict limits.

All 277 registered regression programs pass; the guide regression independently fails on the old code and passes with the fix. The fresh source-matched normal escape passes 63 assertions and one round, with zero script/runtime failures and thirteen retained installed-resource errors. Ordinary startup of the exact package verifies the normal mission and local prisoner, with zero script/runtime failures and seventeen retained installed-resource errors. Strict packaging/startup failures remain; this is not a qualified release.

A bounded admission/reconnect source audit found no demonstrated additional bug. Guide fix and exact validation scope. Native controller replacement, human play, real multiplayer, physical logistics, comparative FPS and clean release remain unfinished. All native sessions stayed hidden/muted and cleaned up; original missions, 61 inherited unstaged paths and the prior 409-file candidate are preserved. Nothing was committed or published. Preservation and build review.

2 October 2026 — finite camp-to-truck ammunition loading: HQ can assign one available original camp responder to carry one exact original cache magazine to a nearby original ammunition truck after delivered radio orders. Recorded finite magazine expenditure gates admission; separate pickup/delivery proof, unchanged rounds, original identities and bounded reservations prevent refill or replay. Existing tactical/logistics work retains priority. Behavior and limits.

The full 277-program regression suite passed before native compilation. The first native run exposed getter formatting and a helper-name conflict; its failed evidence is retained. After those behavior-preserving corrections, all four relevant programs passed again. The corrected hidden/muted normal route completes 63 assertions and one round, with zero script/runtime failures and thirteen retained installed-resource errors. Cleanup and unchanged source/external inputs are confirmed. This qualifies compilation and normal-loop integration only. Independent review, mutation evidence and preservation. The existing playtest package predates this feature. Original missions, inherited changes and that package remain preserved. Physical loading, human play, real multiplayer, comparative FPS and clean release remain unfinished.

2 October 2026 — HQ planning removes repeated force counts: the final pursuit selection pass now counts global commitments once after cleanup/retasking/investigation and increments only for a newly queued order. Separate hunting/global limits, orders and reservations are preserved. A controlled 64-belief/128-unit no-dispatch regression reduces the repeated count scans from over 10,000 unit visits to 128; this measures that subpass only, not FPS.

All 273 registered regression programs pass. Independent review includes a compiled failing increment-removal mutation and 360 before/after order, reservation and cooldown comparisons. The hidden/muted frozen-source normal escape completes 63 assertions and one round, with zero script/runtime failures and thirteen retained installed-resource errors. Cleanup and unchanged inputs are confirmed. Scope and preservation. Existing missions, inherited changes and the prior packaged playtest remain preserved; human play, real multiplayer, physical logistics, measured performance and clean release remain unfinished.

2 October 2026 — finite replacement for empty designated engineers: HQ can now dispatch one existing convoy PMN4 to an original engineer whose startup designation and settled grant are recorded, using fresh complete delivered zero-stock reports. Unknown inventory does not count as empty; the same original actor and zero/one mode stay fixed through retries. Shared finite stock, spent items and unresolved cross-truck claims remain protected. No replacement mine is spawned and no mine-laying attempt is reset.

All 272 registered regression programs pass across a resumed run, with independent review and a compiled regression failure on the old planning method. The hidden/muted frozen-source normal route passes 63 assertions and one round, with zero script/runtime failures and thirteen retained installed-resource errors. This qualifies compilation and normal-loop integration, not physical mine delivery or placement. The initial temporary-quota failure, verified recovery and preservation evidence are retained. Existing missions, inherited work and the prior playtest package remain unchanged; the package predates this increment. Human play, real multiplayer, physical maintenance/resupply, comparative FPS and clean release remain unfinished.

2 October 2026 — casualty and terminal-lifecycle fixture corrected: the old death check incorrectly expected an ordinary protected prisoner to die. The repaired editor-only fixture first verifies living unconsciousness, then explicitly forces fatal loss on its exact registered actor to check spent-life spectator selection, native camera and all-dead defeat. Ordinary game/server casualty protection is unchanged. The native run passes 38 assertions and one round, with zero script/runtime failures and thirteen retained installed-resource errors.

All 272 registered regression programs pass across a resumed run, including the actual hitzone damage cap and deferred processing. Earlier failed native attempts and validation environment failures are preserved; the historical premature Workbench reload was not reproduced and remains unexplained. Tests stayed hidden/muted with confirmed cleanup. Original missions, all inherited working changes and the existing playtest package are preserved. Repair, independent review and exact limits. Human play, real multiplayer, physical maintenance/mine operations, comparative FPS and clean release remain unfinished.

1 October 2026 — automatic local restart and readmission verified: the current combined source completes two distinct scripted Everon escape rounds: first victory/results, inherited native world restart, fresh prisoner preload/admission, then the full second route and victory. The sealed native archive records 126 assertions, two completions, zero script/runtime failures and thirteen retained installed-resource errors. An independent raw-log review confirms separate world instances rather than duplicate completion markers. Sequence and preservation.

All 400 authored files match the existing convoy-stock candidate. Hidden/muted execution and cleanup are confirmed; original missions, inherited changes and the candidate are unchanged. This qualifies local automatic restart/readmission only: human play, death/spectators, exhaustive cleanup, real multiplayer, comparative FPS and clean release remain pending. No production code changed for this check.

1 October 2026 — refreshed development playtest candidate: the separate convoy-stock handoff packages the current combined successor: 400 authored files, 343 exact PAK payloads and three runtime files, with matching editable source. It includes the recent finite mine systems and loaded-truck inventory correction. Artifact hashes and packaging limits.

A fresh normal Everon route completes 63 assertions through extraction/results, with zero script/runtime failures and thirteen retained installed-resource errors. Ordinary startup of the exact package verifies the normal mission and local prisoner, with zero script/runtime failures and seventeen retained installed-resource errors. The existing 271-regression pass and 202-assertion mine-stock result match this unchanged source. Strict packaging/startup failure verdicts are retained; this is not a qualified release.

Radio-document recovery and restart cleanup audits found no demonstrated new bug; one stale historical fixture heading was corrected. The unexplained death/restart Workbench reload was not rerun or worked around. Full human escape, real multiplayer, mine transfer/placement, maintenance/mounted interactions, comparative FPS and clean release remain unfinished. All native sessions stayed hidden/muted with confirmed cleanup. Original missions, 61 inherited unstaged paths and prior candidates are unchanged; nothing was committed or published. Review.

1 October 2026 — loaded convoy sampling fixed; physical mine stock observed: native diagnostics identified deposited cargo exhausting the mounted sampler's shared 128-node queue. Separate structural/cargo budgets now preserve bounded inspection without misreporting cargo as mounted weapons. All 271 registered regression programs pass, including failing-before/passing-after cases and independent mutations of every budget guard. Fix and preservation.

The corrected hidden/muted native run completes 202 assertions and one fixture round, with zero script/runtime failures and thirteen retained installed-resource errors. One original automatic convoy contains two callback-proved inactive PMN4s, whose exact identities and physical custody remain unchanged through real mounted-ammunition radio delivery; 64 primary cargo callbacks also remain settled and unchanged. The earlier diagnosed failure remains archived. Both sessions have confirmed cleanup and unchanged inputs.

This establishes initial mine stock in one convoy, not walking resupply, mine transfer or placement. The prior field-update package is unchanged. Original missions and all 61 inherited unstaged paths are preserved; no commit or publication was made. Full human escape, true multiplayer, maintenance/mounted interactions, comparative FPS and clean release remain unfinished.

1 October 2026 — bounded convoy mine-stock check: the new optional read-only fixture preserves the original convoy/batch and checks exact PMN4 callback identities and physical custody around normal radio delivery. All 271 registered regression programs pass (counted from the current runner). Independent negative controls reject empty stock and missing callback proof. Review and preservation.

The single hidden/muted native run compiles and passes 39 assertions, then fails the existing ammunition-truck mounted snapshot completeness check before the mine assertions. Two test failures and thirteen underlying installed-resource errors remain recorded. Native mine insertion and transfer are still unverified. Source and external inputs are unchanged, cleanup is confirmed, and no second native attempt was made.

RHS: Status Quo, WCS Armaments and WCS BMP-1 remain declared dependencies. A separate installed-catalog/equipment audit found no reproduced automatic-equipment mine duplication defect. Original missions, inherited working changes and the packaged candidate are preserved. Human play, multiplayer, physical maintenance/mounted/mine interactions, FPS and release qualification remain unfinished.

1 October 2026 — finite mine top-up integration: HQ can now authorize one original truck PMN4 for an original carrier with exactly one usable mine, using fresh delivered status and the existing radio/rendezvous controller. Infantry and mounted ammunition retain priority. Startup grants must settle first; uncertain moves retain both claims so another truck cannot duplicate a late delivery. Behavior and limits.

All 268 regression programs pass. Independent mutation controls demonstrate the startup, one-mine entitlement and cross-truck quarantine guards. The hidden/muted native normal route from frozen source compiles and completes 63 assertions and one round, with zero script/runtime failures and thirteen retained installed-resource errors. This qualifies compilation/base-loop integration only; actual mine approach/transfer remains unverified. Review and preserved inputs.

Original missions and the existing packaged candidate are preserved. Concurrent automatic-equipment edits are retained; the first native run was invalidated by source changes, so the repeated check used a frozen combined-source copy. Its evidence does not silently qualify later source edits. No extra mine grant, stock refill or placement reset was added. Depleted-zero resupply, repeated placement, full human escape, true multiplayer, maintenance/mounted interactions, comparative FPS and clean release remain unfinished; the field-update package predates this source change.

1 October 2026 — finite optional convoy mine cargo: each original ammunition truck now attempts up to two PMN4s once, after its primary weapons and ammunition have settled. Separate callbacks keep ordinary stock initialization independent. Exact initial mine identities are frozen with ownership/custody checks; failures, late callbacks and looting never refill the truck. Behavior and remaining delivery work.

All 265 regression programs pass, including independent review and a failing mutation that attempts to adopt preexisting stock. The hidden/muted native normal route compiles and completes 63 assertions and one round, with zero script/runtime failures and thirteen retained installed-resource errors. This proves base-loop integration, not physical mine insertion or delivery. Evidence and preservation.

No original mission or inherited working change was altered. The existing field-update package is preserved and predates this source addition. A separate radio-to-extraction eligibility audit found no reproduced progression bug. Human escape, real multiplayer, physical maintenance/mounted/mine interactions, comparative FPS and clean release qualification remain unfinished.

1 October 2026 — carried mine capability reaches HQ: formation status now carries independent, bounded counts of exact inactive PMN4s from the original owned roster. Unknown inventory/custody stays unknown. Counts and completeness travel through the normal radio route, remain detached in delivered history and appear in the private HQ status journal. Mine scarcity alone creates no extra urgent call, task or replacement stock. Behavior and scope.

All 264 regression programs pass, including actual inventory/snapshot methods, interrupted/stale delivery and no-extra-urgency checks. The native normal route compiles and completes 63 assertions and one round, with zero script/runtime failures and thirteen retained installed-resource errors. This is base-loop integration evidence; native mine reporting/placement, replenishment and multiplayer remain unqualified. Independent review, regression evidence and preservation.

The native run waited for another private test's lock, then stayed hidden/muted with confirmed cleanup and unchanged inputs. Existing missions, unrelated working changes and the packaged field-update candidate are preserved; that package predates this addition. The prior death/restart reload remains unexplained after comparison with exact historical source; no workaround was applied. Full human escape, multiplayer, maintenance/mounted interactions, FPS and clean release qualification remain unfinished.

1 October 2026 — terminal cargo loss releases convoy holds: a submitted mounted pickup now settles uncertainty when its exact incoming entity is deleted. A swap requires both original exchange entities to be deleted; damage, capture or one surviving item retain quarantine. Stock stays spent and matching holds can release for later requests using surviving original cargo. Fix, independent review and preservation.

All 263 regression programs pass, including failing-before/passing-after actual-method checks. The integrated normal escape route completes 63 assertions and one round, with zero script/runtime failures and thirteen retained installed-resource errors. This verifies compilation and base-loop integration, not physical mounted rearming or terminal deletion.

A separate pre-fix death/restart check timed out after 30 setup assertions: Workbench reloaded before death/spectator checks, for an unknown reason. Neither death nor restart is qualified by that run. Both sessions stayed hidden/muted with confirmed cleanup and unchanged inputs. Original missions, prior working changes and the packaged field-update candidate remain preserved; the package predates this correction. Human play, real multiplayer, maintenance/mine/mounted interactions, FPS and clean release qualification remain outstanding.

1 October 2026 — bounded maintenance follow-up: one hidden/muted run of the unchanged field-update source passes 60 assertions, including original-can pickup and held equip, then loses the exact-held support-station condition after the fixture's scripted approach. It stops before tank depletion or refuel action; fuel transfer remains unverified. Two diagnostic failures and thirteen underlying installed-resource errors are retained, with confirmed cleanup and unchanged inputs. No guard was relaxed and no second attempt was made. Result and preservation.

Three parallel bounded reviews of HQ memory, base progression and owned-AI settings/equipment found no demonstrated new defect; ten focused regression programs passed. The verified development candidate below remains unchanged. Human play, real multiplayer, maintenance/mine/mounted interactions, FPS and clean release qualification remain outstanding.

1 October 2026 — field-update playtest candidate: the new separate handoff packages recovered mine warnings, recent HQ pursuit/cooldown corrections and consistent Stinger Random commands: 392 authored files, 336 exact PAK payloads and three runtime files, with matching editable source. All 263 regression programs pass. The exact-source normal route completes 63 assertions and one round through extraction/results, with zero script/runtime failures and thirteen retained installed-resource errors.

Ordinary packed startup verifies the normal mission and local prisoner, with zero script/runtime failures and seventeen retained installed-resource errors. Native packaging retains its strict failed verdict despite exact output and exit zero. All sessions stayed hidden/muted with confirmed cleanup and unchanged inputs. Existing missions, prior working changes and previous candidates remain preserved; nothing was published.

The legacy hq stinger alias now accepts/displays Random through the shared parser without rerolling existing equipment. The optional refuel fixture's corrected range reaches the native context, then fails before transfer on its node snapshot. Subsequent snapshot bounds/detachment is regression-tested and compiled by the normal route; fuel transfer remains unverified. Fixes, initial test failure, native failure and review. Human play, real multiplayer, maintenance/mine/mounted interactions, comparative FPS and release qualification remain unfinished.

1 October 2026 — HQ can replace unavailable pursuit squads: losing the only assigned squad no longer leaves its abandoned long-distance order blocking other available forces for up to 13 minutes. HQ releases that work, retains surviving active/pending orders and recomputes the hunt's delay. Completed-search quiet intervals remain remembered across later losses, replacement orders and either cleanup order; capacity trims and already shorter holds are preserved. No force or player observation is created.

Actual-method regressions reproduce the original bug and review-found expiry/order boundaries; all 263 regression programs pass. The integrated normal route compiles and completes 63 assertions and one escape round, with zero script/runtime failures and thirteen retained installed-resource errors. This is normal-loop integration evidence, not native qualification of force-loss replacement. Changes, independent review and preservation.

The separate bounded refuel run now confirms original-can pickup, callback/slot custody and held equip, then times out before any refuel action. Its optional reach check is stricter than the inspected native interaction-retention logic; ordinary refuelling failure is not demonstrated. Fuel transfer, repair, human play, multiplayer, mounted rearming, comparative FPS and release qualification remain pending. Both native sessions stayed hidden/muted with confirmed cleanup and unchanged inputs. Original missions, prior working changes and the existing packaged candidate are preserved.

1 October 2026 — optional refuel diagnostic corrected: RHS: Status Quo, WCS Armaments and WCS BMP-1 remain declared external dependencies. The corrected native action-context fixture compiles, but its one hidden/muted run stops after 54 passing assertions at its first clock check, before fuel selection or transfer. It retains two script test failures and thirteen underlying installed-resource errors, with confirmed cleanup and unchanged inputs.

The fixture had reconstructed its start time by adding/subtracting 120000 milliseconds; float rounding could put that value after the current tick. It now stores the original start directly. Actual clock initialization fails before the fix and passes afterward across fractional timestamps. All 263 regression programs pass. The timestamp fix has not been rerun natively; refuelling, interruption/depletion and repair consumption remain unverified. The fixture is opt-in and does not change ordinary gameplay. Original missions, existing working changes and the packaged handoff are preserved. Evidence and scope.

1 October 2026 — recovered mine warnings: successful engineer arming can seal a historical 500 m mine warning into the same generic intel folder already carried when that job began. Recovering that exact document adds a persistent warning alongside its existing site clue; objective documents and normal spending remain unchanged. Unknown records stay server-local, and recovery never refreshes live mine or soldier positions. The service is bounded to 32 records and 128 folder bindings. Behavior and limits.

All 262 regression programs pass, including actual sealing/recovery, caps, marker lifecycle and controller/discovery integration methods. Review caught and corrected contradictory exhausted-intel feedback and marker cleanup after list shrinkage. The integrated normal route compiles and completes 63 assertions through extraction/results, with zero script/runtime failures and thirteen retained installed-resource errors. That route does not execute physical mine/intel interactions or qualify warning rendering/remote replication. Review and preservation evidence.

The run remained hidden and muted, with confirmed cleanup and unchanged inputs. Existing missions and the last packaged handoff are preserved; that package predates this source addition. Human play, multiplayer, physical mine placement/arming, mounted rearming, comparative FPS and release packaging remain unfinished.

1 October 2026 — refreshed dependency-enabled playtest: the new separate candidate includes Southern maintenance supplies, HQ reservation/cooldown corrections and finite engineer mines: 388 authored files, 332 exact PAK payloads and three runtime files, with matching source. RHS, WCS and BMP remain declared dependencies.

Independent reviews fixed observed foreign mine custody being reaccepted after a nearby redrop, and redundant intel folders flooding global chat. Both have failing-before/passing-after actual-method regressions. All 260 regression programs pass. The fresh normal route completes 63 assertions through extraction/results, with zero script/runtime failures and thirteen retained installed-resource errors. Review and preservation checks.

Ordinary packaged startup verifies the mission and local prisoner, with zero script/runtime failures and seventeen unchanged installed-resource errors. Native packaging retains its strict failure despite matching output and exit zero. An initial native-tool crash produced no package; its evidence is retained alongside the fresh retry. All native checks stayed hidden/muted with confirmed cleanup and unchanged inputs. Physical mine placement/arming, mounted rearming, human escape, multiplayer, FPS improvement and release qualification remain unfinished. Previous handoffs and original missions are preserved.

1 October 2026 — finite engineer mine behavior integrated: an existing squad holding a delivered HQ road-interception order can use one original carried PMN4. The engineer approaches, prepares for ten continuous seconds, submits one tracked inventory drop and withdraws before guarded native pressure arming. Original actor/task/item ownership, combat cancellation, friendly clearance and retained late callbacks are enforced. HQ permits two simultaneous jobs, 32 retained jobs per round and one new road-site query per tick. No mines or forces are created. Behavior and limits.

All 260 repository regression programs pass. The final integrated normal route compiles and completes 63 scripted assertions through extraction/results with zero script/runtime failures and thirteen retained installed-resource errors. Physical engineer placement/arming and multiplayer are not yet demonstrated; this route proves base-gameplay integration, not that interaction. Both native runs stayed hidden and muted with confirmed cleanup and unchanged inputs. Original missions, 53 prior unstaged paths and the existing packaged handoff remain preserved. Independent review and exact evidence.

1 October 2026 — interrupted HQ orders release their unused delay: failed or expired radio retasks no longer prolong pursuit cooldowns using an order that never arrived. Active and pending surviving orders keep their own deadlines and waypoints. Two actual-method regressions fail before the correction; all 257 repository programs pass afterward. The current-source normal escape route completes 63 assertions through extraction/results, with zero script/runtime failures and thirteen retained installed-resource errors.

The separate HQ awareness check compiles and passes 53 assertions, then times out waiting to queue its completed-sweep fixture report; that failed qualification is retained. Both runs stayed hidden and muted, with confirmed cleanup and unchanged inputs. The original missions and existing packaged handoff remain unchanged. Fix, review and limits.

1 October 2026 — bounded maintenance test retained as a failure: the optional fuel-transfer fixture did not compile because the installed fuel manager has no GetOwner method. It executed no gameplay assertions. The entire experimental fixture and integration were removed, restoring the earlier playable source; existing finite maintenance stock and HQ retasking remain unchanged. Native fuel transfer and repair consumption remain unverified. The failed launch and its source snapshot are retained. All 257 repository checks pass again after restoration. No additional native retry was made; the private muted runtime was cleaned up.

1 October 2026 — live maintenance supplies and safer HQ retasking: the Southern cache now carries one finite repair kit (20 supplies) and two fuel cans (five litres each) alongside its existing weapons and radio documents. The hidden/muted normal route verifies the exact original stock and completes 63 assertions through extraction/results. Held repair/refuel consumption remains unverified. Player behavior and scope.

HQ now reserves a squad's active destination and pending replacement together, preventing another search from taking the old cell while a radio retask is in transit. It retains the active approach bearing during retask admission and still counts each squad once. The bug and a review-found bearing gap both have red-before/green-after actual-method evidence. All 257 repository regression programs pass. The integrated-source native awareness/radio run completes 77 assertions; only the two HQ files differ from the earlier maintenance-route snapshot. Both runs have zero script/runtime failures and thirteen retained installed-resource errors, confirmed cleanup and unchanged inputs. Implementation, review and limits.

The packaged candidate below remains unchanged and predates these source improvements. Original reference files and all previous working changes are preserved. Manual play, multiplayer, mounted rearming, FPS and release qualification remain unfinished.

1 October 2026 — integrated playtest handoff refreshed: the new isolated candidate now includes the recent admission, HQ evidence, finite-stock and mounted courier changes: 384 authored files, 329 exact PAK payloads and three runtime files with matching editable source. All 256 regression programs pass. Its unchanged addon source exactly matches the retained 55-assertion normal generated escape route; no redundant route run was needed. Artifact hashes and scope.

A fresh ordinary packed startup verifies normal modules, exact dependency mounts, mission readiness and a local prisoner with zero script/runtime failures. Its seventeen installed-resource errors match the preceding handoff and retain strict failure. Native packaging also retains localization/shutdown and completion-semantics failures despite exit 0 and matching output. All runs stayed hidden/muted with confirmed cleanup and unchanged inputs. The player guide now names the precise gate and vehicle actions. Mounted physical rearming, full human escape, multiplayer, FPS improvement and release qualification remain unfinished. Previous packages, the original reference workspace and pre-existing working changes are preserved.

1 October 2026 — mounted courier integration: finite mounted resupply is now connected to the existing HQ planner and original convoy stock, with shared infantry reservations, radio-delivered holds, one original non-driver courier, bounded pickup/swap/reboarding and retained uncertain operations. The 256-program regression suite passes; final changed-method checks also pass. The normal generated escape route completes 55 assertions and one round, with zero script/runtime failures and thirteen retained installed-resource errors. Physical mounted rearming is not yet demonstrated: one native trip failed at pickup, another timed out approaching cargo; both journals record original-seat return and hold release. All failures, compiler fixes, source/dependency invariance and cleanup are retained in the review. Existing missions and packaged handoffs remain unchanged. Behavior and remaining work.

Current source now uses one combined addon. Open addons/core/addon.gproj and Missions/ERR_Everon.conf; see single-mod migration. The older five-addon checkpoints below retain their original scope and do not qualify the merged source. 1 October 2026 — admission timeout and physical HQ evidence: a delayed preload can no longer bypass the server's admission deadline. HQ rejects stale containment after radio transit, plans only from valid movement headings, reports exact original vehicle positions, and requires an original soldier physically present before reporting a negative search. 251 regression programs pass. The hidden/muted normal generated escape route completes 55 assertions and one round with zero script/runtime failures; thirteen installed-resource errors retain strict failure. Source/dependency invariance and cleanup are confirmed. A reviewed mounted-transfer second-leg proposal is retained but remains unapplied until the physical courier/HQ coordinator exists. Changes, evidence and limits. Existing missions and packaged handoffs remain untouched.

1 October 2026 — finite mounted stock and native eligibility: convoy startup now requests a small, once-only stock matching exact originally installed mounted magazines, after the existing infantry cargo priority. Original identity, callback settlement and physical headroom checks prevent delayed replacement seeding or extra overbooking. Independent review caught and fixed the late-original-callback case. 250 regression programs pass. The hidden/muted native run completes 34 assertions and one round, finds a real compatible PKM box and gets a successful read-only swap-eligibility result with both slots unchanged. No worker is on foot at the required location and no transfer occurs. Zero script/runtime failures; thirteen installed-resource errors retain strict failure. Cleanup and unchanged source/dependency inputs are confirmed. Implementation and limits. The packaged candidate remains unchanged; mounted physical rearming, multiplayer and release qualification remain unfinished.

1 October 2026 — native mounted delivery and cheaper refused convoy startup: the production mounted-report fixture now completes 56 assertions and one round, proving original six-root ownership, cargo exclusion and a detached matching snapshot delivered through the real radio path. UAZs report one installed gun each; BMP counts remain explicitly incomplete. One convoy deployed, not the configured three. Zero script/runtime failures and thirteen installed-resource errors are retained.

New-convoy startup now skips terrain surveys when its source cannot fit the shared body allowance, while reusing already reserved original receipts correctly. 249 regression programs pass, including actual pool/startup red-before/green-after evidence; no measured FPS gain is claimed. A separate read-only mounted-slot probe verifies the original PKM loaded slot, muzzle and storage owner, then stops because no eligible compatible cargo candidate is found. It retains 32 passing assertions, two fixture failures and thirteen installed-resource errors; CanSwap was not called and no transfer occurred. Final completion wording now keeps eligibility separate from radio proof; its post-run change has executable focused regression evidence. Review and scope.

Both native runs were hidden/muted and confirm cleanup plus unchanged source/external inputs. All 52 pre-existing unstaged file contents are retained apart from explicit test/runner additions; 533 reference sources and previous packages remain unchanged. Physical mounted rearming, manual escape, multiplayer, full-fleet reliability, FPS and release qualification remain unfinished.

1 October 2026 — consistent fire-support memory and finite logistics ownership: a reproduced bug allowed fire-support contacts to infer 30 m/s on-foot motion that HQ memory rejected. Contacts now use the same accepted delivered history as pursuit, retain the original time/position, and leave radio reports unchanged. Infantry transfer now consumes a shared finite-magazine reservation; mounted sampling consumes a read-only original-root query while preserving permanent loss/capture observation. These are physical-rearming prerequisites, not mounted rearming. Behavior and regression review.

All 247 repository regression programs pass. The hidden/muted native awareness run completes 61 scripted assertions and one round, with zero script/runtime failures and thirteen retained installed-resource errors. It verifies compilation and the existing physical radio/memory path; the new movement edge cases have actual-method regression evidence. Cleanup, source/external invariance, all 52 pre-existing unstaged file contents (apart from the added test registration), and 533 reference sources are verified. The packaged alarm-memory handoff below remains unchanged and predates this source checkpoint. Manual play, multiplayer, mounted rearming, FPS and release qualification remain unfinished.

1 October 2026 — refreshed combined development handoff: a new isolated playtest build now contains matching editable source and package for all recent memory, mounted-reporting and alarm fixes: 377 authored files, 322 exact PAK payloads and three runtime files. Current source completes 55 normal-route scripted checks through extraction/result display, with zero script/runtime failures and thirteen installed-resource errors. Normal-route evidence, artifact hashes.

Ordinary packed startup verifies the exact dependency mounts, normal modules, ready mission and local prisoner with zero script/runtime failures; the same seventeen installed-resource errors retain its strict failed verdict. Native packaging also retains its localization/shutdown failures despite exit 0 and complete hash-matched output. All native runs remain hidden/muted, with confirmed cleanup and unchanged inputs. The playtest guide now uses the combined addon and current scenario identity. All 246 regression programs pass for this unchanged source; independent resupply and object-lifetime reviews found no new defect. Existing handoffs, existing missions and all 533 reference sources remain unchanged. Manual play, multiplayer, mounted rearming, performance and release qualification remain unfinished.

1 October 2026 — native alarm delivery and mounted low-stock check-ins: an existing AI witness now demonstrably hears the native alarm event and sends its original-time, coarse anonymous report through the actual radio route into HQ memory. The hidden/muted controlled run completes 55 scripted assertions and one round, with zero script/runtime failures and thirteen installed-resource errors. The earlier active-scene attempt exposed a real memory-ingestion lifetime crash; retaining the sanitized report through ingestion fixes that path, and its failed evidence remains archived. Native result, arrangement and limits.

Complete low mounted magazines can also request early status through the existing scan, shared cooldown and radio gate, without entering carried-ammunition totals or authorizing a refill. All 246 repository programs pass; independent review found no additional demonstrated base-loop defect. Mounted behavior and remaining rearming work, regression/review evidence. Human breach input, audible and remote presentation, physical alarm investigation, mounted rearming, multiplayer and FPS remain unqualified. Existing packaged handoffs and all 533 reference sources are unchanged.

1 October 2026 — conservative movement memory and bounded diagnostics: HQ no longer infers a stationary/forward track by skipping a contradictory recent sighting. Mounted sampling normalizes exact native slot wrappers to their physical gun before counting it, and convoy startup reports the actual shared-body budget and refusal reason. All 246 repository programs pass. The first alarm fixture incidentally records mounted UAZ magazines and a convoy refusal at 134/135 bodies, 25 required; full mounted snapshot/radio proof is still outstanding. Review and evidence, memory correction, mounted correction.

The current-source hidden/muted alarm diagnostic compiles, then correctly refuses emission because the relocated witness is inactive at native LOD 10, despite valid group, binding, distance and danger-event configuration. It passes 34 assertions and retains two fixture failures plus thirteen installed-resource errors. No event was emitted in that retry, so native hearing and radio delivery remain unqualified. Both attempts preserve failures, exact source/external inputs and confirmed cleanup. Alarm fixture limits and next step. The latest packaged handoff below predates these changes and remains untouched; all 533 reference sources are unchanged. No multiplayer, FPS or release qualification is claimed.

30 September 2026 — current-source handoff and installed-slot correction: mounted weapons/magazines now use their exact native weapon-slot or muzzle ownership when ordinary inventory storage is unavailable. The same check protects structural seat admission, while retaining cargo exclusion, original crew/ledger checks and traversal bounds. All 245 repository programs pass. An independent lifecycle/objective review found no demonstrated additional bug. Implementation and remaining native scope, review record.

The integrated source again completes 55 normal-route scripted assertions through extraction/result display with zero script/runtime failures and thirteen installed-resource errors. A fresh separate development handoff contains matching source and PAK: 376 authored files, 321 exact PAK payloads and three verified runtime files. Ordinary packaged startup verifies the normal mission and local prisoner, with zero script/runtime failures; seventeen installed-resource errors retain its strict failed verdict. Native packaging also retains localization/shutdown failures despite native exit 0 and confirmed cleanup. All runs remain hidden/muted with unchanged inputs. The bounded mounted fixture still does not qualify installed counts or delivery: no production convoy appeared within its 180-second window. Native alarm hearing, mounted rearming, fleet reliability, manual play, multiplayer and measured FPS remain unfinished. Earlier handoffs and all 533 reference sources are unchanged.

30 September 2026 — local alarm intelligence and structural vehicle sampling: successful vehicle alarms now emit one tagged native horn event. Eligible nearby enemy witnesses retain the original observation time and send a coarse, targetless report through ordinary radio delivery. HQ sanitizes that evidence and can assign one existing mobile search group; it cannot turn an alarm into a tracked player, road interception or fire-support target. Native compilation succeeds; actual native hearing and remote delivery remain unqualified. All 245 repository programs pass. Alarm behavior, regression and review record.

Mounted vehicle eligibility now traverses structural seats without descending into soldiers' carried inventories or deposited cargo; exact original crew/ledger guards remain. The latest production-fleet test passes 48 assertions, including all six original roots and exclusion of eight actual cargo weapons, but fails to observe installed weapon magazines. It does not reach radio-delivery proof. Earlier compilation and production-fixture failures remain archived. Thirteen installed-resource errors and two final fixture failures remain explicit; hidden/muted cleanup and unchanged source/external inputs pass. No armed-count, three-convoy reliability, rearming, multiplayer or FPS qualification is claimed. Existing packaged handoffs remain unchanged.

30 September 2026 — separate mounted-ammunition reports: admitted convoy crews now report bounded original-vehicle ammunition snapshots through normal radio delivery, separate from carried infantry stock. Capture, foreign crew, lost roots or changed ledger ownership invalidate mounted sampling; deposited cargo is excluded. All 242 repository programs pass, with focused checks after the final diagnostic phase fix. Behavior and remaining scope, regression/review evidence. Native compilation succeeds, but direct mounted sampling remains unproved: the first convoy fixture deadlocked waiting for HQ during prison; its checked escape transition is now fixed. The second run passes 33 assertions and road survey, then rejects canonical convoy dispatch before sampling. Both failures and the thirteen installed-resource errors are preserved; both confirm hidden/muted cleanup and unchanged inputs. Mounted rearming, real depletion/delivery, multiplayer and performance qualification remain unfinished. Existing packaged handoffs are unchanged.

30 September 2026 — one-shot vehicle horn alarm: successful UAZ lock breach now starts a replicated eight-second alarm with one owned audio handle. Duplicate state cannot replay it; expiry, destruction, mission inactivity and deletion clean up. Dedicated servers skip playback. All 240 repository programs pass, including final focused audio-query regressions. The hidden/muted native vehicle run completes 135 assertions, observes the playing handle and fixed stop/no-replay behavior, and retains thirteen installed-resource errors with zero script/runtime failures. The earlier failed diagnostic interpretation is preserved. Implementation, evidence and limits. Audible/spatial presentation, remote clients and AI-hearing/radio integration remain unqualified or absent. The matching normal-route handoff below predates this alarm source change and remains untouched.

30 September 2026 — normal generated-route checkpoint: the ordinary Everon catalog now completes the scripted prison → physical clues → interrupted/resumed radio defence → helicopter extraction → victory/result-screen path, with 55 assertions and zero script/runtime failures. The Southern optional UAZ passes its parking/readiness checks and starts locked; safe omission remains regression-tested. Generated sites were retained, unlike the older historical route fixture. Thirteen installed-resource errors still prevent strict qualification. Source/external hashes and hidden/muted cleanup are verified. Native evidence, transport scope. The earlier 236-program check and occupied-prefix refusal remain preserved. A fresh matching development handoff contains 373 authored files, 318 verified PAK payloads and three runtime files. Ordinary packed startup verifies normal modules, mission readiness and a local prisoner with zero script/runtime failures; seventeen installed-resource errors retain its strict failure. The packaging report also retains localization, Steam stats and resource-leak errors despite native exit 0 and confirmed cleanup. Ordinary human escape, driving, multiplayer and FPS qualification remain pending; older handoffs below remain untouched.

30 September 2026 — normal-route guidance and editable handoff: in-game objectives and the player guide now match the prison backpack and normal Southern-cache/Field-hospital-1 clue route. The Western cache/locked UAZ is legacy-fixture content, not a normal starting option. A verified updated source handoff contains the latest integrated changes; only the guidance strings differ from the last native escape snapshot, and focused feedback checks pass. Native packaging was deferred by its existing-game guard; the active user play session and older packages were left untouched. Source hashes and refusal records.

30 September 2026 — empty-magazine return: ground resupply can now return one exact unused compatible empty magazine to its original truck when inventory capacity blocks incoming ammunition. Separate callbacks and ownership proof guard both moves; failure or shutdown retains uncertain operations without retries. All 234 repository programs pass, and hidden/muted native compilation plus the 52-assertion scripted escape completes with zero script/runtime failures. The thirteen installed-resource errors remain; the empty-return branch itself still needs native validation. Implementation, provenance and limits. The original feature ledger now distinguishes implemented systems from absent behavior and unfinished qualification. Existing packaged candidates remain unchanged.

30 September 2026 — report chronology and retry ownership: delayed negative reports about another target no longer overwrite newer positive sightings in a shared HQ search cell; old admission callbacks cannot consume a reconnected controller's retry budget; completed Intel reroll entries no longer consume native-work slots. All 234 repository programs pass. The focused hidden/muted HQ awareness run completes 61 scripted assertions with zero script/runtime failures; thirteen installed-resource errors remain. The separately failed legacy convoy/memory fixture is retained. Changes, evidence and limits. The packaged candidate remains the older snapshot.

30 September 2026 — all-convoy infantry resupply: HQ can now use every existing finite convoy's original ammo truck, up to the configured twenty, rather than only the first. Per-truck stock stays separate; shared report/cooldown history prevents cross-truck replay, and planning rotates donors with at most one new trip per five-second cadence. All 234 repository regression programs pass. A hidden/muted native run initializes three independent 56-magazine stocks and completes the 52-check scripted escape with zero script/runtime failures; the thirteen installed-resource errors remain. No actual multi-truck delivery was exercised. Implementation and evidence. The packaged development candidate below predates this source change and remains untouched.

30 September 2026 — combined development candidate: a fresh single-addon handoff contains matching editable source and native PAK. The focused combined-mission escape fixture completes 52 assertions through victory and the result screen, with zero script/runtime failures. Ordinary packaged startup independently loads the exact ten engine/vanilla/owned/dependency mounts and verifies a local prisoner in the ready mission. Strict qualification still fails on installed-resource errors and the retained packaging verdict. Evidence, scope and build details.

30 September 2026 — earlier settings checkpoint: the complete repository check now passes all 232 registered regression programs, including the settings-save recovery correction and full-route fixture budget. The subsequent route-selector and cleanup changes pass their focused regressions; the older 231-program, 191-program and 101-assertion results below are historical checkpoints, not acceptance for the current tree. Latest fixes and preserved native attempts.

RHS Status Quo, WCS Armaments and WCS BMP-1 are current mission dependencies, alongside the separately authorized Parachute Framework and their supporting packs. Infantry resupply now waits for both real convoy cargo phases and captures faction-independent finite magazine identities. The hidden, muted infantry run compiled and captured 56 original magazines, but failed to select an eligible compatible patrol recipient before transfer. Cleanup and unchanged source/external inputs were confirmed. Thirteen existing resource/property/localization errors also remain. Changes, failed evidence and remaining scope.

The later empty-weapon ammunition fix now derives cargo from the native carried-weapon default when the last magazine has been removed, while preserving loaded variants and excluding auxiliary launcher rounds. Actual-method and neighboring policy regressions pass. The later radio fixture compiled the combined source and completed seven scripted assertions with zero script/runtime failures; native ammunition delivery remains unverified. Review confirmed that the earlier unavailable recipient was a fixture population limitation, not a demonstrated support-reservation defect.

A failed first settings save no longer leaves a rejected primary file that disables changes after restart; existing backups and runtime settings remain preserved. Two earlier combined route/administrator-stress attempts are retained as failures: the first reached interrupted radio defence before its old total deadline; the bounded retry completed the 129-actor, 100-percent intel reroll but exhausted the separate two-batch reroll budget. Neither completed extraction; the later route-only fixture does complete it without claiming the administrator stress passed. All runs used hidden/muted private profiles; the sealed attempts confirm unchanged source/external inputs and cleanup. The thirteen installed-resource errors remain explicit.

Use the updated player route guide for the single combined scenario. A full ordinary escape, multiplayer acceptance and an equivalent-workload FPS improvement are still unverified. Prison input automation and experimental AI helicopter flight remain paused. Existing September 29 medical, spectator, mortar and body-recovery work remains preserved in the working tree; no release or Workshop publication is implied.

20 September 2026 — report-driven road interception: HQ can now use fresh delivered movement history to select a forward point on an authored road and order an existing infantry group to hold it temporarily. The bounded selector respects reserved destinations, physical clearance and elevated-road geometry; old or weak evidence falls back to search. Existing radio delivery, force limits, home guards and absolute task expiry remain in charge. No barricades, vehicles, mines or new troops are created. Implementation and scope.

All repository checks pass. The native113607 raw checkpoint completes101 assertions/one round with zero script/runtime failures, including an actual Everon road selection and stale-belief refusal from arranged private-memory reports. Four external localization errors remain. A process-exit race prevented the runner's final cleanup seal; its failed verdict is retained. A later independent read-only check found the reported PID absent, the private prefix idle and source bytes unchanged. This is not infantry-arrival, natural-interception, multiplayer or FPS evidence. The refreshed development handoff now contains all five packages and matching editable source:261 authored files,222 exact PAK payload entries and15 verified runtime files. Packed Core starts cleanly. Full external startup verifies the13-addon paths, ordinary modules, mission header and local prisoner admission without script/runtime failures, but remains failed on four external localization errors appearing twice. Both packed runs confirm unchanged inputs and hidden/muted cleanup. Build/handoff record. All533 reference sources are unchanged; previous handoffs remain intact. Native packaging shutdown failures, full human escape, multiplayer and FPS acceptance remain unqualified.

20 September 2026 — nearby sighting handoff and resupply approach: A squad without a usable own radio route can now pass its fresh visual report through an original member to a living friendly radio carrier within 100 m. Original source, position and timestamp remain intact; HQ learns only after radio delivery. Shared callers cannot overlap their originating calls, and interrupted or repeated sightings cannot bypass delivery. The native checkpoint completes one round/81 assertions without script/runtime failures: an arranged snapshot reaches HQ unchanged, while removing the second caller's radio prevents the next snapshot from arriving. The fixture deliberately removes radios and positions a witness after startup fitting settles; it is not natural perception or multiplayer proof. Details and retained setup failure. Four external localization errors remain, with source/external fingerprints and hidden/muted cleanup confirmed.

Resupply now waits through unsubmitted geometry/capacity failures instead of spending that magazine and aborting the trip. A submitted native attempt remains strictly once-only. Move/hold radii also no longer accept an approach five metres from the reported truck position. Actual-method regressions reproduce and fix both issues; full native walking rendezvous remains unproved. Full repository checks pass, with the final fixture adjustment covered by focused tests and native compilation/execution. All 533 reference sources remain unchanged. An updated editable source bundle is recorded here; packaged playtests remain older snapshots. Manual play, multiplayer, packaging and FPS qualification are still unfinished.

20 September 2026 — native finite magazine transfer: Before moving a magazine, infantry now need unobstructed physical reach to a root-owned authored truck storage context. The native transfer checkpoint completes one round and 43 assertions, with zero script/runtime failures: one original magazine moves from the automatic convoy's original ammo truck to an original patrol actor, preserving ammunition count and the force ledger. This fixture deliberately positions the recipient and waits for its native pose update; it does not prove autonomous rendezvous. Four installed external localization errors still prevent strict qualification. Access and retained diagnostic failures. Actual-method tests cover obstructions, stock identity, report consumption, reservations, native submission and interrupted fixture cleanup. Source/external input fingerprints and hidden/muted cleanup are confirmed. Full walking resupply, multiplayer, FPS and refreshed packaging remain unfinished; existing handoffs are unchanged.

20 September 2026 — automatic convoy and result feedback: The full AI scenario now defaults to one automatic initial convoy after a 30-second startup grace and existing-force admission. Automatic and manual requests share the same finite receipt, with no automatic retry or replacement. /esc hq convoy auto set 0|1 saves the next-round choice; old disabled convoy settings migrate correctly. Startup details. Original physical turret occupants receive scoped skill100, while other enemy crew retain at least80. The native checkpoint completes 93 assertions and one round, proving six automatic vehicles, 19 original seated crew, five turret specializations and duplicate-dispatch rejection, plus the existing HQ radio-memory tests. Zero script/runtime failures; four external localization errors remain. All repository checks pass, and 533 tracked reference sources remain unchanged. Hidden/muted cleanup and unchanged input fingerprints are confirmed. Defeat screens now refresh a late replicated end reason; callback/lifecycle tests pass, but real remote-client timing remains untested. Existing packaged handoffs remain older snapshots; native logistics, multiplayer and FPS qualification remain unfinished.

20 September 2026 — finite nearby infantry resupply: HQ now uses delivered low-ammunition reports to reserve an existing patrol and the manually dispatched convoy's original ammo truck. Separate radio orders stop the truck, request its stopped-position report and send infantry to a nearby rendezvous. Existing captured magazine identities transfer at most once; no replacement stock is created. Low-stock reporting uses 30-second local scans and a 60-second urgent-call cooldown. Scope and limits. The current native run compiles the complete integration and completes 59 HQ-memory assertions/one round with zero script/runtime failures and verified hidden/muted cleanup; four external localization errors remain. The first native compile failure is retained and corrected. Direct native resupply/navigation, automatic dispatch, broad logistics parity and multiplayer remain unfinished. All repository checks pass and all 533 tracked reference sources remain unchanged. The existing packaged handoff remains the older 915476f snapshot.

20 September 2026 — radio and finite maintenance: Enemy groups now use bounded one-time radio fitting, preserving existing radios and excluding mortar-owned allocations. Uplinks hold their original caller for three seconds before network hops and fail on live consciousness/ownership loss. The native radio/HQ-memory checkpoint completes 59 assertions and one round, with zero script/runtime failures; four installed external localization errors remain. All six tested groups were already equipped, so native insertion remains unproved. The western supply cache now holds one finite repair kit and two fuel cans. Its native stock/transport checkpoint passes 131 assertions with zero captured errors, confirming 20 supply units and two five-litre cans plus prior lock/vehicle-loss behavior. Ordinary repair/refuel consumption remains untested. Both runs preserve exact sources and confirm hidden/muted cleanup. Current external packaging has a separate explicit v3 development workflow; the matching separate handoff is .build/playtest-2026-09-20-radio-maintenance. All five PAKs match their authored payloads; Core ordinary startup passes without captured errors. Full packed Chat verifies the exact thirteen-addon closure but remains failed on installed localization errors and did not establish participant readiness before its diagnostic ended. Native build shutdown failures remain; older handoffs are unchanged. All repository checks pass and 533 tracked reference files remain unchanged.

20 September 2026 — optics and base interaction follow-up: Startup optics fitting now uses verified vanilla/RHS resources, preserves existing attachments and remains independent of finite Stinger processing. The supply UAZ has a successor-owned held lock-breach action and scoped entry guards; the native supply-vehicle checkpoint completes 124 assertions with zero captured errors, including lock rejection, one-time unlocking, native driver availability with its declared door context, scripted seating, fuel depletion and no replacement after loss. Ordinary held input and multiplayer verification remain pending. Player guidance now explains pilot responsibility and whole-round extraction consequences, and repeats the current objective after a controlled-body change. The native convoy diagnostic compiled the optics integration but failed a combined gunner consciousness/seat/identity check after 170 passing assertions; it did not reach the new radio HOLD/RESUME test. The second run passed those driving/seat checks but received no qualifying cover sighting before a combined preservation guard failed. Native HOLD/RESUME remains unverified; more precise diagnostics are included without weakening either guard. The final full-addon run compiles all current source changes and completes 56 HQ-memory assertions with no script/runtime failures; the four known external localization errors remain. All repository checks pass, and all 533 tracked reference sources are unchanged. Existing packaged playtests remain older snapshots.

20 September 2026 — delivered ammunition and convoy cover: HQ now receives detached small-arms ammunition counts with real radio status and avoids new armed assignments only when fresh, complete evidence proves the squad empty. Per-vehicle convoy HOLD/RESUME commands share the original crews' radio downlinks and preserve route/crew/cargo identity. The ammunition run completes 49 assertions; the current convoy driving recheck completes 181. Both have zero script/runtime failures and confirmed cleanup, with four external localization errors retained. Native combat HOLD/RESUME and depletion still need direct tests; general resupply, multiplayer/FPS qualification and updated packaged playtests remain unfinished. See ammunition scope and convoy scope.

20 September 2026 — delivered casualty follow-up: HQ now merges body and squad-status evidence by immutable original member identity. A native corpse/radio test completes45 assertions: actual visual observation, no knowledge before delivery, real overlapping status and no double-counting. Transfer-before-death and deleted-corpse safeguards are covered by focused regressions. Four external localization errors remain; packaged playtest binaries have not been refreshed.

20 September 2026 — HQ memory and external dependencies: The editable successor now includes the AI migration checkpoint: bounded report-derived memory/prediction, infantry task selection, delivered negative-search coverage, routine check-ins and missing-patrol investigations, local body observation, finite Stinger grants and the Core force ledger. RHS/WCS/BMP are declared and audited. Native memory (56 assertions) and actual-sighting HQ response (35 assertions) complete with zero script/runtime failures; four external localization errors keep strict qualification failed. The older playtest below has not been rebuilt with these changes. The convoy checkpoint now proves exact nineteen-person native seating, finite physical truck cargo and duplicate-dispatch rejection. The native driving follow-up completes181 assertions: all six vehicles move at least20m and the lead over100m, preserving exact crew and rejecting repeat dispatch. Combat tactics, unloading and long-route reliability remain unfinished.

20 September 2026 — refreshed playtest ready: .build/playtest-2026-09-20 now contains the mission-owned Chat menu and current owned AI/Intel behavior from source 5e74269. All 216 authored source files and all five native PAK payloads match; fifteen runtime files are verified. Core and full scenario pass ordinary packaged startup with zero captured errors, unchanged inputs and confirmed hidden/muted cleanup. Build record and launch/route instructions. Separate muted manual launchers and local profiles/runtime are prepared; no visible launcher was run. The old handoff and 533 original reference files are unchanged. The packager's shutdown failures remain, while a narrowly fixed disappearing-audio-stream race passes44 tests and its separate Chat retry produces matching artifacts. Human full escape, multiplayer and FPS remain unqualified.

19 September 2026 — mission-owned chat administration: Core now owns /esc, the native settings/HQ/journal menu, authenticated sessions and player tools in dedicated classes. AI and Intel register optional providers; Chat is only the existing full-scenario/development wrapper. Open with /esc menu. Implementation and command reference. Final native regression: one full scripted escape round, 101 assertions, zero captured errors, unchanged source and verified private cleanup; checks include actual menu/owner RPCs, saved settings, god-state restoration, visible journal text and scrolling to the newest entry. Earlier Core and two-round full-scenario runs are linked in the implementation notes. All repository checks pass. Original 533 reference files remain unchanged. The frozen playtest package has not been rebuilt; multiplayer and release acceptance remain pending.

19 September 2026, 22:59 — owned AI/Intel migration: Added admin Intel summary/reroll commands, native-operation callbacks and bounded retry handling, coalesced team discovery notifications, and fair per-squad reporting of multiple current visual contacts. Change details. The updated five-addon source passes two native escape/restart rounds, 186 assertions, zero captured errors, unchanged source and confirmed hidden/muted test cleanup. All repository checks pass. The frozen playtest package below remains its earlier snapshot; these source changes have not been repackaged. Human/multiplayer and release qualification remain pending.

Updated 19 September 2026,22:12. The prison and the complete intended base sequence are implemented: prisoner spawning, physical intel/scavenging, radio defence, player-flown helicopter extraction, individual results and restart. Five independent successor projects use vanilla assets without the original mod. Scripted local integration and ordinary startup have native evidence. This is an implemented development build awaiting gameplay qualification, not a completed multiplayer release.

Priority correction from the user: stop spending disproportionate time on automated prison keypress proof and experimental AI aircraft flight. Both experiments are paused. Active work now targets concrete base gameplay bugs, missing user-visible behavior and companion integration. The reproduced first-admission deadlock is fixed, and casualty loading now gives denial/failure feedback to its initiating rescuer. Each clue cache carries one finite replacement map. Manual play and real multiplayer remain necessary, but absence of automated input proof does not mean the prison is still being built.

The frozen202-file playtest source now passes two Core escape/restart rounds,616 assertions, zero captured errors and confirmed cleanup. All repository checks pass. The development playtest handoff is ready in .build/playtest-2026-09-19: exact-source native packages and editable source, separate user-run play-full.sh/play-core.sh, prepared isolated local profiles/runtime and a seven-step route guide. Packed Core and full five-addon startup both pass with verified cleanup and unchanged artifacts. Workbench packaging errors remain recorded separately; this is a development candidate for human testing, not a qualified release.

Recent retained checkpoints:

• Ordinary coarse approach/facing/lock selection passed using actual private mouse/W input and one wheel pair. Facing took2.726seconds; no F was sent. The first opt-in held-action attempt later refused its independent facing prerequisite before wheel/F, confirmed all releases and cleaned up. Further input automation is paused.
• Typed aircraft service20m route passed40 assertions, destination hold, contact landing and shutdown at its201-file snapshot. The100m survey experiments found terrain/building/tree obstructions before allocating an aircraft; the last survey records the workshop bounds. There is no100m flight or operational HQ aircraft qualification. A reviewed contact check prevents ground friction receiving airborne-braking credit; its focused policy checks pass, native validation remains pending.
• All repository checks passed after integrating the optional held-action helper and independent validators. The subsequent narrow contact fix has focused regressions. These are development checks, not manual gameplay or release acceptance.

All seventeen first-release acceptance cases remain pending. Full ordinary escape, real multiplayer, improved FPS and clean native packaging are unqualified. The empty-addon packaging control still reproduces25 shutdown errors. Tests remain hidden/muted, and the original533 reference files were verified unchanged at21:42.

The route gain comparison measures one native20m route per gain: translation through arrival hold improved155.365→69.293seconds, and final target error improved0.130→0.099m. The candidate passed38assertions, physical contact landing and engine shutdown. This is an isolated flight-controller result, not an FPS comparison or operational HQ air support; the production callback bridge has separate native evidence, while the later retained-service route/Stop passes are separate historical snapshots and useful field-length routes remain pending.

Ordinary prison approach191750 now passes end to end using actual private mouse/W input:14turns,9walking pulses,4.741m path,27.199s native interval, stationary0.490m from the interior waypoint. A disposable2560x720 viewport provides pointer travel while retaining every containment/ownership check. No gate action was sent; the exact lock/context remains unselected from the final view. Earlier pointer-edge, cross-position-API, calibration-return and legacy-summary failures remain archived. The first physically completed route191342 has a separate hashed raw-log review, not a rewritten runner verdict. The later 194128 alignment attempt acquires the native gate context with the lock available, but does not select the lock; it remains failed. Read-only selected-action diagnostics precede any action cycling or heldF proof.

The relative-look observer now passes an ordinary Chat run: actual +24/−24 pixel input produced a measured 1.935° yaw response and return within 0.149°, with stationary body, then verified W/Tab input. Zero captured errors, source unchanged and cleanup confirmed. The earlier run remains failed because its independent checker assumed identical SAMPLE/READY milliseconds; its separate corrected review preserves the raw archive. The current-source Core attempt reached 292 assertions without errors but exhausted an undersized 180-second budget; its timeout remains a failure. The later 184647 run used a 600-second budget and completed both rounds with614 assertions; the earlier timeout remains failed. No gate interaction or full normal-input escape is qualified.

The primary deliverable is an independently authored replacement for the abandoned Escapists base mission, with companion behavior integrated through its interfaces. Five successor addon projects have their own identities, authored Everon sites and vanilla asset references. The first release targets up to twelve players completing prison → scavenging/intel → radio defence → helicopter extraction without the original mod or dependent extensions. Scripted development checkpoints exist; a dependable, manually playable multiplayer release is still unfinished.

Established development checkpoints

Area	Evidence	Practical limit
Integrated base loop	Core 130347 completes two rounds, 612 assertions and zero errors, including canonical participant rejection/restored document recovery, rough/exact native markers, radio feedback, extraction and restart. Companion 131041 completes two rounds, 96 assertions and zero errors at its source snapshot.	Scripted local integration with deliberate state/position changes, not a normal-input escape. These earlier archives share their captured source snapshot; the new Core/companion/ordinary runs linked above qualify the later native-end correction. The earlier flight mechanism remains separately source-bound. Future addon edits require fresh qualification. Earlier failures remain archived.
Ordinary game startup	Chat 125906 loads all five addons in the regular game, verifies the header/MissionSystems and admits the real local controller to a living canonical prisoner, then observes a clean ready interval. Native screenshots show the real prisoner view and the correct escape objective; the stock-scale yard decal creates a larger irregular bare patch, with substantial wheat remaining.	Explicit diagnostic noSplash and a scoped standalone round-local identity; no complete ordinary route or remote identity proof. The latest bounded keyboard cycle described above passes with visible inventory, while the earlier failed cycles remain archived. Admission design.
Packed addon consumption	Packed Core 110729 passes ordinary startup from the archived project/PAK/resource database plus installed vanilla: exactly three expected addons, real canonical prisoner, a 15-second ready interval and zero captured errors. Package and log hashes are retained.	Artifact-bound startup with explicit noSplash; no loose successor addon was loaded. The artifact predates current mortar edits. Archived packed Chat 131942 passes startup from all five 1317 packages, with no loose successor source, a real prisoner and zero captured errors. All 151 PAK entries match the captured 183-file addon snapshot before the native-end correction; all fifteen runtime artifacts retain exact hashes. Native packaging remains unqualified: an empty-addon control reproduces the same UI resource-leak errors, without fixing or suppressing them.
Native game-over	Preparation 133847 and active 134044 each pass two rounds/21 assertions: actual inherited game-over, unchanged native data, one shutdown, cancelled preparation/tick/binding, inert stale callbacks and vanilla restart.	Local fixture; pending native preloads and real clients are not arranged. Existing successor extraction results remain covered by normal escape/restart regressions.
Prison and scavenging	Prisoner capacity uses one real player plus eleven physical characters, exact starter kits and native clue transfers. Prison boundary 100148 covers the gate/progression corrections.	Extra physical actors are not twelve connected clients. Native action completion and deliberately repositioned boundary crossings do not prove held input or walking through the gate/debris. Equipment scarcity and combat balance need playtesting.
Medicine and extraction casualties	Medical treatment demonstrates finite supplies and native recovery at its earlier snapshot. Casualty 102037 passes 101 clean assertions at the committed checkpoint: grounded-aircraft checks, real incapacitation, helper rejection, seat/LOS constraints, one owner-handshake load and idempotent stop. Native removal proves the inherited exit mechanism.	Casualty loading explicitly adapts helper membership and invokes action completion. Held input, real remote ownership, competing rescuers and disconnect/death/deletion races remain separate. The older medical snapshot retains its historical catalog errors.
Infantry and HQ	Actual perception response carries an original soldier's observation through both physical radio legs and HQ to a different original squad, which physically moves. Patrol/preemption/resumption are implemented.	The prisoner is arranged and temporarily protected. Broader combat and interrupted/captured support require additional qualification; no response force is created for this test.
Finite support	Mortar expiry verifies fresh native commitments followed by stale-report withholding without duplicate orders. Courier 095513 passes 154 clean assertions through actual radio, original-patrol walking, exact depot-shell delivery and patrol restoration.	Mortar observations are synthetic; impact accuracy and genuine late callbacks remain unproved. The new refresh now passes the bounded 112900 fixture: three actual radio updates, eight physical launches, native event completion, 19 surviving original shells and 25 seconds without replay. The current 114751 expiry regression also passes 48 clean assertions. 115232 crew registration proves all four physical crew receive their one Intel carrying roll after setup, then exercises inventory depletion/loss; broader support-loss checks remain separate. Courier depletion is arranged by physically sequestering the original 27 rounds, not firing or replacing them. Broader losses and multiplayer remain unqualified.
Aircraft mechanism	Flight 114504 passes 81 assertions with zero captured errors: signed actor-local collective consumption, native autohover, powered takeoff, five-second 7–9m hover, stable contact landing and an engine-off check with finite fuel. The same aircraft and living AI pilot remain inside the original physical limits.	Translation 120245 additionally passes 85 clean assertions for a fixed four-metre target, five-second hold and landing. The reusable production controller separately passes 123439, 37 assertions including actual post-spawn qualification and its own complete vertical operation. Airborne cancellation 124915 passes 39 assertions with retained control through contact landing and engine-off. The same reusable controller then passes fixed-target movement 130038, 38 assertions including a physical 2.9m translation and landing. These are isolated flight mechanisms; rotors still coast after engine shutdown. The fixed 20 m route now passes one unloaded flight, target hold, contact landing and engine-off with 38 assertions. Useful field-length navigation, operational HQ support, repeated-flight reliability and manual/multiplayer piloting remain unqualified. Earlier input, drift, hover and shutdown failures remain archived.
Shared field map	Map ownership 120633 passes native replacement-view, delayed-callback, mode-clear and spare/interrupted deletion checks. The fixture observes actual cleanup and waits for native component references to expire.	Camera restore authorization is observed; no public native render-state getter exists. Visible held-map usability, previously focused stock gadget callbacks and remote presentation remain separate.
Independent runtime controls	Archived packed Linux Chat 132456 compiles the integrated game scripts, loads all five packages and prepares the empty prison mission in an isolated network namespace. Its four resource errors also occur in the earlier vanilla control. All fifteen packed inputs remain unchanged. Vanilla ordinary 102533 reproduces the initial splash unknown-class error with exactly two vanilla addons and no successor.	No real dedicated client joined. The vanilla ordinary control remains failed despite entering the menu; it does not test scenario reload or input. Splash diagnosis.

Immediate work

1. Play the frozen development candidate through the normal route and fix reported blockers. First-spawn exhaustion, silent casualty-loading failures and missing spare maps have been addressed; do not resume disproportionate input/flight automation.
2. Review normal-player guidance and supplies across the authored escape route. Fix evidenced usability defects with proportionate checks.
3. Distinguish genuinely absent base behavior from existing behavior awaiting playtesting. Pre-round setup UI, broader island population and vehicle break-in/alarm behavior are potential remaining features; the narrow escape sequence already exists. Keep later-scope feature parity separate.
4. Prepare and validate the playable development build. Ordinary manual play, real multiplayer, packaging and equivalent-workload FPS tests remain release work. Do not resume elaborate gate-input or experimental aircraft automation at the expense of those priorities.

First-release qualification

The acceptance ledger still requires the complete ordinary escape loop, death/unconsciousness/recovery, reconnect/respawn/spectators, partial escape, defeat/restart, interrupted/stale reports, support/ammunition losses and duplicate-free cleanup with up to twelve connected players. A passed development checkpoint does not promote those pending cases.

Collect matched original/successor workloads with repeated client-frame and server-tick measurements. No FPS improvement is demonstrated; the comparison tool has synthetic regression evidence only. Complete provenance/dependency review, obtain a clean native build and satisfy the release checker. The packed Core startup is now demonstrated for its exact archived PAK, while the packaging shutdown/control failures remain unresolved and unqualified. The development source bundle provides editable projects; it is separate from that native candidate and from a qualified release. No release package is published.

Private test cleanup now verifies Proton’s trailing-slash prefix spelling, checks idle state under the shared lock, and reaps only positively identified adopted test-device helpers after owned shutdown. The latest companion and ordinary runs record verified cleanup. Earlier strict-byte idle checks could miss those helpers; their historical logs are retained unchanged.

Original missions remain untouched. Engine tests use private profiles/prefixes, hidden displays and muted test audio. RHS/WCS/BMP are now authorized dependencies for AI/full integration. Additional terrains, complete original feature parity, alternate starts and distant-unit materialization remain unfinished. The validation ledger preserves the detailed historical checkpoints and failures.