Prepare independent successor playtest with spawn recovery and casualty feedback

docs/current-status.md

@@ -1,14 +1,20 @@
 # Current development status
 
-Updated **19 September 2026, 20:59**. All repository checks pass after integrating the typed aircraft service, opt-in100m fixture and read-only held-action observer phase extension. The [first native100m trial](evidence/native-2026-09-19-205734-field-survey-refusal/report.json) compiles the201-file snapshot but refuses its fixed corridor before any test aircraft allocation. Its failure is retained; clearance diagnosis comes next. The current clean-runtime development gate is pending again. No100m flight, braking adequacy, operational HQ aircraft or held-F completion is established.
+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.
 
-The [coarse prison approach trial](evidence/game-2026-09-19-205021-coarse-selection-refusal/runner.json.txt) physically completes approach and facing, then refuses selection with1.457s remaining against its unchanged1.5s admission requirement. All attempted keyboard presses were paired with releases; no wheel or F was sent. Approach took25.605s and facing5.824s. These partial observations do not turn the failed overall trial into a pass.
+**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 earlier [finite aircraft service route](evidence/native-2026-09-19-202253-retained-aircraft-route/report.json) passes40native assertions and [airborne service Stop](evidence/native-2026-09-19-202706-retained-aircraft-stop/report.json) passes42, both at their197-file snapshot through retained physical control, contact landing and engine shutdown. The [200-file map regression](evidence/native-2026-09-19-204500-field-compile-map/report.json) passes58assertions. Subsequent typed-service and observer changes need their own successful integrated runtime evidence.
+The frozen202-file playtest source now passes [two Core escape/restart rounds](evidence/native-2026-09-19-215437-playtest-core-loops/report.json),616 assertions, zero captured errors and confirmed cleanup. All repository checks pass. The [development playtest handoff](playtest-build.md) 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](evidence/packed-core-2026-09-19-playtest/report.json) and [full five-addon startup](evidence/packed-chat-2026-09-19-playtest/report.json) 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.
 
-**All seventeen first-release acceptance cases remain pending.** The ordinary held lock action/full escape, real multiplayer, improved FPS and clean native packaging remain unqualified. The [empty-addon exit-after-init control](evidence/package-control-2026-09-19-201532-exit-after-init/review.json) still reproduces25shutdown errors. Tests remain hidden and muted, with separate profiles and guarded cleanup; original missions remain untouched.
+Recent retained checkpoints:
 
-The [route gain comparison](evidence/route-comparison-2026-09-19-192238/comparison.json) 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 retained-service qualification and longer routes remain pending.
+- [Ordinary coarse approach/facing/lock selection](evidence/game-2026-09-19-212117-coarse-facing-selection/runner.json.txt) 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](evidence/game-2026-09-19-214138-held-prerequisite-refusal/runner.json.txt) later refused its independent facing prerequisite before wheel/F, confirmed all releases and cleaned up. Further input automation is paused.
+- [Typed aircraft service20m route](evidence/native-2026-09-19-210233-typed-service-route/report.json) 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](evidence/native-2026-09-19-213726-field-workshop-refusal/report.json) 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](evidence/package-control-2026-09-19-201532-exit-after-init/review.json) still reproduces25 shutdown errors. Tests remain hidden/muted, and the original533 reference files were verified unchanged at21:42.
+
+The [route gain comparison](evidence/route-comparison-2026-09-19-192238/comparison.json) 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](evidence/game-2026-09-19-191750-prison-approach/runner.json.txt) 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](evidence/alignment-review-2026-09-19-194128/review.json) 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.
 
@@ -34,10 +40,10 @@ The primary deliverable is an independently authored replacement for the abandon
 
 ## Immediate work
 
-1. **Prove the ordinary player route.** The inventory first-open path is now visibly demonstrated without its former slot errors. Next implement the [bounded normal-input gate exercise](prison-input-proof-plan.md), verify reopen/refresh/item transfer, and use normal document/map, radio and medical interactions; travel the authored route, board and pilot the actual extraction helicopter, and verify partial escape. Keep finite supplies, vanilla recovery and explicit round abandonment intact. Direct-completion fixtures cannot settle these usability questions.
-2. **Extend the proven bounded flight mechanism.** Signed actor-local collective and native autohover now pass vertical takeoff, hover, landing and engine-off checks. A bounded four-metre translation and one fixed 20 m route now pass too. Longer routes and operational HQ support still need implementation and native qualification. The reusable controller now passes a native vertical operation; airborne cancellation also passes; optional fixed-target movement now passes too. Operational allocation and useful field-length paths remain next; the later gain experiment shortened the sampled translation/hold interval to69.293s within the existing160s stage. Keep unqualified flight modes out of operational HQ support, retain failed observations, and re-run applicable integration checks after source changes.
-3. **Establish real multiplayer behavior.** Test accepted client identities, simultaneous/late joins, preload cancellation, reserved-body reconnect/expiry, spent lives, spectator streaming, remote task/map/radio/result updates and seat contention. Local controller injections and helper actors are not substitutes for connected clients.
-4. **Broaden support-loss and observer checks.** Refreshed full salvo, current expiry and late crew registration now have source-bound native evidence; wider support-loss regressions remain. Spectator reason messages and survivor-cycling guidance have been added and compiled; visible behavior and real-client streaming remain unverified. Exercise actual interrupted reports, captured/dead couriers, pending inventory callbacks and support losses. Preserve stock and original patrols; retain historical failures alongside source-bound successful regressions.
+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