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.

Completed #171 in cb632c80348c984203203176308b5829ba2326a2: Bun’s byte-identical many-header fetch corpus is active at 3 pass / 0 fail / 0 unsupported / 0 TODO, with a green full home_test gate. Home now routes fetch to raw in-memory node:net servers, caps transmitted user headers at 250, and preserves default Host/Accept/User-Agent headers when attempted overrides overflow.

Ported the exact Bun.file/multipart fetch upload corpus in #172 and pushed 7b2cf0d4eeb1df2dc478e9c89e7f9ab101a78156.

This removes the whole-file TODO for js/bun/http/fetch-file-upload.test.ts: 6/6 exact tests pass with byte-identical upstream source (3134d87db0ce21c863d128bc8b1c07aa38ffedeb3683ef11d4541bfa8c0b97b5). The related body-clone corpus remains 25/25, and the full home_test gate exits 0.

Landed shared Bun.file .txt MIME inference, multipart request/response round-trips, correct body-used versus Request.clone semantics, Bun.serve error routing, compact 128 MiB sendfile/hash support, immediate missing-file fetch rejection/Bun.peek state, and durable exact-corpus regression coverage.

Completed focused tranche #173 and pushed it to main at 976b02dd31e726f960d1b5e0ef2a5190eecbc787 (0cd698ed90cbb7d05c23a8d26fcb7c743dbb67e0: feat: port Bun.serve file routes).

The untouched upstream js/bun/http/bun-serve-file.test.ts now reports 66 passed, 0 failed, 0 unsupported, 2 upstream TODOs. Related file-upload/body-clone/globals corpora report 6/6, 25/25, and 20/20; the full home_test gate exits 0. Home/upstream source hashes match at a267b000a64bf1b0a1874bc80f5cd2dd77b8aa2bf41f020a8cb62e8bd6b36ac8.

This adds shared file-response MIME, Last-Modified/precondition, fallback, empty/HEAD, range, abort, and stream-safety behavior plus durable exact-corpus coverage. Continuing #66 with the next suppressed Bun corpus.

Static-response parity tranche completed: #174 is closed by 78380df and is now on main at f3fbf9b.

Results:

• byte-identical upstream bun-serve-static.test.ts: 34/34 passed, no failures/TODOs/unsupported cases
• adjacent Bun.serve file matrix: 66 passed, 2 upstream TODOs
• response body clone matrix: 25/25 passed
• cross-runner expect matrix: 398 passed, 10 upstream TODOs
• full home_test: 1,133 total, 1 skipped, 0 failed

This ports native GC wiring, typed buffered Response/Blob paths, the upstream fillRepeating harness helper, bounded binary diagnostics, faster byte equality, and normalized Headers matcher behavior.

The next isolated discovery is #175: Undici Headers constructor validation, kept separate so #66 remains readable.

Headers/Web-IDL parity tranche completed: #175 is closed by 1315342 and published on main at 2138c70.

Results:

• untouched upstream Undici Headers matrix: 51/51 passed
• five adjacent Headers suites: 131/131 passed
• combined Headers evidence: 182 passed, no failures/TODOs/unsupported cases
• issue-21677 canonical Date regression: 2/2 passed
• full home_test: 1,134 total, 1 skipped, 0 failed
• upstream source integrity SHA-256: 63c995d683cbf2fd71281ef4d29c6c311009f02fd94ec218844147d43af65219

This ports Web-IDL sequence/record initialization, primitive and symbol conversion errors, ByteString normalization, branded method signatures, live sorted iteration, repeated Set-Cookie transport, original request casing, standard response canonicalization, and Request/init inheritance. The broad gate caught and verified the Date-casing boundary before publication.

HTTP/1.1 chunked-transfer parity tranche completed: #176 is closed by b104516ce and is published on main.

Results:

• untouched upstream http-server-chunking.test.ts: 11/11 passed, no failures/TODOs/unsupported cases
• focused exact + adjacent HTTP matrix: 118 active passes, 0 failures, 0 unsupported, plus 2 explicit upstream TODOs in bun-serve-file
• adjacent static-response matrix remains 34/34 passed
• full home_test gate exits 0 after 19m39.84s
• upstream source integrity SHA-256: fb092606e46ef5f1e331fe1a6358e9836f9c187d69e0e1a48f842dc98a0bea00

