#693 · home-lang/home

Track the final two whole-file Bun corpus suppressions together. Home already exposes the WebView APIs and Chrome transport, but the top-level Home executable does not honor BUN_INTERNAL_WEBVIEW_HOST before normal CLI dispatch, causing the WebKit host child to exit immediately. Port the early host entry into src/main.zig, promote webview.test.ts and webview-chrome.test.ts to native corpus routing, remove both rewriteNativeTodoCorpus branches, and validate unchanged pinned fixtures. Baselines: WebKit 10 pass / 1 upstream todo / 47 fail in Home versus 57 / 1 / 0 in pinned Bun; Chrome 51 / 1 on the first Home run, then 52 / 0 on a full replay and three focused fresh-process passes, versus 52 / 0 in pinned Bun. No deadline, workload, fixture, or assertion changes.

Published 2129e4a82 to origin/main as Chris Breuer without coauthors. The early macOS host dispatch validates the inherited u31 descriptor and enters the native host before CLI/JSC initialization. Both complete WebView suites and the shell integration matrix now execute through native corpus routes; all three whole-file TODO substitutions and their helper are removed.

Unchanged WebKit is 57 pass / 1 upstream TODO / 0 fail; shell is 378 / 83 / 0. The four ordinary native routes total 487 passes / 89 upstream TODOs / 0 failures. WebSocket's five TODOs supply no implemented coverage. Optimized build is 46/46; the focused restoration regression passes with zero logged errors and leaks.

The initial strict Chrome run still has its first-navigation timeout (51/1), despite a later 52/0 run and passing focused Home/Bun probes. That pre-existing intermittent failure is explicitly retained in #694; passing repetitions do not resolve it. No deadlines, assertions, fixtures or workloads were changed. Closing this host-startup/routing integration issue only; #66 and #202 remain open, as do the newly isolated #695, #696 and #697 aggregate gaps. Native C++ backend build ownership also remains external.