Bun parity: remaining open items to reach 100% test-suite pass

Native Bake full-suite checkpoint: source ccecdcf9b and 1,185 Git-verified evidence artifacts. All 24 unchanged Bake files pass 177 cases with zero failures/zero skips and two original TODOs; native output, exact identities and source inventory validate. Genuine frozen Home locks replace the empty React marker. The suite budget preserves per-test deadlines; spawned fixture cwd and production source-map retrieval are repaired. Canonical graph identities fix changed-dependency path aliases. Coordinator controls retain 29 complete journals; development/HMR/production pass. The fresh 157-file regression has 396 passing cases, 142 process checks, zero failures, 37 case skips and three file skips. Build, validators, ABI, lint and corpus integrity pass. The initial 175-pass/two-failure run remains retained. #902 is complete for this tranche; #901 keeps optimized native/platform gates and #564 keeps Linux TODO coverage. TODOs/skips receive zero pass credit. The full Bun feature/suite/all-platform objective remains open.

Tracking issue for the remaining work to reach 100% parity with Bun's official test suite (~/Code/bun; current native artifact source SHA 4982b91e3702094330f3be3883354c52b8c01323, original historical pin fd0b6f1a27), runnable here via home test. Each item has the root cause traced during investigation. We tackle them top-to-bottom; check off as landed (small fix:/feat: commits, pushed).

Current main checkpoint (2026-10-13)

Native console methods, buffered replay and cleared-realm lifetime (2026-10-13) landed in source 56df99d7f, merged integration be4364972, and verified evidence de6aea239. Canonical SDK records provide count/reset, typed timeLog/timeEnd and per-session buffered replay with actual stacks/timestamps. Owner attachment differs from VM console state; Runtime.disable suppresses notifications while preserving connected state. groupEnd/clear arguments match the native contract. Clearing the buffer and remote group now retires idle realm injected-script roots; actual still-bound handles, pending calls and paused debugger state prevent retirement. Unrelated object handles and an in-flight async call remain usable. Last frontend detach retires injected-script state, and the non-owning console registry retires across finalization threads. Both source and merged builds pass 56/56 steps; fresh merged validation passes all nine focused commands, six broad drivers, 33 native groups, seven Node/seven Home realm controls, 14 ABI tests/453 assertions and 32 report-validator tests. All 64 report outcomes match expected counts/errors/exits, including twelve negatives. Twenty unchanged originals retain 53 passed cases, one unchanged unsupported-method expectation failure and 17 passed process checks, with zero skips/TODO/filter/retries; #886 receives no pass credit. Failed Node oracle assumptions, the Home post-clear lifetime failure and resource stops remain immutable; temporary tracing is removed. Full schema, independent remote-object/session ownership, evaluated-realm retirement outside explicit console clearing, module/export/callback/owner-shutdown acceptance and full suite/platform validation remain open under #888/#428/#885/#66.

Native profiler sharing at 5cd57e8ea with verified evidence: CLI and inspector owners consume actual JSC samples through detached native records, preserving CLI JSON/Markdown history and independent repeated session windows. Shortest active owner interval is selected; session stop/disconnect preserves CLI profiling and active-session process exit exports successfully. Debug 56/56, all 28 native groups, 14 ABI controls/453 assertions and 32 report-validator controls pass. Twenty unchanged originals retain 53 passed cases, one failed unsupported Runtime.evaluate expectation and 17 process checks; no skips/TODO/filter/retries and no #886 pass credit. Evidence preserves the first inlined-workload assertion failure and 64 replayed report outcomes including 12 negatives; earlier eight resource stops remain in investigation evidence. Full Bun parity, complete realms, worker-to-main inspector attachment, coverage, precise cadence measurement, all ownership schedules, Release/ASAN/all-platform remain open under #428/#66.

Historical publication checkpoint (2026-09-20)

Native phase/context work landed in 64481fe09 with evidence publication b83c54f4d. Vendor checkout and install/build became separately verified phases, with revision checks before hooks and live remap/Docker settings carried into children. The build passed 23/23 steps and 21/21 harness tests, plus launcher, service/lifetime and validator controls. Fresh pinned Elysia setup matched all 283 expected source hashes; all 129 selected original files completed once with 1,516 registered passes, zero failures/skips/TODOs, retaining the one original WebSocket exclusion. This checkpoint did not claim complete primary execution, Linux Docker verification, or full parity. Boundary and API · Evidence

Previous publication / remaining work (2026-09-08)

Full logical Bun parity remains incomplete. Published to origin/main: native service/preparation source a2e2863fc, verified evidence c9fc9bf63. Home SHA256 91d6b1024f9d4c02c6b7f9089b476d8a0646294f4ed7392e5e3ce549e52db763.

Native service lifetime and explicit vendor preparation are implemented. home test --bun-corpus-remap launches the original installed remap service with its original arguments and 5,000 ms startup deadline, drains output throughout its lifetime, and owns shutdown until parent stdin closes or the service exits unexpectedly. home test --bun-corpus-prepare-vendor elysia selects and journals clone/fetch/checkout/revision/install/build, retains separate Git/Home executable identities, and preserves the original 180-second Git/install and 60-second build deadlines. A failed install leaves build visibly unstarted. These operations earn zero registered-case or passing-process credit.

23/23 native build steps and 21/21 harness tests pass, along with four service lifetime units, four journal units, 18 validator controls and five private CLI controls. The private CLI evidence retains invalid readiness, the five-second deadline after output EOF, unexpected service exit with parent stdin open, install failure and build failure. The real pinned remap service passes five HTTP protocol checks through the native command, with complete captures and unchanged dependency hashes. Fresh native Elysia preparation completes all seven steps in 49.8 seconds; its 283 resulting source hashes match the earlier independently verified setup/lockfile normalization. Formatting, targeted Pickier and 50 pinned setup-input checks pass.

The latest complete Elysia run is not green: all 129 selected files complete once with 1,515 registered passes, one failure, zero skips/TODOs. handle distinct union in test/validator/response.test.ts calls .listen(3000); the unrelated PredictHQ development server (PID 28404 at diagnosis) owns that port. Pinned Bun fails the same unchanged case in a separate one-file diagnostic (27 passes, one failure). The listener and original tests were not changed, and no retry or alternate port was used to obtain a pass. Both full-run source integrity and the original selection match. The original WebSocket exclusion remains separate. The first diagnostic verifier expected the same error literal; a separate retained-capture analysis confirms the conflict without rerunning either runtime. A private error-object comparison additionally found message/errno/address/port differences, now tracked in #726; Home's existing preservation of real OS failures must be retained while auditing compatibility.

572 committed compressed artifacts have verified decompressed hashes. Restored journals reproduce successful service/preparation, failed private controls, the failed complete Elysia run and failed pinned-Bun diagnostic separately. The first build was stopped below the unchanged 1 GB critical disk floor after macOS allocated more swap; verification did not run. A cleanup preflight and refused admission are retained too. Corrected cleanup preserved protected binaries and linked native inputs; the completed rebuild required 5 GB free to start. Removed 6,083,408,581 logical bytes of generated caches/dependencies, old vendor data and unused build outputs. Source and other active work are preserved.

