Alice first-command readiness and module diagnostic failure, 2026-11-03
The repaired first-command readiness worked in the sole original session. The
session reached the personally inspected New Game menu at1600 batches, then an
incorrect read-only module diagnostic stopped it before menu selection. The
query referenced wasmBytes, which is absent from the restricted control
evaluator. This was a harness mistake, not a native guest fault. No New Game /
Easy opening, world1022 capture, movement stack arguments, Player allocation
continuity, neutral supported samples, airborne comparison or route progress
was obtained. The accepted predecessor cave and offline reserved-world repair
remain separate evidence. usableForFooting=false.
Exact input was 08e25a4091a019c25e6afb3a092267bbe5aed246, including Alice
fault retention 0c2bc2da5641695157703a778a377e6f44b16d74. Verification refused
reuse of accepted WASM0a58: eight committed WAT/compiler files differ from its
compile input200832ae. compile-input-diff.patch and module-reuse.json retain
that result. After Jedi's explicit18:46:51Z runtime release, exact committed Git
blobs and separately pinned dependencies were streamed to the own fresh boat;
foreign WIP, including Jedi's active decoder changes, was excluded.
All5916 staged inputs passed full hashes. All43 external dependencies—15
original game files,27 pngjs files and actual stdole2.tlb—passed full hashes
locally and remotely. Actual imports, system-data mounts, fonts, PNG encode /
decode and the original14-file companion manifest passed before launch. No
compilation archive download or accepted prerequisite fixture rerun occurred.
Exact node tools/build-compile-wat.js compilation passed and produced
2125703-byte WASM SHA256
c523ed9fa266253b5635bf0b1c1d98940367efd713c73d7097d04b3d2c91b749.
The process's original compile/instantiate observer confirms those actual bytes.
No production source changed; no new full-build or production-test claim is made.
Actual launch and first failure
PID6938/session 47fd9c8a-2c3f-402e-af01-c5e205a102a4 started
18:48:14.838Z. commands-ready.py was integrated before launch and admitted
command1 only after the same live PID/start tick and actual server.listen
callback line. control-readiness.json retains that admission. The pinned
request, contact and capture helpers were installed unchanged. The seven
previously accepted readiness controls were reused; their live admission now
has original-session evidence.
Fault-status, snapshot and fault-arm passed. Four400-batch chunks completed;
all pending polls used get-local.py LABEL 0 without command resubmission.
startup.png is gray; menu.png clearly shows New Game highlighted. Both were
personally inspected. No key, mouse, attack, jump, cheat, save/config edit,
injected guest call or guest-memory write occurred. One premature host file
fetch before startup.png existed failed without sending a guest request; the
later completed capture was fetched normally.
The module observer's timer file initially contained empty arrays. Command10
actual_module attempted to inspect lexical variables outside the evaluator's
exposed scope and returned wasmBytes is not defined. Its unchanged receipt
and first-error.json preserve the error. The repaired first-error writer
triggered ordinary supervisor stop; exit0 at18:53:05.089Z after290.251 seconds.
The command was never retried, and there was no second original launch. All11
commands, including supervisor quit, are retained. No held movement phase or
selected fgame module/lifecycle chain existed to capture. Missing native bytes
cannot be reconstructed.
Bounded host-only repair
Post-failure module_receipt.py and module-status.py read the original host
observer receipt instead of using a control evaluator. They distinguish absent
or incomplete receipts as pending, require the original PID, compare every
compiled and instantiated module's complete hash/size with runtime pins, and
reject foreign PID, wrong hash and unknown instantiation. Seven controls pass
locally and on the same boat, with zero guest requests. Reading the actual
failed session also passes and confirms c523ed9f. Python syntax checks pass.
This is a host-only diagnostic repair, not new native gameplay qualification.
module-receipt-repair-pins.json pins it separately from the originally staged
helpers. The failed request and original source pins remain unchanged.
Reproduce the new focused repair without a boat:
python3 scratch/runs/20261103-alice-ready-world-ground-route/test-module-receipt.py
Recovery and custody
Full evidence and the restore recipe are under
scratch/runs/20261103-alice-ready-world-ground-route/. All6007 remote payloads
passed local size/full-SHA verification before delegated normal STOP.
Archive116491644 bytes, SHA256
c9bf94358c4e3f6e0b6b9f2a1034223dba47ff14fb68e232f395917d30015817.
RECOVERY.md, SHA256SUMS, archive-verification.json, exact source/dependency
pins, actual module, original log, readiness/failure/exit receipts, screenshots
and host-only repair tests are retained. Own original/supervisor PIDs were
absent and8123 closed before STOP. Local disk remained above2GB.
Fresh own boat bx_2jefq82t, TTL3600, original expiry
2026-11-03T19:47:02.734Z, was recorded before use. Runtime ownership followed
Jedi's explicit release; RUNTIME RELEASE was18:53:46Z after original exit.
Stop stop_361e535f5dde8ed7 completed18:54:49.134Z, error null, forced false.
Actual STOPPED18:54:49.099Z; available completed snapshot verified
18:54:49.057Z. Original expiry is inactive; custody returns to coordinator.
No predecessor/foreign boat, resume, subworker, public deployment or successor
was used. Single task ends here. The remaining gameplay work is unchanged:
complete the native repaired world1022 capture and lifecycle/stack evidence,
prove allocation continuity, then supported/airborne samples and ordinary route.