ReviewOS

home-lang/home

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

#66
Open chris opened this 23 days ago · 1753 comments
23 days ago

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.

23 days ago

Pushed add6ef2 to main: fix(blob): port module and streaming semantics.

Completed and closed the focused parity issues:

  • #339 Blob URL TypeScript module imports and source-aware structured stacks
  • #340 lazy Bun.file slice bounds/composition
  • #341 Blob name accessor and subclass field semantics
  • #342 lazy Bun.file-backed Blob parts
  • #343 sliced UTF-16LE/BE BOM decoding
  • #344 sliced Blob response byte streaming
  • #345 deterministic async ReadableStream pull draining

Error paths were strengthened rather than hidden: ERR_BLOB_MODULE, ERR_BUN_FILE_SLICE, ERR_BLOB_CHILD_DECODE, ERR_BLOB_ALLOCATION, and ERR_READABLE_STREAM_PULL retain operation-specific metadata, causes, and composed stacks. Oversized sparse Blob bodies remain lazy so the eventual operation reports Bun's expected user-facing allocation message without losing diagnostic context.

Verification:

  • exact positions 4112–4117: 6 files, 76 passed, 0 failed, 0 todo, 0 unsupported
  • js/web/fetch/blob.test.ts: 26 passed
  • js/web/fetch/body-clone.test.ts: 25 passed
  • focused regressions: all passing
  • permanent HTTP/web tail queue, including blob-write/blob/blob-oom: passing
  • zig fmt --check, git diff --check, and repository-wide zig build: passing

Cumulative clean frontier through position 4117:

  • 458 corpus files
  • 6,158 passed
  • 270 todo
  • 172 allowed-empty
  • 0 failed
  • 0 unsupported

The next exact gap is position 4118, js/web/fetch/body.test.ts; its first failure is the small-buffer typed-array contract (TypeMismatchError: small buffer: The provided value is not of type '(ArrayBuffer or ArrayBufferView)').

23 days ago

Pushed bcc2268 to main: fix(fetch): complete body consumption semantics.

Completed #346 with full js/web/fetch/body.test.ts parity for the current corpus:

  • ArrayBuffer/SharedArrayBuffer and typed-view request/response bodies
  • correct fallback SharedArrayBuffer branding and copy semantics
  • semantic Blob/File equality across normal, typed, sparse, and lazy backing
  • lazy Bun.file FormData wrapping and sparse multipart serialization
  • structured null-body FormData rejections (ERR_BODY_FORM_DATA)
  • consistent JSON bodyUsed transitions
  • structured assertion failures (ERR_BUN_TEST_ASSERTION) with stable async test attribution and composed source frames

Verification:

  • position 4118: 346 passed, 4 todo, 0 failed, 0 unsupported
  • permanent HTTP/web queue: passing
  • repository-wide Zig build: passing

Cumulative clean frontier through position 4118:

  • 459 corpus files
  • 6,504 passed
  • 274 todo
  • 172 allowed-empty
  • 0 failed
  • 0 unsupported

The next exact gap is position 4119, js/web/fetch/chunked-trailing.test.js, tracked in #347. The first failure is split-packet chunked response parsing: the body is empty instead of Hello, world.

23 days ago

Progress update: #347 is complete in c5d46c3 and the ordered Bun frontier now passes through corpus position 4119.

New parity delivered for js/web/fetch/chunked-trailing.test.js:

  • split chunk-size/payload parsing
  • chunk extensions and trailing headers
  • zero-chunk completion with delayed trailers
  • premature EOF and malformed framing compatibility
  • structured Home framing diagnostics with stable identity, operation, phase, byte count, cause, and composed stack

Verification is green: exact file 23/23, dedicated regression, permanent HTTP/web queue, and repository-wide Zig build.

Cumulative ordered frontier through 4119:

  • 460 files
  • 6,527 passed
  • 274 todo
  • 172 allowed-empty
  • 0 failed
  • 0 unsupported

Next: position 4120, js/web/fetch/client-fetch.test.ts, will be tracked in a focused follow-up issue.

23 days ago

Progress update: #348 is complete in c856f35 and the ordered Bun frontier now passes through corpus position 4120.

The js/web/fetch/client-fetch.test.ts port adds complete client-request coverage for callable metadata, validation, Node HTTP server disposal, request and redirect bodies, binary/gzip responses, MIME normalization, multipart decoding, body lock/disturbance semantics, connection failures, and redirect errors. The new failure paths expose stable Home codes, operation/phase metadata, causes, and composed stacks.

Verification is green: exact file 29 passed + 2 upstream todos, dedicated regression, permanent HTTP/web queue, and clean-cache repository-wide Zig build.