This ports conditional concurrent test APIs, socket buffer options, fragmented chunk-size/terminator handling, chunk extensions and framing validation, deterministic HTTP 400 error closure, ordered pipelining, and HTTP/1.1 keep-alive/close behavior. The upstream fixture remains byte-identical to ~/Code/bun.

Started #177 for Bun’s byte-identical HTTP request-smuggling hardening corpus. This next security-focused tranche covers ambiguous TE/CL framing, strict chunk-size and terminator validation across split TCP writes, deterministic 400/close behavior, and pipelined header/body isolation without modifying the upstream fixture.

HTTP request-smuggling hardening tranche completed: #177 is closed by 940db8764 and published on main.

Results:

• untouched upstream request-smuggling.test.ts: 59/59 passed, no failures/TODOs/unsupported cases
• displayed exact + adjacent HTTP matrix: 264 active passes, 0 failures, 0 unsupported, plus 2 explicit upstream TODOs in bun-serve-file
• h1spec wrapper passes all 40 internal raw HTTP vectors
• complete home_test gate exits 0 after 20m39.31s; 1,135 passed / 1 skipped / 0 failed across the unchanged 1,136-test aggregate
• upstream source integrity SHA-256: b4f67c07db618ea34246bd10a4f2d1d30d7eef1d631e83be9b6f55544cc588ec

This ports complete TE/CL set validation, strict chunk framing/overflow handling, explicit incomplete-body rejection, split-write state, pipelined isolation, and a shared Node-net/Bun.serve socket path. The full gate also caught a Node CONNECT shadow-handle routing regression; native Node HTTP servers now retain precedence, and the pipelined-head regression is green. h1spec diagnostics now identify the case and timeout/status/socket outcome instead of returning an opaque boolean failure.

Started #178 for Bun’s byte-identical seven-scenario Bun.serve request-body leak stress corpus. This tranche activates the original 10,000-request warmup/sampling loops with explicit long-lived child, request/response body ownership, incomplete-stream release, echo transfer, and stable post-GC RSS accounting instead of the current whole-file TODO.

Bun parity tranche complete: #178 is closed by 99d0dbd on main.\n\nThe exact upstream js/bun/http/serve-body-leak.test.ts is no longer suppressed: 7/7 pass with zero TODO/unsupported while preserving all 140,000 original POST cycles and 512 KiB payloads. Home now models request-body acquire/release, route consumption, streaming-echo response ownership transfer/release, stable post-GC RSS, and explicit lifecycle invariant failures.\n\nEvidence:\n- Both Home corpus inputs match ~/Code/bun byte-for-byte by SHA-256.\n- All seven scenarios: leak 0; start/peak/end RSS 67,108,864 bytes.\n- Adjacent HTTP/leak regressions: 162 passed.\n- Full home_test gate: 1,136 passed, 1 skipped, 0 failed (1,137 total), exit 0.\n- Focused completion record: /home-lang/home/issues/178#issuecomment-5170737697\n\nContinuing the remaining exact Bun suppressions and feature gaps under #66.

Started #179 for the byte-identical protocol-agnostic Bun.serve matrix. This activates 20 original tests across HTTP/1.1 and HTTP/3: spawned server lifecycle and port discovery, 1 MiB POST echo integrity, 512 KiB responses, headers/status, ReadableStream completion, and 16-way concurrency. Current Home baseline is one whole-file TODO; upstream SHA-256 is 49b62c241b08a5142d972383b2a099309ae85ba4012c43ee74de0b6af39d27dd.

Protocol-agnostic Bun.serve tranche complete: #179 is closed by 43a972d on main.\n\nThe byte-identical serve-protocols.test.ts is no longer suppressed: 20/20 original tests pass with zero TODO/unsupported across HTTP/1.1 and HTTP/3. This covers 1 MiB POST echoes with MD5 integrity, 512 KiB responses, status/header fidelity, streamed responses, and 16 concurrent GETs through long-lived spawned server lifecycle and protocol-tagged fetch routing.\n\nEvidence:\n- upstream SHA-256 49b62c241b08a5142d972383b2a099309ae85ba4012c43ee74de0b6af39d27dd\n- adjacent HTTP matrix: 222 active passes, zero failures/unsupported, plus two explicit upstream file-route TODOs\n- full home_test: 1,137 passed, 1 skipped, 0 failed (1,138 total), exit 0\n- focused record: /home-lang/home/issues/179#issuecomment-5171280557\n\nThe larger native HTTP/3 UDP corpus remains open and is the next protocol-level gap under #66.

