Invisible War chain integration on current main — 2026-10-15

Source integration prepared off main and subsequently merged by root at 3fdb29373325607fc2780a5d64832e5b3dd4ac08. Subsequent normal build and native conformance passed on module 04ede with the reviewed fixture repair: see combined validation results. The preparation record below describes the earlier source-only phase.

This task branch starts at main 88cb3c77973aee82b55255fce1a13f4339cc2298. It applies the selected diff from held base eb26d3a567d0a71ba6c1672afbebd82836d36d65 to 4a65118df097b7a9f9244bde186862a70d56c9ae, excluding tools/iw-native-validation.py. Historical documents retain their original commands and claims; that omitted Python controller can be recovered from its historical commit, but is not a supported current integration runner.

The three-way application had no textual conflicts. The integrated lib/thread-manager.js retains main's guarded cooperative crash diagnostics and the held chain's send scheduling, callback ownership, loader publication, and exact receiver retirement. Relative to the held thread manager, the only difference is the current-main crash diagnostic block. Other unrelated main changes remain intact. Scalar cross-process messages remain the supported scope; pointer marshalling and original Invisible War execution are not proven.

Two historical native test filenames are explicitly assigned to the E2E tier in tools/test-tiers.js: receiver-retirement-native and scoped-dll-native. They require an admitted module and are inappropriate for default unit runs.

Local verification completed in a 6.9 MB explicit non-cone sparse checkout:

During that initial preparation, no full WAT/WASM build, native full-module test, remote command, browser, original IW run, main merge, or deployment was performed for this integration. The prior receiver-retirement evidence is scratch/runs/20261015-iw-receiver-native/attempt1-reviewed, archived with SHA-256 5fa94ff85bd3e54d362d2939e8c26c639ee29bf21d62a6b2429a0e6aad5588f5. It tested candidate 66 / old f859 / restored under canonical a948. It does not prove the combined current-main build.

The subsequent validation used a separately reviewed bounded JavaScript controller to stage the complete tracked build closure and dependencies in an isolated remote checkout, pin physical source bytes, run the full build, record the produced module hash, and run combined native conformance. The existing historical native controllers deliberately pin older sources and a948; they must not be relabeled as current-build proof. Updating the native fixtures for an explicit expected combined module hash and running admission, scoped loader, receiver retirement and cross-process native routes is recorded in the linked result. Root owns the sole remote lane, its grant, TODO/STATUS, and any integration decision.

Selected held paths: