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

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

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

Current main checkpoint (2026-10-13)

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

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

Historical publication checkpoint (2026-09-20)

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

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

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

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

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

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

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

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

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

Earlier prepared Elysia execution checkpoint

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

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

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

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

API and verification boundary · Complete execution evidence

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

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

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

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

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

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

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

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

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

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

Earlier checkpoints

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

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

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

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

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

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

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

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

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

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

How to run / verify

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

Historical publication checkpoints (through 2026-08-28)

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

A. node:tls socket layer

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

B. Bun Shell ($)

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

C. fetch / HTTP client

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

D. HTTP/2 & HTTP/3

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

E. Deep/unported subsystems

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

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

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

G. Environmental / infra (mostly resolved)

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

Done this session (context)

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

Native isolation checkpoint — 6e092777a

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

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

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

Native fake-clock checkpoint — d0ed7c906

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

Verification:

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

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

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

Native POSIX spawn checkpoint — 6d797186c

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

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

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

Zig 0.18 migration progress for #884: pushed 5d046b50c directly to main, an exact three-file build-subsystem collection/ownership slice.

The direct packages/io shipped/test gate already passes unchanged on both compilers. The newly activated cross-compilation, linker-script, and packaging tests pass 9/9 on pinned Zig 0.17 and Zig 0.18-dev.146 after the migration (283 MB / 248 MB peak). Temporary roots and caches were removed; detailed ownership fixes are recorded on #884.

Build-package Zig 0.18 migration progress: pushed 5fd816740 to origin/main with the explicit-std.Io watcher migration, owned event paths, cache-metadata leak fix, and a shipped-library/test build gate. Both pinned Zig and 0.18.0-dev.146 pass the fresh-cache 15-test gate with no leaks or warnings.

Full evidence and the remaining incremental/cache failures are recorded in #884: /home-lang/home/issues/884#issuecomment-6175456759

Incremental build/cache progress: pushed 35ea544d6 to origin/main. Activating the previously excluded incremental suite exposed 5 failures and 422 allocator leaks; the ownership, I/O lifetime, concurrency, scheduling, and eviction fixes now pass 22/22 with zero leaks on both pinned Zig and 0.18.0-dev.146.

Full diagnosis and fresh-cache evidence: /home-lang/home/issues/884#issuecomment-6175673156