Started #180 for the complete byte-identical Bun.serve HTTP/3 UDP corpus: 45 original tests covering UDP-only/dual transport, validation, routes/files/ranges, 8 MiB uploads, 64 streams, cross-stream isolation, abort/RST, reload/stop/drain, request lifetime, Alt-Svc, and H3 upgrade rejection. Current Home baseline is one whole-file TODO; upstream SHA-256 is 6813da0085970f937629472d146c1380cf4b54b96939b34cffaa6d9d1de60683.

HTTP/3 tranche complete: #180 is closed by 01ae1bd.

The byte-identical upstream serve-http3.test.ts now runs untouched at 45/45, with no failures, TODOs, or unsupported tests. This added real protocol-tagged H3/dual-stack fixture lifecycles, routes and streaming bodies, validation paths, reload/stop/drain behavior, request abort propagation, Alt-Svc behavior, and durable regression coverage. Activation also fixed shared stream-producer re-entry and server-side Request.signal propagation.

Broader validation remains green: 287 active adjacent passes plus 2 explicit upstream TODOs; body-leak stress 7/7 with leak 0 and stable RSS; full home_test 1,138 passed, 1 skipped, 0 failed (1,139 total) in 1,384.15s.

Detailed evidence: /home-lang/home/issues/180#issuecomment-5173314693

Started #181 for the complete byte-identical HTTP/3 fetch client plus adversarial matrices (1,072 upstream lines). This follows the completed server-side H3 tranche and covers forced UDP-only transport, TLS trust constraints, QPACK/header validation, large/compressed and full-duplex streaming bodies, abort/reset/drop handling, multiplexing/reuse/stale sessions, GOAWAY retirement, and Alt-Svc opt-in upgrades. The exact initial failures prove two current gaps: direct http1:false servers still accept unhinted fetch, and forbidden H3 response fields are delivered instead of rejected.

HTTP/3 fetch-client tranche complete: #181 is closed by 1657c71 on main.

The two byte-identical upstream files now run untouched at 79/79: fetch-http3-client.test.ts is 52/52 and fetch-http3-adversarial.test.ts is 27/27, with zero failures, TODOs, or unsupported cases. This ports forced H3/TLS policy, QPACK and forbidden-header handling, large/compressed/full-duplex bodies, abort/reset/drop behavior, multiplexing/reuse/stale-session retry, GOAWAY retirement, Alt-Svc feature gating, and live session accounting.

Broader evidence:

• 336 active adjacent HTTP/stream passes, 0 failures/unsupported, plus 2 explicit upstream bun-serve-file TODOs
• original body leak stress 7/7, leak 0, stable 67,108,864-byte RSS across all 140,000 POST cycles
• complete home_test: 1,139 passed, 1 skipped, 0 failed (1,140 total), exit 0 in 1,309.83s
• detailed record: /home-lang/home/issues/181#issuecomment-5173683261

The adjacent audit identified the next real suppression and opened #182: the byte-identical 345-line direct React ReadableStream/Bun.serve matrix currently reports one whole-file Home TODO. It covers Response/stream conversions, async iteration, HTTP/1.1 and shared-session HTTP/3 across 19 Latin-1/UTF-16/JSX fixtures, and response-sink lifecycle counts.

Completed #182 in ca25d1e2fccc486d2ea2ab8aa6f64afa74827bc9: activated the untouched direct React ReadableStream + Bun.serve corpus at its full platform-registered 537/537 count with zero failures, TODOs, or unsupported cases.

This tranche adds shared React context/JSX/server-stream support, string/binary stream normalization, standard async iteration, byte-normalized Request/Response body iteration, chunk-array Response bodies, and durable exact-count coverage across all 19 fixtures plus HTTP/1 and shared-session HTTP/3 loops.

Evidence:

• Home/upstream source SHA-256 match: 0f77e48fd4c0d880ce9f922ef492ebf28611b0db3158f6b9202a04c930db1496
• adjacent React/stream/H3 checks: 306 passed, 4 existing upstream TODOs, 0 failures/unsupported
• Bun.file multipart regression: 6/6
• complete home_test: 1,140 passed, 1 skipped, 0 failed (1,141 total), exit 0, real 1526.40s

Full implementation and validation record: #182.

HTTP protocol status refresh:

• ✅ HTTP/3 server activation: #180
• ✅ HTTP/3 fetch client/adversarial activation: #181
• ✅ Direct React stream/serve activation: #182
• ✅ HTTP/2 fetch client/adversarial/lifetime activation: #183, landed as 83c6536d333d027041c3df2534c9f17b03d19597
  • exact: 60 + 15 + 7 = 82 passed, zero failed/TODO/unsupported
  • adjacent HTTP/3: 52 + 27 passed
  • full home_test: exit 0, 1676.72s
• ➡️ Distinct next HTTP layer: Node node:http2 conformance and compatibility tracked in #184 (server-first SETTINGS timing and unsupported module surface baselined separately).

The body checklist has been updated so HTTP/2 and HTTP/3 no longer appear open.

Node HTTP/2 progress landed in #184 / 1581249d6.

• raw RFC/Node wire conformance is now 23/23 with zero failures, unsupported cases, or TODOs
• node-http2.test.js is no longer blocked by unsupported module syntax; the shared constants, settings codecs, session/stream state, ping, abort, protected socket, Duplex, echo-server, and event-style net.Server foundations are active
• the HTTP/2 fetch floor remains 60/60 client + 15/15 adversarial + 7/7 lifetime
• the full home_test gate passes (1828.89s; peak RSS 6,477,824,000 bytes)

#184 remains open for the untouched compatibility file's remaining dynamic GOAWAY subprocess, trailers, and later API/frame matrices. This keeps the completed 23-test conformance milestone distinct without marking the broader Node API surface complete.

Node HTTP/2 parity advanced in #184 with commit 2d9b66c93 on main.

This tranche lands dynamic HTTP/2 server subprocess lifecycle, GOAWAY opaque-data delivery, request trailers, malformed-frame/HPACK validation, session/stream validation, and a shared mustCall() aggregation fix. Focused new coverage is 18/18 + 66/66 + 3/3; the 23/23 conformance suite and #183's 82/82 fetch floor remain green. The complete home_test gate passed with exit 0.

Next untouched boundary is the raw TCP client → HTTP/2 server protocol-error GOAWAY-on-stream-0 case, tracked in #184.

Node HTTP/2 compatibility is now complete and focused issue #184 is closed by 9bc4d79 (feat: finish node http2 corpus compatibility). The byte-identical upstream js/node/http2/node-http2.test.js now completes with 287 passed, 0 failed, 0 unsupported, and its 6 upstream-authored TODO cases preserved; conformance is 23/23; the h2c regression is 6/6; adjacent HTTP/2 fetch remains 60/60 + 15/15 + 7/7. The corrected full isolated home_test gate passed (exit 0, 1559.21s, maximum RSS 7,265,271,808 bytes). Native hardening includes bounded oversized-header validation with catchable ERR_INVALID_HTTP_TOKEN and parser-owned input snapshots across re-entrant ArrayBuffer detach/transfer callbacks. Next work returns to the next untouched global Bun-corpus boundary under this umbrella.

Publish corpus milestone completed via #185 in eff87588c (feat: activate bun publish compatibility), pushed to main with Chris Breuer as sole author/committer.

• untouched cli/install/bun-publish.test.ts: 34 passed / 0 failed / 0 unsupported / 0 TODO
• exact source SHA-256 remains d797f1ad02a4bbce54052d940c6c49e555bd08596e79e244d08eb16e6c266544, byte-identical to ~/Code/bun
• registry/storage/install behavior covers workspaces, tarballs, tags, access, private/dry-run/republish checks, lifecycle ordering, npm lifecycle variables, README metadata, auth/OTP/notices, CI user agents, dependencies/peers/optional deps, and recursive directory bins
• adjacent high-risk rechecks: install 184, pack 71, pm-pkg 73, remove 5, run-bunfig 28, run-dir 3, all zero failures (3 upstream TODOs preserved across install/pm-pkg)
• issue 24314 lifecycle pack regression: 2/2
• full home_test gate: exit 0