Still open: connect these operations with the original CI ordering and selection gates, Docker coordination, live service settings and default unified coordinator (#724); free the original fixed-port prerequisite before claiming a successful new Elysia run; resolve the missing optional legacy DuckDB and earlier lifecycle failures (#725); audit bind-error compatibility (#726); execute the whole applicable primary/vendor suite and finish remaining runtime features, native Linux/Windows/ASAN verification and independent native ownership. Earlier root/test setup process success and the separate 18-case N-API DuckDB run remain evidence on their recorded earlier binary; they are not new execution on this one.

API and scope · Native service/preparation evidence · Earlier native setup evidence

Earlier prepared Elysia execution checkpoint

Published to origin/main: implementation 9d6815afa, evidence 176f685f7. Home SHA256 19e41223c7fc2d2dcda763470fcc84570900db08b4d547340bdae5286d42bc98.

Complete pinned-selected Elysia execution: 129/129 files completed, 1,516 registered cases passed, zero failed, zero registered skips, zero TODOs. The run used no positional filter or start/limit and one attempt with original per-file deadlines. The selection matches pinned Bun exactly, including the separately recorded original ws/connection.test.ts exclusion; that excluded file earns no passing or skipped-case credit. All 129 captures reached EOF. Raw output and JUnit hashes, registered cases, selection completeness, all 283 post-install vendor source hashes and the Home executable hash validate.

The production home test --bun-corpus-prepared-vendor elysia command verifies Git HEAD against the manifest tag and executes each selected vendor file in its own project's cwd with ordinary config discovery, forced vendor test mode, correct validation paths and serial environment. Ordinary failures remain recorded and later files continue. This command explicitly requires prior checkout/install/build and journals setup_performed: false. The preceding Home 716f39bd… build performed the independently verified native install/build; the new 19e41223… build executed the suite. This is not a fresh end-to-end CI setup claim.

23/23 build steps, 17/17 native harness tests and 11/11 validator controls pass. Private controls exercise project config, custom test paths/extensions, serial environment and a real assertion failure followed by a successful file. Targeted Pickier and whitespace checks pass. 409 committed compressed artifacts have verified decompressed hashes; restoring the archived reports reproduces all 129 complete outcomes and 1,516 passing cases. Cleanup removed another 371,467,160 bytes of obsolete owned generated objects, preserving source work.

API and verification boundary · Complete execution evidence

Earlier outcome and lifetime batch at 61670c72b (#722/#723): 23/23 build steps and 12/12 native corpus harness tests pass, plus 2 child-ownership units, 3 journal units, 9 validator units and targeted Pickier. The original per-file deadline now covers a child that stays alive after both output pipes reach EOF. Actual libc close through Home FFI reproduced the pre-fix 30-second supervisor failure; the corrected native runner times out at the unchanged 20-second Node deadline and preserves early successful exit. Child status remains unreaped until final cleanup. The wait helper also cross-compiles for x86_64 Linux/musl and Windows/GNU; native Linux/Windows execution remains unverified, so #723 stays open for that work. Schema 2 records verified stream completeness; legacy schema 1 remains readable with completeness marked unknown.

That earlier six-file original batch validates with 402 passing cases, 1 original platform skip, 10 TODOs, one successful Node script, one verified expected-failure process check and one comment-only file. All six captures reached EOF. The original negative fixture retains its one-failure JUnit case and contributes no passing test credit. Every selected original source/snapshot hash and the executable identity remain unchanged. Private controls verify mixed outcomes, invalid negative contracts, overwrite refusal, both open-pipe and actual closed-pipe timeouts, SIGTERM, interruption, and failed writes. Original failures and first unsuccessful controls remain retained. Final evidence; baseline and remaining scope.

#724 remains the full-suite prerequisite: selection/API and Elysia setup are now verified as described above; native host discovery, complete root/test installation and registry/service setup, vendor execution, and complete applicable-suite outcomes remain unfinished. The pre-exclusion discovery inventory alone is not the complete CI suite. Excluded, skipped, TODO, unstarted and unsupported files never count as passing implementation coverage.

Previous native launch batch (#703): 23/23 native/harness build steps and 9/9 harness tests pass. Five focused units pass. All 19,016 launch-rule selections match pinned Bun over 4,754 discovered files and four CI/local/ASAN contexts; these are rule comparisons, not passing corpus files. Production capture now applies original ordinary/integration/Node/script deadlines, CI GC/integrity/transpiler-cache settings, validation-list rules, fresh per-file storage and real Home command aliases. Real cache/child/cleanup regressions verify the corrected allocation ownership and initially empty install cache. Launch baseline, 64 final artifacts.

Prior grouped launch verification: seven native private regression files pass. Unique selected original cases are Home 71 pass / 1 fail; pinned Bun 72 pass: HTML 45, link/binlink 11, audit 16. Two additional original Node files complete real process checks, and one original comment-only file contributes no passing cases. All selected original sources and snapshots remain unchanged. The generated fresh-cache control passes in both runtimes. The first build's three allocator crashes and Home-only cache-control failure are retained, with their fixes independently verified.

#721 retains the one failing original audit snapshot assertion. Audit remains Home 15/16 versus pinned Bun 16/16. The only differing line expects express › connect › csurf › csrf › uid-safe › base64-url. Its pinned fixture resolves that UID package to csrf/uid-safe@2.1.4, which depends on random-bytes and has no base64-url edge. Home reports the actual express › connect › express-session › uid-safe@2.0.0 › base64-url@1.2.1 path. No nonexistent edge or passing assertion was fabricated. #720/#721 remain open; native protocol/authentication, exact production reachability, affected-version/workspace paths, cycles and lock preservation are covered by the passing native audit regression.

#722 retains the remaining full-inventory execution and outcome-verification requirement, following the verified storage/JUnit/skip/TODO implementation above. The inventory contains 4,754 pre-exclusion entries (1,863 test-runner entries and 2,891 scripts); a completed full-suite execution is still missing. Synthetic corpus rewriting/bootstrap fallback is removed. Full integration/vendor/service setup, native ASAN and other platforms, default CLI fallback removal, and independent native build ownership remain open under #703/#709/#202.

Previous patch checkpoint a4b73596f passed 58 original cases per runtime (link 4, native-binlink 7, patch 29, install-patch 18), six private files, and build 46/46; evidence. #719 is complete for native patch activation and tested lifecycles. The original patch aggregate was not rerun for this launch batch; all six older private files plus audit were. #718 bin ownership is fixed on macOS, with native Windows filesystem verification still open. #717 remains complete for the tested native link lifecycle.

Previous package milestones #713/#714/#715/#716 remain verified and closed: local dependency identity/deduplication, long-prerelease frozen lock equality, native update/outdated and cache-freshness regression. The preceding selected original update/outdated/interactive/semver batch passes 78 cases per runtime, excluding filtered-out cases. Create entrypoints and required native parser restoration are verified. #190 self-upgrade and #710 fixture validity are now closed; #438 JSX failures and #701/#694 unexplained deadline failures remain open.

Current compressed build/test artifacts are committed under docs/docs/bun-port-evidence/. Generated fixtures and aged compiler cache data were cleaned after preserving evidence; source changes and installed binaries were retained. Earlier raw logs lost when the previous worktree disappeared are not claimed retained; their committed summaries/hashes remain historical evidence.

Earlier checkpoints

Earlier verified checkpoint: 1cbac2921, with implementation e1a5d0e20 and scanner correction 6448d628a, all pushed to origin/main. #702 is complete for native HTML activation and removal of fabricated FormData child output/RSS. 100% logical Bun parity remains incomplete.

• Ordinary and single-native-VM HTML directory routes each pass 145 tests / one original Linux-only skip / zero failures. The native aggregate's 530 assertions match pinned Bun. Home's real 100-iteration file-error child measures 1.78 MB growth, within the unchanged 10 MB limit. Build 46/46; focused harness 23/23 steps / 3/3 tests, with independent registration metadata.
• Adjacent routes pass: Blob 65/65, body/stream 9,467 passes / four upstream skips, Headers/Response 170/170, Request 24/24, bootstrap FormData 5/5, microtasks 2/2. #701 remains unexplained and open; a passing run is not a repair. #694 remains open.
• #703 is the next broad migration. Exact routing predicates show 175 native test-runner paths, 266 native scripts and 4,267 bootstrap paths among Home's 4,708 classifications. Exact pinned CI discovery selects 4,754 tracked paths before exclusions, exposing 78 missing and 32 extra Home entries, plus mode/config differences. These are inventory counts, not suite passes. The audit command and full path sets are now published in the repository.
• The native triage scanner no longer extends original test deadlines or retries timeout-only failures as slow. Its negative control retains one attempt and a failure. It remains a triage tool, not the complete acceptance gate; discovery and full outcome preservation remain in #703.
• Pinned-object integrity remains 12,990 identical regular files, five raw-identical symlinks, zero missing paths and zero mode differences, with only historical expectations metadata different. Remaining substitutes, faithful full-suite execution, other platforms and independent native build ownership remain unfinished under #202/#703. Logs: zig-out/bun-port-702/; verified Home SHA-256 4a937ded48d609b76e336fdc192dd96439653a228073a234aaafcba176a5e783.

Previous Blob publication: f491cacd7 closed #700 with 65 native passes, preserved the original allocation/prototype/ownership workloads and four snapshots, and removed UTF-16 child and array-prototype descriptor substitutes.

Previous body/stream publication: 04644b2d0 closed #699 with 9,467 native passes and four original skips, removed three clone-specific substitutes, and retained the full HTTP/3 matrix and child/GC workloads. Its adjacent Request run exposed the original 5-second deadline failure now tracked in #701; subsequent diagnostic passes were not counted as a repair.

Previous Headers/Response publication: 649c3c48f closed #698 with 170 native passes, corrected mirror cwd/startup environment and absolute-path CLI rewriting, and preserved the original Response snapshot. Its build passes 46/46 and focused harness 6/6; the initial 4/5 run exposed the additional CLI root defect and remains recorded as historical evidence.

Previous Request publication: 5e45c58a3 closed #697 for native Request activation and removed unused bootstrap VM initialization from native corpus dispatch. Its complete four-file matrix passes 24/24. Direct native stress peak footprints were 22,594,376 bytes for clone stress and 194,872,232 bytes for method-allocation stress; original loops and limits remain intact. The older bootstrap implementation is not claimed repaired.

Previous paired repair: e148e06c1, published to origin/main. #695 and #696 are fixed: complete TypeScript conformance is 1,419/1,419; both optimized Bake integration scripts and gzip decoding with both libdeflate settings pass. 100% logical Bun parity remains incomplete.

The preceding main commit 2129e4a82 enters the macOS WebView host before CLI/JSC initialization and restores native execution of the shell and both complete WebView matrices. All three remaining whole-file TODO substitutions and their helper are removed. #693 is complete for that integration.

• Unchanged pinned WebKit: 57 pass / 1 upstream TODO / 0 fail / 141 assertions. Shell: 378 pass / 83 upstream TODOs / 0 fail / 1,035 assertions.
• Four ordinary native corpus routes: 487 pass / 89 upstream TODOs / 0 fail / 0 unsupported registrations. Chrome WebSocket contributes zero passes and five upstream TODOs, not implemented coverage.
• The first strict Chrome run still fails its original first-navigation deadline (51 pass / 1 fail); pinned Bun passes 52/52. Later probes and a full Home run pass but do not erase that failure: #694 remains open. No retry, warm-up, sleep, timeout extension, assertion change, or workload reduction was added.
• Optimized native build: 46/46 steps. Earlier feature-flag units: 6/6 with defaults and in each explicit 0/1 fresh-process run; unit build 23/23 steps. Both complete Bake production/development integration scripts pass; absent/0/false opt-in is correctly rejected. Unchanged gzip/fetch is 24/24 / 43 assertions with each libdeflate setting.
• Nested-rest checker regressions: 4/4; complete TypeScript conformance 1,419/1,419; standalone reproduction exits zero. The original regression now requires zero diagnostics, and new negatives retain element-type and tuple-order errors.
• Earlier source-restoration regression: 1 pass, zero logged errors/leaks. Earlier completed native runtime units: 1,826 pass / 19 skip / 0 fail; that entire unit artifact was not rerun for the latest paired repair.
• The earlier optimized aggregate was interrupted (exit 143) and is still incomplete. Its nested-rest and Bake/feature-flag failures are repaired and verified separately above (#695, #696); no completed aggregate or whole-suite pass is claimed. The default Debug aggregate was not established by that run.
• The earlier bootstrap Request stress test reached 13.7 GB sampled footprint / 14.4 GB peak and was stopped. Its obsolete execution path is replaced by verified native coverage in #697 above; the bootstrap shim used by other adapters is not claimed repaired. The earlier full aggregate was not resumed, and no completed corpus aggregate or whole-suite pass count is claimed.
• Pinned Bun 4982b91e3702094330f3be3883354c52b8c01323: 12,996 tracked paths present; 12,990 identical regular files, five identical symlinks, one differing expectations.txt, zero missing. The expectation delta removes four historical FAIL entries; executable test sources are unchanged.
• Changed-file formatting, documentation Pickier and whitespace checks pass. Repository Pickier retains 59,302 findings (31,238 errors / 28,064 warnings). The README's Settlers checkout is absent. External Bun C++ build artifacts, other adapters (#202), upstream TODOs/skips, other platforms and full source/build ownership remain unfinished.

Publication correction: all 18 commit URLs in this issue's historical body were verified as ancestors of main at this checkpoint. Historical statements below saying those commits were not merged describe their original publication state and are superseded by this audit.

How to run / verify

• Native debug build: zig build debug -Denable_jsc=true -j2 --summary all from the Home repository. External native dependencies and ownership limits are documented in docs/docs/NATIVE_RUNTIME_BINDINGS.md.
• Native regression: HOME_NATIVE_VM=1 ./zig-out/bin/home-debug tests/runtime/native-worker-inbox-shutdown.test.mjs (substitute the desired regression file).
• Strict native corpus: HOME_NATIVE_VM=1 HOME_CORPUS_FULL_VM=1 ./zig-out/bin/home-debug test <corpus-file>; both overrides are required to bypass the pragmatic corpus adapter.
• Outer corpus CLI: unset HOME_NATIVE_VM and HOME_CORPUS_FULL_VM; any nonempty value, including 0, enables those overrides. Keep native execution and the pragmatic adapter's results separate.
• Use bounded subprocesses and per-child timeouts; limit concurrency to 2–3 small fixtures. Clean only owned temporary artifacts. Do not use blanket pkill commands.
• Leak measurements must retain their original workloads and thresholds; Debug and ReleaseSafe results are not interchangeable.
• Skips, disabled bodies, timeouts, unsupported cases, external dependencies, and failing negative controls do not count as completed parity.

Historical publication checkpoints (through 2026-08-28)

• Published HTTP/3 verification-isolation checkpoint: 0fd884f59, pushed on codex/runtime-port, not merged to main. #539 is closed after a controlled environment correction: the complete unchanged adversarial file passes 12/12 serialized Home processes and 12/12 serialized pinned Bun processes, all 27/27 / 163 assertions. Three eight-way waves reproduce the same first-64-KiB deadline sequence in both binaries (Home 11/12 process passes; pinned Bun 5/12) while all sixteen UDP ports are distinct and the shared eleven-CPU host is saturated by native tests, a ReleaseFast build, and system work. No runtime source, test deadline, workload, retry, sleep, skip, or protocol fallback changed. Heavy HTTP/3 files must be verified serially and away from builds. #530 retains platform/integration and native dependency ownership; all other explicit suite gaps remain. 100% logical Bun parity is not achieved.
• Previous native TLS SNI/ALPN checkpoint: a9a95f6a4, pushed on codex/runtime-port, not merged to main. #542 now ports per-connection synchronous/asynchronous SNICallback, pending-certificate resumption, original callback error propagation, same-host precedence, offered-protocol ALPNCallback validation, callback-safe teardown, and ALPN selector handoff across SNI contexts. The complete unchanged server file is 38/38 / 147 assertions, exactly matching pinned Bun. The new combined lifecycle regression passes 20/20 independent processes plus VM destruction. The seven-file TLS sweep is 120 pass / 1 skip / 3 TODO / 2 fail / 380 assertions; both failures are live bun.sh OCSP checks reproduced in pinned Bun. Build 17/17; units 1,828 pass / 19 skip / 0 fail (19/19 steps); sequential regressions 63/63, including full spawn and child-process. Home's vendored C source compiles with reconstructed pinned release flags, while the debug build still links the pinned Bun object. Darwin only; #530 platform/integration, other open subsystems, skipped/TODO behavior, dependency ownership and whole-suite parity remain incomplete. 100% logical Bun parity is not achieved.
• Previous native TLS session/keylog checkpoint: 04569d8f9, pushed on codex/runtime-port, not merged to main. #543 replaces the no-op native dispatch with retained FIFO session/keylog delivery for direct TCP TLS and upgraded Duplex TLS, preserving session-before-data ordering across destructive callbacks. The complete unchanged connect file is now 28 pass / 2 fail / 1 skip / 106 assertions, exactly matching pinned Bun; both remaining live OCSP assertions also fail in Bun. The native lifetime/GC regression passes 20/20 independent processes. Build 17/17; units 1,828 pass / 19 skip / 0 fail (19/19 steps); sequential regressions 62/62, including 31 native files. Adjacent TLS is 47 pass / 2 skip / 7 fail / 424 assertions; all seven failures are SNI/ALPN work in #542, now next. The checked-in Home uSockets source has the logical queue implementation and compiles with the linked release object's exact flags, but the debug build still links that pinned Bun object. Darwin only; platform/integration, skipped/TODO behavior, native dependency ownership and full parity remain incomplete. Whole-suite parity is not achieved.
• Previous native TLS context checkpoint: fbdfbf890, pushed on codex/runtime-port, not merged to main. #532 now provides private contexts/CA isolation, binary PFX, detailed certificate chains, hostname authorization and TLS min/max propagation. Six unchanged core files pass; context 7/7, cache 9/9, cert 28 pass / 3 TODO, hostname 5/5. Native normal/destruction and original leak checks pass. Native build 17/17; runtime units 1,828 pass / 19 skip / 0 fail, 19/19 steps; sequential regressions 61/61, including 30 native files. Complete compression 32/32, HTTP/2 client 60/60, HTTP/3 client 52/52, both proxy files, full body-stream 9,086/9,086 / 135,984 assertions, five EOF/fetch files and both abort files pass. The initial HTTP/3 adversarial run failed 24 pass / 3 fail / 160 assertions, followed by three 27/27 / 163 serial replays. #539 remains unresolved; passing retries do not erase the final artifact’s initial failure or prior Home/Bun failures. 249 TLS sources, 48 HTTP/regression sources, and 13 TLS implementations match the pin. Full TLS server/connect files still fail: #542 tracks SNI/ALPN callbacks, #543 session/keylog delivery; two live certificate assertions also fail in pinned Bun. Failed attempts and all skips/TODOs are retained. Darwin only; integration, platform and full ownership remain incomplete. Whole-suite parity is not achieved.
• Previous compression/CONNECT checkpoint: 2c5df8cce, pushed on codex/runtime-port, not merged to main. #531 ports all four request-compression encodings and file/buffer ownership; #535 repairs CONNECT writer/envelope handling. Complete unchanged compression 32/32 / 78 assertions, HTTP/2 client 60/60 / 197, HTTP/3 client 52/52 / 241, and both proxy files pass against pinned controls. Full body-stream 9,086/9,086 / 135,984; build 17/17, units 1,827 pass / 19 skip / 0 fail (19/19 steps), regressions 60/60, including 29 native files; all five EOF/fetch and both abort files pass. HTTP/3 reliability remains unresolved in #539: initial adversarial failure, then three passing Home replays; failures also reproduce in published Home and pinned Bun. TLS context work remains #532. Forty-eight test/harness/fixture sources and eleven implementations match the pin. Failed attempts remain recorded. Darwin only; skips/TODOs, platform/integration and full source ownership remain incomplete. Whole-suite parity is not achieved.
• Previous HTTP/2 checkpoint: fd239c3ac, pushed on codex/runtime-port, not merged to main. #533 now preserves the idle-session Host hash and rejects invalid response-name tokens while consuming complete HPACK blocks. Complete unchanged HTTP/2 adversarial 15/15 / 33 assertions (parent 13 pass / 2 fail); lifetime 7/7 / 21 assertions with original 200-request workloads. Full body-stream 9,086/9,086 / 135,984 assertions. Build 17/17, units 1,825 pass / 19 skips / 0 fail (19/19 steps), sequential regressions 59/59 including 28 native files. HTTP/2 client remains 58 pass / 2 fail / 2 errors; HTTP/3 client 50 pass / 2 fail, both compression #531. HTTP/3 adversarial retains 27/27. Newly exercised CONNECT-proxy crashes reproduce in both parent and candidate; pinned Bun passes both files, tracked separately in #535. TLS context work remains #532. Forty measured test/harness/fixture sources and six consulted implementations match the pin. Darwin only; platform/integration, skips/TODOs and full source ownership remain unverified. Whole-suite parity is incomplete.
• Previous TLS/HTTP transport checkpoint: 29c196835, pushed on codex/runtime-port, not merged to main. TLS ABI offsets, HTTP/3 trust eligibility and duplex progress are repaired. Full unchanged body-stream 9,086/9,086 / 135,984 assertions; HTTP/3 adversarial 27/27; client 50 pass / 2 fail (compression #531). HTTP/2 client 58 pass / 2 fail / 2 errors (#531); adversarial 13 pass / 2 fail (#533 verification-host isolation/header validation). TLS server validation 16/16; remaining context/CA/version work is #532. Build 17/17, units 1,824 pass / 19 skips / 0 fail (19/19 steps), sequential regressions 58/58 (27 native files); full spawn 126 passes, child-process 32 passes. Five complete fetch files and both abort files retain their passes. 72 test/harness sources and six implementation sources match the pin. Earlier timeout and disk-exhaustion attempts are retained; complete sequential reruns pass with original workloads/deadlines. See #530 for detailed evidence. Shared Darwin checkout; platform/integration, skipped/TODO behavior and full ownership remain unverified. Whole-suite parity is incomplete.
• Earlier body-abort checkpoint: fb161314a, pushed on codex/runtime-port, not merged to main. #529 ports terminal response-error settlement before upload cancellation; unchanged abort file 2/2 / 6 assertions (parent 1 pass / 1 fail), queued-abort 1/1, and native 24-scenario normal/destruction/reentry checks pass. Build 17/17; units 1,824 pass / 19 skips / 0 failures (19/19 steps); regressions 57/57 (26 native files); 64 measured upstream sources match the pin. Five body files pass, including clone 25/25 and body 346 passes / 4 skips; five fetch files retain their passes including gzip 24/24. At that earlier checkpoint, the full body-stream matrix was not green: parent 4,883 pass / 4,203 fail / 2 errors, candidate 4,883 pass / 4,203 fail / 10 errors, pinned Bun 9,086/9,086. #530 tracks the HTTP/3 server path: parent client/adversarial files are 6 pass / 46 fail and 5 pass / 22 fail; both clients fail against Home's server before its JS handler, both succeed against Bun's server. Original assertions/workloads/deadlines retained. Historical HTTP/3 completion claims below are corrected. Shared Darwin checkout; unrelated compiler edits excluded. Platform/integration, skips/TODOs and full source ownership remain unverified. Whole-suite parity is incomplete.
• HTTP/installer checkpoint: 90ced0ed6, pushed on codex/runtime-port, not merged to main. #526 repairs buffered EOF completion and fragmented tar-format selection; native real-install, streaming-handshake, VM-destruction and three 404 transport controls pass. #527 advances unchanged fetch-gzip from 22/2 to 24/24 / 43 assertions, preserving the 1,025 MiB workload. #528 advances unchanged streaming-extract from 5/1 to 6/6 / 180 assertions, enforcing the pinned 2 GiB buffered limit against the original 2.25 GiB payload. Four further complete fetch files pass; full zlib retains 378 passes / 2 skips / 434 assertions. Retains bun-run 291/291, native hard-link-PATH bunx 33 pass / 1 Windows-only skip / 0 fail, workspaces 58/58, eval 33/33, tsconfig 6/6, resolver 39 pass / 2 skips / 1 TODO plus its spawned 9 pass / 1 TODO, and 21 config controls. Build 17/17; units 1,824 pass / 19 skips / 0 failures (19/19 steps); regressions 56/56 (25 native files); 46 measured upstream test sources match the exact pin. No upstream assertion/workload/deadline changes. #526–#528 retain platform/integration scope. Shared Darwin checkout; unrelated compiler edits excluded. Skips/TODOs, other platforms, integration and full source ownership remain unverified. Whole-suite parity is incomplete.
• Resolver checkpoint: 9b3a5c1ad, pushed on codex/runtime-port, not merged to main. #525 ports canonical resolver diagnostics and fallible, retained installer initialization errors; readable-file dispatch now precedes cwd scanning. Unchanged tsconfig-override 6/6 / 17 assertions (parent 5/1), resolver 39 pass / 2 skips / 1 TODO / 0 fail / 59 assertions plus spawned file 9 passes / 1 TODO / 41 assertions (parent's unreadable-cwd failure resolved under the original 5,000 ms deadline). Native repeated-error and VM-destruction checks pass. Retains bun-run 291/291 / 416 assertions, native hard-link-PATH bunx 33 pass / 1 Windows-only skip / 0 fail / 161 assertions, workspaces 58/58 / 192 assertions, eval 33/33 / 70 assertions, and 21 config controls. Build 17/17; units 1,820 pass / 19 skips / 0 failures (19/19 steps); regressions 56/56 (25 native files); 37 sources match the exact pin. No upstream assertion/workload/deadline changes. #526 remains a reproduced failure: EOF-delimited registry 404s trigger a pending-task assertion in parent and final candidate; length-delimited controls pass. Other platforms, branch integration, skips/TODOs and full source ownership remain unverified. Shared Darwin checkout; unrelated compiler edits excluded. Whole-suite parity is incomplete.
• CLI config checkpoint: 828ecc729, pushed on codex/runtime-port, not merged to main. #517 optional-config and entrypoint scanning now match all 21 pinned-control boundary cases; native normal/destruction regression passes and published parent fails the new assertion. Full unchanged bun-run 291/291 / 416 assertions, native hard-link-PATH bunx 33 pass / 1 Windows-only skip / 0 fail / 161 assertions, workspaces 58/58 / 192 assertions, and eval 33/33 / 70 assertions (declared React dependency installed by Home). Build 17/17; units 1,820 pass / 19 skip / 0 fail (19/19 steps); regression commands 56/56 (25 native files); 35 measured sources byte-identical to pin. No upstream assertion/workload/deadline changes. New #525 tracks the unchanged tsconfig-override failure: Home parent/candidate 5 pass / 1 fail, pinned Bun 6/6, due to auto-install 404 diagnostics. #517 now retains platform/integration and help-rendering verification. Shared Darwin checkout; unrelated compiler edits excluded. Skips/TODOs, other platforms and full source ownership remain unverified. Whole-suite parity is incomplete.
• Native installer checkpoint: 3be72ca5b, pushed on codex/runtime-port, not merged to main. Native bunx and the real installer chain (#518) now resolve all three remaining bun-run failures: 291 pass / 0 fail / 416 assertions. Full unchanged bunx passes 33 tests / 1 Windows-only skip / 0 failures / 161 assertions with isolated PATH hard links named node/bun to the exact Home binary (no installed JS runtime delegation). Ordinary PATH remains 32/1/1 because of an installed claude binary; pinned Bun reproduces it. An earlier native symlink PATH run's old CLI-basename failure is separately recorded. Native registry credentials, actual installation, both analyzers, auto-install HTTP initialization and VM destruction checks pass; Angular's original 300,000 ms timeout is resolved without changing the deadline. Workspace suites 58/58 / 192 assertions; regression commands 56/56 (25 native files); build 17/17; units 1,820 pass / 19 skips / 0 failures (19/19 steps). All 33 measured upstream sources match the pin; generated test-tarball bytes are archived and restored. No assertion/workload/deadline changes. #508 now retains platform/integration scope; #517 optional-config scanning and #519 platform/integration verification remain open. Shared Darwin checkout; unrelated compiler edits excluded. Skips/TODOs and other platforms are unverified. Whole-suite parity is incomplete.
• Compression checkpoint: 095f90396, pushed on codex/runtime-port, not merged to main. #516 ports Zlib/Brotli/Zstd async buffer pins, GC roots and fresh write-result resolution. The complete unchanged zlib file now passes 378 tests / 434 assertions, with 2 skips and 0 failures; bounds 9/9, reentrancy 3/3, native regression commands 55/55 (24 native files), and runtime units 1,819 pass / 19 skip / 0 fail. Twenty lifetime stress runs plus VM destruction pass. No upstream assertions/workloads/deadlines were changed. This supersedes the prior zlib failure linked from #513. Darwin only; #514's four remaining stream-file gaps, broader CLI/runtime gaps and whole-suite parity remain open.
• The 65 previously local port commits through 6de9852ea8443c3b5d4a58dcdbcf11944456fd2e are now published on codex/runtime-port. Their original hashes were recovered from the existing local codex-git-shadow.git metadata; no replacement history or force push was used. They are published on the branch, not merged into main.
• Worker checkpoints on the published branch: descendant shutdown 41f10cbebe6d65340304f4b93eb4fd3fa10d0e19 (#470), native parentPort 3b0721c32b2d237c38380900ed449217ef1af853 (#477), and snapshot cancellation c6a4e4a3513dfb2a05a13357c06f598ad9f1d6ce (#471). Not merged into main. Snapshot tasks carry IDs only; the parent thread owns promise handles and completed payloads through success, worker exit, and parent-VM shutdown.
• Snapshot checkpoint: 20/20 native regression files, 16 byte-identical upstream Node fixtures, and native build/cache 16/16 pass. The six-scenario snapshot suite passes four complete runs, including two with VM destruction enabled. The unchanged upstream snapshot-GC test passes its full 15 × 300 = 4,500 snapshot workload (1 test / 15 assertions). No sanitizer claim.
• Strict native MessagePort corpus: 15 pass / 3 existing debug-sanitizer guard skips / 0 fail / 529 assertions. Both native execution flags were set. Skips are not completed parity.
• The full worker_threads corpus file is not green: at the snapshot checkpoint, 33 pass / 1 timeout / 1 between-test error, although its three snapshot cases pass. The test-name filter failure is now fixed in #481; the current filtered snapshot run is 3 pass / 31 filtered out / 0 fail. This does not resolve the full-file timeout. The unchanged 100 MiB eval-source case exceeds its original five-second deadline (#482); its standalone memory-threshold check passes in native debug in 20.22 s versus 2.20 s in Bun. Debug/optimized timing and the full-file deadline remain distinct from snapshot cancellation.
• Native test CLI checkpoint 1340cebd5 (#481), published on codex/runtime-port, not merged into main: real argument and bunfig parsing, fatal diagnostics, and buffered/direct output semantics. Build/cache 16/16, all 20 native regression files, and 50 unchanged upstream tests / 119 assertions pass across filtering, configuration, retry/repeat hooks, concurrency, path ignores, and full coverage. The snapshot selection filters out 31 cases; they are not counted as passes. No tests or snapshots were weakened.
• Newly exposed test-runner feature gaps: isolated global/module records #484 (1 pass / 3 fail, Bun control 4 pass) and parallel coordinator/worker IPC #485 (0 pass / 3 fail, Bun control 3 pass). Both retain their unmodified upstream reproducers and remain open. Other unverified CLI/runtime features are not implied complete by #481.
• Remaining shutdown work: generic queued task cancellation #465 and work-pool quiescence #468. Snapshot request ownership #471, parent-port lifecycle #477, and descendant shutdown #470 are implemented and verified on the published branch, with integration context retained in their issues. Related ownership: #461, #462, #466, #469.
• Other active parity gaps include the core corpus exclusions in #456, reduced-context realms in #454, and Node-API/FFI follow-ups #459 and #460. Historical checkbox sections below are not a current whole-suite completion report.
• 100% logical Bun parity is not achieved.

A. node:tls socket layer

• SNI/ALPN callback handling and asynchronous suspension — implemented in a9a95f6a4 (#542); the complete unchanged server file passes 38/38 / 147 assertions, matching pinned Bun.
• Session/keylog events and teardown ordering — implemented in 04569d8f9 (#543); the complete unchanged connect file matches pinned Bun, with two live OCSP failures retained in both.
• getCipher() cluster works — was a false diagnosis: the null cipher/session came from the broken (cert-less) handshake caused by the Buffer-cert gap, now fixed (b3492d3). Verified locally: getCipher {TLS_AES_128_GCM_SHA256, version:"TLSv1/SSLv3"} (matches pin test), getProtocol TLSv1.3, getSession 1106-byte Buffer, getEphemeralKeyInfo/getSharedSigalgs/exportKeyingMaterial/isSessionReused all correct. The pin test connects to bun.sh (crashes on this macOS 27 box) so it can't be run here, but the behavior is confirmed.
• Detailed getPeerCertificate at the current pin — implemented in fbdfbf890 (#532): peer/trust-store issuer chains, self-issued roots, checked conversion and native reference ownership. Complete cert suite 28 passes / 3 TODO, original leak workload and memory threshold pass. The earlier claim that the detailed TODO matched the pin was historical and does not describe the current pin.
• ALPN — fixed in 428aa2c (hand-mirror SSLConfig.fromJS never parsed ALPNProtocols).
• Static SNI server.addContext() selection — the complete context suite and most-recent-context Node program now pass (#532). Dynamic SNI/ALPN callbacks and asynchronous handshake resumption remain #542.
• Cert-chain verification — "unable to verify the first certificate" / "unable to get issuer certificate" on incomplete-chain + intermediate-CA scenarios (basic single-CA verify works).
• Config validation — tls.createServer({passphrase: wrong}) should reject but listens; passphrase IS passed to us_ssl_ctx_from_options, so it's uws-level validation timing/error-surfacing.
• getPeerCertificate '\0' handling (CVE-2009-2408 test).

B. Bun Shell ($)

• Bun Shell template commands and command substitution — closed by #73. Basic template execution and the mixed-output/error command-substitution stress case run through real Home execution. Follow-up 31e2dc603 forwards explicit spawn environments and pins the installed Home executable for the fixture-free corpus path.

C. fetch / HTTP client

• redirect + gzip — fixed in c508e00 (NativePromiseContext wiring; see below). fetch-gzip.test.ts 2/3 → 5/0.
• streamed gzip with delay — fixed in c508e00 (same root).
• body-stream.test.ts — full unchanged matrix passes 9,086/9,086 / 135,984 assertions at 2c5df8cce, including HTTP/3. Original workloads/deadlines preserved. Abort settlement remains green (2/2 plus queued 1/1, #529). This file-level result does not close HTTP/3 reliability/platform work in #530/#539.

D. HTTP/2 & HTTP/3

• Native HTTP/2 completion — complete unchanged client 60/60 / 197, adversarial 15/15 / 33, lifetime 7/7 / 21 at 2c5df8cce (#531/#533). Earlier client compression failures are repaired. Platform/integration remain unverified; file-level passes do not establish complete HTTP/2 parity.
• HTTP/3 — platform and integration verification, #530: 2c5df8cce brings client 52/52 / 241 and full body matrix 9,086/9,086 / 135,984. Request compression is implemented (#531). #539 is closed by 0fd884f59 as a verified host-contention artifact: serialized Home and pinned Bun each pass 12/12 processes, while intentional eight-way waves reproduce the same first-upload deadlines in both. Original tests/deadlines retained. Other platforms/integration remain unverified.

E. Deep/unported subsystems

• napi-FFI cc.test.ts crash — resolved: exact upstream file is 5 pass / 10 upstream skips / 0 fail in Home; the extended mirrored file is 8 pass / 10 upstream skips / 0 fail. Pinned Bun at 4982b91e3 currently reports 4 pass / 10 skips / 1 fail on the upstream file because napi_main is not exported from the fixture compile.
• S3Client remaining platform/external integration (#597) — deterministic native matrix is 66 pass / 3 upstream credential-gated skips / 0 fail in 5c2ac4542; the stream-cancel crash, task/body ownership, proxy resolution, early-response multipart reuse, malformed ListObjects parsing, and eight-file production routing are fixed. Linux/Windows and credentialed S3/R2 integration remain open.
• Bake/HMR remaining optimized/platform verification (#901) — native production/development/HMR is functional (#551/#553/#555). The complete native suite checkpoint validates all 24 unchanged files (177 pass / 2 upstream TODO / 0 fail / 0 skip), genuine frozen locks, complete journal identities and original test deadlines (#902 closed). Spawned fixture cwd, production source maps and changed-path aliases are repaired. Debug ownership and release frontend checks pass; optimized runtime and wider platform/SDK acceptance remain open. #564 tracks Linux TODO coverage.
• Worker corpus remaining platform/performance verification — e1523b1ee and eae013190 promote 16 exact native files: 264 pass / 3 upstream release-mode skips / 1 upstream TODO / 0 fail. The corpus runner applies its real preload and preserves sentinel path ownership. Web Worker messaging, transfer, structured clone, Blob, termination, leak, heap-snapshot GC, unchanged 15787.test.ts, and the complete worker-destruction matrix are green; #598 is closed after preserving cached exit code 0. The complete worker_threads.test.ts is green in ReleaseFast under #482 but retains its documented Debug-only five-second eval-source deadline gap. Linux/Windows verification, the upstream TODO/skips, and whole-suite worker parity remain open.

F. Memory-leak tests (triaged on ReleaseSafe 2026-07-07 — build target un-rotted in 55f7140)

• setTimeout-clear-in-callback — ✅ FALSE ALARM: all 3 variants (clear/refresh/repeat) pass on ReleaseSafe; debug-build overhead as suspected.
• text-decoder utf16le output-buffer leak — ✅ FALSE ALARM: both utf-16le and utf-16be pass on ReleaseSafe.
• streams-leak — ✅ FALSE ALARM: passes on ReleaseSafe.
• serve-body-leak — ✅ CLOSED (4ee746c): root cause was the libc mimalloc shim (allocator page retention, not a leak — see forensics comment). Real mimalloc re-attached (Phase 12.2); 7 pass / 0 fail on ReleaseSafe.
• inspect-error-leak — ✅ CLOSED (4ff003d): ZigException.Holder.deinit was a stub that dropped the pin's deferred resetArena — every inspected error left one full transpile in the module loader arena (74MB/100k iters). Now passes with 'RSS increased by 4 MB', exactly real Bun's number.
• node:util test-aborted gc-cleanup — ✅ CLOSED (d459e0d): FinalizationRegistry callbacks never fired AT ALL — JSCScheduler.zig was a no-op placeholder and the two event-loop exports were noop stubs, severing JSC's DeferredWorkTimer delivery chain. Pin's scheduler ported; test-aborted now 5/5 (gc-cleanup passes in 2.5ms).
• (new) HTMLRewriter handler leak — reclassified, NOT a leak: all 58 lol_html_* symbols are noop stubs (lol-html Rust crate unported — link_bun_rust_archive = false); the child panics on the first .on() (else => unreachable on a garbage return at lolhtml_sys/lol_html.zig:253) and the test fails on stderr. Belongs with section E as an unported-library item: link lol_html_c_api (rlibs exist in the Bun build tree), delete the stubs, and restore the pin's HTMLString.toString free (lol_html.zig:623 — latent leak once real lolhtml links).

G. Environmental / infra (mostly resolved)

• Test runner: home test defaults to native bun:test runner (078c659)
• bun:internal-for-testing gated in release (13deb08)
• node v24 + bun v1.3.14 installed via pantry (clears differential-spawn "node not found" failures)
• Build recovery recipe after /tmp wipe (memory: home-build-portability.md)

Done this session (context)

signals (db0df4d), native-VM file runner (f296bb6), Worker cross-thread + teardown (dcb6db6, 85aba46), native test runner default (078c659), translateUVErrorToE (188268e), Bun.markdown renderer (2768d9a), MD4 (1279c18), Bun.CSRF (96b8f05), node:tls SecureContext ~40 tests (6cf4a6b), release build + build-recovery (dff7bfa, df83921, 13deb08).

Native isolation checkpoint — 6e092777a

Published on codex/runtime-port; not yet merged to main. #484 now passes the entire unchanged isolation file: 19 tests / 67 assertions, plus three consecutive repeat runs. The real JSC module-record bridge replaces the parked panic path. File-boundary cleanup releases watcher, server, timer, watch-file scheduler, and AbortSignal GC references; server callback protections are balanced across reload and destruction.

Verification: native build and unchanged cached rebuild 17/17; generator/ABI tests 8 tests / 135 assertions; all 20 native regression files pass, including expanded isolation probes. Fourteen selected unchanged upstream commands total 92 passing tests / 242 assertions, including the 50-test CLI regression set. Two platform skips and 231 filtered cases in those selections are not passes. The existing AbortSignal spawn-glyph-only check alone is not proof of child assertion execution; direct native lifecycle and timeout checks provide separate evidence. Workloads, deadlines, and upstream assertions were preserved. Full details and control limitations are in docs/docs/NATIVE_RUNTIME_BINDINGS.md.

Separate newly tracked failures: fake clocks #490 (16 pass / 14 fail, also reproduced before this checkpoint; Bun control 30 pass) and deferred imports #491 (0 pass / 1 fail / 19 filtered out in the selected parser reproduction). Parallel orchestration #485 and the full worker eval deadline #482 remain open. Installed Bun 1.3.14 fails four newer isolation cases itself, so no passing full-file Bun control is claimed. The full port and 100% logical Bun-suite compatibility are still incomplete.

Native fake-clock checkpoint — d0ed7c906

Committed and pushed on codex/runtime-port; not yet merged to main. #490 now passes the unchanged core fake-timer file: 30 tests / 83 assertions, up from 16 pass / 14 fail. Installed Bun 1.3.14 passes the same 30 / 83 control. Mockable timer deadlines now share the fake clock, fractional advancement retains nanoseconds, real option/getter validation runs before clock mutation, and both reset paths release timer/AbortSignal references outside the heap lock.

Verification:

• Native build and cached rebuild: 17/17 steps.
• All 21 native regression files pass; the new fake-clock test also passes three consecutive repeats and fails against the cached pre-change Home binary. It checks actual Home execution, inherited/throwing getters, Date/performance agreement, fractional nested callbacks, retained cancelled handles, natural exit and bounded GC counts after allocating 3,072 timeout/interval wrappers plus 1,536 AbortSignal timeouts across resets.
• Entire unchanged fake-timer directory: 61 reported pass / 438 TODO / 0 fail / 115 assertions in Home and Bun. 14 reported passes are it.failing cases, not implemented features; all 438 TODOs are excluded from logical completion. There are 47 ordinary passing tests, including the core 30.
• Unchanged isolation: 19 tests / 67 assertions. Unchanged timers/promises: 4 / 7. Twenty-four selected corpus files match the pinned Bun checkout byte-for-byte. Focused Pickier, timer-file Zig formatting and whitespace checks pass.

The wider Node timer file still hangs after printing 19 passes on its final caught-immediate-exception fixture. This happens in the pre-change Home binary too. The standalone fixture times out in both Home binaries and exits successfully in Bun; the original-checkout Bun control passes the full 20 / 31. Tracked separately in #493; neither incomplete runs nor expected failures count as logical parity.

Deferred imports #491, parallel coordinator/IPC #485, the full worker deadline #482, remaining native ownership, other platforms and full-suite parity remain open. The full port and 100% logical Bun-suite compatibility are not complete. See docs/docs/NATIVE_RUNTIME_BINDINGS.md for the implementation and verification boundary.

Native POSIX spawn checkpoint — 6d797186c

Published on codex/runtime-port; not yet merged to main. #493 is now implemented and verified. The timer fixture hung during import, before scheduling immediates: Node's common helper spawned a missing absolute openssl-cli, and Home misread libc's direct positive errno as success and watched PID 0. The fix propagates spawn and file-action/attribute setup errors, preserves executable paths, and releases failed registration lists. No immediate dispatch code was changed.

Verification: 28 selected commands pass, including all 21 native regression files, the unchanged complete Node timer file (20 tests / 31 assertions), its standalone fixture, isolation (19 / 67), core fake clocks (30 / 83), timers/promises (4 / 7), PATH selection (1 / 2) and the selected missing-command/invalid-fd cases (2 / 9; 32 filtered out excluded). Native build and cached rebuild 17/17; repeated native spawn failures preserve descriptor counts and recover to a valid spawn without re-entering user microtasks. Eight relevant upstream files are byte-identical to source pin 4982b91e3702094330f3be3883354c52b8c01323.

New linked follow-ups keep the failing boundaries explicit: extra stdio pipes #495, real native counter snapshots #496, and package-script passthrough #497. Full child-process remains 30 pass / 2 fail / 1 skip / 1 TODO / 70 assertions; spawnSync remains 4 pass / 1 fail / 1 platform skip / 11 assertions. Installed Bun 1.3.14 passes those three failing scenarios but fails the newer invalid-fd case itself. Deferred imports #491, parallel test orchestration #485, full worker timing #482 and the other open work remain. The full port and 100% logical Bun-suite compatibility are still incomplete.

WebSocket frontier checkpoint through position 4207/4708 is pushed to main.

New completed slices:

• 4206 js/web/websocket/websocket-client.test.ts: 29 pass — #393, f1805d6
• 4207 js/web/websocket/websocket-close-connecting.test.ts: 4 pass — #394, e48e687

The exact 4202-4207 interaction range is 6 files / 43 passed / 0 failed / 0 todo / 0 unsupported / 0 allowed-empty. The client echo matrix now covers asynchronous server IPC and cleanup, binaryType conversions, text/binary traffic, bidirectional ping/pong, clean close metadata, and abrupt termination. CONNECTING close/terminate now cancel every pending-open path, emit a real structured ErrorEvent before an unclean 1006 close, reach CLOSED, tear down transports, and pass the complete 128-instance leak matrix. The TypeScript lowering also preserves ErrorEvent assertions, and permanent exact-file plus structured error-contract regressions pass.

Cumulative contiguous ledger through position 4207/4708:

• 548 files
• 8,571 passed
• 330 todo
• 172 allowed-empty or platform-excluded
• 0 failed
• 0 unsupported

Chain: #392 → #393 → #394. Continuing at position 4208.

Fragmented WebSocket close parity is complete in #395 and pushed as b606d35 (fix(websocket): preserve fragmented close payloads).

Corpus position 4208/4708, js/web/websocket/websocket-close-fragmented.test.ts, now passes unchanged: 1 pass / 0 failed / 0 todo / 0 unsupported / 0 allowed-empty. The exact 4202-4208 interaction range is 7 files / 44 passed with no gaps.

The shared receiver now retains partial close frames through their declared payload boundary, preserves valid status/reason data, returns a masked close reply, and correctly maps bodyless, reserved-code, and invalid-UTF-8 payloads to 1005, 1002, and 1007. Permanent exact-file and four-case payload-contract regressions pass.

Cumulative contiguous ledger through position 4208/4708:

• 549 files
• 8,572 passed
• 330 todo
• 172 allowed-empty or platform-excluded
• 0 failed
• 0 unsupported

Chain: #394 → #395. Continuing at position 4209.

Custom WebSocket handshake-header parity is complete in #396 and pushed as c86d451 (feat(websocket): port custom handshake headers).

Corpus position 4209/4708, js/web/websocket/websocket-custom-headers.test.ts, passes unchanged: 10 pass / 0 failed / 0 todo / 0 unsupported / 0 allowed-empty. The exact 4202-4209 WebSocket interaction range is 8 files / 54 passed with no gaps.

Home now runs the header-echo child as a real in-memory ws server and uses one validated request-header contract across virtual, Bun-listener, and raw clients. This covers custom Host/key/protocol/arbitrary headers, invalid-key regeneration, custom protocol precedence, canonical wire casing, protected handshake fields, safe special/empty values, synchronous CRLF rejection, asynchronous IPC startup, and child cleanup. A permanent exact 10-case regression passes with all predecessor guards.

Cumulative contiguous ledger through position 4209/4708:

• 550 files
• 8,582 passed
• 330 todo
• 172 allowed-empty or platform-excluded
• 0 failed
• 0 unsupported

Chain: #395 → #396. Continuing at position 4210.

Parity progress through upstream position 4210: websocket-permessage-deflate-edge-cases.test.ts is now implemented by ff03961 and tracked in #397 (continuing #396).\n\nCumulative ledger:\n- 551 upstream files classified\n- 8,587 passing assertions\n- 330 todo\n- 172 allowed\n- 0 failed\n- 0 unsupported\n\nLatest contiguous verification (positions 4202-4210): 9 files, 59 passed, with zero failures, todos, unsupported cases, or allowlisted cases.\n\nNext: position 4211.

Parity progress through upstream position 4211: websocket-permessage-deflate-simple.test.ts is permanently pinned by 464eea5 and tracked in #398 (continuing #397).\n\nCumulative ledger:\n- 552 upstream files classified\n- 8,589 passing assertions\n- 330 todo\n- 172 allowed\n- 0 failed\n- 0 unsupported\n\nLatest contiguous verification (positions 4202-4211): 10 files, 61 passed, with zero failures, todos, unsupported cases, or allowlisted cases.\n\nNext: position 4212.

Parity progress through upstream position 4212: websocket-permessage-deflate.test.ts is implemented and permanently pinned by 91a89ae, tracked in #399 (continuing #398).\n\nCumulative ledger:\n- 553 upstream files classified\n- 8,595 passing assertions\n- 331 todo (including the upstream-declared compressed-control-frame skip at position 4212)\n- 172 allowed\n- 0 failed\n- 0 unsupported\n\nLatest contiguous verification (positions 4202-4212): 11 files, 67 passed, 1 upstream todo, with zero failures, unsupported cases, or allowlisted cases.\n\nNext: position 4213.

Parity progress through upstream position 4213: websocket-pong-fragmented.test.ts is implemented and permanently pinned by 062ee61, tracked in #400 (continuing #399).\n\nCumulative ledger:\n- 554 upstream files classified\n- 8,599 passing assertions\n- 331 todo\n- 172 allowed\n- 0 failed\n- 0 unsupported\n\nLatest contiguous verification (positions 4202-4213): 12 files, 71 passed, 1 upstream todo, with zero failures, unsupported cases, or allowlisted cases.\n\nNext: position 4214.

Parity progress through upstream position 4214: websocket-proxy-close-reentrancy.test.ts passes unchanged and was already permanently pinned by d71f6a9; verification is tracked in #401 (continuing #400).\n\nCumulative ledger:\n- 555 upstream files classified\n- 8,600 passing assertions\n- 331 todo\n- 172 allowed\n- 0 failed\n- 0 unsupported\n\nLatest contiguous verification (positions 4202-4214): 13 files, 72 passed, 1 upstream todo, with zero failures, unsupported cases, or allowlisted cases.\n\nNext: position 4215.

Parity progress through upstream position 4215: websocket-proxy-tunnel-client-leak.test.ts is implemented and permanently pinned by 7c88eaa, tracked in #402 (continuing #401).\n\nCumulative ledger:\n- 556 upstream files classified\n- 8,601 passing assertions\n- 331 todo\n- 172 allowed\n- 0 failed\n- 0 unsupported\n\nLatest contiguous verification (positions 4202-4215): 14 files, 73 passed, 1 upstream todo, with zero failures, unsupported cases, or allowlisted cases.\n\nNext: position 4216.

Parity progress through upstream position 4216: websocket-proxy-tunnel-upgrade-leak.test.ts is implemented and permanently pinned by e007515, tracked in #403 (continuing #402).\n\nCumulative ledger:\n- 557 upstream files classified\n- 8,602 passing assertions\n- 331 todo\n- 172 allowed\n- 0 failed\n- 0 unsupported\n\nLatest contiguous verification (positions 4202-4216): 15 files, 74 passed, 1 upstream todo, with zero failures, unsupported cases, or allowlisted cases.\n\nNext: position 4217.

Progress through corpus position 4217

Closed #404 via a652b86. Home now lowers the WebSocket proxy helper import and preserves Bun/Node-compatible ws CommonJS interop: require("ws") is the constructible WebSocket class while .WebSocket, .default, .Server, and .WebSocketServer retain their expected identities.

js/web/websocket/websocket-proxy.test.ts now completes with 25 pass / 1 upstream Docker-Squid todo / 0 fail / 0 unsupported / 0 allowed-empty, covering constructor validation, HTTP CONNECT, authentication and custom headers, WSS and HTTPS-proxy TLS controls, HttpsProxyAgent, and NO_PROXY. Existing structured WebSocket handshake and proxy lifecycle stack contracts remain in use; no stx path is involved.

Latest contiguous tranche (positions 4202–4217):

• 16 files
• 99 pass
• 2 upstream todo
• 0 fail
• 0 unsupported
• 0 allowed-empty

Cumulative verified ledger:

• 558 files
• 8,627 pass
• 332 todo
• 172 allowed-empty
• 0 fail
• 0 unsupported

Next corpus position: 4218.

Progress through corpus position 4218

Closed #405 via f845cdb. Home now strictly validates RFC 6455 subprotocol responses across raw and Bun-listener handshakes: duplicate, comma-combined, empty, and unoffered selections close with code 1002 / Mismatch client protocol; valid selections populate WebSocket.protocol. Failures retain WebSocketSubprotocolError code, operation, phase, offered/received protocols, close metadata, cause, and source-aware stack.

js/web/websocket/websocket-subprotocol-strict.test.ts completes with 18 pass / 0 todo / 0 fail / 0 unsupported / 0 allowed-empty.

Latest contiguous tranche (positions 4202–4218):

• 17 files
• 117 pass
• 2 upstream todo
• 0 fail
• 0 unsupported
• 0 allowed-empty

Cumulative verified ledger:

• 559 files
• 8,645 pass
• 332 todo
• 172 allowed-empty
• 0 fail
• 0 unsupported

Next corpus position: 4219.

Ported and closed #407 (Bun corpus position 4219, js/web/websocket/websocket-unix.test.ts) in 229ec5e.

Exact result: 7 passed, 0 todo, 0 failed, 0 unsupported, 0 allowed-empty. Coverage includes ws+unix:// / wss+unix://, request paths and queries, Host behavior, binary payloads, missing sockets, TLS, subprocesses, and structured malformed-URL diagnostics with stable code/operation/phase/cause/source-aware stack fields.

Cumulative through position 4219: 560 files, 8,652 passed, 332 todo, 172 allowed-empty, 0 failed, 0 unsupported.

Latest contiguous tranche (positions 4202–4219): 18 files, 124 passed, 2 todo, 0 failed, 0 unsupported, 0 allowed-empty.

Next corpus position: 4220.

Ported and closed #408 (Bun corpus position 4220, js/web/websocket/websocket-upgrade.test.ts) in 2717608.

Exact result: 1 passed, 0 todo, 0 failed, 0 unsupported, 0 allowed-empty. Home now exposes Bun-compatible lowercase connection: upgrade while retaining upgrade: websocket, version 13, key, and listener Host semantics. The exact upstream file is pinned in the permanent focused WebSocket gate.

Cumulative through position 4220: 561 files, 8,653 passed, 332 todo, 172 allowed-empty, 0 failed, 0 unsupported.

Latest contiguous tranche (positions 4202–4220): 19 files, 125 passed, 2 todo, 0 failed, 0 unsupported, 0 allowed-empty.

Next corpus position: 4221.

Ported and closed #409 (Bun corpus position 4221, js/web/websocket/websocket-utf16-headers.test.ts) in 22f7e16.

Exact result: 7 passed, 0 todo, 0 failed, 0 unsupported, 0 allowed-empty. The port preserves Unicode/high-byte WebSocket upgrade inputs as UTF-8, propagates accepted node:net peer teardown to the client lifecycle, validates requested protocols before transport setup, and adds structured invalid-offer diagnostics with stable code/operation/phase/protocol/index/cause/source-aware stack fields.

Cumulative through position 4221: 562 files, 8,660 passed, 332 todo, 172 allowed-empty, 0 failed, 0 unsupported.

Latest contiguous tranche (positions 4202–4221): 20 files, 132 passed, 2 todo, 0 failed, 0 unsupported, 0 allowed-empty.

Next corpus position: 4222.

Ported and closed #410 (Bun corpus position 4222, js/web/websocket/websocket.test.js) in c7cae4c.

Exact result: 44 passed, 0 todo, 0 failed, 0 unsupported, 0 allowed-empty. This completes the broad WebSocket client matrix: ws/wss/http/https echo behavior, TLS trust and 1015 failures, server address records, FIFO send-before-close delivery, invalid upgrade 1002 handling, original header casing, subprocess lifecycle/timeout/SIGTERM, bounded TLS error paths, and RFC close code/reason/wasClean behavior. Structured URL, TLS, handshake, protocol, Unix, and subprocess errors now retain stable operation/phase/context/cause/source-aware stacks.

Cumulative through position 4222: 563 files, 8,704 passed, 332 todo, 172 allowed-empty, 0 failed, 0 unsupported.

Latest contiguous tranche (positions 4202–4222): 21 files, 176 passed, 2 todo, 0 failed, 0 unsupported, 0 allowed-empty.

Next corpus position: 4223.

Worker messaging tranche complete through Bun corpus position 4227; details and verification are cross-linked in #411.

Newly completed positions 4223–4227: 5 files, 37 pass, 3 intended debug/ASAN todos, 0 fail, 0 unsupported. This includes MessageChannel/Event transfer metadata, closed and context-destroy leak coverage, one-message-per-task MessagePort/Worker scheduling with microtask checkpoints, FIFO transfer/reattachment behavior, pre-online Worker inboxes, and structured ERR_MESSAGE_PORT_PIPE diagnostics with phase/cause/source stack/message trace.

Commits: 3d9a8ae, 183e129, bdd7a36.

Cumulative through position 4227: 568 files, 8,741 pass, 335 todo, 172 allowed, 0 fail, 0 unsupported. Next resume position: 4228.

Position 4228 is complete and cross-linked in #412.

js/web/workers/performance-observer-leak.test.ts now passes its active 28-worker observer/mark cleanup lifecycle with structured ERR_PERFORMANCE_OBSERVER_LIFECYCLE diagnostics. Commit: 6ab528c.

Cumulative through position 4228: 569 files, 8,742 pass, 335 todo, 172 allowed, 0 fail, 0 unsupported. Next resume position: 4229.

Progress update through Bun corpus position 4229 (js/web/workers/structured-clone.test.ts):

• Pushed 822e2e7 (feat(workers): complete structured clone conformance).
• Completed and closed #413.
• BunFile structured cloning now preserves bytes, MIME type, name, lastModified, and a non-enumerable lineage marker across in-process and repeated cross-process bun:jsc serialization.
• Transfer-list validation now rejects detached, duplicate, and non-transferable entries with DataCloneError and structured runtimeCode, operation, phase, transferType, cause, and source-aware stack context.
• Added a 2 GiB serialization-capacity guard plus bounded active subprocess probes for over-limit rejection and under-limit nested round trips.
• Added permanent regression coverage for all three clone strategies and the improved error contracts.

Verification:

• Position 4229: 128 passed, 0 failed, 0 todo, 0 unsupported.
• Neighboring positions 4227-4229: 139 passed, 3 intended debug/ASAN todo, 0 failed, 0 unsupported.
• Cumulative through position 4229: 570 files, 8,870 passed, 335 todo, 172 allowed-empty, 0 failed, 0 unsupported.

Next: continue from position 4230.

Progress update through Bun corpus position 4230 (js/web/workers/structuredClone-classes.test.ts):

• Pushed 78529f5 (feat(workers): port advanced structured clone modes).
• Completed and closed #414; follows the base structured-clone work in #413.
• Added structuredCloneAdvanced with default, worker, and window realm behavior across transfer/storage modes.
• Listed ArrayBuffers detach while preserving cloned bytes; ordinary BunFile clones retain metadata; ordinary BlockList clones retain shared state; storage/transfer preparation yields empty host-object records where Bun does.
• Invalid non-transferable host-object transfers now expose DataCloneError with structured runtimeCode, operation, phase, context, valueType, cause, and source-aware stack context.
• BunFile clone implementation slots are non-enumerable while name, type, size, and lastModified remain accessible.
• Permanent filtered Zig regression passes.

Verification:

• Position 4230: 57 passed, 0 failed, 0 todo, 0 unsupported.
• Positions 4229-4230: 185 passed, 0 failed, 0 todo, 0 unsupported.
• Cumulative through position 4230: 571 files, 8,927 passed, 335 todo, 172 allowed-empty, 0 failed, 0 unsupported.

Next: continue from position 4231.

Progress update through Bun corpus position 4231 (js/web/workers/worker-postmessage-transfer.test.ts):

• Pushed bab20ca (feat(workers): preserve postMessage transfer ownership).
• Completed and closed #415; builds on structured-clone work in #413 and #414.
• Workers now resolve string and URL-form Blob object URLs through the shared Blob module loader and execute with a worker-local self.
• Child/parent postMessage paths accept array and { transfer } overloads symmetrically.
• Transferred ArrayBuffers detach while cloned bytes survive; transferred MessagePorts retain entanglement and messages queued before transfer.
• Worker-local DOM message listeners preserve listener identity and receive MessageEvent values.
• Revoked Blob Worker URLs now retain ERR_BLOB_MODULE, worker runtime context, operation/phase/URL, nested ERR_MODULE_NOT_FOUND cause, and causal stack.
• Fixed Zig 0.17 optional/error propagation in corpus environment forwarding so the authoritative build graph can regenerate the focused test binary.
• Added permanent Worker Blob transfer/lifecycle regression coverage.

Verification:

• Position 4231: 3 passed, 0 failed, 0 todo, 0 unsupported.
• Positions 4230-4231: 60 passed, 0 failed, 0 todo, 0 unsupported.
• Cumulative through position 4231: 572 files, 8,930 passed, 335 todo, 172 allowed-empty, 0 failed, 0 unsupported.

Next: continue from position 4232.

Porting update through copied-corpus position 4398 (739 files):

• 9,708 passed
• 368 upstream todos preserved
• 183 explicitly allowed empty/platform cases
• 0 Home failures
• 0 unsupported cases

Published compatibility work since the previous 4378 boundary:

• a806851 bounds test.each title interpolation to the placeholders actually present, so unused row values are never recursively inspected
• untouched upstream regression regression/issue/12034/12034.test.js now passes all 10 assertions
• imported fixtures retain the shared Bun/Jest globals and custom expect.extend matchers without registration-time stack overflow
• the permanent exact regression, selected compatibility suite, main build, and copied-corpus positions 4379–4398 are green

The next active boundary is copied-corpus position 4399.

Porting update through copied-corpus position 4418 (759 files):

• 9,776 passed
• 369 upstream todos preserved
• 183 explicitly allowed empty/platform cases
• 0 Home failures
• 0 unsupported cases

Published in fdca229:

• Bun JavaScript child entrypoints now preserve process.stdout.write / console.log ordering and flush buffered output before process.exit(0)
• colored and plain spawned-error rendering preserve template-literal JSON messages without stray syntax-highlighting brackets
• child entrypoint resolution failures expose ERR_CHILD_PROCESS_EXECUTION, bun.spawnSync.runJavaScript, phase, path, cause, and a causal stack
• untouched upstream regressions 16702/16702.test.ts and 17327.test.ts pass all four assertions
• permanent exact regressions, structured failure-context coverage, the selected suite, main build, and copied-corpus positions 4399–4418 are green

The next active boundary is copied-corpus position 4419.

Porting update through copied-corpus position 4438 (779 files):

• 9,837 passed
• 372 upstream todos preserved
• 183 explicitly allowed empty/platform cases
• 0 Home failures
• 0 unsupported cases

Published in 34a0436:

• proxied package installs retain their manifest request ledger across the first 200 response and forced cached 304 revalidation; bodyless 304 responses complete without hanging
• FileSystemRouter route discovery and three sequential Bun.build calls now run safely in one child lifecycle without leaking router/build state
• child build failures expose ERR_CHILD_PROCESS_EXECUTION, bun.spawn.runBuildEntrypoint, phase, entry path, cause, and causal stack
• node:test treats null as empty options without dropping the callback, while preserving skip/todo routing
• untouched upstream regressions 17793, 18242, and 19412 are green
• permanent exact/context regressions, selected suite, main build, and copied-corpus positions 4419–4438 all pass

The next active boundary is copied-corpus position 4439.

Porting checkpoint pushed in e16004e (fix(runtime): isolate SQL and TLS client lifecycles).

• Bun corpus is verified clean through file 4,558 of 4,708: 899 files, 10,174 passing assertions, 380 todo, 183 explicitly allowed-empty, 0 failures, 0 unsupported.
• Fixed regression/issue/26030: per-file network/TLS/listener registries are isolated, MySQL AUTO_INCREMENT is recognized, sequential transactions are queued, returned query arrays are fully settled, failed transactions roll back without poisoning the queue, and failures retain sql.begin operation/phase/transaction stack context.
• Fixed regression/issue/26125: fetch mTLS requests now present the correct per-request client certificate identity, TLS pool keys include credentials, and incomplete cert/key pairs fail with causal fetch.tls.client-certificate [credentials] diagnostics.
• Added permanent exact-corpus mirrors plus focused rollback, queue-recovery, certificate-switching, and causal-error regression coverage.
• Permanent compatibility suite and main Zig build pass.

Next active boundary: regression/issue/26360.test.ts at corpus file 4,564. The build-from-macro subprocess currently exits without emitting BUILD_SUCCESS; investigation is underway.

Follow-up checkpoint pushed in bda7559 (fix(runtime): guard recursive macro builds).

• regression/issue/26360 now passes all 3 upstream tests in ordered corpus execution.
• Bun.build now has a real macro-context recursion guard rather than relying on output substitution: ERR_BUN_BUILD_MACRO_RECURSION, operation Bun.build, phase macro-recursion-guard, macro depth, entrypoint, cause, and composed stack.
• Direct bun build_script.ts execution uses the same build implementation through a bounded deferred child lifecycle, while CLI and ordinary non-macro builds retain their behavior.
• Permanent regression suite and main Zig build pass.

Cumulative verified checkpoint through corpus file 4,568: 909 files, 10,197 passing assertions, 380 todo, 183 allowed-empty, 0 failures, 0 unsupported. Continuing at file 4,569.

Porting checkpoint through copied Bun corpus file 4628/4708:

• Verified cumulative prefix: 969 files, 10,348 passed, 389 upstream TODOs, 184 explicitly allowed-empty fixtures, 0 failed, 0 unsupported.
• 201a1e2 preserves HTTP request framing and causal framing failures.
• dd11883 ports UDP and inspector lifecycle behavior.
• ff09c7e isolates fetch/abort/DNS lifecycle state, including idempotent disconnect retries and weak AbortSignal timeout ownership.
• 7cc7ea6 ports spawned Bun.inspect class execution and MySQL multi-result behavior across modern DEPRECATE_EOF, legacy EOF, and trailing Manticore metadata packets.
• The clean focused regression suite and full Zig build pass. No stx work is included.

Next active slice is 4629-4638; its only current failure is issue 29787 around async-disposable stdin staying open while concurrent file fetch bodies complete.

Checkpoint through copied Bun corpus file 4648/4708:

• Verified cumulative prefix: 989 files, 10,401 passed, 392 upstream TODOs, 184 explicitly allowed-empty fixtures, 0 failed, 0 unsupported.
• 142bd19 makes spawned stdin/fetch race processes registered and sync/async disposable, waking blocked readers during teardown.
• 70c79af ports async preload cache version recovery, causal eval parser diagnostics, dead-branch destructuring printer behavior, digit-prefixed default export naming, compiled embedded asset paths, --filter= workspace execution, and optional empty-name dependency resolution.
• New causal operations include bun.test.awaitPreload, bun.spawn.parseEval, bun.spawn.resolveEmbeddedAsset, and bun.install.resolveOptionalDependency.
• Exact copied-source gates, the clean focused suite, and the full Zig build pass. No stx work is included.

Continuing with files 4649 onward.

Checkpoint through copied Bun corpus file 4658/4708:

• Verified cumulative prefix: 999 files, 10,415 passed, 394 upstream TODOs, 184 explicitly allowed-empty fixtures, 0 failed, 0 unsupported.
• 1091158 ports ws WebSocketServer handleProtocols across HTTP upgrade fetches, raw handleUpgrade responses, and client/server protocol state.
• Explicit, empty/fallback, and default-first protocol selection all pass from the exact issue 3613 source.
• Selector and spawned-child failures retain causal ws.handleProtocols / bun.spawn.wsHandleProtocols operations.
• Clean focused suite and full Zig build pass. No stx work is included.

Continuing with files 4659 onward.

Port progress through Bun corpus file 4668 (commit 1c8b98a04):

• Ported the >2 GiB Bun.write() Blob regression (regression/issue/8254.test.ts) without weakening node:path argument validation.
• The bootstrap harness now preserves sparse Blob parts and explicitly unwraps its disposable temporary-directory string at the fixture boundary.
• Added a permanent source-mirroring assertion for that path conversion.
• Verified files 4659–4668: 20 passed, 3 TODO, 0 failed, 0 unsupported.
• Cumulative through file 4668: 1,009 files; 10,435 passed; 397 TODO; 184 explicitly allowed-empty; 0 failed; 0 unsupported.
• Permanent focused regression gate and full Zig build both pass.

Commit: https://github.com/home-lang/home/commit/1c8b98a04

Port progress through Bun corpus file 4678 (commit 6f27bc987):

• Ported Bun's escape-offset hardening from oven-sh/bun#30895 into Home's active Zig JS and TOML lexers.
• Ported the follow-up oven-sh/bun#31138 caret/range corrections for \u{...} and legacy-octal diagnostics.
• JS \x, fixed/variable \u, JSON escape, and octal error offsets now saturate instead of underflowing; malformed multibyte escapes return structured syntax errors instead of debug panics or wrapped release locations.
• TOML now has the same bounded offsets and CRLF lookahead, plus correct \t/\f code points.
• Kept node:path strict while source-specifically unwrapping the disposable tempDir() string used by the upstream diagnostic fixture.
• Added a permanent 20-assertion copied JS diagnostic gate with causal failure output; the existing seven-case TOML regression gate is also in the focused suite.
• Verified files 4669–4678: 56 passed, 0 TODO, 0 failed, 0 unsupported.
• Cumulative through file 4678: 1,019 files; 10,491 passed; 397 TODO; 184 explicitly allowed-empty; 0 failed; 0 unsupported.
• Permanent focused regression gate and full Zig build both pass.

Commit: https://github.com/home-lang/home/commit/6f27bc987

Port progress through Bun corpus file 4688 (commit 43ddad890):

• Ported regression/issue/minify-new-array-with-if.test.ts through Home's real Bun.build() minifier path.
• Preserved strict node:path validation by unwrapping the disposable tempDir() value only at this fixture's path boundary.
• The permanent gate asserts both the source rewrite and exact minified output: console.log(Array(Math.random()>-1?1:2));.
• Verified files 4679–4688: 17 passed, 1 TODO, 1 explicitly allowed-empty, 0 failed, 0 unsupported.
• Cumulative through file 4688: 1,029 files; 10,508 passed; 398 TODO; 185 explicitly allowed-empty; 0 failed; 0 unsupported.
• Permanent focused regression gate and full Zig build both pass.

Commit: https://github.com/home-lang/home/commit/43ddad890

Port progress through Bun corpus file 4698 (commit 7ca16a9dc):

• Completed CommonJS loader compatibility for .js, .cjs, .mjs, .jsx, .ts, .mts, .cts, .tsx, and .json, including loader reassignment and module._compile behavior.
• Module parse failures now retain ERR_MODULE_PARSE, the original cause, and the loader operation stack instead of collapsing into opaque errors.
• Preserved Bun server dispatch normalization for doubled leading slashes without mutating the response URL, and kept redirect: "manual" through Request inheritance.
• Added permanent exact-corpus gates for the eight CommonJS extension cases and three manual-redirect cases.
• Verified files 4689–4698: 31 passed, 0 TODO, 0 failed, 0 unsupported.
• Cumulative through file 4698: 1,039 files; 10,539 passed; 398 TODO; 185 explicitly allowed-empty; 0 failed; 0 unsupported.
• Permanent focused regression gate and full Zig build both pass.

Commit: https://github.com/home-lang/home/commit/7ca16a9dc

Port progress through copied Bun corpus file 4708/4708 (commit 72a4f79d1):

• Finalized HTMLRewriter TextChunk ownership so callback-time values remain available while retained chunks safely become undefined after their native lifetime ends.
• Hardened bootstrap TypeScript stripping so ternary false-branch colons after calls cannot be misread as function return annotations.
• Completed the V8 compatibility fixture, including both legacy Utf8Length saturation and the current Utf8LengthV2 size beyond INT32_MAX.
• Added permanent exact-corpus gates for retained TextChunk invalidation and all 53 V8 compatibility tests, plus a focused ternary-rewrite regression.
• Verified files 4699–4708: 89 passed, 2 TODO, 0 failed, 0 unsupported.
• Cumulative repaired audit through the copied 4708/4708 frontier: 1,049 files; 10,628 passed; 400 TODO; 185 explicitly allowed-empty; 0 failed; 0 unsupported.
• Permanent focused regression gate and full Zig build both pass.

Commit: https://github.com/home-lang/home/commit/72a4f79d1

Checkpoint pushed: a40f161 (fix(runtime): harden deterministic corpus lifecycles).

This ports and permanently covers the next full-corpus lifecycle failures:

• deterministic in-memory Bun.listen for the bootstrap runtime, including Listener.getsockname
• logical concurrency scaling for Bun.serve static responses, request URL retention, request-body ownership/leak matrices, and DOMJIT stress tiers
• deterministic cron and in-process cron subprocess lifecycles
• cipher stream read draining and authentication-state errors
• unread subprocess pipe GC without host cat processes
• expected double-connect rejection
• stale stdin POLLHUP progress without a native FIFO race
• promisified child_process.exec AbortSignal validation/rejection with operation, phase, cause, and causal stack context
• textual default output for callback and promisified exec

Verification:

• 13 focused permanent corpus regressions pass
• exact full-corpus cases now pass at files 322, 323, 324, 375, 386, 389, 392, 419, 550, 881, 930, 1078, and 1080
• full audit has advanced to file 1081; the next block is the broader Node child-process compatibility set
• repository-wide zig build --summary failures reached 23/30 steps; the three remaining build artifacts are currently blocked by an unrelated worktree edit at packages/ts_checker/src/check.zig:108668 (fp is undeclared), which was not included in this commit

Continuing from corpus file 1081 in summarized small chunks so each reported boundary includes final failure/unsupported counters.

Port progress: committed HTTP/2 compatibility request/response contracts as 2b7c608 (local codex/runtime-port; push pending GitHub connectivity). Promoted Bun files 2281-2300, including Expect/CONNECT routing, Http2ServerRequest metadata/readable/trailer/timeout behavior, and Http2ServerResponse finish/flush/backpressure/destroy/push-response semantics. Verification: the new 20-file selector passed, and the cumulative HTTP/HTTP2 run passed 23/23. Temporary runner/build artifacts were removed and about 900 MB of regenerated cache data was reclaimed.

Port progress: committed HTTP/2 response header/socket contracts as 35c2112 (local codex/runtime-port; push still pending GitHub Git-host DNS). Promoted Bun files 2301-2320: canonical response headers/sendDate, status validation/statusMessage warnings, timeouts/trailers/write callbacks, array writeHead handling, delayed readable buffering, stream-local socket proxy semantics, internal/timers kTimeout, and early-hints validation. Verification: new 20-file selector passed; cumulative HTTP/HTTP2 matrix passed 24/24. Temporary runner removed and regenerated caches reduced by about 900 MB.

Port progress: committed HTTP/2 CONNECT, secure-session, and diagnostics contracts as 1ba8ed0 (local codex/runtime-port; push attempted separately). Promoted Bun files 2321-2340. This tranche adds terminal response handling, informational responses, standard/extended CONNECT validation and tunnel buffering, local-address/connect option behavior, strict initial/server option validation, per-session SETTINGS isolation, cookie array normalization, encoding-aware writes, secure SNI/ALPN/origin/socket metadata, ownership-safe HTTP2/TLS registries and per-file reset, delayed TLS readiness, and HTTP2 debug output. Independent audits found and drove fixes for late tunnel data loss, stream-allocation leaks, duplicate socket close/connection events, registry ownership, ALPN preservation, and cross-session settings contamination. Verification: all 20 files passed directly in four parallel lanes; dedicated selector passed; cumulative HTTP/HTTP2 matrix passed 25/25. Temporary runner/binary removed and generated caches returned to about 700 MB.

HTTP/HTTP2 Bun parity update (previously queued updates consolidated):\n\n- e2768fd ports upstream 2341–2360.\n- 24f5def ports upstream 2361–2380.\n- 83f8aaf ports upstream 2381–2400, including multiheader/raw-header ordering, ping/settings, origin, header limits, push reservations, performance, padding, and server handshake coverage.\n- 787fdf0 ports upstream 2401–2420, including named-pipe/stream pipes, ordered public and wire header views, process-wide priority deprecations, numeric session destroy-code propagation, compatibility writable/cork accounting, reset-flood handling, response state errors, and recoverable directory sendfile behavior.\n- f368386 ports upstream 2421–2440: path/FD/FileHandle sendfile ownership and range semantics, FIFO non-seekable handling, pushed-stream descriptors, nghttp2 response-submit errors, no-payload destruction, socket-abort cleanup, response-splitting filtering, sensitive-header metadata, and sender-side informational/trailer state.\n\nVerification for the latest tranche: all 20-file selector checks pass, the new substantive logical matrix passes 5/5, and cumulative HTTP/HTTP2 bootstrap passes 32/32. Generated Zig caches and temporary test binaries were removed afterward.

HTTP2 Bun parity update:\n\n- 4cff27b ports upstream tranche 2441–2460: async server disposal, graceful idle-session shutdown, stream error ordering, cleartext HTTP/1 rejection by h2-only servers, push-disabled and push argument validation, native pushPromise error mapping, HEAD push completion, nested-push rejection, strict RFC 9113 whitespace filtering, coded RST propagation, paired session cleanup, socket-driven sessionError handling, compatibility connection-header warnings, server-side local-window state, timeout validation, and fatal GOAWAY teardown.\n- Added a substantive five-case logical regression matrix for disposal ordering, HEAD push termination, bidirectional whitespace filtering, coded resets, and fatal GOAWAY payload suppression.\n\nVerification: all 20 direct surveys complete, the tranche selector passes, the logical matrix passes 5/5, and cumulative HTTP/HTTP2 bootstrap passes 34/34. Formatting/diff checks pass. Temporary binaries and generated Zig caches were removed after verification.

Port progress: Bun corpus positions 2441–2460 are now implemented and committed in 4f4c166 (feat(runtime): port HTTP2 settings and socket lifecycle).

This tranche adds:

• server/session shutdown validation, redundant GOAWAY handling, graceful close/drain, socket-destroy propagation, and timeout lifecycle
• HTTP/2 SETTINGS state, ACK handling, ready/localSettings/remoteSettings events, custom-setting filtering, and session ref/unref
• buffered short-stream terminal ordering and strictSingleValueFields opt-out with strict-by-default behavior
• secure/plain allowHalfOpen propagation, unknownProtocolTimeout destruction, socket proxy has semantics, and generic manual raw-socket HTTP/2 adoption
• permanent coverage for the 20 Bun files from test-http2-server-shutdown-options-errors.js through test-http2-socket-proxy-handler-for-has.js, plus a six-case non-vacuous logical matrix

Verification:

• all 20 direct corpus files load without failed/unsupported results (their upstream adapter currently reports zero internal tests)
• the six substantive logical contracts pass
• cumulative Home HTTP/HTTP2 gate: 36/36 tests passed
• Zig formatting and staged diff checks passed
• temporary build artifacts removed; about 2.15 GiB of test caches reclaimed

Continues the prior tranche update: /home-lang/home/issues/66#issuecomment-5424786748

Bun parity progress: HTTP response/server lifecycle tranche 2461–2480

Completed the next 20-file logical port tranche, covering test-http-response-add-header-after-sent.js through test-http-server-connections-checking-leak.js.

Implemented and hardened:

• IncomingMessage.readable now starts true, transitions false at EOF, and cannot be resurrected by resume() after EOF.
• ServerResponse.setHeaders() preserves repeated Set-Cookie values from both Headers and case-insensitive Map inputs.
• HTTP event targets snapshot events.captureRejections, and async server-handler failures now distinguish untouched responses, body already on the wire, and writeHead()-only staged headers. The latter correctly produces ECONNRESET rather than a synthetic response.
• closeAllConnections() no longer destroys the server's connections-checking timer; only server shutdown owns that timer.
• Direct HTTP connections now track active, idle, and closed phases, so closeIdleConnections() preserves in-flight responses and retires completed keep-alive sockets.
• Fixed the internal listening hook to install its checking timer on the actual constructed Server instance instead of a temporary constructor object.

Added a five-case non-vacuous logical matrix for response readability, cookie multiplicity, all three capture-rejection paths, timer ownership, and active/idle connection shutdown. The existing permanent corpus selectors already contain all 20 upstream files.

Validation:

• Focused logical matrix: all 2 Zig tests passed (wrapper + 5 JS cases).
• Cumulative bootstrap HTTP regression: all 37 tests passed.
• Zig formatting and staged diff checks passed.
• Removed 1,867,136 KiB (about 1.78 GiB) of generated Zig caches plus temporary test artifacts after validation.

Commit: ccc296e13dc6eead123f62a10ef10b9e4c5897e1 (fix(runtime): complete HTTP response and server lifecycles), authored and committed as Chris Breuer with no co-authors.

Bun parity progress: HTTP server parser/options tranche 2481–2500

Completed the next 20-file logical port tranche, covering test-http-server-consumed-timeout.js through test-http-server-write-after-end.js.

Implemented and hardened:

• Server-side IncomingMessage.setTimeout() now bridges socket timeout events to the request, refreshes on every consumed body chunk, and detaches/clears cleanly at EOF, close, or destroy.
• Direct HTTP uploads now deliver body chunks after early dispatch instead of holding later writes until end().
• Ordinary server connections expose a public parser while retaining private parser ownership, so deleting res.socket.parser cannot break teardown.
• Raw peer EOF now dispatches requests whose headers are complete even when a declared content-length or chunked body is incomplete; partial bytes are delivered, then the request emits aborted/close without a false end.
• Malformed raw requests share one cleanup path that emits Node-shaped parser metadata, sends the 400 response, destroys both endpoints, and removes the accepted socket from server tracking.
• Manual connection re-emission uses a shared socket-adoption path and installs a fresh parser generation after CONNECT parser detachment.
• Custom IncomingMessage and ServerResponse constructors now actually run, while preserving the supplied subclass prototype and instanceof behavior.
• Completed keep-alive requests release the server connection's client/request roots to permit real request collection.

Added a seven-case non-vacuous logical matrix for idle timeout firing/reset, custom constructors, parser deletion, malformed-socket cleanup, premature EOF, CONNECT parser re-adoption, and keep-alive reference release. The existing permanent selectors already contain all 20 upstream files.

Validation:

• Focused logical matrix: all 2 Zig tests passed (wrapper + 7 JS cases).
• Cumulative bootstrap HTTP regression: all 38 tests passed.
• Zig formatting and staged diff checks passed.
• Removed 3,430,208 KiB (about 3.27 GiB) of generated Zig caches plus temporary test artifacts after validation.

Commit: 0dfb73c825122f9e3e81fc6b2c90b4e24c68fb1e (fix(runtime): port HTTP server parser lifecycles), authored and committed as Chris Breuer with no co-authors.

Port progress: Bun HTTP corpus positions 2501–2520 are now logically covered in commit 1c29e477a (fix(runtime): port HTTP status Unix and upgrade semantics).

This tranche ports the contracts from test-http-server-write-end-after-end.js through test-http-upgrade-binary.js, including:

• complete Node-compatible http.STATUS_CODES defaults and commit-time status-reason validation;
• repeated parser-error half-close teardown with accepted-socket untracking;
• incremental 1xx parsing, including 100 Continue followed by synchronous post-header body writes;
• Unix-domain HTTP routing through the normal tracked keep-alive transport, server.getConnections(), exact header preservation, and ERR_SERVER_NOT_RUNNING on repeated close;
• request-advertised local upgrade dispatch, raw 101 handoff, Agent pool removal before the upgrade callback, no-listener socket destruction, and byte-exact binary upgrade heads even when Transfer-Encoding is present.

Verification:

• both focused imported corpus tranches passed (20/20 files, no failures/todos/unsupported cases);
• six promise-backed logical lifecycle tests passed;
• cumulative bootstrap HTTP/HTTP2 suite passed: 39/39 Zig tests;
• Zig formatting and diff checks passed;
• generated test caches and focused-runner artifacts were removed, reclaiming about 3.49 GiB.

The commit is local on codex/runtime-port; Git push is being retried separately because the GitHub Git endpoint has intermittently failed DNS in this environment.

Porting progress for Bun corpus positions 2521–2540 is committed as d2f8265a0 (fix(runtime): port HTTP URL upgrade and write semantics).

This tranche covers the sorted HTTP files from test-http-upgrade-client.js through test-http-write-information.js. Shared runtime work includes:

• reciprocal in-memory socket EOF/close sequencing and one-shot upgrade shutdown
• exact upgrade request/response head preservation, parser detachment, no-listener fallback, and synchronous handler exception routing
• distinct HTTPS Agent identity plus secure client/server socket state for legacy URL requests
• auth/URL request behavior, encoded ClientRequest write/end chunks, and ordered write callbacks
• HTTP/1.0 close-delimited bodies without accidental chunking or implicit Content-Length
• transactional flat/tuple header validation, preserved raw casing/duplicates, nonstandard status reasons, and full writeInformation() validation
• premature request abort propagation to the active ServerResponse while preserving writable lifecycle semantics

Verification:

• current URL/write focused group: all 3 Zig tests passed
• adjacent status/Unix/upgrade focused group: all 3 Zig tests passed
• cumulative bootstrap HTTP: all 40 Zig tests passed
• new logical matrix: 6/6 explicit cases passed
• zig fmt --check and git diff --check passed
• removed ~4.01 GiB of temporary Zig caches and focused test artifacts

Push is being retried separately; the local shadow branch currently contains the commit with Chris Breuer as sole author/committer and no coauthor trailers.

HTTP/Bun parity update — sorted corpus positions 2541–2560 are now implemented and tracked.

Commit: 9c2a5cd (feat(runtime): port HTTP2 transition semantics), authored and committed solely as Chris Breuer with no co-authors.

This tranche adds logical runtime coverage for:

• zero-length HTTP writes without spurious data events;
• secure HTTP/2 allowHTTP1 request forwarding and TLS socket state;
• WSS upgrade routing through an allowHTTP1 HTTP/2 server;
• HTTP/2 ALTSVC validation, origin normalization, and session/stream event delivery;
• consumption-paced stream queues with observable high-water-mark backpressure and correctly ordered drain;
• NGHTTP2_CANCEL propagation without an incorrect client error;
• captureRejections behavior before and after response headers, including 500 fallback and peer reset errors;
• asynchronous push callbacks preserving parent response ordering;
• isolated spawnSync child argv, filename, require cache, stdout/stderr, and exit status;
• TLS-over-CONNECT and nested HTTP/2 duplex transport ownership;
• in-memory socket read/unshift semantics, h2c preface routing, late HTTP/2 ownership discovery, and byte-exact HTTP/1 vs HTTP/2 autoselection;
• manual net connection events now invoke createServer handlers, and adopted HTTP sockets parse and dispatch buffered requests.

Verification:

• tracked 11-case logical transition/ALTSVC/backpressure/rejection/transport matrix: pass;
• sorted transition corpus selector (including zero-length HTTP, allowHTTP1/WSS, ALPN, ALTSVC): pass;
• sorted HTTP/2 client/session selector (async-local-storage through client-jsstream-destroy): pass;
• cumulative bootstrap HTTP/HTTP2 regression suite: all 41 Zig tests pass;
• zig fmt --check and git diff --check: pass.

Cleanup: removed the temporary focused runner/response file and reclaimed about 6.6 GiB from the local/global Zig caches; both cache directories are empty.

The next audited block starts with test-http2-client-onconnect-errors.js. Highest-priority gaps queued there are nested proxy-over-HTTP2 stream ownership hardening, reset-code name normalization, and exactly-once lookup/transport terminalization.

Push retry is still blocked by local DNS resolution for github.com; the commit remains on codex/runtime-port and will be retried.

HTTP/2 port progress update:

• 63019e4 hardens client lifecycle semantics: nested CONNECT adoption, lookup and transport error deduplication, reset-before-connect handling, max-concurrency defaults, and upload completion.
• 36ea93a completes the next compatibility lifecycle tranche: ordered trailers, peer terminalization, early-response half-close behavior, push response validation/delivery, and request routing.
• 1a93bf4 completes compatibility response behavior through short-stream handling: backpressure and drain state, HEAD/bodyless END_STREAM completion, response destruction and active-stream release, header/date/status fidelity, atomic writeHead arrays, binary/encoded writes, trailer validation, timeout behavior, and close bookkeeping.

Verification: the focused logical response suite passes all 8 non-vacuous cases, both adjacent Bun HTTP2 compatibility corpus tranches pass, and the cumulative bootstrap HTTP/HTTP2 gate passes all 44 tests.

Next: continue into the following sorted Bun HTTP2 corpus tranche and keep replacing allowed-empty coverage with tracked logical contracts.

HTTP/2 compatibility follow-up completed in dae9d98:

• fixed graceful request/response proxy-socket destruction and terminal stream bookkeeping
• made final response and informational header delivery non-reentrant and ordered
• added strict atomic early-hint link/header validation, connection and pseudoheader rejection, raw header metadata, late-hint no-op behavior, and informational header recording
• hardened writeInformation argument/state validation, caller status handling, and scalar value rendering
• added 5 non-vacuous logical cases spanning socket forwarding, delayed destruction, early hints, closed/destroyed response streams, and informational responses

Verification: cumulative bootstrap HTTP/HTTP2 gate now passes all 45 tests, including both adjacent Bun compatibility corpus selectors. Temporary isolated caches were removed after the run.

HTTP/2 SETTINGS parity tranche completed locally in d693547 (fix(runtime): enforce HTTP2 settings limits). Home now counts the initial SETTINGS frame toward maxOutstandingSettings, tracks acknowledgements independently on client/server sessions, and terminates overflow with ERR_HTTP2_MAX_PENDING_SETTINGS_ACK plus peer error code 2. Promoted test-http2-too-many-settings.js from expected failure into the maintained session/settings tranche. Verification: focused logical contract passed, copied 21-file session/settings tranche passed, and cumulative bootstrap HTTP sweep passed all 51 Zig tests. Push is being retried as connectivity permits.

Internal HTTP/2 header utilities completed in 8ae98c1 (fix(runtime): add HTTP2 header utilities). Added assertValidPseudoHeader, getAuthority, buildNgHeaderString, and toHeaderObject with pseudo-header ordering, NUL/SOH nghttp2 serialization flags, strict single-value enforcement, connection-header rejection, authority precedence, null-prototype materialization, and cookie/set-cookie folding. Promoted test-http2-util-assert-valid-pseudoheader.js and test-http2-util-headers-list.js from expected failures. Verification: focused logical contract passed, copied headers/control-plane tranche passed, cumulative bootstrap HTTP passed all 52 tests. This closes a Node internal compatibility gap that the current Bun checkout itself still marks failing. Push retry remains pending on DNS.