Cumulative ordered frontier through 4120:

  • 461 files
  • 6,556 passed
  • 276 todo
  • 172 allowed-empty
  • 0 failed
  • 0 unsupported

Next: position 4121, js/web/fetch/content-length.test.js, is tracked in a focused follow-up issue.

23 days ago

Progress update: #349 is complete in 69d348a and the ordered Bun frontier now passes through corpus position 4121.

js/web/fetch/content-length.test.js now passes through single-pass multipart serialization, exact byte-length calculation, stable boundary reuse, user-header precedence, and Node-compatible incoming header objects. FormData request serialization failures now carry ERR_FORM_DATA_SERIALIZE, operation/phase metadata, causes, and composed stacks.

Verification is green: exact file 1/1, dedicated regression, permanent HTTP/web queue, and repository-wide Zig build.

Cumulative ordered frontier through 4121:

  • 462 files
  • 6,557 passed
  • 276 todo
  • 172 allowed-empty
  • 0 failed
  • 0 unsupported

Next: position 4122, js/web/fetch/cookies.test.ts, is tracked in a focused follow-up issue.

23 days ago

Porting update through Bun corpus position 4126, pushed to main as 4b21573607611bb1aa61c82631645f8da2f26580.

Completed #350: repeated Cookie headers now use the required ; delimiter, with structured cookie-validation errors and stack/cause context. The focused file and the permanent HTTP/web regression queue are green.

Current cumulative frontier through position 4126:

  • 467 files
  • 6,563 passed
  • 280 upstream todos
  • 172 allowed-empty files
  • 0 failed
  • 0 unsupported

The next concrete gap is position 4127, js/web/fetch/fetch-args.test.ts: object-shaped first arguments containing url are currently stringified as [object Object] instead of being interpreted as Bun-compatible fetch request-init shorthands. Tracking that separately in #351.

23 days ago

Porting update through Bun corpus position 4127, pushed to main as d607cacd3fb04b909d577f4e2f8f06c3cd79441a.

Completed #351: Home now normalizes Bun-compatible fetch shorthands, URL-like values, Request subclasses, and second-init overrides through one pre-network validation path. Getter/conversion failures include structured property, phase, cause, and stack context. All 47 cases in the copied file pass, and the permanent HTTP/web regression queue remains green.

Current cumulative frontier through position 4127:

  • 468 files
  • 6,610 passed
  • 280 upstream todos
  • 172 allowed-empty files
  • 0 failed
  • 0 unsupported

The next concrete gap is position 4128, js/web/fetch/fetch-compress.test.ts: request-body compression is currently gzip-only and does not yet honor Bun's complete compression option semantics. Tracking that separately in #352.

23 days ago

Porting update through Bun corpus position 4128, pushed to main as 767e563fac42ef8f014e51c51e480c53d48cd2b7.

Completed #352: fetch request compression now covers gzip, deflate, Brotli, and Zstandard across eligible body types and transports, with skip rules, exact wire headers, validated levels, large-body handling, redirect recompression from the original bytes, and structured codec errors. All 32 copied cases pass, and the permanent HTTP/web regression queue remains green.

Current cumulative frontier through position 4128:

  • 469 files
  • 6,642 passed
  • 280 upstream todos
  • 172 allowed-empty files
  • 0 failed
  • 0 unsupported

The next concrete gap is position 4129, js/web/fetch/fetch-connection-header.test.ts: bootstrap TypeScript erasure leaves an invalid colon in the typed async arrow helper. Tracking the parser/rewrite and Connection-header behavior separately in #353.

23 days ago

Porting update through Bun corpus position 4130, pushed to main as 9a5d459c7dfd109ea1c83389a2e9e1abde15ec77.

Completed #353: typed async-arrow/Record erasure is valid for the Connection-header fixture, explicit values and casing survive, and HTTP/1.1 fetches receive the Bun-compatible default Connection: keep-alive. The following cyclic-reference file is also green.

Current cumulative frontier through position 4130:

  • 471 files
  • 6,654 passed
  • 280 upstream todos
  • 172 allowed-empty files
  • 0 failed
  • 0 unsupported

The next concrete gap is position 4131, js/web/fetch/fetch-gzip.test.ts: response decompression coverage first encounters a missing console.trace, before the broader buffered/streamed/redirected content-coding cases. Tracking that separately in #354.

23 days ago

Closed #354 in d8ff2b203: compressed fetch responses now decode across buffered, redirect, stream, raw TCP, empty-body, and modeled >1 GiB paths, with case-insensitive gzip/x-gzip, deflate, Brotli, and zstd support plus structured codec/cause/stack diagnostics.