Build migration progress landed on main in e3ed6652a (tracks #884).

The five-file slice makes the real build pipeline, integration scenarios, LTO, and linker declarations compile through the active package test root instead of remaining lazy/unverified. It ports their clocks, filesystem access, process spawning, and output writing to explicit std.Io, while preserving process failure checks and fixing ownership on newly exercised LTO paths.

Fresh guarded verification passed with both Zig 0.18.0-dev.146+35accc06e and pinned Zig 0.17.0-dev.2163+89ff10d56 using the package's identical check test build configuration. Peak process-tree footprints were 1,097 MB and 1,034 MB respectively, with no allocator leak report.

Detailed migration evidence: #884.

Recursive readdir stress work continues in #896: baseline and pending native traversal/queue changes. A same-tree diagnostic confirms large host/runtime timing differences; it is not original-test pass credit. The native rebuild and twelve unchanged pinned directory/filesystem originals are pending. Original iterations/deadlines and the full Bun-suite acceptance requirement remain unchanged.

Recursive readdir checkpoint (2026-10-14): source 26a428426 and 27 Git-verified baseline/build artifacts are on main through e6ee69738. The native batch removes repeated descendant path parsing and parent-path encoding, and repairs queue-allocation error/cleanup behavior. Node integration, Pickier, Zig formatting and diff checks pass. Home compilation and twelve unchanged pinned originals are pending: two native rebuilds were stopped by the resource monitor after repeated kernel-probe deadlines, and a fourth guarded build is queued behind a live Home job. Same-tree 200-traversal timings are diagnostic only, with no original-test pass credit. Original iterations/deadlines and the full Bun-suite/all-platform goal remain unchanged; #896 tracks completion.

Corpus/native build checkpoint (2026-10-14): source a8be1de85 and 23 Git-verified evidence artifacts are on main through cf6d284db. The new full inventory audit passes all 12,996 pinned entries, explicitly reporting three adopted upstream TLS revisions from #710 and four removed failure exclusions. The pinned CLI init original is restored; its Home entry-preservation regression moved to an owned control. All six verifier controls, Pickier and cryptographic fixture checks pass. Recursive walker source 26a428426 now compiles: native build attempt six succeeded 56/56, peak measured tree footprint 5,697 MB. Owned execution controls, post-change timing measurements and twelve unchanged originals remain queued behind a confirmed-live Home suite; no execution pass credit is assigned. Full feature/suite/all-platform acceptance remains open, with readdir acceptance tracked in #896.

Native readdir validation checkpoint (2026-10-14): walker source 26a428426, corpus/control source a8be1de85, and 837 Git-verified execution/diagnostic artifacts are on main through ecd6216cd. Native build 56/56 and all owned ALPN, fetch-timing, init and recursive traversal controls pass. The final 140-file unchanged filesystem/FileHandle batch and every validator pass: 393 cases, 126 process checks, zero failures, 36 original case skips and three complete-file skips. The earlier twelve-file batch’s one synchronous string-result deadline failure remains recorded; a fresh complete-file recheck passes 262 cases with seven skips, and the later wider batch also passes that file. Original iterations/assertions/deadlines remain unchanged. Timing measurements are diagnostic, vary with host/runtime conditions, and are not attributed wholly to the algorithm; installed Bun is not a rebuilt pinned reference. #896 retains robust stress/pinned-reference acceptance. New #897 tracks observed undefined buffer Dirent names and ignored recursive async name encodings. Full feature/suite/all-platform acceptance remains open.

The #897 native directory batch is implemented locally and builds 56/56. Focused Node/Home controls pass buffer names, parent identity, all name encodings and UTF-16 parents, and plain byte arrays are now real Node Buffers. The first wider 140-file batch remains failed: fs.test.ts aborts with an unreachable-code panic and has no completed case report. No passing case credit is assigned to that abort. A suspected shared StringImpl ownership path has been changed to private per-worker copies; the stripped rebuild passes 56/56, and concurrent controls plus the complete unchanged fs.test.ts are queued behind a confirmed-live validation job. A symbols-enabled diagnostic build hit the existing 8 GB ceiling; that failure is retained. #897 carries the detailed progress and #898 records the independent pure-path UTF-16 gap. Main’s prior validated checkpoint remains separate from this pending batch. Original assertions, iterations, deadlines and full-suite/all-platform acceptance remain unchanged.

Native directory encoding checkpoint (2026-10-14): source 68ac671bf through 5e3cdf8c8 and 2,285 Git-verified evidence artifacts are on main through 9f99fd4f8. Native readdir now returns real Buffer Dirent names and plain Buffer arrays, preserves Buffer root/sibling parent identities and root spelling, applies recursive async encodings, and builds encoded parent displays without changing filesystem traversal bytes. Private worker StringImpl copies, GC roots, conversion cleanup, bulk code-unit copies and a bounded ASCII UTF-8 fast path cover ownership and performance. SDK class/global layouts are unchanged. Final build 56/56; Node/Home encoding/concurrency plus traversal controls pass; ABI checks 10/10 with 58 assertions and Pickier pass. The final unchanged 140-file filesystem/FileHandle batch and all validators pass: 393 cases, 126 process checks, zero failures, 36 original case skips and three complete-file skips. Initial compile/control failures, an unreachable-code file abort, diagnostic memory-ceiling failure and later deadline failures remain recorded. Original iterations/assertions/ten-second deadlines are unchanged. #897 stays open for Linux raw-byte, Windows and lifecycle acceptance; APFS rejects the raw invalid-UTF8 fixture with EILSEQ. #898 tracks the independent pure-path UTF-16 gap; #896 retains robust stress/pinned-reference acceptance. The full feature/suite/all-platform objective remains open.

Native path checkpoint: source c9347d9db and 930 Git-verified evidence artifacts are on main through 96ded4f9f. Native UTF-16 path adapters preserve lone/paired surrogates across related operations; native format now follows getter/coercion order, and Windows resolve preserves validation short-circuiting. Build 56/56; 2,601 actual Node comparisons pass. A fresh unchanged 157-file path/filesystem/FileHandle batch has 396 passing cases, 142 successful process checks, zero failures, 37 skipped cases and three skipped files; all report validators pass. Dirent control, ABI checks (10 tests/58 assertions), Pickier and the full 12,996-entry integrity audit pass. Installed Bun 1.4.2 is a separate baseline, not a rebuilt pinned runtime. #898 retains actual Windows and pinned-reference acceptance; six reproduced Unicode casing mismatches move to #899. #897/#896 retain their platform, raw-byte and stress acceptance. The full feature/suite/all-platform objective remains open.

Native Unicode path checkpoint: source c2e235434 and 836 Git-verified evidence artifacts are on main through 6417fa68f. Native Windows comparisons use the engine's full locale-independent lowercase conversion and Node's component algorithm when lowercase changes length, preserving destination spelling and POSIX case sensitivity. Build 56/56; 464 new Node comparisons and all 2,601 code-unit comparisons pass. The fresh unchanged 157-file path/filesystem/FileHandle batch has 396 passing cases, 142 process checks, zero failures, 37 case skips and three skipped files; all validators pass. Dirent control, the 12,996-entry corpus audit, ABI checks and lint pass. The full guard run has 154 passes and one repaired source-provenance assertion; the repaired case passes with 636 assertions. Installed Bun 1.4.2 fails the Unicode control and remains a separate baseline. #899 retains actual Windows/platform acceptance; #898 retains drive-environment and rebuilt pinned-reference acceptance. #66 remains the entire feature/suite/all-platform objective.

Native path format checkpoint: source 6826c3f99 and 841 Git-verified evidence artifacts are on main through ac74dd8cd. Native format now preserves indexed extension reads, strict dot comparison, JavaScript truthiness, empty coercions, root identity, direct base returns and getter/coercion order, with GC roots across callbacks. Build 56/56; all 358 new actual Node comparisons plus the prior 2,601 code-unit and 464 Unicode comparisons pass (3,423 total). A fresh unchanged 157-file batch has 396 passing cases, 142 process checks, zero failures, 37 case skips and three skipped files; all validators pass. Dirent control, ABI (10 tests/58 assertions), Pickier, Zig formatting and the 12,996-entry integrity audit pass. Earlier failures and the separately installed Bun 1.4.2 baseline remain retained. #900/#898/#899 retain actual Windows and rebuilt pinned-reference gates. The next broad audit is the unfinished Bake/HMR graph and its relaxed ClientFile.Packed invariant. The entire #66 feature/suite/all-platform objective remains open.

Native Bake graph/JUnit checkpoint: source d8c890b03 and 945 Git-verified evidence artifacts are on main through 1daa83a11. Bake's exact 32-byte release invariant is restored and compiler-enforced; actual ReleaseFast frontend checking passes, and a 33-byte negative control fails as required. Debug remains 56 bytes with safety checks; layout/240 metadata combinations/source-map ownership controls pass. Native promise callbacks link in filtered roots. JUnit now emits valid XML while preserving exact original identities, fixing describe double escaping; 34 validator controls and the actual XML/journal control pass. Eight unchanged Bake files pass with 73 cases/zero failures/two upstream TODOs. Production/development/HMR controls pass. The fresh 157-file regression has 396 passing cases, 142 process checks, zero failures, 37 case skips and three skipped files; validators, ABI, lint and the 12,996-entry integrity audit pass. Optimized graph execution exceeded the unchanged 8 GB ceiling, and the whole ReleaseFast CLI attempt hit the critical disk floor; neither receives passing credit. #901 retains these runtime/platform gates. The full #66 feature/suite/all-platform objective remains open.

The first retained complete 24-file run finished with 175 pass, 2 fail, 2 TODO. Its journal, JUnit, exact case metadata and source inventory validate without evidence-format errors; the two failures are actual runtime failures, so this is not a passing suite checkpoint.

The failures expose two implementation gaps being repaired together:

• deinitialization.test.ts: native test dispatch changes a spawned fixture's working directory from its requested fixture directory to the corpus project root. The unchanged child asserts its actual working directory before exercising server deinitialization.
• dev/production.test.ts: the ported production source provider obtains Bake's per-thread state but never retrieves its stored source map. The unchanged React error assertion receives generated minified source instead of its original throw new Error line. This concerns the source-map behavior previously tracked in #563.

Both repairs have targeted regression controls. The rebuild and a fresh complete suite run remain pending. The original failed run is retained, and the two upstream TODOs remain separate from executed-case pass credit.

Completed the native Bake corpus checkpoint in ccecdcf9b, with 1,185 Git-verified evidence artifacts.

• All 24 unchanged pinned Bake files: 177 passing cases, zero failures, zero skips, two original upstream TODOs. Native Home and the independent validator exit zero; source membership, exact identities, terminal counters and complete streams validate.
• Genuine base/React native locks replace the empty cache placeholder. Home's frozen installs preserve both lockfiles byte-for-byte; a manifest mismatch is rejected without changing its lock.
• The suite's outer capture budget derives from its 24 distinct sources. Original assertions, fixtures, workloads and per-test deadlines remain unchanged.
• Native test dispatch retains a spawned fixture's requested working directory; the unchanged deinitialization child passes nine tests.
• Production source providers retrieve actual stored map JSON, restoring original React source lines in errors. The expanded production control verifies the original line and file location; this follows the behavior tracked in #563.
• --changed dependency graphs compare canonical file identities, handling Git/caller path aliases without changing execution/report paths. The full coordinator controls, including an explicit symlink case, pass with 29 complete journals. Development/HMR and production controls pass.
• Fresh 157-file regression: 396 passing cases, 142 passing process checks, zero failures. Its 37 case skips and three file skips retain zero pass credit. Validator, ABI, lint, formatting and the 12,996-entry corpus integrity checks pass.

The initial full run's 175 pass / 2 fail / 2 TODO and intermediate control failures remain in the evidence history. Committed raw Git blobs were independently decompressed and hash-checked against the manifest, including exact committed implementation hashes.

This completes #902's native runner/execution tranche. #901 retains optimized native execution and platform gates; #564 retains the Linux Bake TODO coverage. The two upstream TODOs, all-platform verification and the full #66 Bun feature/test-suite objective remain open.

Two direct-main runtime parity commits were published under Glenn's identity, without coauthors:

• 9839b10338c9233bded21a45e88c7973c81a17ec — fix(build): restore native runtime binding builds (#66) (exactly three files). Threads the pinned WebKit root into Home's owned BunProcess.cpp rebuild so HomeICUBinding.cpp resolves the ABI-matched ICU headers, and removes an invalid Bun-only debug allocator initialization from the standalone Home runtime entrypoint. Fresh isolated-cache native binding build: 50/50; build-support tests: 5/5 on pinned Zig 0.17 and Zig 0.18.0-dev.146.
• 5c2404bb280f55c195b2db366b7f57609022773f — fix(node): expose native Temporal capability (#894) (exactly three files). Reports Temporal capability from the actual JSC global and ports Node main's common-harness CJS/ESM hasTemporal exports. Formatter, Pickier, exact disabled/enabled expression controls, and CJS/ESM export controls passed.

The unchanged positive Temporal stat original is not claimed as passing: guarded full-runtime builds exceeded the fixed 3,840 MB ceiling by small margins and were terminated without raising the limit. #894 remains open for that native execution. Full Bun-suite and all-platform acceptance remain open here.

Package-manager progress: #903 is implemented on main in 4725e70. The in-memory registry solver now includes selected-version transitive dependencies and backtracks on later incompatibilities, with deterministic output and failure-path ownership tests. Standalone and top-level package tests pass 35/35 on Zig 0.17 and 0.18 in Debug and ReleaseFast. This is one scoped package feature, not a claim of complete Bun parity; the remaining suite/platform work in this issue stays open.

Scoped build-system progress only: #904 is fixed on main in 4ef6f1f, with 33/33 build-package tests on Zig 0.17 and Zig 0.18 in Debug/ReleaseFast. This prevents cache-key generation from mutating dependency hashes above 256 and is not Bun suite pass credit. A fresh native build for the #894 Temporal original stopped at the unchanged 3840 MB guard (exit 125), so that original remains unverified; no all-suite/all-platform claim.

Progress checkpoint: #905 was fixed by a441cc5, pushed directly to origin/main under glennmichael123 and closed. The TS emit cache no longer aliases distinct source/config pairs; a versioned length-framed digest makes old disk entries unreachable. Public cache regressions, full pinned driver (214/214) and Program (321/321) suites, focused Zig 0.18 driver (4/4), and standalone shipped-library/test builds on Zig 0.17 and 0.18 in Debug/ReleaseFast (18/18 each) passed under the unchanged 3,840 MB guard. This is a scoped correctness and #884 build-coverage improvement, not a claim that the Bun corpus or full parity is complete.

Progress checkpoint: #906 was fixed by 093ff6a, pushed directly to origin/main as glennmichael123 and closed. TS cache replacement is now allocation-atomic: a failed replacement retains the prior output and diagnostics; failed new insertions leak no entry/key/value. The retained failing baseline had one failed fault test and four leaks. The fixed package passes 20/20 on Zig 0.17 and 0.18 in Debug/ReleaseFast; full pinned driver 214/214 and Program 321/321 pass, plus focused Zig 0.18 driver 4/4, all under the unchanged 3,840 MB guard. This is a scoped correctness/build-coverage result, not a Bun-suite or full parity pass.

Progress on Chris’s corpus issue #876: a845b8a is pushed to origin/main under glennmichael123. It fixes suite-inventory ownership on read/allocation failure and adds direct fault-injection coverage; the pure planner passes 5/5 on Zig 0.17 and 0.18 in Debug/ReleaseFast. The full home_test build attempt was stopped by the unchanged 3,840 MB guard at 4,016 MB, even with JSC disabled. No native corpus or full-suite pass is claimed, and #876 stays open for its remaining CLI, mixed-root and runtime verification.

TypeScript conformance input-fidelity checkpoint: df55762 is on origin/main under glennmichael123. Selected fixture-variant compiler options no longer depend on whether an expected .errors.txt or .js baseline exists. Red-to-green four-variant regression control passes on Zig 0.17 and 0.18; focused neighboring controls pass. This is only one #841 slice, not full TS corpus or Bun parity. The broader corpus-input filter timed out without a terminal aggregate. Details and retained limitations: #841 and docs/docs/bun-port-evidence/2026-10-16-ts-baseline-input-invariance/.

Conformance honesty update: 8ad7879 is on origin/main under glennmichael123. Selected TypeScript fixture I/O/OOM/short-read errors now fail loading rather than disappearing from the corpus aggregate; comparison mode no longer toggles the ES5 option diagnostic flag. Focused 0.17/0.18 controls pass under 3,840 MB, with retained limits in #841 and its evidence. Upstream ES5 fixtures remain skipped, the full corpus is unverified, and this is not full Bun parity.

Input-fidelity update: e9f03c1 is on origin/main under glennmichael123. Explicit TypeScript conformance baseline roots that are files/inaccessible no longer silently become missing expected baselines; a valid empty root still permits genuinely absent case baselines. Dual-toolchain focused controls pass under the 3,840 MB guard. This remains a partial #841 correction; full corpus and Bun parity are not claimed. Details: #841 and docs/docs/bun-port-evidence/2026-10-16-ts-baseline-input-invariance/.

Input-fidelity checkpoint dccf0b7 is on origin/main under glennmichael123: TypeScript conformance baselines are opened relative to held root handles, so pathname replacement cannot redirect selected expectations on the verified macOS control; exact reads reject short files. Focused 0.17/0.18 controls pass under 3,840 MB. The five-case exact survey timed out at 240 seconds without a final aggregate and earns no passing-case credit. Full corpus, Windows and Bun parity remain open; details in #841 and docs/docs/bun-port-evidence/2026-10-17-ts-baseline-handles/.

TypeScript conformance progress via #841: 1b07917 is pushed to main under glennmichael123, fixing case-insensitive // @fileName: virtual fixture handling. The pinned ts-expect-error-js exact baseline now passes 1/1 on Zig 0.17 and 0.18 with a 3840 MB guard. Evidence: docs/docs/bun-port-evidence/2026-10-17-ts-virtual-filename-case/README.md. The exact program path takes about two minutes for this one fixture; the prior five-case window timed out and is not credited. Full corpus/Bun parity remains open.

Guarded follow-up after 1b07917: the exact ts-expect-error-js fixture still passes 1/1 (cached Zig 0.17 executable, peak 349 MB), but two live five-second samples locate its about-two-minute runtime under Program.loadImportClosure -> compileAll -> Checker.checkInterfaceDecl -> generic lowering/substitution. The next single-fixture exact window hit 240 seconds without a terminal aggregate, so it is not credited. Tracked separately in #908 and related to #842. Also, #884 now records 8/8 real packages/io tests on both Zig 0.17 and 0.18; that is a narrow migration control, not full parity.

TypeScript exact-corpus update: a guarded six-variant control has four passes, one upstream skip and one failure (conditionalTypes1). #909 now tracks the shared structural-type/alias-metadata ownership defect; two seemingly simple display refreshes were rejected because they suppress a genuine TS2540 readonly diagnostic. No parity gain, code commit or full-suite pass is claimed. Direct main remains in sync with origin/main after fetch; no rebase was required.

Verified main checkpoint: https://github.com/home-lang/home/commit/0f965b757bd9eb243c596a01f0e850b909062777 fixes concrete-receiver reads through keyof-constrained type parameters, with a negative TS2536 control (not diagnostic suppression). Exact keyofAndIndexedAccess now passes; the 13-case neighboring window is 12 pass / 1 fail, with keyofAndIndexedAccess2 still failing at line 121. Checker 4650/4650 and Program 321/321 pass under the 3840 MB guard; focused Zig 0.18 also passes. Evidence: https://github.com/home-lang/home/tree/0f965b757bd9eb243c596a01f0e850b909062777/docs/docs/bun-port-evidence/2026-10-17-ts-keyof-concrete-index. This is one TypeScript conformance improvement only, not a full TypeScript or Bun-suite completion claim. #832 and #909 remain open.

TypeScript parity progress on origin/main: 4751ce3 (see #832). The generic indexed-access write relation now follows TypeScript by allowing numeric index signatures while still rejecting unsafe generic string-index writes. The previously remaining keyofAndIndexedAccess2.ts extra TS2345 is gone; the unchanged 13-case neighboring exact window is now 13/13. Unfiltered checker 4,651/4,651 and Program 321/321 passed under the 3,840 MB guard. Details and immutable fixture/baseline hashes: docs/docs/bun-port-evidence/2026-10-17-ts-generic-numeric-index-write/README.md. This is scoped progress, not a claim that the full TypeScript or Bun corpus passes.

Zig 0.18/source-coverage checkpoint: 1e7655c landed directly on main under #884. The storage memory and S3 driver roots are now exercised in the actual standalone package graph; 10 distinct tests ran as 16 executions across three roots on both Zig 0.17 and 0.18, Debug and ReleaseFast, with all runs passing. Memory directory deletion now preserves same-prefix siblings and handles 1,025 children. The local filesystem storage driver remains unported to Zig 0.18 and receives no passing credit. This does not establish the full Bun corpus, runtime or all-platform goal; details and measured limits are on #884.

Zig 0.18/storage checkpoint: 8169786 is on origin/main under #884. The local filesystem driver and upload path now compile and pass the same native Debug/ReleaseFast test graph under Zig 0.17 and 0.18: 17 distinct tests, 68 executions across four roots. Linux/Windows cross-target checks compile, but no runtime parity is claimed there. Symlink-safe path traversal and Windows visibility semantics remain open. Details: /home-lang/home/issues/884#issuecomment-6222271395 . This does not establish complete Bun parity.

Zig 0.18 readiness checkpoint (not Bun parity credit): 2f71514 is on origin/main under glennmichael123 with no coauthors. It migrates the separately exported Basics fs utility to std.Io and adds real tests; both pinned Zig 0.17 and Zig 0.18 passed 3/3 tests in Debug and ReleaseFast under the 3,840 MB process guard. See #884 for exact evidence and the still-failing broader basics.zig aggregator. This does not change the open Bun corpus count or establish full 0.18 compatibility.

Compatibility checkpoint, not Bun-suite credit: 0023559 is verified on origin/main under glennmichael123 with no coauthors. The Basics JSON utility now passes 4/4 dedicated tests on both Zig 0.17 and 0.18 in Debug and ReleaseFast; red-before/green-after controls cover escaped object keys and duplicate-key allocation ownership. See #884 for the exact command/evidence and remaining basics.zig aggregate failures. Full Bun parity and the 0.18 migration remain open.

Zig 0.18 readiness checkpoint only: 05320ff is verified on origin/main under glennmichael123 with no coauthors. Temporal clock/TZ calls now compile under both compiler pins; its 96 original tests pass in native Debug and ReleaseFast on each, and the uncached libc-linked TZ target passes 2/2 with explicit override and empty fallback. Linux/Windows checks were compile-only. See #884 for the exact matrix. This does not change Bun corpus passing credit or complete the aggregate Basics/0.18 migration.

Zig 0.18 migration progress (tracked in #884): pushed 0a1b5a1 to main as glennmichael123. Basics public time helpers now use std.Io clocks/sleep, include explicit-I/O variants, and have a hosted aggregate test target. Zig 0.18.0-dev.146 and pinned 0.17 each passed 108/108 tests in Debug and ReleaseFast; Linux/Windows compile-only checks passed on both. Remaining work is real: the freestanding Basics root is blocked in std.Io.Threaded, and other lazy Basics exports still need ports. Details: #884.

Another issue-linked Zig 0.18 migration slice is on main: a8bfcf0, three files, authored/committed as glennmichael123 with no coauthors. Basics mapped-memory protection now uses the typed POSIX flags and reports checked OS errors; 4/4 new native tests pass on Zig 0.17 and 0.18 in Debug/ReleaseFast, with Linux GNU/musl compile-only checks. The 108/108 Basics aggregate test also remains green on Zig 0.18. Details and remaining platform/CI limits are in #884. This does not close the full Bun-port or all-platform acceptance.

Pushed issue-linked three-file commit 3686b69 directly to main as glennmichael123, no coauthors. Basics process execution now uses explicit std.Io and drains both output pipes, fixing a Zig 0.18 compile failure and the large dual-output deadlock risk. Four native tests pass on pinned Zig 0.17 and Zig 0.18 in Debug/ReleaseFast; the Basics aggregate remains 108/108. Linux/Windows checks were compile-only, and other process APIs remain unported. Detailed scope: #884. Full Bun parity remains open.

Pushed issue-linked three-file commit c8ad5c9 to origin/main as glennmichael123 with no coauthors. Basics execWithInput now feeds nonempty child stdin concurrently with bounded dual-output capture; empty stdin works without concurrency, and unavailable concurrency reports an error rather than hanging. Combined process tests pass 9/9 on pinned Zig 0.17 and Zig 0.18 in Debug/ReleaseFast; Basics aggregate is 108/108 on Zig 0.18. Cross-platform checks are compile-only. Remaining process APIs and the full Bun/CI parity objective are still open; details in #884.

Zig 0.18 compatibility progress tracked in #884: pushed 6d6b611 to origin/main as glennmichael123, porting Basics SpawnedProcess/ProcessBuilder to std.process.spawn and std.Io, with five lifecycle tests. The combined process suite passes 14/14 on Zig 0.17 and 0.18 in Debug and ReleaseFast. This is build/migration progress, not a claim of additional Bun corpus parity or full-suite success. Details and remaining process gaps: #884.

Pushed process-pipeline migration d373a32 to origin/main as glennmichael123 (details: #884). The Basics pipeline now streams between live child processes without the old pipe-capacity deadlock, preserves the last stage status, and cleans up on output-limit failure. The process test group passes 19/19 on Zig 0.17 and 0.18 in Debug and ReleaseFast under the 3,840 MB guard. This is migration/test coverage, not a claim that the Bun corpus or full #66 feature set is passing.

Build/migration checkpoint: pushed a4ee192 to origin/main under glennmichael123 (details in #884). Basics process helpers now use explicit Zig std.Io/environment/argument snapshots with owned copies and allocation-failure cleanup; combined process tests pass 24/24 on Zig 0.17 and 0.18 in Debug and ReleaseFast under the 3,840 MB guard. This does not establish full Bun corpus parity, full native release compilation, or other-platform runtime behavior; #66 remains open.

Progress: 480af47 is on main and advances the Zig 0.18 Basics process migration tracked in #884. It fixes host-specific signal numbers, child-handle semantics on Windows, and std.Io sleep. The macOS basics_process group passed 28 tests (1 Windows-only skip) in Debug/ReleaseFast on Zig 0.17 and 0.18; Linux/Windows were compile-checked only. This is infrastructure progress, not a claim that Bun corpus parity or #66 is complete. Details: /home-lang/home/issues/884#issuecomment-6268653107.

Progress linked to #884: 1b5a6dc9b is now on main, migrating the Basics filesystem facade to Zig std.Io with a real-file regression test. Targeted facade tests pass 2/2 on Zig 0.17/0.18 in Debug and ReleaseFast; Basics core remains 108/108. This is a scoped portability step, not a claim that the Bun corpus is fully passing; broader parity work remains open.

Further #884 portability progress: afadba7f4 is on main. Image async-result waiting now uses explicit std.Io and atomic release/acquire publication instead of Zig APIs removed in 0.18. The registered image suite passes 97/97 on Zig 0.17/0.18 in Debug/ReleaseFast. This is a scoped migration result, not a full Bun-corpus parity claim; #66 remains open.

Scoped portability progress linked to #884: b6b62e886 migrated Home’s file package to std.Io and put its previously unregistered real-file tests into the build graph. The 10 package tests pass on Zig 0.17/0.18 in Debug and ReleaseFast; this does not establish Bun corpus parity or all-platform runtime coverage. #66 remains open.

Scoped loader/portability progress via #884: 5f700aa68 is on main. The previously uncompiled real ModuleLoader now has five temporary-directory tests passing on Zig 0.17/0.18 in Debug/ReleaseFast, including owned AST source, visibility, size-limit and parse-failure cleanup. Relative imports and full Bun corpus parity remain incomplete; this is not a whole-suite pass.

Progress: ca881af fixes module import path ownership and cache identity (tracked in closed #920, related to #884). Real two-root module tests are 6/6 on Zig 0.17/0.18 Debug and ReleaseFast under the 3,840 MB guard. Windows/Linux runtime parity and the broader Bun suite remain unverified; this does not claim full #66 completion.

Module-loader follow-up 5fa14ef restores first-load bare-name cache behavior after source removal without duplicating canonical AST ownership (#920). Real regression was red before/final 7/7 tests are green on Zig 0.17/0.18 Debug and ReleaseFast under the 3,840 MB guard. This is a scoped module correctness fix, not a full Bun-suite or cross-platform parity claim.