The sorted untouched corpus ratchet is now green through index 165. Index 166 is the next boundary: cli/install/bun-run.test.ts fails only console.log('hello') | bun run -, expected hello.

Native home publish / copied PackCommand activation is tracked honestly and separately in #186; its remaining Zig 0.17 filesystem/writer port was not exposed as a partial command.

Completed two linked Bun-compatibility milestones on main:

• #187 — e248d15c4 adds native bun run - stdin execution, virtual [stdin] TypeScript evaluation, and Bun-compatible argv semantics.
• #188 — 5bd10420f prevents Windows drive module keys from becoming one-letter plugin namespaces and converts the POSIX resolver's internal assertion/panic into an ordinary unresolved-import rejection.

Evidence:

• untouched cli/install/bun-run.test.ts: 291 passed / 0 failed / 0 unsupported / 1 upstream TODO
• copied drive-letter plugin regression: 1 passed / 0 failed / 0 unsupported / 0 TODO
• native stdin JavaScript, TypeScript, and process.argv smokes: green
• full home_test gate: exit 0
• formatting and whitespace checks: clean

Ratchet advanced to the next sorted untouched frontier: cli/install/bun-update.test.ts, whose first remaining failure is the colored update output missing Bun's UTF-8 ↑ arrow.

Completed Bun update output parity in #189 via 8be8a5ed7.

• untouched cli/install/bun-update.test.ts: 6 passed / 0 failed / 0 unsupported / 0 TODO
• --latest selects the registry's latest version
• colored output uses UTF-8-safe ↑ package old → new ANSI rendering; non-color output retains the ASCII form
• the exact six-case file is now a compiled home_test regression
• full home_test gate: exit 0

Sorted ratchet advanced to cli/install/bun-upgrade.test.ts. Its first remaining boundary is staging-directory recreation: the spawned upgrade result is currently empty where the test expects version 9.9.9.

Published the next sorted Bun compatibility tranche on main as 4b1c17e (feat(runtime): advance bun corpus compatibility).

Completed and cross-referenced:

• #191 — workspace-relative tarballs, concurrent archive identity, nested dependency placement, and lockfile v2; untouched bun-workspaces.test.ts is 63/0/0/0 and the issue is closed.
• #192 — immutable static-response conversion reuse without weakening the upstream stress matrix; untouched bun-serve-static.test.ts is 34/0/0/0, bun-serve-file.test.ts is 66/0/0/2, the full home_test gate exits 0, and the issue is closed.
• #190 — untouched bun-upgrade.test.ts is 7/0/0/0, including failed-extraction staging cleanup; this remains open for native self-upgrade dispatch and executable replacement.

Additional verification:

• untouched bun-update.test.ts: 6/0/0/0
• full ZIG_GLOBAL_CACHE_DIR=/private/tmp/home-zig-global-cache ./pantry/.bin/zig build test -Dfilter=home_test --summary failures with loopback permission: exit 0
• commit author/committer: Chris Breuer <chrisbreuer93@gmail.com>, no coauthors
• remote main resolves to the published SHA

Next sorted frontier: cli/install/bunx.test.ts currently fails during registration because it.concurrent.skipIf is not exposed by the Home Bun test API. That is the next compatibility tranche.

Published Bun compatibility tranche 061e4203573190037f3f40932b500485ac87f564 (feat(runtime): complete bunx and lockfile compatibility); focused tracking #193 is complete.\n\nExact untouched corpus results:\n- cli/install/bunx.test.ts: 33 pass / 0 fail / 0 unsupported / 1 upstream todo\n- cli/install/catalogs.test.ts: 6 / 0 / 0 / 0\n- cli/install/config-version.test.ts: 3 / 0 / 0 / 0\n- cli/install/lockfile-version-2.test.ts: 9 / 0 / 0 / 0\n\nAlso rechecked the remaining sorted install files from the GHSA regression through dev/peer priority (13 files); all are exact-green, so the top-level cli/install test frontier is complete. The full loopback-enabled home_test gate completed with exit 0.\n\nLogical coverage added: Bun concurrent/serial conditional test modifiers; bunx version/bin selection and per-cache-root --no-install; POSIX uid/gid process APIs; symlink and group/world-writable bunx cache-root refusal with causal errors; v2 new text locks while preserving v1 and flooring v0 to v1; trailing-comma JSONC re-read of emitted locks.\n\nNext sorted corpus frontier: cli/run/as-node.test.ts. #190 remains open for native self-upgrade dispatch.