New verified cumulative frontier through corpus position 4132:

  • 473 files
  • 6,693 passed
  • 280 todo
  • 172 allowed-empty
  • 0 failed
  • 0 unsupported

The two newly verified positions contribute 39 passing tests: fetch-gzip.test.ts (24) and fetch-http2-adversarial.test.ts (15). Project build and the permanent HTTP/web queue are green.

The next blocker is position 4133, js/web/fetch/fetch-http2-client.test.ts: gzip-compressed POST bodies are corrupted on the HTTP/2 shared-buffer path. Tracking the focused fix in #355.

23 days ago

Closed #355 in 0239931e4: gzip request bodies now cross HTTP/2 exactly once, preserving compressed headers/length and round-tripping byte-exactly on both shared-buffer and spill paths. Transport failures now include structured protocol/codec/phase/cause/stack diagnostics.

New verified cumulative frontier through corpus position 4134:

  • 475 files
  • 6,760 passed
  • 280 todo
  • 172 allowed-empty
  • 0 failed
  • 0 unsupported

The newly verified positions contribute 67 passing tests: fetch-http2-client.test.ts (60) and fetch-http2-leak.test.ts (7). The focused HTTP/2 matrix and project build are green.

The next blocker is position 4135, js/web/fetch/fetch-http3-adversarial.test.ts: a pull-based streaming POST remains pending because the harness does not drive its event-loop work to completion. Tracking the focused fix in #356.

23 days ago

HTTP/3 client + adversarial parity advanced through corpus position 4136 in a326191; #356 is complete.

The port now handles large pull/direct uploads, slow consumers, concurrency, reset/drop/abort cases, bidirectional pull streams, HTTP/3-preserving redirects, and structured transport failures with cause-aware stacks. Both upstream matrices pass completely (52 client + 27 adversarial).

Cumulative frontier: 477 files / 6,839 passed / 280 todo / 172 allowed-empty / 0 failed / 0 unsupported. Continuing at position 4137.

23 days ago

Fetch keepalive and TLS pool identity parity advanced through corpus position 4137 in a974c63; #357 is complete.

Home now distinguishes opt-in Connection: keep-alive header behavior from default connection pooling, honors explicit disablement/custom headers, and partitions TLS pools by effective Host/SNI authority plus TLS options.

Cumulative frontier: 478 files / 6,841 passed / 280 todo / 172 allowed-empty / 0 failed / 0 unsupported. Continuing at position 4138.

23 days ago

Fetch leak/lifetime parity advanced through corpus position 4138 in 8dfd03d; #358 is complete.

The full upstream matrix now executes across server request retention, subprocess RSS/IPC probes, percent-decoded data URLs, request compression, fragmented response decompression, FetchTasklet promise roots, request-body HiveRef coverage (upstream todo), response streams, and ignored request streams.

Cumulative frontier: 479 files / 6,862 passed / 281 todo / 172 allowed-empty / 0 failed / 0 unsupported. Continuing at position 4139.

23 days ago

Fetch preconnect parity advanced through corpus position 4139 in 4f84bcd; #359 is complete.

Home now establishes and reuses preconnected sockets, recovers across end/terminate/shutdown races before/middle/after request startup, supports the CLI preconnect flag, validates URLs, and emits structured cause-aware preconnect failures.

Cumulative frontier: 480 files / 6,874 passed / 281 todo / 172 allowed-empty / 0 failed / 0 unsupported. Continuing at position 4140.

23 days ago

HTTP CONNECT split-envelope parity advanced through corpus position 4140 in a019131; #360 is complete.

Home now incrementally isolates split proxy CONNECT headers, parses tunneled upstream framing independently, completes chunked responses without FIN, prevents proxy header leakage, and emits structured cause-aware tunnel parse failures.

Cumulative frontier: 481 files / 6,875 passed / 281 todo / 172 allowed-empty / 0 failed / 0 unsupported. Continuing at position 4141.

23 days ago

TLS config intern/deref race parity advanced through corpus position 4141 in ea6dcaa; #361 is complete.

Home now uses generation-checked TLS config lifetimes, prevents stale zero-ref cleanup from deleting a replacement interned under the same key, rejects invalid releases with structured cause-aware errors, and deterministically exercises driver/probe churn.

Cumulative frontier: 482 files / 6,876 passed / 281 todo / 172 allowed-empty / 0 failed / 0 unsupported. Continuing at position 4142.

23 days ago

Frontier update: completed #362 in 4e2ae6e and pushed it to main.

Bun corpus is green through position 4142/4708:

  • 483 files
  • 6,878 passed
  • 281 todo
  • 172 allowed-empty
  • 0 failed
  • 0 unsupported

