Forsaken software corridor gameplay; paired combat remains open, November 18
The unchanged registered original forsaken_demo reached a readable Volcano
world using the actual software executor. Four individually reviewed finite
forward gestures moved from the green starting room into the metal corridor.
No living enemy was confidently identified, no original firing gesture was
sent, and enemy hit/defeat remains unproved. The independent disk watchdog
closed this scope at 1,499,869,184 free bytes on /home, before the attempted
pause command. That command was rejected locally; no command file, endpoint
request or replay followed closure. WebGL original gameplay and ordinary Quit
were not executed in this task. The requested paired enemy-combat goal is unmet.
Evidence is scratch/runs/20261118-forsaken-current-paired-reviewed-enemy-gameplay/.
result.json is written last. No shutdown fallthrough investigation, guest
patch, error suppression, forceflags/gueststate or Wine reference was used.
The preceding ordinary Quit13 remains an ERROR, not clean exit. This task
has no new ordinary-exit13 receipt and does not substitute host cleanup for it.
The real Windows VM reference is still pending.
Exact graph and actual execution
The original graph is the already-proven published Git
30d1f8d8c20be3eee960dff0599eb3d54b079fcb, with the retained existing
2,418,137-byte module SHA256
d8e7c4b0fe678597cfeedc7af57c91659c6c13bc76260d55826c21cfcb647490.
There was no recompilation for the original. Every pinned runtime source and
all 873 original-media pins were verified before execution, and all 873 media
pins again afterward. Every successful original HTTP response was checked
against that immutable graph/module or the media pins. The original EXE
remains 366ec5d0943daca839836296f9fb52724e94dc155630c6b0c30d7181106b5e24.
The helper files are separately pinned to the preparation Git and checked
against Git bytes. Shared WIP was not served. Exact source differences and
run-input patches/recovery are retained without a source snapshot or media copy.
The actual production route selected d3d-renderer=software, with ordinary
Workers/default slicing, on headful Chrome and an authenticated private Xvfb
whole-display capture. A run-only passive observer delegates each executor
call exactly once, preserves returned/thrown identities, and reads counters
only after successful DRAW/DRAW_UP/PRESENT execution. Its native controls pass.
The live original observation identifies an actual GpuStreamSoftware.Executor
instance after a completed DRAW_UP, 6,822 completed draws, 7,767 native draws,
193 presents and 136 readbacks. These are cumulative executor counters; the
193 PRESENT records are earlier history, not a world-action-local presentation
delta. The world screenshots show actual displayed gameplay; the world route
also reads back into DirectDraw. No WebGL context was executing in this scope;
context null is explicit. No selector/vendor string establishes this result.
Late original Worker bytecode was not read before cancellation; served module
identity is verified, and actual live bytecode reads in the successful authored
control match d8e7c4b0. No original late-bytecode claim is made.
Selected whole frames are original main-menu.png, volcano.png,
world-neutral.png, and corridor-forward-result.png. The latter two retain
lives5, shields/hull128 and PULS2000 while showing changed room/corridor geometry.
They do not establish an enemy target or combat consequence. No unreadable scene
was used to authorize an aimed shot. Seven original finite gestures (three
Enter plus four A) each had an independently prearmed UP process, actual child
wait0/both EOFs, and passive physical-neutral state after release. Transport
completion is not described as a guest consumption acknowledgement. The later
attempted Escape was never published or sent.
Preparation fixes and limits
Several authored preparation scopes are recorded separately, never replayed:
- The initial software control was closed by the disk watchdog before input. Its launcher child was signalled SIGTERM; browser/display/driver waits are unavailable. Native-supervisor cleanup and later filesystem-only absence checks are retained. The old invoker exit0 does not mean this control passed.
- Moving Chrome temporary growth into tmpfs first exposed an AF_UNIX socket path-length failure. That failed scope has finite display/supervisor waits. A short owned tmpfs directory and native socket-budget control correct it.
- Continuous 128-triangle and one-triangle controls completed software frames while the whole display remained the shell; a passive read found publication held. Both were closed normally without any input. This is not an established original-game defect. No scheduler/publication state was forced.
- The fresh authored message-driven one-triangle control visibly showed a yellow triangle on blue; reviewed Enter200 changed it to red. A finite A+Control+Space200 chord had balanced independent releases, and reviewed Escape200 produced actual guest exit0. Full browser/display/driver/watchdog/ enclosing waits and both EOFs are retained.
The floor watchdog now writes a sticky filesystem cancellation first, allowing
owned browser/display children to be waited before its fixed escalation.
A native deadline/cancellation control passes, and the affected original's disk
cancellation has actual browser/openbox/Xvfb/watchdog wait0, supervisor/enclosing/
invoker wait1, null signals and both EOFs. The nonzero waits are retained as
failures. The last run-input revision also propagates signalled child status
rather than code || 0; native exit0, exit13 and SIGTERM143 controls pass.
That final signal-propagation revision was not exercised by another original
scope. No historical wait was rewritten.
The independent bounds were fixed before launch: startup180s, original1200s including Quit reserve240s, cleanup20s, terminal60s, capture10s, transport15s, review90s, release-prearm20s, fallback5s, maximum hold1800ms. The original ran about280s before floor cancellation. No limit was extended. The successful control and original have complete retained child waits; the initial failed control's missing waits remain explicit. A postclosure filesystem audit found all228 recorded PIDs absent. The external coordinator worker's parent wait is unavailable to this worker.
Native software executor tests pass (six presents,15 native draws). The native WebGL test explicitly skips because optional native GL dependencies are absent; it is not a WebGL pass. The canonical locked build passes on the later shared worktree. Its module differs from d8e7c4b0 and was not adopted by the original. No production runtime/helper files were changed; the fixes above are owned run-only preparation inputs. No held-title or other-owner work was edited.
Remaining cause and preservation
The immediate execution blocker is repeated shared-filesystem floor breach, despite this task's runtime/capture/profile/cache/temporary growth living in owned tmpfs. Continuous floor compliance is false. No WebGL scope or fresh original was launched after the last disk cancellation. Meaningful combat still requires a readable living target interval and a reviewed shot with a visible target consequence, followed by ordinary Quit retaining its actual error status. Neither outgoing ammo nor incoming player damage is promoted to enemy damage.
Selected unique evidence is retrieved and SHA-verified before owned tmpfs removal; recovery uses Git plus patches and existing unchanged module/media. No source trees, frame series or media bundles are retained. No workers, boxes, hardware/FPS/parity claims, public deployment, Python or Wine were used. Box ID null, state NOT_CREATED, expiry null, stop receipt null.