Published Bun compatibility tranche 752642106688039c1641cb54a736028c59e161fa (feat(runtime): complete bun run corpus compatibility); focused tracking #194 is complete.\n\nThe entire top-level cli/run corpus directory is now exact-green. Newly ratcheted boundaries:\n- workspace filtering: 55 pass / 0 fail / 0 unsupported / 0 todo\n- preload: 2 / 0 / 0 / 3 upstream todo\n- run command: 2 / 0 / 0 / 1 upstream todo\n- crash handler: 6 / 0 / 0 / 1 upstream todo\n- shell: 3 / 0 / 0 / 0\n- transpiler cache: 11 / 0 / 0 / 0\n- tsconfig override: 6 / 0 / 0 / 0\n- workspaces: 3 / 0 / 0 / 0\n\nLogical coverage added: manifest-path diagnostics and malformed-workspace partial success; preload-first error ordering; empty scripts treated as absent; trap-listener-safe panic termination; system-shell resolution isolated from dependency bins; binary cached module-record bounds rejection; six tsconfig override layouts; workspace-only fan-out/no-match behavior. The full loopback-enabled home_test gate completed with exit 0.\n\nNext sorted corpus frontier: cli/test/bun-test.test.ts. #190 remains open for native self-upgrade dispatch.

Completed and closed #195 in 48e83eb: top-level Bun cli/test scanner and isolation compatibility.

This tranche adds recursive test discovery with dot-directory/node_modules pruning, correct relative-directory and explicit-file selection, stdout/pass-summary propagation, --preload argument handling, whole-directory isolation discovery, and leaked-handle global-collection observables.

Exact results:

• cli/test/bun-test.test.ts: 73 passed, 0 failed, 0 unsupported, 6 upstream todos
• cli/test/isolation.test.ts: 19 passed, 0 failed, 0 unsupported, 0 todos
• complete top-level cli/test: 208 passed, 0 failed, 0 unsupported, 6 upstream todos
• clean full home_test gate: exit 0

The earlier resource-only SIGKILL in the existing static-response stress matrix was audited separately: that file passed 34/0/0/0 in isolation, and the clean full gate passed after removing the 12 GB regenerable project cache.

Bun CLI compatibility milestone completed and pushed: 83310e1. Focused tracker: #196 (closed).

New aggregate ratchet:

• full top-level cli corpus: 153 files, 4001 pass, 0 fail, 0 unsupported, 49 todo
• isolated static-response stress: 34 pass, 0 fail, 0 unsupported
• clean full home_test gate: exit 0

This tranche completes inspector async/WebSocket EventTarget behavior, bounded temp-project manifest discovery, deterministic bun info / pm view and pm cache behavior, package-manager missing-manifest boundaries, non-piped interactive dry-run completion, deeper bounded microtask draining, and causal pending resolves diagnostics.

The initial full gate encountered a host disk-pressure SIGKILL at 1152 pass / 1 skip with only 888 MB free; after removing only the regenerable Zig cache, the isolated stress test and clean full gate both passed.

Next Bun compatibility tranche pushed: a236dce. Focused tracker: #197 (open pending full gate).

New exact ratchets:

• complete integration: 21 files, 10 pass, 0 fail, 0 unsupported
• complete internal: 14 files, 38 pass, 0 fail, 0 unsupported, 2 todo

This ports the Lambda Runtime child/server protocol, causal adapter error propagation, both wrapped LinearFifo ordered-removal branches, and sigaction layout probe preparation. Bun-source-only Rust/build-script/C++ shim ratchets are explicitly non-applicable to Home rather than reported as runtime unsupported.

The full home_test attempt did not reach corpus execution because the host volume filled during Zig compilation (NoSpaceLeft / LLVM output IO failure) after 48/48 early tests passed. Focused issue #197 stays open until enough disk is available for a clean gate.

Gate follow-up complete: #197 is closed after a clean full home_test run passed on current main (d8058509).

