NFS3 current native connection prerequisite, 2026-11-17
The required genuine COMCTL32 connection cannot be proved on the current published execution path: COMCTL32 is now deliberately builtin-only. No fresh NFS catalogue, setup, chooser or game sequence was started. The authorized original sequence remains unused; Controls, transmission, Pause, Continue, acceleration, steering, road progress, speed/camera/collision effects and native Quit are unproved.
Evidence: scratch/runs/20261117-nfs3-current-native-connection-driving/.
Compared with the November 14 original failure, published changes now include
KERNEL.651 LS16 registration (f51ce2e1d), PE LS32 pairing (601bc0859), FT
relay/lifetime (fc63bbcba), QT/LS32 execution (655fd301d), leased-stack
validation (caa970b11) and nested NE image loading (57c40c5c3). However,
a6e88fb7d intentionally removed COMCTL32 from native loadable DLLs and
classifies it as builtin-only. The later absent-companion TRUE settlement
(56bfa6cf6) publishes no connection and is not genuine connection evidence.
Prepared one coherent graph from published origin commit
a166c1e9d352dfebf41f6652f81895ba9b814d49. The run-local helper reads Git blobs
into process memory and compiles the canonical include closure with its matching
compiler and region-layout section. It retains the module and complete source
hash inventory, not a source archive. It excludes shared foreign WIP and refuses
unpublished runtime source. Shared build outputs were not overwritten. This was
a focused run-local compilation, not a new full canonical build or production
repair.
All 135 original media pins from the retained November 14 manifest matched.
The unchanged original COMCTL32 is 577808 bytes, SHA-256
28a41e6a35c4509924a32a99841a815cf49e1d3ee6912ec26a823e45472edfa4.
Its actual header still identifies LS01/LB01, checksum 0x1e9a, QT offset 36,
FT offset 68. Matching KOMMCTRL is 155136 bytes, SHA-256
39bbfafa8b759ebfcf6a00ee878fa494581a9144891bbd788bded61441de13f9,
with Cctl1632_ThunkData16 exported at ordinal 301. The ordinary DLL path
already links to this matching media; the rejected 48112-byte companion was
not used. No media was copied.
The existing genuine attachment fixture ran once against that compiled graph.
Its media/Win4 metadata checks passed; loadDll then refused before mapping:
Builtin-only module cannot be mapped as native code: comctl32.dll.
No genuine attach, FT publication or retirement is claimed from this attempt.
The read-only contract check independently confirms the current builtin-only
policy. This is an intentional published policy boundary, not a demonstrated
new implementation bug warranting a speculative repair. No older source graph,
forced DLL policy, absent-companion scalar success or guard relaxation followed.
Recovered the prior local controllers from their recorded patch. Their eight key-review requirements, thirteen invalid pointer reviews and real normal/hung child wait/EOF checks pass. They were not used for game input; the existing acceleration-only controller would need a focused steering extension if a later authorized task reaches that point. No broad qualification loop was run.
Compilation and native prerequisite checks each had an observably armed finite independent deadline/disk watchdog, actual child wait and both pipe EOFs. The native check held the heavy-runtime lock and the compilation held the build lock. All owned children/watchdogs were joined. No box, browser, worker, source edit, guest/private call, configuration/clock/save edit, forced pump, registry import or deployment occurred. Historical terminal UNKNOWN results remain closed.
Next: resolve whether the intended current supported route should use the published WAT common-controls implementation or restore an explicitly supported genuine native connection route. Prove that prerequisite before spending the single fresh original catalogue/setup/driving sequence. This task does not silently substitute the builtin route for the requested connection proof.