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.

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.

Inspector realm follow-up: evidence c8c0db677 confirms Node enumerates real named VM contexts/origins and evaluates through contextId, while verified Home emits only its owner and fails the named-realm assertion. Pinned JSC owns one global per runtime controller and rejects execution-context IDs. Native weak realm metadata, original-order name/origin capture, owner-loop retirement and per-realm controller/object routing are drafted on recovery source a7b7b86ab, excluded from main. The initial helper namespace compile failure and repaired source are preserved; repair builds were refused below disk admission. No new runtime pass credit. Remote-object arguments/groups, controller roots and realm/owner teardown require implementation and tests. Main runtime remains at the verified profiler-sharing checkpoint. #428/#66/#885/#886 stay open.

Inspector realm lifecycle/routing follow-up: evidence 5c00c7ef6 preserves recovery source 753992ce5: identity-checked deferred realm retirement, owner registry cleanup, nested object-ID argument unwrapping, object-group forwarding, suppression of internal responses, explicit empty names and owner-context evaluation dispatch. Prepared metadata/evaluation/object/getter controls remain unexecuted against a completed repaired executable. Three admission refusals and one admitted build stop at 427 MB free (512 MB floor) retain failure status; the supervisor stopped an escaped compiler child. No new runtime pass credit; source stays excluded from main. Native controller roots, object/argument/group/exception schemas, async commands, retirement/worker teardown and all regression/ABI proof remain required. Main runtime remains the verified profiler-sharing checkpoint; #428/#66/#885/#886 remain open.

Inspector realm build follow-up: evidence 78b31c237 preserves recovery source b0c7b30b4, with common native execution-context IDs and repaired JSON Ref<value> routing access. Initial native build reached 50/56 steps and failed only on the two corrected Ref dereferences. The repaired admitted build stopped at the disk guard: 509 MB free versus 512 MB critical floor. More than 6 GiB old duplicate native objects were removed, preserving newest/active/protected outputs; cache manifests were preserved and invalidated normally. Controls remain unexecuted against a completed repaired executable, with zero new runtime pass credit. Shared-volume exhaustion has repeated across three consecutive realm-work turns and blocks validation until stable build headroom exists. Main retains the verified profiler-sharing runtime; recovery realm source remains excluded. Native controller roots, all protocol/lifecycle/worker schedules and complete original/native/ABI/all-platform proof remain required. #428/#66/#885/#886 remain open.

TypeScript/Bun parity progress landed on main in c20152cff, tracked in #846.

Home now preserves primitive mutable/readonly array JSDoc types from checked JavaScript imports across declarations, function signatures, and constructor-assigned fields, including nested T[], Array<T>, Array.<T>, and ReadonlyArray<T> forms. Unsupported compound leaves remain conservative rather than being guessed.

Validated with Program 276/276 under both the pinned compiler and Zig 0.18.0-dev.146+35accc06e, checker 4589/4589, driver 207/207, stream integration 10/10, a successful stripped ReleaseSafe home-tsc build, and a TypeScript differential fixture matching the four expected primary diagnostic codes/locations with no false TS2339.

#846 remains open for the remaining admitted-JavaScript shapes (unions/intersections, object expressions, generic signatures, rest parameters, and related cases).

Build/parity progress landed on main in ec5e07048, tracked under #884.

The public FFI module now owns its libc requirement instead of depending on test/example roots to compensate. The standalone package graph compiles independently of unrelated basics sources, its public C aliases are restored, and CAllocator.resize no longer loses a relocated realloc result.

Verified with top-level 6/6 and standalone 38/38 tests under both pinned Zig and Zig 0.18.0-dev.146, 38/38 standalone ReleaseFast tests under both, real math-consumer execution under both, and x86_64-linux Debug/ReleaseFast cross-linking under both. The Linux checks are compile/link evidence only, not runtime execution.

Zig-master compatibility progress: pushed c6e950e04 to origin/main, migrating the five-file packages/session slice to std.Io while preserving fallible secure-random error propagation. It also updates the ChaCha20-Poly1305 namespace, activates the previously undiscovered driver tests, adds real file round-trip coverage, and verifies tampered-cookie rejection plus cleanup.