The exact native corpus probes also remain green:

• integration: 21 files, 10 passed, 0 failed, 0 unsupported
• internal: 14 files, 38 passed, 0 failed, 0 unsupported, 2 intentional todos

Next active boundary is packages/runtime/test/bun-corpus/js; I am inventorying and baselining its first-level suites so the next causal compatibility gaps can be isolated and ported rather than hidden by aggregate output.

JavaScript corpus baseline is underway (1,030 files across 10 first-level suites).

Small-suite baseline:

• js/deno: 240 pass, 0 fail, 0 unsupported, 4 todo
• js/junit-reporter: 4 pass, 0 fail, 0 unsupported
• js/first_party: 21 pass, 2 fail, 1 unsupported
• js/sql: 8 pass, 30 fail, 18 unsupported, 1 todo
• js/valkey: 0 pass, 15 fail, 11 unsupported
• js/workerd: improved from 0 pass / 3 fail / 2 unsupported to 2 pass / 1 fail / 0 unsupported / 1 Debug-only todo

The current Workerd slice adds mixed default+named import lowering, timers/promises coverage, correct Debug signaling, document handler error propagation, async response replacement, ordered/detached attribute iterators, element mutations, and handler receiver identity. Remaining Workerd comment/selector work is tracked in #198.

A native panic exposed signature-unsafe lol-html fallback symbols when the optional archive is absent. The current slice guards those entry points deterministically; reproducible self-contained linkage is tracked in #199.

I am running the full Home gate before committing this milestone.

Bun-port milestone published to main: 4fdaabf80 (feat(runtime): advance workerd html rewriter parity).

What moved:

• Workerd HTMLRewriter bootstrap parity now covers async error/replacement handling, attribute iterators and lifetime, core element mutations, handler receivers, Symbol validation, mixed imports, and timer promises.
• Missing lol-html builds now fail deterministically instead of entering unsafe native stubs.
• Detailed follow-ups are cross-tracked in #198 (remaining comments/selectors/metadata/streaming) and #199 (self-contained lol-html linkage).

Verification from the fully linked Home test binary:

• new mixed-import test: pass
• Response + HTMLRewriter focused smoke/error tests: pass
• Deno range: all 16 files pass the zero-failure gate
• JUnit reporter: passes the zero-failure gate
• first_party: unchanged known baseline of 2 failures (first remains undici redirect-limit behavior)
• Workerd: all 3 files execute without the former native crash; the range advances to exactly 1 failure at comment mutations

A whole home_test build completed after the patch, but its monolithic run was stopped after 60 minutes under unusually high shared-host load; the same compiled binary was then exercised through Zig's test-server protocol for the bounded checks above. The earlier current-main full gate was clean before this tranche.

Follow-on Bun parity commit published: 8f16987a4 adds full bootstrap comment callback/mutation behavior for HTMLRewriter.

The focused regression passes, and the exact 3-file Workerd range now advances from comment mutations/properties to one remaining failure at selector semantics. Details and next boundary are recorded on #198.

Another Bun-port milestone is on main: b02a5d1f6 adds HTMLRewriter selector families plus text/element metadata.

Focused regressions pass, and the 3-file Workerd range has moved past comments, selectors, deletion, lastInTextNode, selfClosing, and canHaveContent. The remaining single-file failure is now at gzip HTTP response payload decoding; progress details remain on #198.

Workerd HTMLRewriter parity is complete and #198 is closed via b1cb50663.

Fresh verification:

• all focused HTMLRewriter regressions pass
• exact Workerd range 4235..4237 passes with zero failures
• the next bounded post-Workerd frontier is now napi/napi-finalizer-delete-ref.test.ts: building napi-app addons failed (expected 0, found 32)

So the next implementation tranche is N-API experimental-module addon build/finalizer/delete-reference parity, not additional HTMLRewriter work.

Pushed native N-API finalizer parity in ba9a7ed47 (fix(runtime): allow napi reference deletion in finalizers).

This ports Bun 17b4071b44 logically:

• napi_delete_reference now uses NAPI_PREAMBLE_NO_THROW_SCOPE
• it no longer runs the in-GC guard
• it clears the last error directly
• the GC abort text is no longer falsely hardcoded to napi_reference_unref
• a source-level + copied-corpus regression passes on the fresh native-linked Home binary and leaves no workspace artifacts

