Jedi Knight missing-payload diagnosis — 2026-10-21

Historical source last updated, 2026-10-21. Runtime and implementation claims below describe that dated source; see current app notes and source for subsequent changes.

Blocked at the source-file contract; no localized emulator defect established. One ordinary traced replay reproduces 0 MB and Finish/exit 0 with no game payload. The installer searches C:\WebJedi\*.*; the exact retained source capture has no such directory. Its unchanged game originals are at C:\. Returning failure for that absent directory is consistent with the mounted filesystem. Changing lookup to return root files would hide the mismatch. No production change, source-layout alteration, registry fabrication, original patch, rebuild, bootstrap, second replay or game launch was performed.

Minimized observed failure

recovered/replay1/output.log records:

The unchanged setup.ins contains WebJedi at byte 0x4590 and *.* at 0x45ac. controls.json preserves surrounding raw bytes. This is an original script operand, not a guessed host path. Runtime tracing uses existing --trace-fs, filtered --trace-api and --trace-stack facilities.

The package's 39 local ZIP headers all have flat names; both historical extractors recover those names and bytes. That verifies byte recovery, not the original self-extractor's directory semantics. The package has data outside compressed member bodies. This task has not decoded its outer layout metadata or observed the outer self-extractor producing its source tree. Consequently the upstream cause of the source-layout mismatch is unresolved; an emulator defect cannot be responsibly inferred from these observations. Resolving that would be broader source-layout recovery work, outside this bounded emulator repair. No speculative rearrangement was tried.

Controls and actual installation result

Nine read-only controls use exact-source lib/filesystem.js and the same 96 captured files, mounted at their retained paths with the runner's ensureParentDirs/setLazyFile mechanism. All pass: absent WebJedi with both *.* and *, both absent sound paths, and an absent directory containing the basename jedi.exe return no match. Existing root Jedi.exe (305664), JKDEMO.EXE (1388032), res1demo.gob (31326451), and Linstall.bmp (50686) return their correct sizes. Root enumeration finds Jedi.exe and no WebJedi directory. These controls do not create an installed layout or alter the captured tree. A preliminary harness used nonexistent addFile; its TypeError receipt is retained, then corrected to the runner's real mounting API. No guest ran in that failed control.

Replay 1 ran 13:16:09–13:16:13 UTC, terminal 13:16:13.465Z, exit 0. The driver verifies each expected page, captures it, then sends ordinary renderer clicks. Actual licence Yes was click:415:395 at batch 14611, 13:16:10.235Z, followed by Welcome; the prior authorization record remains unchanged. README No was click:354:277; actual Finish was click:415:395, batch 135129. The 0-MB and Setup Complete images were inspected.

The saved destination again contains only deisl1.isu (3659 bytes), jedi knight demo readme.lnk (241), and uninstall jedi knight demo.lnk (205), identical hashes to the predecessor. No installed Jedi.exe/JkDemo.exe/GOB, startup, gameplay or input qualification. Setup completion is not installation. There is no baseline-versus-fix result because no fix was justified.

Provenance, recovery and handoff

Evidence archive: 839450 bytes, SHA-256 122663afcec1d296b8c1a206e917c8af5a947f4b7369c4a03088b5f28b3c4c6e. It contains 56 sealed evidence files and a seal, with full trace, page/input receipts, images, registry, controls, identities and recovery payloads. recovery-trees.json maps all 104 output VFS files to exact source blobs, unchanged originals or included content-addressed payloads. Use the predecessor restore.py with this recovered directory to restore the observed failed tree; do not treat it as an installed game. No duplicate original package was fetched.