Validated 6/6 in Debug and ReleaseFast on both Zig 0.18.0-dev.146 and the pinned Zig 0.17.0-dev.2163, plus x86_64-linux compile-only checks on both. Detailed record: /home-lang/home/issues/884#issuecomment-6145661082

Zig-master compatibility progress: pushed 5bb45b03f to origin/main, migrating syslog authentication/encryption runtime services to std.Io with secure-random failures preserved and propagated. The slice also replaces removed fixed-buffer streams and activates previously undiscovered auth/encryption tests.

Validated 9/9 in Debug and ReleaseFast on both Zig 0.18.0-dev.146 and pinned Zig 0.17.0-dev.2163, plus x86_64-linux compile-only on both. Details: /home-lang/home/issues/884#issuecomment-6145789570

Zig-master compatibility progress: pushed 7c11db726 to origin/main, completing syslog clock/sleep/mutex/atomic migration and activating the full access/rate-limit/remote test surface. The package now runs 18/18 rather than the previous root-only 2/2.

Validated Debug and ReleaseFast on both Zig 0.18.0-dev.146 and pinned Zig 0.17.0-dev.2163, plus x86_64-linux compile-only on both. Details: /home-lang/home/issues/884#issuecomment-6145858963

Zig-master compatibility progress: pushed 05cc320a8 to origin/main, migrating coredump metadata/key clocks and cryptographic key/ID/nonce generation to std.Io while preserving all fallible secure-random checks. Root coverage increased from 2 to 10 executed tests.

Validated Debug and ReleaseFast on both Zig 0.18.0-dev.146 and pinned Zig 0.17.0-dev.2163, plus x86_64-linux compile-only on both. Details: /home-lang/home/issues/884#issuecomment-6145961574

Zig-master compatibility progress: pushed a7bbbbe6e to origin/main, fixing the confirmed auth build failure from removed global randomness and migrating JWT clocks plus Argon2 KDF to explicit std.Io. Auth root coverage now executes 12/12 tests.

Validated Debug and ReleaseFast on both Zig 0.18.0-dev.146 and pinned Zig 0.17.0-dev.2163, plus x86_64-linux compile-only on both. Details: /home-lang/home/issues/884#issuecomment-6146055240

Zig-master compatibility progress: pushed 9a9865b0a to origin/main, completing coredump persisted-file migration to std.Io with private permissions, exact positional parsing, checked lengths, and real key/dump/directory round trips. The coredump root now executes 21/21 tests.

Validated Debug and ReleaseFast on both Zig 0.18.0-dev.146 and pinned Zig 0.17.0-dev.2163, plus x86_64-linux compile-only on both. Details: /home-lang/home/issues/884#issuecomment-6146214572

Zig 0.18 audit progress: pushed e94a935 to origin/main and documented details in #884.

Modsign key generation now uses explicit std.Io.randomSecure, keeps the new fallible path, and exposes its key tests at the package root. It passes 6/6 tests in Debug and ReleaseFast under both Zig 0.18.0-dev.146 and pinned Zig 0.17.0-dev.2163, plus aarch64-linux compile-only under both. No cryptographic error check was removed.

Detailed result: /home-lang/home/issues/884#issuecomment-6146354041

Zig 0.18 audit progress: pushed 6c97291 to origin/main and documented the full result in #884.

Modsign now exercises its shipped persistence paths rather than only two in-memory tests: 18/18 pass in Debug and ReleaseFast on Zig 0.18.0-dev.146 and pinned Zig 0.17.0-dev.2163, with aarch64-linux compile-only passing on both. The work fixed explicit std.Io migration plus real semantic defects in PEM decoding, persisted key identity/algorithm recovery, signature digest length, cleanup ownership, and forged signature-length validation. No fallible cryptographic check was removed.

Detailed result: /home-lang/home/issues/884#issuecomment-6146508916

Zig 0.18 audit progress: pushed 38dd474 to origin/main and documented details in #884.