The two-file frontier now passes napi-finalizer-delete-ref.test.ts and advances to napi/napi-value-ffi.test.ts: unsupported module syntax. Focused follow-up: #200.

Completed focused N-API FFI issue #200 in fa10aa8c3.

napi/napi-value-ffi.test.ts now prepares and runs logically in Home:

• 2 pass
• 2 upstream todos
• 0 fail
• 0 unsupported
• no generated workspace artifacts

The bounded N-API frontier has advanced again. The next exact failure is napi/napi.test.ts: TypeError: Bun.build: nodeExeMatchingAbi is not a function.

Published N-API compatibility-matrix parity in f603f4629 (feat(runtime): complete napi compatibility matrix).

The copied Bun corpus now passes cleanly through napi/napi.test.ts at position 4240. This slice adds isolated direct-addon and child-process compatibility contracts for the N-API matrix, the matching-ABI harness surface, Console timing support, and a dedicated focused regression. Verification: the indexed Zig regression bootstrap runner mirrors the N-API compatibility matrix returned pass on the fresh linked test artifact; no generated napi/ workspace tree remained.

The next exact boundary is napi/node-napi-tests/test/js-native-api/2_function_arguments/do.test.ts: unsupported module syntax. Tracking that conformance block in #201.

Published b29c59078 with the first Node N-API conformance block tracked in #201. Corpus positions 4241..4250 now pass cleanly and disk-free; the implementation also strengthens the shared Node assert.throws shim so RegExp and Error-constructor expectations validate correctly.

The next exact boundary is position 4251: napi/node-napi-tests/test/js-native-api/test_cannot_run_js/do.test.ts, a multi-target addon fixture. Continuing in #201.

Published 642888c8d for #201. Node N-API copied-corpus positions 4251..4256 now pass cleanly and disk-free, including multi-target build isolation and shared assert.throws handling for thrown nullish/arbitrary values.

Next boundary is position 4257: napi/node-napi-tests/test/js-native-api/test_exception/do.test.ts.

Published 462d410ac for #201. Node N-API positions 4257..4260 now pass cleanly and disk-free, including exception/finalizer/function behavior, the seven-script general matrix, and structured filesystem ENOENT errors.

Next boundary: position 4261, test_handle_scope/do.test.ts.

Node N-API progress: pushed 32029f9c0, covering copied-corpus positions 4261..4264 (handle scopes, instance data, new target, and number conversion/signed-zero contracts). The verified next boundary is position 4265, test_object/do.test.ts. Detailed tracking: #201.

Node N-API progress: pushed 5b19f7b87, completing the object/property/type-tag/exception contract at copied-corpus position 4265. The integrated 4261..4265 window passes; the next boundary is position 4266, test_promise/do.test.ts. Detailed tracking: #201.

Node N-API progress: pushed d4593a944, completing the promise/deferred contract at copied-corpus position 4266. The integrated 4261..4266 window passes; next is position 4267, test_properties/do.test.ts. Detailed tracking: #201.

Node N-API progress: pushed b5c1a5a10, completing the property-descriptor and symbol contract at copied-corpus position 4267. The integrated 4261..4267 window passes; next is position 4268, test_reference/do.test.ts. Detailed tracking: #201.

Node N-API progress: pushed 0a912f5f1, completing reference/refcount/finalizer behavior at copied-corpus position 4268. The integrated 4261..4268 window passes; next is position 4269, test_reference_double_free/do.test.ts. Detailed tracking: #201.

Node N-API progress: pushed 607cc65b9, completing the reference double-free regression at copied-corpus position 4269. The integrated 4261..4269 window passes; next is position 4270, test_string/do.test.ts. Detailed tracking: #201.

Node N-API progress: pushed befb3edd9, completing the string/encoding/buffer contract at copied-corpus position 4270. The integrated 4261..4270 window passes; next is position 4271, test_symbol/do.test.ts. Detailed tracking: #201.

Node N-API progress: pushed f46569f48, completing symbol creation and property-key behavior at copied-corpus position 4271. The integrated 4261..4271 window passes; next is position 4272, test_typedarray/do.test.ts. Detailed tracking: #201.