escapists/EscapistsReintroduced
1
0
Fork 1
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Refresh integrated playtest packages and handle disappearing test audio streams

Browse Source
This commit is contained in:
jakub
2026-09-20 00:33:58 +02:00
parent 5e742691ad
commit e7b4141f69
46 changed files with 4035 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/validation.md
+10 -3
View File
@@ -344,7 +344,7 @@ For the six newly checked 091306/091641/092237/092512/092923/game093115 archives
[105709 flight damping experiment](evidence/native-2026-09-19-105709-flight-damping-refusal/report.json) increases only velocity damping0.3→0.6. It again consumes actual controls and fuel, and reaches roughly9m altitude. It later oscillates horizontally and exceeds the unchanged flight envelope; no stable5s hover or landing passes. Higher outer-loop damping alone is insufficient with the observed native attitude response. This remains opt-in WORKBENCH investigation, never a production aircraft controller.
[105949 silent packaging attempt](evidence/package-2026-09-19-105949-silent/package-report.json) repeats native Core packing with documented-wbSilent, retaining actual successful packing messages and natural native exit0. The corrected runner now distinguishes native completion from its remaining owned display wrapper and confirms cleanup without a timeout. Native UI resource-leak errors still occur, so the attempt remains failed; silent initialization does not solve that environment issue. All captured source bytes remain unchanged.
[105949 silent packaging attempt](evidence/package-2026-09-19-105949-silent/package-report.json) repeats native Core packing with documented-wbSilent, retaining actual successful packing messages and natural native exit 0. The corrected runner now distinguishes native completion from its remaining owned display wrapper and confirms cleanup without a timeout. Native UI resource-leak errors still occur, so the attempt remains failed; silent initialization does not solve that environment issue. All captured source bytes remain unchanged.
[110404 empty-addon packaging control](evidence/package-control-2026-09-19-110404/package-report.json) contains only the five owned project descriptors, with no successor scripts, worlds, compositions or UI resources. The same installed native packer naturally exits0 and repeats the UI resource-leak shutdown errors. Its private input repository remains unchanged and cleanup is confirmed. This isolates the shutdown symptom from successor payload content in this environment; it neither clears the earlier errors nor qualifies a build, mission, package consumption or release.
@@ -437,12 +437,12 @@ The successor-only [layout adapter](inventory-layout.md) preserves the complete
[Ordinary Chat 183944](evidence/game-2026-09-19-183944-relative-look/runner.json.txt) compiles the native camera observer and independently verifies two private relative mouse requests: stationary-body yaw response 1.935°, return error 0.149°, native interval 2101 ms, completion before the W/Tab cycle. Zero captured errors; source unchanged and cleanup confirmed. Full repository checks pass, plus the corrected READY timing regression. The first [183353 run](evidence/game-2026-09-19-183353-look-ready-timing/runner.json.txt) remains failed: its checker demanded equal SAMPLE/READY milliseconds, although the native logger read the clock again 1 ms later. A separate hashed review retains the correction without rewriting that verdict. The [Core 183622 attempt](evidence/native-2026-09-19-183622-core-budget/runner.json.txt) records 292 assertions, no errors, zero completions and timeout at 180 seconds; prior two-round runs take about 395 seconds. No clean Core qualification is claimed for that timeout. All seventeen first-release cases remain pending.
## Ordinary prison approach, 19 September19:17
## Ordinary prison approach, 19 September 19:17
[191750](evidence/game-2026-09-19-191750-prison-approach/runner.json.txt) passes independent native camera/input/gate validation:14turns,9W pulses,4.741m cumulative path,27.199s interval and0.490m final waypoint distance. Original gate remains closed; player stopped; zero captured errors and verified cleanup. The explicit disposable viewport is2560x720, with actual owned window/root dimensions verified in archived display evidence. All physical display and original-mission settings remain unchanged. Earlier190119(pointer limit),190707(mixed body APIs),191122(calibration return0.363° beyond0.35°), and191342(legacy inventory summary) remain failures. The191342 route separately passes raw geometry/input review. Read-only LOOK now uses actor.GetOrigin just like INPUT/GATE; body-facing and camera transform APIs remain unchanged. The approach runner now requires its dedicated raw movement validator, rather than inventory-open-dependent movement summaries. Full checks and focused integration tests pass. Lock selection/hold, exit, full escape,12clients and FPS remain pending.
## Route gain and current Core qualification,19September19:39
## Route gain and current Core qualification,19September 19:39
The [192238 aircraft run](evidence/native-2026-09-19-192238-aircraft-route-gain/report.json) passes38assertions and the [193223 Core run](evidence/native-2026-09-19-193223-core-current/report.json) passes two rounds/614assertions. Both retain zero captured engine/script errors, immutable195-file source provenance and verified private cleanup. The [hashed comparison](evidence/route-comparison-2026-09-19-192238/comparison.json) records one run per gain,55.4% less time from translation start through arrival hold and unchanged landing constraints; it is not controlled FPS or longer-route evidence. Full repository checks pass after adding the explicitly requested yaw-only alignment experiment; its native result is separate. Original workspace guard:533reference files unchanged. Release remains pending17cases.
@@ -461,3 +461,10 @@ The196-file snapshot passes [194527 route flight](evidence/native-2026-09-19-194
Core administration is implemented in dedicated client, session, service/provider, player-tool and native-menu classes. [Core](evidence/native-2026-09-19-232402-core-admin/report.json) passed 316 assertions and one scripted round; [full scenario](evidence/native-2026-09-19-232959-full-admin/report.json) passed 202 assertions across two rounds. Subsequent lifecycle/presentation corrections pass the [final full-scenario run](evidence/native-2026-09-19-234618-chat-complete/report.json): 101 assertions, one round, zero captured errors, immutable source and confirmed hidden/muted cleanup. Actual owner RPCs, all ten settings represented, draft preservation, Apply persistence/restoration, companion capabilities, journal delivery/rendered size/normalized end position, god restoration and authorization-refusal closure are checked. [Private window captures](evidence/admin-ui-2026-09-19-234224/review.json) separately show the three native pages at their recorded earlier source; the final run validates the later initial-scroll correction.
All repository checks pass. Regressions include per-controller authorization and throttles, stale-round messages, provider dispatch, current-body item operations, pending/time-out quarantine across same-body reauthorization, exact previous damage restoration, menu structure and project/menu resource validation. The original 533 reference files and all 26 migration source hashes remain unchanged. Earlier menu binding, layout and diagnostic compile failures remain retained. This is scripted local integration and visual inspection, not remote-client authorization, actual inventory-contention qualification, mouse/keyboard usability acceptance, multiplayer or FPS evidence. Existing frozen playtest packages remain unchanged.
## 2026-09-20 — refreshed Chat/AI/Intel playtest packages
The [refreshed candidate](evidence/playtest-2026-09-20/build.json) has 216 authored source files exactly matching commit `5e74269`; the five PAKs contain 124 Core, 39 AI, 4 Intel, 6 Map and 8 Chat entries, each matching its authored source hash. All 15 runtime files and the matching source ZIP are retained in `.build/playtest-2026-09-20`. [Packed Core](evidence/packed-core-2026-09-20-playtest/report.json) and [packed Chat/full](evidence/packed-chat-2026-09-20-playtest/report.json) both pass ordinary local startup, scenario/header/MissionSystems and canonical player admission, zero captured errors, exact unchanged inputs and verified cleanup. They do not qualify menu input, full human play, multiplayer or FPS.
The packager still records shutdown resource/UI errors and private helper completion failures. The first Chat job also failed when its audio stream vanished during routing, yielding no Chat artifacts. The runner now ignores such failed audio operations only after a fresh valid listing proves that exact stream absent; present/reused indices, malformed/failed reads and timeouts still fail. All 44 focused packaging tests pass. The fresh Chat retry and original failed reports are retained separately. No qualification verdict was rewritten. The source baseline's full repository/native checks remain separately recorded at their commit. The previous handoff and 533 original/reference files remain unchanged.