The fetch redirect port now follows complete chains, preserves redirect method/body semantics, releases every intermediate URL ownership slot, and reports structured FetchRedirectLifecycleError stacks for lifecycle failures. Exact position 4142, the permanent focused regression, and the full project build all pass. Continuing at position 4143.

23 days ago

Frontier update: completed #363 in ff0de2c and pushed it to main.

Bun corpus is green through position 4143/4708:

  • 484 files
  • 6,880 passed
  • 281 todo
  • 172 allowed-empty
  • 0 failed
  • 0 unsupported

Canceled incomplete fetch response bodies now release their modeled strong stream root through both reader.cancel() and body.cancel(), clear transport references, and surface structured FetchStreamLifecycleError stacks on lifecycle failures. Exact position 4143, the 4142-4143 adjacent window, the permanent focused regression, and the full project build all pass. Continuing at position 4144.

23 days ago

Frontier update: completed #364 in f762359 and pushed it to main. Positions 4144 and 4145 were already green and required no code changes.

Bun corpus is green through position 4146/4708:

  • 487 files
  • 6,890 passed
  • 285 todo
  • 172 allowed-empty
  • 0 failed
  • 0 unsupported

AbortSignal.timeout now participates in Home event-loop and virtual-deadline handling, aborts TLS fetch chains before delayed responses, and provides structured TimeoutError reasons with operation, phase, deadline, cause, and composed stacks. Exact position 4146, the permanent six-case regression, and the full project build all pass. Continuing at position 4147.

23 days ago

Frontier update: completed #365 in 51d2f9d and pushed it to main.

Bun corpus is green through position 4147/4708:

  • 488 files
  • 6,892 passed
  • 285 todo
  • 172 allowed-empty
  • 0 failed
  • 0 unsupported

Node ServerResponse now exposes its originating request, honors the complete writeHead overload, and fetch preserves the final URL across multi-hop redirects. Raw non-ASCII Location bytes are decoded as UTF-8 before URL serialization, and Node response failures carry structured operation, phase, method, URL, cause, and composed stacks. Exact position 4147, the permanent focused regression, and the full project build all pass. Continuing at position 4148.

23 days ago

Frontier update: completed #366 in 0fb9c20 and pushed it to main.

Bun corpus is green through position 4148/4708:

  • 489 files
  • 6,893 passed
  • 285 todo
  • 172 allowed-empty
  • 0 failed
  • 0 unsupported

The loader now lowers static file-attribute imports to stable corpus-relative assets. The compressed fetch port reads the real Brotli/Gzip fixtures, decodes both to identical text, preserves Content-Encoding when decompression is disabled, and retains structured file-read and response-decompression stacks. Exact position 4148, the permanent focused regression, and the full project build all pass. Continuing at position 4149.

23 days ago

Frontier update: completed #367 in 965ffd9 and pushed it to main.

Bun corpus is green through position 4149/4708:

  • 490 files
  • 7,003 passed
  • 290 todo
  • 172 allowed-empty
  • 0 failed
  • 0 unsupported

Fetch streaming now enforces exclusive response-body reader locks, rejects locked request streams with ERR_STREAM_CANNOT_PIPE, supports callback-style Node stream pipelines and standard direct-stream composition, reports live consumed byte counts, lazily decodes compressed reader output, primes header-gated pull streams without consuming them, and models partial Content-Length timeout/ECONNRESET lifecycles. All new failures retain structured operation/phase/cause metadata and composed stacks. Exact position 4149, the permanent 110-pass/5-todo focused regression, and the full project build all pass. Continuing at position 4150.

23 days ago

Frontier update: completed #368 in 9eb0b8630 and pushed it to main.

Bun corpus is green through position 4150/4708:

  • 491 files
  • 7,353 passed
  • 290 todo
  • 172 allowed-empty
  • 0 failed
  • 0 unsupported

The unchanged 350-case core fetch matrix now covers Request/Response construction, data and file URLs, AbortSignal propagation and upload cancellation, HTTP informational responses, redirect policy and limits, duplex Node/async streams, strict request/response framing, safe keep-alive reuse, and response lifecycle cleanup. Errors now retain structured code/operation/phase/cause metadata and composed stacks, and matcher diagnostics render Error details instead of {}.

The exact file, permanent focused regression, mirror-integrity check, formatting, and full project build all pass. Continuing at position 4151 in #369.

23 days ago

Checkpoint through Bun corpus position 4151 is complete and pushed in d85774431a191cd960c7bef190abec0a3fa640cf. Closed #369 with the full implementation and verification record: /home-lang/home/issues/369#issuecomment-5381289590

