EscapistsReintroduced/docs/combined-candidate-2026-09-30.md

# Combined development candidate — 30 September 2026

The later [current-source installed-slot handoff](../.build/playtest-2026-09-30-installed-slot/README.md) supersedes this earlier snapshot for development testing: 376 authored files, 321 PAK payloads, matching 55-check normal-route evidence and ordinary local-prisoner startup. Strict packaging/startup qualification still fails on retained errors. [Latest status and limitations](current-status.md). The original candidate record below remains historical and unchanged in scope.

The [earlier handoff](../.build/playtest-2026-09-30-current/README.md) contains one `core` package, a matching source ZIP and editable source. Previous five-addon handoffs remain untouched. Nothing was published or installed over existing missions.

## Latest normal-catalog checkpoint

The newer [normal-route handoff](../.build/playtest-2026-09-30-normal-route/README.md) supersedes the earlier snapshot for development playtesting. It contains **373 authored addon files**, **318 exact PAK payloads**, three verified runtime files and matching extracted/source ZIP bytes. [Handoff hashes](evidence/package-2026-09-30-normal-route/handoff.json).

The [normal-catalog scripted run](evidence/native-2026-09-30-normal-route/report.json) keeps generated placement and completes **55 assertions** through victory and the result screen, including an initially locked Southern UAZ at the accepted parking position. It has zero script/runtime failures and thirteen installed-resource errors. The [ordinary packed startup](evidence/packed-2026-09-30-normal-route/packed-startup-report.json) loads the exact ten mounts, normal Game modules and a local prisoner in the ready mission, with zero script/runtime failures and seventeen installed-resource errors. Raw verdicts remain failed for strict qualification. Its schema-4 evidence was independently recomputed from the sealed console; package/input hashes and cleanup are confirmed.

The fresh [native packaging attempt](evidence/package-2026-09-30-normal-route/package-report.json) emits those exact files and exits natively with code 0. Localization, Steam stats and shutdown resource-leak errors retain `candidate_created: false`; private cleanup is confirmed by the existing guarded runner. No original failed verdict was changed. These observations do not qualify human input, driving/piloting, multiplayer, FPS or release readiness. The sections below retain the earlier snapshot's scope and failure history.

## Completed scripted route

The [focused route](evidence/native-2026-09-30-escape-route/report.json) completes **52 assertions and one round**, with zero script/runtime failures. It uses the combined source with HQ, Intel, Chat and Map present: lock action and physical gate passage, two exact cache documents transferred into player inventory, radio identification, distant-action refusal, defence interruption/reset, continuous defence completion, real helicopter occupancy, boundary detection, victory and the player's result screen.

This explicit `escape-route` outcome uses `Tests/LegacySites.conf` and fixed positions; it does not validate the ordinary generated-site catalog. It excludes administrator-menu and 100/0-percent inventory stress. The existing `victory` outcome retains those checks and its prior timeout evidence. The new selector's executable test verifies both paths, and the route retains its fixed 150-second cap. The fixture arranges player positions, invokes actions and moves the occupied helicopter across the boundary. It is not human-input or piloting proof. Its thirteen resource errors still fail strict qualification; cleanup and unchanged source/external inputs are confirmed.

## Package contents and ordinary startup

The source bundle contains **370 authored files**; the PAK contains **315 payload entries** with exact matching paths and SHA-256 hashes. The package directory contains exactly `addon.gproj`, `data.pak` and `resourceDatabase.rdb`. [Content verification](evidence/package-2026-09-30-combined/content-verification.json) and [handoff hashes](evidence/package-2026-09-30-combined/handoff.json) identify these bytes. External assets remain separately installed.

The [ordinary packed run](evidence/packed-2026-09-30-combined/packed-startup-report.json) uses schema 4 and verifies the combined package plus seven external addons, ten mounts including engine/vanilla. Normal Game modules compile without WORKBENCH and no smoke fixture runs. The mission prepares, its 67 spawn-scene objects and 28 storage items are acknowledged, and a local prisoner is verified. There are zero script/runtime failures, but **17 resource error lines**, including four repeated external localization errors. Thus `packed_consumption_verified` remains false. The [runner](evidence/packed-2026-09-30-combined/packed-runner.json) confirms unchanged package/external inputs and successful cleanup.

## Preserved packaging cleanup failure

The native packer emitted the inspected files and returned native exit code 0, while retaining localization/resource-leak errors and a failed original cleanup verdict. Its adopted private `winedevice.exe` had a user-systemd parent with the observed `--deserialize=10` reexec argument, which the old exact two-argument parent check rejected.

The cleanup guard now accepts only the original user-systemd arguments or that same shape with one bounded ASCII decimal deserialize descriptor. Parent identity, UID, PPid, executable, process start, exact prefix, shared lock and pidfd identity guards remain. Seventeen cleanup tests, eleven cleanup-runner tests, 48 package-tool tests and 18 packed-external tests pass. The [separate follow-up record](evidence/package-2026-09-30-combined/cleanup-followup.json) confirms TERM then KILL of only the positively identified leftover private device helper and verifies the prefix idle. Systemd and unrelated processes were untouched. The [original package report](evidence/package-2026-09-30-combined/package-report.json) remains failed and unchanged.

## Remaining acceptance

Human held actions and piloting, remote join/reconnect/ownership, partial escape with multiple players, twelve-player sessions, equivalent-workload FPS improvement and clean native packaging remain unqualified. The administrator reroll stress timeout also remains unresolved. This candidate is for development playtesting, not release. No physical-display windows or desktop input were used; all native checks were hidden and muted. Prison input automation and experimental AI helicopter flight remain paused.