TPM's apparent 2/2 green baseline did not instantiate any submodule tests. The corrected root runs 14/14 in Debug and ReleaseFast on Zig 0.18.0-dev.146 and pinned Zig 0.17.0-dev.2163, with Linux compile-only passing on both. The slice migrated explicit clock/secure-random services, preserved entropy failures, fixed allocator cleanup, and repaired authorization re-keying that previously returned corrupted plaintext for valid credentials.

Detailed result: /home-lang/home/issues/884#issuecomment-6146622732

Zig 0.18 audit progress: pushed 4d9dca2 to origin/main and documented details in #884.

WebSocket's old 1/1 baseline did not instantiate the server, broadcaster, secure masking, or handshake proof paths. The corrected package runs 7/7 in Debug and ReleaseFast on Zig 0.18.0-dev.146 and pinned Zig 0.17.0-dev.2163, with Linux compile-only passing on both. The slice preserves secure-random failure propagation, ports fixed JSON writers, validates both sides of the RFC 6455 handshake, and removes an attacker-controlled fixed-buffer overflow.

Detailed result: /home-lang/home/issues/884#issuecomment-6146772639

Zig 0.18 migration progress: pushed IPv6 protocol services commit add029156 (tracked in #884). It moves clocks and mutexes onto std.Io, replaces predictable DHCPv6 transaction IDs with fallible secure entropy, and keeps entropy failure visible to callers. The expanded suite passes 29/29 in Debug and ReleaseFast on both pinned Zig 0.17 and Zig 0.18-dev.146, plus Linux compile-only on both.

Zig 0.18 migration progress: pushed build compatibility commit 5b36cd07f (tracked in #884). It distinguishes qualified OptimizeMode aliases from Home-owned enum renames, ports kernel buffers/lists to the new allocator and std.Io.Writer APIs, fixes the Multiboot checksum and mixed flag ownership, and exposes the full 29-test IPv6 suite. Debug/ReleaseFast pass on both pinned Zig 0.17 and Zig 0.18-dev.146; Linux compile-only passes on both.

Zig-master parity advanced with two direct-main variadic commits: bee7cb8 and 1b32f76 (tracked in #884).

The package now compiles and runs its complete 25-test Debug/ReleaseFast suite under both pinned Zig 0.17 and Zig 0.18.0-dev.146. Its shipped three-example build is 7/7 on both, and aarch64-linux-gnu ReleaseFast compile-only passes on both. Removed reflection, stream, ArrayList-writer, clock, and mutex APIs were migrated without dropping fallible checks. The logger example also now exercises a real borrowed std.Io writer instead of silently producing no log output.

Full runtime/Bun parity and the remaining repository-wide std.Io migration are still open.

Zig master compatibility progress: pushed cfb9625cb (fix(cloud): migrate request signing to std.Io (#884)) to main.

Cloud request signing now uses injected std.Io, current allocating-writer and hex-format APIs, and leak-free lowercase header emission. The standalone cloud build was also repaired and its test configuration now instantiates SQS/SES/SNS signing paths instead of only four lazy root tests.

Verified Debug/ReleaseFast and shipped-library/test configurations on pinned Zig 0.17 and Zig 0.18.0-dev.146, plus aarch64-linux-gnu ReleaseFast cross-builds. Detailed record: #884.

Pushed cloud Zig-master follow-up ae2ef57dd to main (details in #884).

S3 now uses explicit std.Io for timestamps, current allocating writers for URL construction, and native byte-hex formatting. More importantly, the cloud package's ordinary test step now reaches every runtime service through one public-root artifact: 18/18 tests pass in Debug and ReleaseFast on both pinned Zig 0.17 and Zig 0.18.0-dev.146. Shipped native and aarch64-linux-gnu ReleaseFast builds pass on both compilers.

Pushed Zig-master compatibility commit 9dc2333e0 to main (details in #884).

Modsign's formerly lazy signatureSummary and keyIdHex paths now use current allocating-writer and byte-hex APIs and are covered by exact-output tests. The top-level modsign target is 19/19 in Debug and ReleaseFast on pinned Zig 0.17 and Zig 0.18.0-dev.146; aarch64-linux-gnu ReleaseFast compile-only passes on both.

Zig 0.18 audit progress: database compatibility and hidden-path coverage landed on main in 4127e828c (tracked in #884).

This batch adds the migrations module to the real database test graph, ports it to explicit std.Io time and current collection/writer APIs, fixes query/text ownership, and fixes a real PostgreSQL MD5 authentication truncation bug (35-byte buffer vs the required 36 bytes).

Verified 20/20 tests in Debug and ReleaseFast with both the pinned Zig 0.17 compiler and Zig 0.18.0-dev.146, plus aarch64-linux-gnu ReleaseFast compilation with both. Full details and the classification of rename/API changes vs semantic fixes are in the #884 update.

Zig 0.18 audit progress: 2eb8d04d4 is now on main (details in #884).

The validation package now injects std.Io for timeout clocks and runs 15 real tests instead of an effectively empty test root. Debug/ReleaseFast pass on the pinned and 0.18 compilers, and aarch64 Linux ReleaseFast compile-only passes on both.

The audit also split the much larger compression build/test and std.Io repair into #887 because both its shipped and test graphs currently stop at nonexistent files before compiling any implementation.

Zig-master compatibility progress landed on main in eaf77c012 (fix(runtime): restore no-JSC substrate tests (#884)).

The slice repairs CSS/nesting/Cow tests and supplies the missing no-JSC HTTP server inspector bridge stubs uncovered by the Zig 0.18 audit. Both Zig versions pass formatting and focused pointer tests; the monolithic runtime aggregate compiles beyond the prior failures but is intentionally not reported as fully passing because the 3,840 MB safety guard stopped the build before completion.

Detailed audit and verification remain tracked in #884.

TypeScript/Bun parity progress landed directly on main in 4dc6f9fe7, tracked in #846.

Admitted checked JavaScript owners now preserve JSDoc rest-parameter shape across the Program boundary, including scalar ellipsis, explicit array, and nested array forms. Unsupported forms stay conservative rather than being guessed, and non-rest functions are not made variadic by JSDoc alone.

Verified with the unfiltered Program suite on pinned Zig and Zig 0.18.0-dev.146, the unfiltered checker suite, a stripped ReleaseSafe home-tsc build, and a production differential matching TypeScript's four expected diagnostic codes and locations.

#846 and this umbrella parity issue remain open for the remaining admitted-JavaScript shapes and broader Bun parity work.

Compression parity progress: 3443c2ea5 landed on main for #887. Brotli/LZ4/Snappy now compile and pass all 21 public-root tests on both Home's pinned Zig and Zig 0.18.0-dev.146, in Debug and ReleaseFast; Linux ReleaseFast cross-compilation also passes. The fixes include real LZ4 empty-frame handling and Snappy correctness beyond 64 KiB, not test workarounds.

Tracked follow-up remains in #887: wire the package build to its real public module/tests and finish the gzip/zstd std.Io migration with malformed-input coverage.

Zig-master/compression progress: e0e205d92 landed on main for #887. The compression package now builds/tests the same public module it ships, gzip uses injected std.Io for its clock and stream APIs, zstd uses the new reader/writer APIs, and malformed gzip/zstd frames are rejected by real public API tests.

The identical Debug + ReleaseFast test matrix passes on Zig 0.17.0-dev.2163 and 0.18.0-dev.146; Linux ReleaseFast compile-only passes on both. This follows the earlier core-codec compatibility commit 3443c2ea5.

#887 is complete and ready to close. The compression migration landed as four small direct-to-main commits: 3443c2ea5, e0e205d92, 995b98946, and the wire-compatibility correction 4294a44d9.

Final evidence: 32/32 package tests pass in Debug and ReleaseFast on both Zig 0.17.0-dev.2163 and 0.18.0-dev.146; both test roots compile for x86_64 Linux ReleaseFast on both compilers. Tests now exercise the shipped public module and malformed inputs for all five advertised codecs.

Zig 0.18 / package-reachability progress from #884 landed on main in 3f53e381e and fa1cdf7f9.

The serialization package's old green-looking build graph referenced nonexistent tests/examples. It now compiles the shipped static-library module and runs real public API coverage. MessagePack, Protobuf, CBOR, Avro, and Cap'n Proto compile on pinned Zig and Zig 0.18; native Debug/ReleaseFast coverage is 25/25 on both, and the shipped aarch64-linux-gnu ReleaseFast graph compiles on both.

This also closes malformed-input gaps in MessagePack ownership unwinding and Protobuf field/tag/varint validation. Full Bun parity remains open; this update is a verified supporting package slice, not a claim that #66 is complete.

Supporting Zig-master parity work landed in fc2937a65. The diagnostics colorizer was unreachable from maintained tests and still used removed ambient environment/stderr/fixed-buffer APIs. It now receives explicit std.Io and environment services, is publicly exported, and has deterministic behavior coverage.

Focused results: 13/13 package tests and 2/2 direct colorizer tests across pinned Zig and Zig 0.18 in Debug/ReleaseFast, plus aarch64-linux-gnu ReleaseFast compile-only on both. This is a verified supporting package slice; full Bun parity remains open.

Progress update: fb20db9ac is on main with exact shipped/test graph coverage for the standalone events and realtime libraries.

Both packages now build through supported Zig library APIs and share one configured module between the installed artifact and tests. Realtime also completed its clock/mutex migration to caller-injected std.Io.

Verified on Zig 0.17 and 0.18 in native Debug/ReleaseFast, plus x86_64-linux-gnu ReleaseFast compile-only. Peak guarded footprint remained below 300 MB.

Zig master compatibility / shipped-graph progress: pushed a742b69f6 to main.

The standalone Redis package now injects std.Io through configuration, uses std.Io.net and std.Io.Mutex, compiles its public API through the exact module shipped by the static library, and has explicit recursive RESP parser errors. This also fixed response leaks and validation gaps during AUTH/SELECT.

Verified on Zig 0.17.0-dev.2163 and 0.18.0-dev.146 in Debug and ReleaseFast, including Linux x86_64-gnu ReleaseFast compile checks. All passed under the 3,840 MB guard.

Inspector realm controls (2026-10-13): evidence b3b54f095 records a completed 56/56-step Debug build of recovery source b0c7b30 (peak 5705 MB), four passing Node controls and the passing Home control that enumerates before/after named VM realms with origins and evaluates through their context IDs. The next Home metadata/disable/re-enable control aborts at 0x5. Code inspection found isString on empty metadata lookup values; explicit empty guards are pushed on recovery repair 6dba78586. Repair runtime remains unverified because its build stopped after eight failed memory measurements. Initial measurement failure, successful build/control and abort are preserved separately in 22 verified artifacts. Realm source remains excluded from main; no complete feature/pass credit. Installed investigation binary is recovery output and must not credit restored main without rebuilding. Metadata/object/lifetime/worker/protocol, full native/original/ABI and all-platform proof remain required; #428/#66/#885/#886 stay open.

More Zig-master/shipped-graph progress landed in 60c673b02.

The cache package now ships and tests one exact module graph, with injected std.Io across time, filesystem, Redis networking, and synchronization. The port also preserved and strengthened malformed-input checks: RESP lengths use checked conversions, cache-file key lengths are bounded before allocation, and short positional reads are rejected.

Verified on Zig 0.17.0-dev.2163 and 0.18.0-dev.146 in Debug/ReleaseFast, including x86_64-linux-gnu ReleaseFast compile checks, under the 3,840 MB guard.

Pushed another verified Zig-master/shipped-graph batch in e7cadfd7f.

The mail package now ships/tests one exact module and injects std.Io into its memory transport for mutex and clock operations. Both Zig versions pass Debug and ReleaseFast tests plus Linux ReleaseFast compile checks under the 3,840 MB guard.

Pushed another verified Zig-master/shipped-graph batch in 2d2abd417.

The rate-limit package now ships/tests one exact module and injects std.Io into token-bucket, fixed-window, and sliding-window time/synchronization paths. Both Zig versions pass Debug and ReleaseFast tests plus Linux ReleaseFast compile checks under the 3,840 MB guard.

Pushed another verified Zig-master/shipped-graph batch in 5e058526c.

The logging package now ships/tests one exact module and uses explicit std.Io for console/file output, clocks, rotation, synchronization, and global logger access. Both Zig versions pass Debug and ReleaseFast tests plus Linux ReleaseFast compile checks under the 3,840 MB guard.

Inspector metadata repair (2026-10-13): evidence 2b9c2058c proves a 56/56-step Debug build, four passing Node controls and two passing Home controls: named-realm enumeration/evaluation and unchanged metadata disable/re-enable. The prior absent-metadata crash is repaired. The next two-realm object control aborts at 0x10; crash frames locate unwrapInspectorObjects, where missing objectId leads to a null string-map key after maps are populated. Null-key guards and maintained regressions are pushed on recovery aac562b7c; their normal rebuild is queued behind a confirmed live qualification job. Zero repaired-object or complete-feature credit. #888 now tracks remote objects, nested arguments/groups/errors, controller roots and teardown; #428 remains the inspector parent. Source stays excluded from main pending focused and original/native/ABI verification. #66/#885/#886 remain open.

Recovery follow-up 311f18d42 adds native execution-context parameter validation to the remote-object guard batch. Previously malformed context IDs could fall through to owner evaluation. Supplied string/null/fractional/out-of-range IDs now produce -32602 parameter errors before dispatch; unknown integer identities retain the separate missing-context error. Maintained regressions and an ordinary Node/Home comparison control are prepared, and Pickier reports zero findings.

The normal native build remains queued behind a confirmed live shared qualification run. These changes remain unverified and excluded from main; no new pass credit. Continue with the same queued build, then focused controls and the required original/native/ABI/report batch. Parent tracking: #888 / #428 / #66.

Recovery follow-up 0d4df1f1f drafts actual cross-realm object arguments. Per-realm JSC controllers can issue identical native object IDs, so merely stripping the public realm prefix can select the wrong object. The owned controller registers its actual InjectedScriptManager; argument routing retrieves the real source JSValue with findObjectById and wraps that value in the target injected script. Controller destruction retires the registry entry, with globals protected and GC deferred during transfer. Public SDK/class layouts remain unchanged.

A maintained callFunctionOn assertion requires two realm objects to sum to 83, and a focused Node/Home control additionally checks object-group release. These remain unverified. The current live build captured the preceding null-key/context-ID batch before this bridge was added, so bridge success requires a normal follow-up build rather than attributing the older executable to newer source. Full focused/native/original/ABI proof and controller lifetime work remain under #888 / #428 / #66.

Another bounded Zig-master compatibility batch is on main: 26baac70d migrates all four database network clients to injected std.Io and the current allocator-explicit collection APIs.

Cross-version evidence: declaration-level checks for each client, package Debug/ReleaseFast tests, and x86_64-linux-gnu ReleaseFast package compilation all pass on both Zig 0.17.0-dev.2163+89ff10d56 and 0.18.0-dev.146+35accc06e. The migration preserves hostname resolution and all real wire-format error checks. Peak guarded footprint was 1,080 MB.

Tracked in #855 and #884.

The preserved null-key/context-ID snapshot (311f18d42) has now completed its normal Debug build: 56/56 steps, peak tree footprint 5649 MB. Its generated inspector headers were compared byte-for-byte against that source commit. The focused controls are queued behind a confirmed live shared module-gates run and are pinned to a hash-verified copy of this completed executable, so a later install cannot change the measured baseline.

The follow-up build for cross-realm bridge source 0d4df1f1f is queued separately under the same resource guard. There is still no new runtime pass credit for either the null-key/parameter batch or the bridge. The earlier metadata passes and object abort remain separately retained. Tracking: #888 / #428 / #66.

Database package build/test parity is now on main in 6aac8dd77, following the network-client migration in 26baac70d.

The shipped static library and all public database modules now compile in the same check graph with matching SQLite/libc configuration. ORM and typed-ORM writer, allocator, reflection, and QueryBuilder drift were fixed and covered with concrete tests. The complete Debug/ReleaseFast/native/Linux matrix passes on both the pinned Zig 0.17 compiler and Zig 0.18 dev. Peak guarded footprint was 1,129 MB.

Tracked in #855 and #884.

The initial cross-realm control assumed Runtime.callFunctionOn accepts an object handle from another execution context. Node v26.10.0 rejected that ordinary request with inspector error -32000: Argument should belong to the same JavaScript world as target object. The control stopped before running Home, so its exit does not establish a Home runtime failure.

The expectation is corrected to require that rejection and to retain checks for separate realm object handles, group release, and usable VM contexts after session disconnect. The draft bridge snapshot 0d4df1f1f3abaf8a5693cabd10b74566eb8cad3c therefore does not establish the intended compatibility behavior; its active build will be retained as evidence, then routing will reject foreign-world arguments instead of transferring objects. The completed null-key/context-ID build remains pinned for its own controls.

Realm routing and lifetime acceptance remain open in #888; this does not establish Bun-suite parity.

Pushed 59dea25b6 to main with another bounded, dual-Zig compatibility batch.

The validation, queue, and scheduler standalone builds now compile installed libraries and tests from the same module graph. Queue also received two real lifetime fixes discovered by the stronger graph: owned map keys and a non-dangling default worker queue selection.

Verification passed on Zig 0.17 and current 0.18-dev for Debug/ReleaseFast host tests and Linux ReleaseFast cross-checks. This improves the reliability of future Bun-parity runs by ensuring green package tests exercise the configuration we actually ship.

The draft bridge build completed normally: 56/56 steps, peak process-tree footprint 5633 MB. Its snapshot remains 0d4df1f1f; this is compilation evidence only.

Corrected reference controls all pass on Node (six controls, including foreign-world argument rejection and same-world success). Against the pinned 311f18d42 null-key/context-ID executable, Home passes realm enumeration/evaluation and metadata disable/re-enable. The ordinary object control now exits 1 with a JavaScript TypeError because the property response lacks the CDP result array; the prior native abort is not reproduced. Later Home controls did not run after that failure.

The pinned SDK declares JSC Runtime.getProperties output as properties. Recovery 6e08014c7 adds request-method-aware translation to CDP result, rejects foreign-world object arguments in owner/realm directions, removes the incorrect object-transfer bridge, and tests same-world success. Its normal rebuild is queued; a raw response diagnostic is queued separately. No new runtime success is claimed for this source.

Raw build/control logs and input hashes remain in zig-out/inspector-metadata-repair-2026-10-13. Realm lifetime acceptance in #888, inspector acceptance in #428, and full Bun parity in #66 remain open.

Published the completed inspector build/control checkpoint on main in 2bd4f8c9c. The manifest preserves 30 raw artifacts, verified by decompression/SHA-256 replay. Documentation paths passed (269 files).

Two normal Debug builds completed 56/56 steps. Corrected Node controls: six passed. Pinned null-key Home controls: two passed, one failed with missing CDP property array, later controls not run. The prior native object abort did not recur in that control. The earlier incorrect foreign-world success expectation is preserved beside the corrected rejection/same-world control.

Repair 6e08014c7 remains separate from main runtime source pending its queued normal rebuild and runtime checks. Its raw-response diagnostic and rebuild are confirmed live behind another bounded validation job. #888 realm routing/lifetime, #428 inspector acceptance, and #66 full parity remain incomplete.

Pushed 565c1fbfa to main with another bounded dual-Zig shipped/test parity batch.

auth, config, and i18n now test the same modules they ship. i18n parameter substitution also uses the current allocator-explicit collection API and retains generated translations under Translator ownership instead of leaking them.

All Debug/ReleaseFast host tests and Linux ReleaseFast cross-checks passed on Zig 0.17 and 0.18-dev. This strengthens the package-level foundation used by the broader Bun parity work; it does not claim the remaining corpus complete.

Pushed 84ae6fd71 to main: inline, intrinsics, and volatile now test the same reusable modules they ship.

The complete dual-Zig Debug/ReleaseFast/Linux-cross matrix passed under the bounded supervisor. This improves the reliability of low-level runtime and compiler building blocks used by the broader Bun parity effort; no corpus-completion claim is made.