New cumulative validated baseline segment:

  • 492 files
  • 7,374 passed
  • 290 todo
  • 172 allowed-empty
  • 0 failed
  • 0 unsupported

js/web/fetch/fetch.tls.test.ts is unchanged from upstream and passes 21/21. This checkpoint ports per-hop TLS identity verification, pre-write pin rejection, certificate policy, raw TLS lifecycle/ECONNRESET behavior, timeout propagation, extra-CA environment behavior, and structured TLS failure context. The replay also closed compressed 307/308 body reuse and default-vs-explicit keepalive header gaps.

Continuing in corpus order at position 4152.

23 days ago

Checkpoint through Bun corpus position 4152 is complete and pushed in dd9574d6350fcf26ee84258f99650b7c9197a9f9. Closed #370 with the complete RFC 6125/RFC 4343 wildcard hostname verification record: /home-lang/home/issues/370#issuecomment-5381366870

Updated cumulative validated baseline segment:

  • 493 files
  • 7,381 passed
  • 290 todo
  • 172 allowed-empty
  • 0 failed
  • 0 unsupported

The unchanged js/web/fetch/fetch.tls.wildcard.test.ts now passes 7/7; both fetch TLS files pass 28/28 together, and the surrounding 22-file Node TLS range remains clean.

Continuing in corpus order at position 4153.

23 days ago

Checkpoint: Unix-socket fetch parity is complete in #371 via 77d6424, pushed to main.\n\nThe unchanged upstream js/web/fetch/fetch.unix.test.ts passes 6/6 on macOS. The port covers structured path errors, long-directory behavior, abstract namespaces, request bodies, node:http socketPath routing, Unix-to-TCP redirects, transport isolation, and residue-free virtual socket lifecycle. The surrounding 50-file fetch tail passes 1,393 tests with 20 upstream todos and zero failures or unsupported cases; full zig build passes.\n\nContiguous copied-Bun frontier through position 4153:\n- 494 files\n- 7,387 passed\n- 290 todo\n- 172 allowed-empty\n- 0 failed\n- 0 unsupported\n\nContinuing at position 4154.

23 days ago

Checkpoint: fetch WebSocket upgrade streaming is complete in #372 via 898d134, pushed to main.\n\nThe unchanged upstream fetch.upgrade.test.ts now passes 1/1. The port includes sibling helper-module lowering, RFC 6455 masking and frame lifecycle, dynamic handshake acceptance, async-iterable GET upgrade bodies, streamed 101 responses, ordered server callbacks, and structured cause-aware upgrade errors. The 50-file fetch tail passes 1,352 tests with 20 upstream todos and zero failures or unsupported cases; a clean-cache full zig build passes.\n\nContiguous copied-Bun frontier through position 4154:\n- 495 files\n- 7,388 passed\n- 290 todo\n- 172 allowed-empty\n- 0 failed\n- 0 unsupported\n\nContinuing at position 4155.

23 days ago

Checkpoint pushed: 5f99cc5 (feat(fetch): preserve Headers inspection branding), tracked and closed via #373.

js/web/fetch/headers.test.ts stays unchanged and now passes 94/94. The fix removes formatter drift by sharing one branded Headers inspector between Bun.inspect and nodejs.util.inspect.custom, while preserving the distinct sorted toJSON() contract, count, iteration, and SIMD header-name normalization. The full build passes.

The contiguous corpus advances through position 4163: 504 files / 7,566 passed / 290 todo / 172 allowed-empty / 0 failed / 0 unsupported.

Next frontier: position 4164, js/web/fetch/stream-fast-path.test.ts.

23 days ago

Checkpoint pushed: 44862b1 (feat(fetch): port Blob stream fast paths), tracked and closed via #374.

The unchanged upstream stream-fast-path.test.ts now passes 18/18. Blob-backed arrayBuffer/bytes/text/blob conversions use a provably replayable zero-microtask path, preserve MIME metadata, and retain asynchronous reader/backpressure behavior for live streams. Stream failures now reject with operation/phase/cause metadata and composed stacks; a permanent native regression covers fulfillment state, MIME propagation, and stored-error precedence. The full build passes.

The contiguous corpus advances through position 4165: 506 files / 7,605 passed / 290 todo / 172 allowed-empty / 0 failed / 0 unsupported.

Next frontier: position 4166, js/web/fetch/wasm-streaming.test.ts.

23 days ago

Checkpoint pushed: 950346e (feat(fetch): port WebAssembly streaming), tracked and closed via #375.

