JS COM native execution — 2026-10-20

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

PARTIAL qualification. The unchanged positive fixture passed (exit 0); the malformed outer AddRef ret 8 fixture failed for the expected actual stack-cleanup mismatch (exit 1). Public lifetime and nested JS callbacks passed. Direct unmodified DLL/CreateInstance bridge coverage passed, but public activation through the JS carrier remains OPEN.

Identities and environment

The observer and generated PE/x86 code were independently read before running. The forwarding observer checks genuine BigInt callback tokens, arguments, zero return sentinel, guest EAX and actual ESP before production restoration. It also asserts restoration of GPRs, EIP, decoded IP, current thunk, steps, handler state, yield state and SEH. These assertions passed in the positive run; full register snapshots and numeric token values are not serialized.

Both commands used the fixture report's exact native arguments and pinned module/source; run-remote.js imposed a 120-second guard on each fresh, detached process group. Positive ran 13:09:37.301–13:09:37.724 UTC; negative ran 13:09:41.262–13:09:41.445 UTC. Neither guard nor log cap fired.

Observed x86 callbacks

Rows are in completion order. ESP includes the sentinel return-address consumption: ret 4 advances 8 bytes, ret 12 advances 16, and ret 16 advances 20. Every recorded return sentinel was zero.

Method Depth Argument words ESP before → completed EAX Parent decoded IP / thunk
nested AddRef 0x402500 2 0x403044 0x616fa0 → 0x616fa8 2 0x1a0000ac / 0x7500000
nested Release 0x402600 2 0x403044 0x616fb0 → 0x616fb8 1 0x1a0000e4 / 0x7500008
outer AddRef 0x402200 1 0x403040 0x616fc0 → 0x616fc8 2 0x1a000078 / 0x7500000
nested AddRef 0x402500 1 0x403044 0x616f8c → 0x616f94 2 0x1a0000ac / 0x7500000
nested Release 0x402600 1 0x403044 0x616f9c → 0x616fa4 1 0x1a0000e4 / 0x7500008
outer Release 0x402300 1 0x403040 0x616fd0 → 0x616fd8 1 0x1a0001b0 / 0x7500008
direct DllGetClassObject 0x602000 1 0x403020, 0x61700c, 0x61701c 0x616fe4 → 0x616ff4 0 0x1a000284 / 0x7500130
direct CreateInstance 0x402400 1 0x403040, 0x12345678, 0x403030, 0x403088 0x616fe0 → 0x616ff4 0x80004005 0x1a000284 / 0x7500130

The last two rows are explicitly direct bridge evidence. Both reentered against the same real suspended decoded loop and thunk. The IID_IClassFactory content checks passed, and CreateInstance preserved E_FAIL despite writing the nonzero output 0x55667788.

Three public activation requests retained resolve-only flags and recorded zero JS carrier callbacks. Guest owner-side activation results, lifetime counters and public caller ESP checks passed. This does not establish public DLL/CreateInstance JS-carrier coverage: the public handlers force resolve-only. No flags were changed and no production caller was introduced.

Expected malformed-ret rejection

The negative completed two genuine depth-2 nested callbacks, then rejected outer AddRef's malformed ret 8:

AssertionError: actual ret N cleanup before parent restore
actual:   6385612 (0x616fcc)
expected: 6385608 (0x616fc8)

The stack identifies checkReturn → observed com_callback_leave → production _invokeComCallback. The observer throws before forwarding com_callback_leave, and production restores the parent only after that call. Thus this is actual executed cleanup rejection before restoration, not a dependency failure or timeout. The failing outer row is not appended to runtimeEvidence.rows; its actual/expected ESP is retained in the error, while the two completed nested rows are serialized. This is an observer conformance rejection, not a claim that production independently validates ret N. No repair or rerun occurred.

Evidence, preservation and recovery

Self-contained evidence: scratch/runs/20261020-js-com-native-run/.

All 6,438 source identities matched the exact production Git tree. Before/after checks preserved 22,984 files across prior Army/ICM/callback/ MadBomber trees and dependency closure; module and fixture hashes matched. Remote postflight free space was 48,162,623,488 bytes. Local evidence was approximately 10 MiB, below the 20 MiB cap, with more than 2 GiB + 60 MiB free. Both process groups were absent. Runtime released at 13:10:49 UTC, left running with the assigned 15:53 UTC TTL.

Public activation JS-route coverage, capacity, serial exhaustion, stale epoch/thread/root, abort/yield, actual spill pressure/reclamation and instance retirement remain unqualified. No game, browser, renderer, gameplay or whole jump-system readiness claim. This report-only branch does not integrate main or modify shared HEAD/index, other workers' files or laptop work.