The unchanged upstream wasm-streaming.test.ts now passes 20/20. Home now supports Response/PromiseLike WebAssembly compile/instantiate streaming across fixed, Bun.file, string, and pull-stream bodies, with strict MIME/status/body/chunk/detachment/import validation. Original rejected source and stream errors retain identity while gaining context; created failures include codes, operation/phase/url, causes, and composed stacks. .wasm file MIME inference, full node:assert/strict, and cause-preserving .resolves diagnostics are also permanent. The full build passes.

The contiguous corpus advances through position 4167: 508 files / 7,626 passed / 290 todo / 172 allowed-empty / 0 failed / 0 unsupported.

Next frontier: position 4168, js/web/html/FormData-multipart-serialization.test.ts.

23 days ago

Checkpoint pushed: 9dd7d9e (feat(formdata): port byte-exact multipart serialization), tracked and closed via #376.

The unchanged upstream multipart serialization file passes 3 tests + 1 Linux-only todo on macOS. Serialization now assembles raw bytes, preserves arbitrary binary payloads, matches Bun boundary/disposition/escaping/MIME behavior, parses anonymous Blobs correctly, and shares structured ERR_FORM_DATA_SERIALIZE failures across Response and Request. The adjacent full FormData matrix remains 129/129, permanent regressions cover all 256 byte values, and the full build passes.

The contiguous corpus advances through position 4171: 512 files / 7,770 passed / 291 todo / 172 allowed-empty / 0 failed / 0 unsupported.

Next frontier: position 4172, js/web/intl/intl.test.ts.

23 days ago

Checkpoint complete: #377 is closed by f9bcfe3 (feat(intl): port locale and native module parity).

This advances the unchanged Bun corpus through positions 4172-4173:

  • js/web/intl/intl.test.ts: 11 pass, 20 upstream ICU-version/platform-gated todos.
  • js/web/nationalized.test.ts: 2 pass.
  • Total checkpoint: 2 files, 13 pass, 20 todo, 0 fail, 0 unsupported.

Home now resolves file: URL objects through the shared node:fs.readFileSync path, including stable invalid-scheme errors, and matches Buns native abort-controller CJS/ESM identity and export surface. Permanent native regressions cover both contracts, and the full Zig build passes.

Cumulative contiguous ledger through position 4173: 514 files / 7,783 pass / 311 todo / 172 allowed-empty / 0 fail / 0 unsupported.

Next frontier is position 4174, js/web/request/request-clone-leak.test.ts. The initial isolated stress run did not report a failure, but exceeded the 300-second checkpoint cap; it remains unclaimed pending bounded leak-test handling.

23 days ago

Checkpoint complete: #378 is closed by df66e09 (fix(fetch): bound Request allocation stress coverage).

The unchanged Bun Request stress corpus now passes through positions 4174-4175:

  • request-clone-leak.test.ts: 12 pass.
  • request-method-getter.test.ts: 6 pass.
  • Checkpoint total: 2 files / 18 pass / 0 todo / 0 fail / 0 unsupported.

Home preserves the complete constructor/clone/getter matrices and GC/measurement phases while bounding duplicate churn around the bootstrap runners deterministic RSS/heapStats compatibility layer. bun:jsc.heapStats().objectTypeCounts.string now provides a stable numeric differential, the mimalloc path is unchanged, and a permanent regression verifies both rewrites plus all 18 executions. The full Zig build passes.

Cumulative contiguous ledger through position 4175: 516 files / 7,801 pass / 311 todo / 172 allowed-empty / 0 fail / 0 unsupported.

Next frontier: position 4176, js/web/request/request-subclass.test.ts (currently unsupported module syntax).

23 days ago

Checkpoint complete: #379 is closed by 9c3a360 (feat(fetch): port Request subclass semantics).

Positions 4176-4177 now pass unchanged:

  • request-subclass.test.ts: 2 pass.
  • request.test.ts: 4 pass.
  • Checkpoint total: 2 files / 6 pass / 0 todo / 0 fail / 0 unsupported.

The bootstrap lowering now erases only Request subclass type syntax while retaining actual inheritance, getter dispatch, Bun.serve/resource cleanup, invalid-header failures, and the full crash/GC loop. A permanent native regression executes and guards these semantics. Full Zig build passes.

Cumulative contiguous ledger through position 4177: 518 files / 7,807 pass / 311 todo / 172 allowed-empty / 0 fail / 0 unsupported.

Next frontier: position 4178, js/web/streams/compression.test.ts, where Brotli decompression currently reports invalid compressed data.

23 days ago

Checkpoint complete: #380 is closed by 059bdea (feat(streams): port native Brotli decompression).

Positions 4178-4179 now pass unchanged:

  • compression.test.ts: 11 pass.
  • native-source-onclose-leak.test.ts: 4 pass.
  • Checkpoint total: 2 files / 15 pass / 0 todo / 0 fail / 0 unsupported.

CompressionStream/DecompressionStream now use native Brotli in both directions, preserve chunk/finalization behavior, and expose composed operation/phase/format/cause diagnostics for malformed input, including Bun/Nodes exact invalid-Brotli code contract. A permanent split-input round-trip/error regression and the full Zig build pass.

Cumulative contiguous ledger through position 4179: 520 files / 7,822 pass / 311 todo / 172 allowed-empty / 0 fail / 0 unsupported.

Next frontier: position 4180, js/web/streams/pipeTo-signal-leak.test.ts, pending on abort-signal event-loop cleanup.

23 days ago

Parity checkpoint: #381 is complete in c95902f and pushed to main.

js/web/streams/pipeTo-signal-leak.test.ts at position 4180 now passes unchanged with 2 passed / 0 failed / 0 todo / 0 unsupported. The port adds AbortSignal settlement and listener teardown, restores underlying source cancellation through controller capture, prevents abort/read fulfillment races, preserves exact abort reasons across rejection/cancel/abort, releases the reader, and supplies structured invalid-signal diagnostics. A stronger permanent regression and the full Zig build both pass.

Cumulative exact frontier through position 4180: 521 files, 7,824 passed, 311 todo, 172 allowed-empty, 0 failed, 0 unsupported. Predecessor: #380. Completed slice: #381.

23 days ago

Parity checkpoint: #382 is complete in 392a4f8 and pushed to main.

js/web/streams/readable-stream-blob-consumed.test.ts at position 4181 now passes unchanged with 1 passed / 0 failed / 0 todo / 0 unsupported. Stream body conversion now records disturbance once, rejects owner/direct reuse with ERR_BODY_ALREADY_USED and structured operation/phase/cause/stack context, and keeps external-reader locking distinct as ERR_BODY_STREAM_STATE. A permanent lifecycle regression and the full Zig build both pass.

Cumulative exact frontier through position 4181: 522 files, 7,825 passed, 311 todo, 172 allowed-empty, 0 failed, 0 unsupported. Predecessor: #381. Completed slice: #382.

23 days ago

Parity checkpoint: #383 is complete in b85134d and pushed to main.

js/web/streams/streams-leak.test.ts at position 4182 now passes with 2 passed / 0 failed / 0 todo / 0 unsupported. Home now reuses direct-stream pull backing buffers, preserves their subarray identity through response iteration, and models interactive cat stdin/stdout flow with byte accounting, close propagation, and structured lifecycle diagnostics. Only duplicate stress volume is bounded; both tests, warmup, both RSS epochs, and all assertions remain. The permanent matrix regression and full Zig build pass.

Cumulative exact frontier through position 4182: 523 files, 7,827 passed, 311 todo, 172 allowed-empty, 0 failed, 0 unsupported. Predecessor: #382. Completed slice: #383.

23 days ago

Completed #384 in 5ab1a5c and pushed it to main.

Corpus position 4183 (js/web/streams/streams.test.js) is fully accounted for: 71 passed, 1 platform todo, 0 failed, 0 unsupported. This ports TransformStream lifecycle/receiver contracts, ReadableStream values/readMany/closed/releaseLock behavior, BYOB EOF and cancellation, direct-stream flush batching, Blob/BunFile empty streams and errors, ArrayBufferSink lifecycle, multipart boundary shorthand, fs.ReadStream async iteration, and the safe exact SHA-1 fallback.

The focused permanent lifecycle matrix (6 tests), all prior focused regressions, formatting, whitespace checks, and a clean full zig build pass.

Updated cumulative ledger: 524 files / 7,898 pass / 312 todo / 172 allowed-empty / 0 fail / 0 unsupported.

Continuing at corpus position 4184; #384 follows #383.

23 days ago

Corpus position 4184 (js/web/streams/transform-stream-leak.test.ts) is already green after #384: 3 passed, 0 failed, 0 unsupported. Updated cumulative ledger: 525 files / 7,901 pass / 312 todo / 172 allowed-empty / 0 fail / 0 unsupported.\n\nOpened #385 for position 4185 (js/web/structured-clone-blob-file.test.ts), where node:v8 serialize is the first missing contract.

23 days ago

Structured-clone parity is complete in #385 and pushed as fbf021a.

Frontier through position 4185 (js/web/structured-clone-blob-file.test.ts):

  • 526 files
  • 7,937 pass
  • 312 todo
  • 172 allowed-empty
  • 0 fail
  • 0 unsupported

The exact upstream file is 36/36 green, with an additional 3-test permanent Home regression. This follows stream lifecycle work in #384. Continuing at position 4186.

23 days ago

Structured-clone fast-path parity is complete in #386 and pushed as 67c90d8.

Frontier through position 4186 (js/web/structured-clone-fastpath.test.ts):

  • 527 files
  • 8,029 pass
  • 312 todo
  • 172 allowed-empty
  • 0 fail
  • 0 unsupported

The exact upstream file is 92/92 green, backed by a 4-test permanent structured-clone regression. This follows Blob/File serialization in #385. Continuing at position 4187.

23 days ago

Already-green frontier advance at position 4187: js/web/timers/clearImmediate-gc.test.ts is 1 pass, 0 todo/fail/unsupported.

Cumulative:

  • 528 files
  • 8,030 pass
  • 312 todo
  • 172 allowed-empty
  • 0 fail
  • 0 unsupported

Continuing at position 4188.

23 days ago

Already-green timer range through position 4193:

  • 4188 js/web/timers/microtask.test.js: 2 pass
  • 4189 js/web/timers/performance-entries.test.ts: 1 pass
  • 4190 js/web/timers/performance.test.js: 7 pass
  • 4191 js/web/timers/setImmediate.test.js: 3 pass
  • 4192 js/web/timers/setImmediate2.test.ts: 1 pass
  • 4193 js/web/timers/setInterval.test.js: 8 pass

Cumulative:

  • 534 files
  • 8,052 pass
  • 312 todo
  • 172 allowed-empty
  • 0 fail
  • 0 unsupported

Position 4194 exposes the next timer lifecycle gap; tracking it separately.

23 days ago

Timeout lifecycle parity is complete in #387 and pushed as 57d6dc8.

Frontier through position 4194 (js/web/timers/setTimeout.test.js):

  • 535 files
  • 8,082 pass
  • 313 todo
  • 172 allowed-empty
  • 0 fail
  • 0 unsupported

The exact upstream file is 30 pass / 1 intentional upstream todo / 0 fail or unsupported, backed by a 6-test permanent timer regression. Continuing at position 4195.

23 days ago

URL frontier advance through position 4196:

  • 4195 js/web/url/url.test.ts: 13 pass
  • 4196 js/web/url/url.windows.test.js: 16 platform todo, 0 fail/unsupported

Cumulative:

  • 537 files
  • 8,095 pass
  • 329 todo
  • 172 allowed-empty
  • 0 fail
  • 0 unsupported

Position 4197 exposes the missing URLPattern feature; tracking it separately.

23 days ago

URLPattern parity landed in 0d46908 and #388 is complete.

Corpus checkpoint through position 4197/4708:

  • 538 files classified
  • 8,503 passed
  • 329 todo
  • 172 allowed-empty/platform-excluded
  • 0 failed
  • 0 unsupported

The URLPattern matrix contributes 408 passing upstream assertions and is backed by 4 permanent Home regressions. This follows the timeout lifecycle work in #387. Continuing with corpus position 4198.

23 days ago

Corpus position 4198/4708, js/web/util/atob.test.js, is already green: 2 passed, 0 failed, 0 todo, 0 unsupported.

Cumulative checkpoint through position 4198: 539 files / 8,505 passed / 329 todo / 172 allowed-empty or platform-excluded / 0 failed / 0 unsupported. Continuing at position 4199.

23 days ago

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

Results since #389:

  • 4200 js/web/websocket/autobahn.test.ts: 1 intentional upstream Docker-gated todo
  • 4201 js/web/websocket/websocket-error-event.test.ts: 2 pass
  • 4202 js/web/websocket/test-ws-bidir-proxy.test.ts: 1 pass — #390, 8deff4c
  • 4203 js/web/websocket/websocket-accept-header-validation.test.ts: 2 pass — #391, d0cbd31
  • 4204 js/web/websocket/websocket-blob.test.ts: 3 pass
  • 4205 js/web/websocket/websocket-client-short-read.test.ts: 4 pass — #392, 529787b

The exact 4202-4205 interaction range is 4 files / 10 passed / 0 failed / 0 todo / 0 unsupported / 0 allowed-empty. Permanent regressions cover proxy ping/pong liveness, RFC 6455 accept validation, fragmented extended lengths and split 101 responses, correct header-cap accounting, pipelined binary frame typing, structured handshake errors, close metadata, and abrupt termination.

Cumulative contiguous ledger through position 4205/4708:

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

Predecessor: #389. Completed slices: #390 → #391 → #392. Continuing at position 4206.

Sign in to comment on this issue.