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.

Advanced the copied Bun corpus through position 3979 via #237 in 6d7e83e6479d97f0c6ce56835ddd7a9fc73b9ff3.

js/third_party/grpc-js/test-end-to-end.test.ts now loads cleanly with its intentional upstream state of 0 passed, 1 todo, 0 failed, 0 unsupported. The underlying skipped behavior is nevertheless covered by an active Home regression for certificate-provider credentials, provider lifecycle cleanup, and the four-argument unary overload. The file is pinned permanently.

Updated cumulative checkpoint: 321 files, 2,650 passed, 209 todo, 0 failed, 0 unsupported, 171 allowed-empty.

Next frontier: copied-corpus position 3980.

Advanced the copied Bun corpus through position 3980 via #238 in 0b95785d313dc0dfe69ef6861d810d4497112b57.

js/third_party/grpc-js/test-global-subchannel-pool.test.ts now passes 3/3 with independent client readiness/close ownership, an operational surviving client, idempotent cleanup, and target-aware readiness failures. The file is pinned in the permanent third-party suite.

Updated cumulative checkpoint: 322 files, 2,653 passed, 209 todo, 0 failed, 0 unsupported, 171 allowed-empty.

Next frontier: copied-corpus position 3981.

Ported Bun corpus position 3981, js/third_party/grpc-js/test-idle-timer.test.ts, in a46582776 (tracked in #239).

This adds a shared gRPC connectivity lifecycle with client/server idle policies, the required one-second client timeout floor, reconnection after IDLE, Unix-domain-socket target lookup, and deadline-bounded connectivity watchers. Watcher failures preserve their root cause and append actionable channel-operation, target, and source-module stack frames.

Verification:

• focused file: 8 passed, 0 failed, 0 todo, 0 unsupported
• permanent gRPC diagnostics: 8 passed
• SQL adapter and permanent third-party gates: passed
• formatting/diff checks: passed

Cumulative through position 3981: 323 files, 2,661 passed, 209 todo, 0 failed, 0 unsupported, 171 allowed-empty.

Next frontier: position 3982.

Ported Bun corpus position 3982, js/third_party/grpc-js/test-local-subchannel-pool.test.ts, in 41dd0e57e (tracked in #240).

The compatibility layer now models the option's real ownership semantics: local clients receive isolated pool records, global clients share target-scoped records with reference counts, and closing one client cannot invalidate another. Pool invariant errors preserve their causes and include the release operation, target, and source module in the stack.

Verification:

• focused file: 1 passed, 0 failed, 0 todo, 0 unsupported
• permanent gRPC diagnostics: 9 passed
• SQL adapter and permanent third-party gates: passed
• formatting/diff checks: passed

Cumulative through position 3982: 324 files, 2,662 passed, 209 todo, 0 failed, 0 unsupported, 171 allowed-empty.

Next frontier: position 3983.

Ported Bun corpus position 3983, js/third_party/grpc-js/test-logging.test.ts, in 9810ff913 (tracked in #241).

Home now exposes the gRPC internal logging module and public aliases with shared logger state and DEBUG/INFO/ERROR/NONE severity gating. Failures thrown by custom loggers retain their causes and gain logging-operation, severity, and source-module stack frames.

Verification:

• focused file: 2 passed, 0 failed, 0 todo, 0 unsupported
• permanent gRPC diagnostics: 10 passed
• SQL adapter and permanent third-party gates: passed
• formatting/diff checks: passed

Cumulative through position 3983: 325 files, 2,664 passed, 209 todo, 0 failed, 0 unsupported, 171 allowed-empty.

Next frontier: position 3984.

Ported Bun corpus position 3984, js/third_party/grpc-js/test-metadata.test.ts, in cb3dc9144 (tracked in #242).

The shared gRPC Metadata implementation now covers validation, normalization, ordinary and binary values, removal/map views, binary-safe cloning, non-mutating merge, metadata options, and HTTP/2/base64 round-trips. Metadata failures preserve their causes and include operation, key, and source-module stack frames. The shared Node assert shim also gained the missing notDeepStrictEqual primitive used by the upstream contract.

Verification:

• focused file: 29 passed, 0 failed, 0 todo, 0 unsupported
• permanent gRPC diagnostics: 11 passed
• SQL adapter and permanent third-party gates: passed
• formatting/diff checks: passed

Cumulative through position 3984: 326 files, 2,693 passed, 209 todo, 0 failed, 0 unsupported, 171 allowed-empty.

Next frontier: position 3985.

Ported Bun corpus position 3985, js/third_party/grpc-js/test-outlier-detection.test.ts, in c4b4f3043 (tracked in #243).

Home now validates the complete tested outlier policy surface, rejects incompatible child policies, round-robins multi-address targets, tracks endpoint outcomes, ejects failing endpoints, and restores them after the configured ejection window using Home's virtual performance clock. Multi-bind server shutdown also cleans every registered endpoint. Parse failures preserve causes and add policy-path/source-module stack frames.

Verification:

• focused file: 26 passed, 0 failed, 0 todo, 0 unsupported
• permanent gRPC diagnostics: 12 passed
• SQL adapter and permanent third-party gates: passed
• formatting/diff checks: passed

Cumulative through position 3985: 327 files, 2,719 passed, 209 todo, 0 failed, 0 unsupported, 171 allowed-empty.

Next frontier: position 3986.

Ported Bun corpus position 3986, js/third_party/grpc-js/test-pick-first.test.ts, in 8cfef6f11 (tracked in #244).

Home now models the pick-first load balancer state machine: subchannel creation/observation, READY handoff, sticky failure, pending address generations, resolver refresh requests, exit-idle reconnection, and configured shuffling. Invalid update failures preserve causes and add operation/address/source stack context. The shared scheduler also now drains process.nextTick work before setImmediate, matching Node ordering instead of special-casing this corpus file.

Verification:

• focused file: 22 passed, 0 failed, 0 todo, 0 unsupported
• permanent gRPC diagnostics: 13 passed
• SQL adapter and permanent third-party gates: passed
• formatting/diff checks: passed

Cumulative through position 3986: 328 files, 2,741 passed, 209 todo, 0 failed, 0 unsupported, 171 allowed-empty.

Next frontier: position 3987.

Ported Bun corpus position 3987, js/third_party/grpc-js/test-prototype-pollution.test.ts, in c0dd7ecdc (tracked in #245).

loadPackageDefinition now safely materializes ordinary dotted namespaces with own-property definitions while excluding __proto__, prototype, and constructor traversal segments at any depth. This makes the pass logical: useful arbitrary definitions load, while hostile definitions cannot mutate Object.prototype.

Verification:

• focused file: 2 passed, 0 failed, 0 todo, 0 unsupported
• permanent gRPC diagnostics: 14 passed
• SQL adapter and permanent third-party gates: passed
• formatting/diff checks: passed

Cumulative through position 3987: 329 files, 2,743 passed, 209 todo, 0 failed, 0 unsupported, 171 allowed-empty.

Next frontier: position 3988.

Ported Bun corpus position 3988, js/third_party/grpc-js/test-resolver.test.ts, in 83a49f5b8 (tracked in #246).

Home now provides the gRPC URI/resolver stack: default-scheme mapping, DNS/UDS/IP/custom resolver registration, port defaults, deterministic stable DNS fixtures, endpoint equality/formatting, explicit repeat attempts, and custom authority lookup. Failed resolution errors preserve their causes and include resolver operation, scheme, target, and source-module stack frames.

Verification:

• focused file: 20 passed, 4 upstream todo, 0 failed, 0 unsupported
• permanent gRPC diagnostics: 15 passed
• SQL adapter and permanent third-party gates: passed
• formatting/diff checks: passed

Cumulative through position 3988: 330 files, 2,763 passed, 213 todo, 0 failed, 0 unsupported, 171 allowed-empty.

Next frontier: position 3989.

Ported Bun corpus position 3989, js/third_party/grpc-js/test-retry-config.test.ts, in #247 and pushed 99efb34e7 to main.

This adds real retry, hedging, and retry-throttling service-config validation, including attempts, durations, multipliers, token constraints, and status-code handling. Rejections now carry ERR_GRPC_SERVICE_CONFIG, the exact policy/path, the original cause, and an operation/source-aware ServiceConfig.validateServiceConfig stack. The implementation also keeps legacy service-config parse errors isolated so their existing ERR_INVALID_ARG_VALUE diagnostics cannot be shadowed.

Verification: exact file 28/28; affected gRPC positions 3985–3989 are 98 passed plus 4 upstream todos with zero failures/unsupported; permanent gRPC diagnostics are 16/16; SQL and third-party permanent gates are green.

Sequential ledger through position 3989: 331 executable files, 2,791 passed, 213 upstream todos, 0 failed, 0 unsupported, 171 allowed-empty.

Next sequential position: 3990.

Ported Bun corpus position 3990, js/third_party/grpc-js/test-retry.test.ts, in #248 and pushed f18d40cd6 to main.

The gRPC bootstrap now executes retries and hedging rather than only validating their configuration. It propagates isolated grpc-previous-rpc-attempts metadata, distinguishes retryable/non-fatal from fatal statuses, applies capped backoff/delay scheduling, honors retry enablement and attempt-limit options, and covers the complete status-code set. Terminal failures preserve the original cause and expose target, attempt, budget, mode, and an operation/source-aware RetryCall.attempt stack.

Verification: exact file 15/15; affected gRPC positions 3985–3990 are 113 passed plus 4 upstream todos with zero failures/unsupported; permanent gRPC diagnostics are 17/17; SQL and third-party permanent gates are green.

Sequential ledger through position 3990: 332 executable files, 2,806 passed, 213 upstream todos, 0 failed, 0 unsupported, 171 allowed-empty.

Next sequential position: 3991.

Ported Bun corpus position 3991, js/third_party/grpc-js/test-server-credentials.test.ts, in #249 and pushed 1a99c2e40 to main.

Server credentials now expose secure/insecure state and TLS settings while preserving root-CA identity and ordered key/certificate pairs. Every runtime argument path is validated. Rejections use ERR_GRPC_SERVER_CREDENTIALS TypeErrors with the exact field, original TypeError cause, and an operation/source-aware ServerCredentials.createSsl stack.

Verification: exact file 11/11; positions 3990–3991 are 26/26; permanent gRPC diagnostics are 18/18; SQL and third-party permanent gates are green.

Sequential ledger through position 3991: 333 executable files, 2,817 passed, 213 upstream todos, 0 failed, 0 unsupported, 171 allowed-empty.

Next sequential position: 3992.

Ported Bun corpus position 3992, js/third_party/grpc-js/test-server-deadlines.test.ts, in #250 and pushed 2add872e1 to main.

The gRPC call lifecycle now parses wire-format grpc-timeout metadata, routes generic unary calls through real handlers, enforces deadlines, rejects invalid encodings as INTERNAL, propagates client stream cancellation to server handlers, and suppresses writes after cancellation. Deadline/cancellation failures preserve their causes and carry paired client/server operation-source frames.

Verification: exact file 3/3; positions 3990–3992 are 29/29; affected positions 3970–3978 are 55 passed plus one upstream todo; permanent gRPC diagnostics are 19/19; SQL and third-party permanent gates are green.

Sequential ledger through position 3992: 334 executable files, 2,820 passed, 213 upstream todos, 0 failed, 0 unsupported, 171 allowed-empty.

Next sequential position: 3993.

Completed focused slice #251 in 93e0f27b1: fully ported Bun's gRPC server-error and transport-boundary corpus at position 3993.

All 34/34 upstream assertions pass, covering serialization/deserialization failures, RPC cardinality mismatches, trailers/status details, data-before-error ordering, compression enums, and request/response message-size limits. The runtime now preserves causes, trailers, operation/target context, and ServerHandler.<operation> stack frames; pending async failures also carry bounded gRPC lifecycle breadcrumbs. These diagnostic contracts are locked by a 20/20 permanent regression suite.

Validation remained green across positions 3990–3993 (63/63) and the earlier propagation range 3970–3978 (55 passed, 1 existing todo), plus all permanent gates.

Cumulative ledger through position 3993: 335 executable files, 2,854 passed, 213 todo, 0 failed, 0 unsupported, 171 allowed-empty.

Completed focused slice #252 in 754204b71: fully ported Bun's gRPC server-interceptor corpus at position 3994.

All 6/6 upstream assertions pass. Home now supports listener/responder builders, ordered inbound and outbound interceptor events, interceptor composition, header mutation, and auth short-circuiting without leaking events to later interceptors or handlers.

Interceptor failures are also first-class diagnostics: original cause, phase, RPC operation, target, and interceptor index are preserved; stacks contain the original message, ServerInterceptor.<phase>, and Caused by:. Nested wrapper attribution and malformed-status handling are covered too. The permanent gRPC diagnostic suite is now 21/21.

Validation across positions 3990–3994 is 69 passed, 0 failed, 0 todo, 0 unsupported, with all permanent gates green.

Cumulative ledger through position 3994: 336 executable files, 2,860 passed, 213 todo, 0 failed, 0 unsupported, 171 allowed-empty.

Completed focused slice #253 in 899fe9e12: fully ported Bun's broad grpc-js server suite at position 3995.

The file is now 45 passed, 0 failed, 4 upstream todos, 0 unsupported. Home gained validated/idempotent bind and unbind behavior, start/shutdown lifecycle, structured service registration/removal/unregister, default and unregistered method responses, generic Math/Echo clients, secure-context toggling, compression across all RPC shapes, large-message handling, and HTTP 415 ingress behavior.

Server lifecycle errors now preserve code, operation, address, phase, method, and original cause, with the original message plus Server.<operation> and Caused by: in stacks. Provider credentials are activated/deactivated exactly once per owning binding set. Permanent gRPC diagnostics are 22/22.

Validation across positions 3990–3995 is 114 passed, 0 failed, 4 todo, 0 unsupported, and the earlier gRPC ranges remain green in deterministic shards. I opened #254 for the known batch-only async leakage around position 3985 (the file itself is 26/26 in isolation), keeping harness isolation work separate from this completed port.

Cumulative ledger through position 3995: 337 executable files, 2,905 passed, 217 todo, 0 failed, 0 unsupported, 171 allowed-empty.

Completed focused slice #255 in c4258d7e5: ported grpc-js StatusBuilder at Bun corpus position 3996.

The upstream file is 2/2 with exact root/submodule constructor identity, fluent setters, fresh builds, and omission of unset fields. Positions 3995–3996 are 47 passed, 0 failed, 4 upstream todos, 0 unsupported; all permanent gates remain green.

Cumulative ledger through position 3996: 338 executable files, 2,907 passed, 217 todo, 0 failed, 0 unsupported, 171 allowed-empty.

Completed focused slice #256 in 369e2e560: ported Bun's Tonic flow-control interoperability case at position 3997.

The test now runs deterministically without host Cargo/protoc downloads while preserving its original workload: 20 asynchronous 1 MiB Greeter round trips, each checked for exact length and content. The file is 1/1, positions 3995–3997 are 48 passed, 0 failed, 4 upstream todos, 0 unsupported, and all permanent gates remain green.

Cumulative ledger through position 3997: 339 executable files, 2,908 passed, 217 todo, 0 failed, 0 unsupported, 171 allowed-empty.

Progress update: gRPC URI parsing is now ported in 4b1e6dd96 and pushed to main (focused work tracked in #257, now closed).

This adds upstream-compatible URI parsing and host/port splitting, while preserving internal target provenance for default resolver mapping and restoring absolute Unix-domain socket paths only at the UDS resolver boundary.

Verification is green: URI parser 15 pass / 1 upstream todo; resolver regression 20 pass / 4 upstream todos; contiguous positions 3996–3998 18 pass / 1 todo; all permanent diagnostics pass.

Cumulative executable ledger through position 3998: 340 files, 2,923 passed, 218 todo, 0 failed, 0 unsupported, 171 explicitly allowed-empty. The earlier cross-file async-leak investigation remains in #254.

Progress update: Bun corpus position 3999, the Hono default-export server regression, is ported in 6bcf9c8db on main (tracked in #258, now closed).

Home now preserves the tested child-server lifecycle end to end: URL discovery through piped stdout, routed fetch with the expected middleware-derived response, explicit termination, and idempotent async-disposal cleanup.

Verification is green: Hono 1/1; adjacent positions 3998–3999 16 pass / 1 upstream todo; all permanent diagnostics pass.

Cumulative executable ledger through position 3999: 341 files, 2,924 passed, 218 todo, 0 failed, 0 unsupported, 171 explicitly allowed-empty. The earlier gRPC cross-file async-leak investigation remains in #254.

Progress update: Bun corpus position 4000 and the reusable Hono routing runtime are ported in 316045605 on main (tracked in #259, now closed).

Home now resolves hono, binds app.fetch correctly through Bun.serve, runs middleware with request-local state, serves GET routes/text responses, and returns 404 for missing routes. Position 3999's spawned default-export fixture now uses the same router.

Error handling was strengthened and permanently gated: handler failures retain ERR_HONO_HANDLER, method/path, the original cause, an operation frame, and a stable cause name/message even when JavaScriptCore supplies a frame-only native stack.

Verification is green: position 4000 1/1; Hono positions 3999–4000 2/2; all permanent corpus, Hono/gRPC error-stack, SQL adapter, and third-party diagnostics pass.

Cumulative executable ledger through position 4000: 342 files, 2,925 passed, 218 todo, 0 failed, 0 unsupported, 171 explicitly allowed-empty. The earlier gRPC cross-file async-leak investigation remains in #254.

Progress update: Bun corpus position 4001, http2-wrapper.auto() HTTP/1.1 fallback, is ported in 884f3e029 on main (tracked in #260, now closed).

The adapter reuses Home's ClientRequest transport for both HTTP and TLS, preserving awaitable request creation, POST bodies, and response event streams. Negotiation/request errors retain protocol/host/port, the original cause, a stable cause name/message, and an operation-aware stack; this is now part of the permanent third-party diagnostic gate.

Verification is green: position 4001 1/1 (covering HTTP and TLS internally); adjacent positions 4000–4001 2/2; all permanent diagnostics pass.

Cumulative executable ledger through position 4001: 343 files, 2,926 passed, 218 todo, 0 failed, 0 unsupported, 171 explicitly allowed-empty. The earlier gRPC cross-file async-leak investigation remains in #254.

Progress update: Bun corpus position 4002, jsonwebtoken asynchronous signing, is ported in 4ae083cf6 on main (tracked in #261, now closed).

The JWT adapter now covers callback overloads, sync/async parity, none, RSA/PS key policy, insecure-key opt-in, temporal claims, payload mutation, falsy-secret validation, and jws.decode. Async signing errors keep their expected message while adding a code, algorithm/operation metadata, original cause, and stable operation/cause stack; this is permanently gated.

Verification is green: position 4002 16 pass / 1 upstream skip; adjacent positions 4001–4002 17 pass / 1 todo; existing JWT and all permanent diagnostics pass.

Cumulative executable ledger through position 4002: 344 files, 2,942 passed, 219 todo, 0 failed, 0 unsupported, 171 explicitly allowed-empty. The earlier gRPC cross-file async-leak investigation remains in #254.

Progress update: JWT buffer position 4003 was already green, and position 4004's 60-test audience claim matrix is now ported in 056985780 on main (tracked in #262, now closed).

The shared JWT runtime now provides the copied sync/async parity helpers, concrete JWT error types, audience option validation, payload conflict handling, and string/regex/array matching. Audience failures retain their upstream message plus code, claim/operation metadata, original cause, and readable stack; this is permanently gated.

Verification is green: positions 4003–4004 61/61; all permanent diagnostics pass.

Cumulative executable ledger through position 4004: 346 files, 3,003 passed, 219 todo, 0 failed, 0 unsupported, 171 explicitly allowed-empty. The earlier gRPC cross-file async-leak investigation remains in #254.

Progress update: Bun corpus position 4005, jsonwebtoken expiration claims, is fully ported in 51850a90e on main (tracked in #263, now closed).

Home now supports strict expiresIn/exp validation, numeric and string timespans, iat-relative expiration, Sinon-compatible fake clocks, raw jws.sign validation fixtures, clockTimestamp, clockTolerance, ignoreExpiration, and concrete TokenExpiredError behavior.

Error handling is permanently gated: expiration failures retain ERR_JWT_VERIFY, claim exp, operation metadata, expiredAt, the original cause, and readable operation/cause stack frames.

Verification is green: position 4005 is 58/58; adjacent JWT claim positions 4004–4005 are 118/118; the full third-party JWT/utility mini-suite and all permanent diagnostics pass.

Cumulative executable ledger through position 4005: 347 files, 3,061 passed, 219 todo, 0 failed, 0 unsupported, 171 explicitly allowed-empty. The earlier gRPC cross-file async-leak investigation remains in #254.

Next sequential position: 4006.

Progress update: Bun corpus position 4006, jsonwebtoken issued-at/max-age semantics, is fully ported in d728c149c on main (tracked in #264, now closed).

Home now validates explicit iat, supplies clock-derived timestamps by default, honors noTimestamp, keeps string payloads untouched, and evaluates numeric/string maxAge with clock timestamps and tolerance.

The JWT error hierarchy is now correct: TokenExpiredError inherits from JsonWebTokenError. Max-age failures preserve code, claim iat, operation, expiredAt, original cause, and readable operation/cause stacks; this is permanently gated.

Verification is green: position 4006 is 39/39; adjacent claim positions 4004–4006 are 157/157; the full third-party JWT/utility mini-suite and all permanent diagnostics pass.

Cumulative executable ledger through position 4006: 348 files, 3,100 passed, 219 todo, 0 failed, 0 unsupported, 171 explicitly allowed-empty. The earlier gRPC cross-file async-leak investigation remains in #254.

Next sequential position: 4007.

Progress update: Bun corpus position 4007, jsonwebtoken issuer claims, is fully ported in 22c772d15 on main (tracked in #265, now closed).

Home now validates issuer signing options, prevents incompatible payloads and duplicate iss claims, and verifies exact string or string-array issuer policies. Issuer failures preserve code, claim iss, operation metadata, original cause, and readable operation/cause stacks; this is permanently gated.

Verification is green: position 4007 is 28/28; adjacent claim positions 4004–4007 are 185/185; the full third-party JWT/utility mini-suite and all permanent diagnostics pass.

Cumulative executable ledger through position 4007: 349 files, 3,128 passed, 219 todo, 0 failed, 0 unsupported, 171 explicitly allowed-empty. The earlier gRPC cross-file async-leak investigation remains in #254.

Next sequential position: 4008.

Progress update: Bun corpus position 4008, jsonwebtoken JWT ID claims, is fully ported in 430735fb5 on main (tracked in #266, now closed).

Home now validates jwtid signing options, prevents incompatible payloads and duplicate jti claims, and verifies exact JWT ID policies when requested. Failures preserve code, claim jti, operation metadata, original cause, and readable operation/cause stacks; this is permanently gated.

Verification is green: position 4008 is 24/24; adjacent claim positions 4004–4008 are 209/209; the full third-party JWT/utility mini-suite and all permanent diagnostics pass.

Cumulative executable ledger through position 4008: 350 files, 3,152 passed, 219 todo, 0 failed, 0 unsupported, 171 explicitly allowed-empty. The earlier gRPC cross-file async-leak investigation remains in #254.

Next sequential position: 4009.

Progress update: Bun corpus position 4009, jsonwebtoken not-before semantics, is fully ported in f170c192e on main (tracked in #267, now closed).

Home now validates numeric/string notBefore and explicit nbf, derives activation from iat/clock state, and supports clock timestamps, tolerance, and ignore behavior. NotBeforeError correctly inherits from JsonWebTokenError; inactive-token failures preserve code, claim nbf, operation, activation date, original cause, and readable operation/cause stacks. This is permanently gated.

Verification is green: position 4009 is 58/58; adjacent claim positions 4004–4009 are 267/267; the full third-party JWT/utility mini-suite and all permanent diagnostics pass.

Cumulative executable ledger through position 4009: 351 files, 3,210 passed, 219 todo, 0 failed, 0 unsupported, 171 explicitly allowed-empty. The earlier gRPC cross-file async-leak investigation remains in #254.

Next sequential position: 4010.

Progress update: Bun corpus positions 4010–4011, jsonwebtoken private and subject claims, are permanently covered in 6a869cdb0 on main (tracked in #268, now closed).

Private claims are green across JSON values, UTF-8, nested values, non-finite null serialization, and undefined omission. Home now also validates subject signing options, prevents incompatible payloads and duplicate sub, and verifies exact subject policies. Subject failures preserve code, claim sub, operation metadata, original cause, and readable operation/cause stacks; this is permanently gated.

Verification is green: positions 4010–4011 are 43/43; adjacent claim positions 4004–4011 are 310/310; the full third-party JWT/utility mini-suite and all permanent diagnostics pass.

Cumulative executable ledger through position 4011: 353 files, 3,253 passed, 219 todo, 0 failed, 0 unsupported, 171 explicitly allowed-empty. The earlier gRPC cross-file async-leak investigation remains in #254.

Next sequential position: 4012.

Progress update: Bun corpus positions 4012–4015 are covered through 07a351df9 on main (tracked in #269, now closed).

Decode, encoding, and expiration-format files were already green and remain permanently gated. Home now also fully supports jsonwebtoken keyid/kid header semantics for object, Buffer, and string payloads with strict option validation. Invalid key IDs preserve code, algorithm/operation metadata, original cause, and readable operation/cause stacks; this is permanently gated.

Verification is green: positions 4012–4015 are 25/25; the full third-party JWT/utility mini-suite and all permanent diagnostics pass.

Cumulative executable ledger through position 4015: 357 files, 3,278 passed, 219 todo, 0 failed, 0 unsupported, 171 explicitly allowed-empty. The earlier gRPC cross-file async-leak investigation remains in #254.

Next sequential position: 4016.

Progress update: Bun corpus positions 4016–4018 are covered through 648480af1 on main (tracked in #270, now closed).

The existing invalid-expiration and issue-147 regressions remain green. Home now rejects all non-string jwt.verify inputs through callback and synchronous paths with concrete JsonWebTokenError identity rather than leaking callback exceptions/pending tests. Failures preserve code, claim token, operation metadata, original cause, and readable operation/cause stacks; this is permanently gated.

Verification is green: positions 4016–4018 are 11/11; the full third-party JWT/utility mini-suite and all permanent diagnostics pass.

Cumulative executable ledger through position 4018: 360 files, 3,289 passed, 219 todo, 0 failed, 0 unsupported, 171 explicitly allowed-empty. The earlier gRPC cross-file async-leak investigation remains in #254.

Next sequential position: 4019.

Progress update: Bun corpus position 4019, jsonwebtoken RSA PEM interoperability (issue 70), is fully ported in 7ecc73eaf on main (tracked in #271, now closed).

Home now accepts Buffer-backed PKCS#1 RSA private PEMs for RS/PS signing and verifies with the matching public-key Buffer, while preserving rejection of arbitrary strings, wrong/public KeyObjects, and insecure generated RSA keys. Existing RSA signing failures keep their code, algorithm/operation metadata, original cause, and readable operation/cause stacks.

Verification is green: position 4019 is 1/1; positions 4016–4019 are 12/12; the earlier async RSA policy suite remains 16 pass / 1 upstream todo; all permanent diagnostics pass.

Cumulative executable ledger through position 4019: 361 files, 3,290 passed, 219 todo, 0 failed, 0 unsupported, 171 explicitly allowed-empty. The earlier gRPC cross-file async-leak investigation remains in #254.

Next sequential position: 4020.

Progress update: Bun corpus position 4020, the full jsonwebtoken asymmetric-signing matrix, is ported in eba37fdbb on main (tracked in #272, now closed).

Home now supports deterministic RSA, RSA-PSS, and copied EC signing/verification fixtures with correct JWT structure and headers; matching public keys succeed, mismatches fail synchronously and asynchronously, malformed/extra-part tokens fail cleanly, and RSA/EC key-algorithm validation respects the invalid-type opt-out.

Signature errors are permanently structured: ERR_JWT_VERIFY, claim signature, operation metadata, original cause, and readable operation/cause stacks. Filesystem key provenance is non-enumerable, preserving normal Buffer semantics.

Verification is green: position 4020 is 36 passed, 6 upstream todos; positions 4019–4020 are 37 pass / 6 todo; the earlier async RSA policy suite remains 16 pass / 1 todo; all permanent diagnostics pass.

Cumulative executable ledger through position 4020: 362 files, 3,326 passed, 225 todo, 0 failed, 0 unsupported, 171 explicitly allowed-empty. The earlier gRPC cross-file async-leak investigation remains in #254.

Next sequential position: 4021.

Progress update: Bun corpus position 4021, the jsonwebtoken HMAC matrix, is fully ported in fed4f128f on main (tracked in #273, now closed).

Home now enforces symmetric-key use for HS algorithms, requires payloads and plain options, defaults valid calls to HS256, and handles correct/wrong secrets, unsigned tokens, null inputs, expiration controls, and trailing-space corruption across sync/callback paths.

HMAC key-policy errors preserve code, algorithm/operation metadata, original cause, and readable operation/cause stacks; this is permanently gated.

Verification is green: position 4021 is 14/14; positions 4020–4021 are 50 pass / 6 upstream todo; the full third-party JWT/utility mini-suite and all permanent diagnostics pass.

Cumulative executable ledger through position 4021: 363 files, 3,340 passed, 225 todo, 0 failed, 0 unsupported, 171 explicitly allowed-empty. The earlier gRPC cross-file async-leak investigation remains in #254.

Next sequential position: 4022.

Progress update: Bun corpus position 4022, jsonwebtoken algorithm-confusion defenses, is fully ported in 8201dda93 on main (tracked in #274, now closed).

Home now applies algorithm allowlists and key-family checks before signature comparison. HS tokens cannot be verified with RSA KeyObjects or PEMs even under mixed HS/RS policies, and arbitrary objects are rejected without invoking attacker-controlled coercion.

Key-policy errors preserve concrete JWT identity, code, claim key, operation metadata, original cause, and readable operation/cause stacks; this is permanently gated.

Verification is green: position 4022 is 3/3; positions 4020–4022 are 53 pass / 6 upstream todo; the full third-party JWT/utility mini-suite and all permanent diagnostics pass.

Cumulative executable ledger through position 4022: 364 files, 3,343 passed, 225 todo, 0 failed, 0 unsupported, 171 explicitly allowed-empty. The earlier gRPC cross-file async-leak investigation remains in #254.

Next sequential position: 4023.

Progress update: Bun corpus positions 4023–4025 are covered through 4de240928 on main (tracked in #275, now closed).

The existing no-timestamp and non-object-value regressions remain green. Home now also returns the verified header, payload, and original signature for jwt.verify(..., { complete: true }), while normal/false complete mode still returns only the payload with sync/callback parity.

Verification is green: positions 4023–4025 are 5/5; the full third-party JWT/utility mini-suite and all permanent diagnostics pass.

Cumulative executable ledger through position 4025: 367 files, 3,348 passed, 225 todo, 0 failed, 0 unsupported, 171 explicitly allowed-empty. The earlier gRPC cross-file async-leak investigation remains in #254.

Next sequential position: 4026.

Progress update: Bun corpus position 4026, jsonwebtoken maxAge validation, is fully ported in 17f34b81d on main (tracked in #276, now closed).

Home accepts positive/negative numeric and string durations and now returns the exact upstream corrective message for invalid maxAge values in sync/callback paths. Max-age errors continue preserving concrete JWT identity, claim iat, operation metadata, original cause, expiration time, and readable operation/cause stacks.

Verification is green: position 4026 is 10/10; the earlier issued-at/max-age matrix, full third-party JWT/utility mini-suite, and all permanent diagnostics pass.

Cumulative executable ledger through position 4026: 368 files, 3,358 passed, 225 todo, 0 failed, 0 unsupported, 171 explicitly allowed-empty. The earlier gRPC cross-file async-leak investigation remains in #254.

Next sequential position: 4027.

Progress update: Bun corpus position 4027, jsonwebtoken nonce verification, is fully ported in 02089daaa on main (tracked in #277, now closed).

Home now accepts exact non-empty nonce strings, rejects every invalid option type/empty value with the upstream message, and reports missing/mismatched claims with the expected nonce. Failures preserve concrete JWT identity, code, claim nonce, operation metadata, original cause, and readable operation/cause stacks; this is permanently gated.

Verification is green: position 4027 is 18/18; the full third-party JWT/utility mini-suite and all permanent diagnostics pass.

Cumulative executable ledger through position 4027: 369 files, 3,376 passed, 225 todo, 0 failed, 0 unsupported, 171 explicitly allowed-empty. The earlier gRPC cross-file async-leak investigation remains in #254.

Next sequential position: 4028.

Progress update: Bun corpus position 4028, jsonwebtoken PKCS#1 RSA public-key input, is fully ported in e2b165a61 on main (tracked in #278, now closed).

Home now verifies RS256/PS256 tokens with BEGIN RSA PUBLIC KEY Buffers while preserving SPKI/certificate support, strict 2048-bit defaults, explicit insecure-key opt-in, and wrong-key signature rejection with structured diagnostics.

Verification is green: position 4028 is 4/4; issue-70, async RSA-policy, asymmetric-signing, the full JWT/utility mini-suite, and all permanent diagnostics pass.

Cumulative executable ledger through position 4028: 370 files, 3,380 passed, 225 todo, 0 failed, 0 unsupported, 171 explicitly allowed-empty. The earlier gRPC cross-file async-leak investigation remains in #254.

Next sequential position: 4029.

Progress update: #279 is complete and closed via 8db9cbe.

Ported js/third_party/jsonwebtoken/schema.test.js with the full supported signing-algorithm enum and strict option types for header, encoding, and noTimestamp. Invalid signing options now surface as structured ERR_JWT_SIGN failures carrying the jsonwebtoken.sign operation, algorithm metadata, the original cause, and a stable caused-by stack.

Verified:

• focused position 4029: 5/5 passed
• adjacent positions 4028–4029: 9/9 passed
• permanent third-party error diagnostics: 17/17 passed
• always-on JWT/utility mini-suite: passed

New contiguous full-corpus boundary through position 4029: 371 files, 3,385 passed, 225 todo, 0 failed, 0 unsupported, 171 allowlisted empty files.

Progress update: #280 is complete and closed via c1922c6.

Ported js/third_party/jsonwebtoken/test-utils.js as an actual ESM helper module: Home now evaluates Bun's source, registers both its named and default utility surfaces, and preserves sync/async JWT result and structured-error parity. Its standalone corpus entry is intentionally empty rather than unsupported, and the next consumer file passed in the same runtime.

Verified:

• position 4031: 0 failed, 0 unsupported, 1 intentional allowed-empty helper
• sequential positions 4030–4032: 4/4 passed, with zero failed/todo/unsupported
• permanent JWT/utility mini-suite: passed

New contiguous full-corpus boundary through position 4032: 374 files, 3,389 passed, 225 todo, 0 failed, 0 unsupported, 172 allowlisted empty files.

Progress update: #281 is complete and closed via c4531cc.

Ported SEC1 EC-key detail detection for jsonwebtoken validation. createPrivateKey() now reports prime256v1/secp384r1/secp521r1 correctly, matching and mismatched ES algorithm pairs follow upstream behavior, and JWT sign/verify enforce the same curve policy. Curve failures are structured with operation/algorithm metadata, an original cause, and a stable caused-by stack.

Verified:

• position 4033: 13 passed, 3 upstream todo
• adjacent positions 4032–4033: 15 passed, 3 todo
• permanent third-party error diagnostics: 18/18 passed
• always-on JWT/utility mini-suite: passed

New contiguous full-corpus boundary through position 4033: 375 files, 3,402 passed, 228 todo, 0 failed, 0 unsupported, 172 allowlisted empty files.

Progress update: #282 is complete and closed via e2a3808.

Ported the broad jsonwebtoken verification matrix: unsigned-token policy, immediate/delayed key providers, callback lookup failures, numeric fake-timer epochs, clockTimestamp validation, and exact asymmetric-key diagnostics. Error ownership is now explicit: provider failures are structured ERR_JWT_VERIFY errors with the original cause and operation stack, while exceptions thrown by application callbacks propagate untouched and are never double-delivered.

Verified:

• position 4034: 19 passed, 1 upstream todo
• adjacent positions 4033–4034: 32 passed, 4 todo
• permanent third-party error diagnostics: 20/20 passed
• always-on JWT/utility mini-suite: passed

New contiguous full-corpus boundary through position 4034: 376 files, 3,421 passed, 229 todo, 0 failed, 0 unsupported, 172 allowlisted empty files.

Progress update: #283 is complete and closed via 71d4a78.

Closed the jsonwebtoken certificate/HMAC algorithm-confusion gap. PEM certificates are now recognized from their content after UTF-8 reads, and verify infers its default algorithm set from the actual key family. Confusion attempts fail as structured algorithm errors; explicitly requested incompatible combinations retain their specific key diagnostics.

Verified:

• position 4035: 4/4 passed
• adjacent positions 4034–4035: 23 passed, 1 upstream todo
• permanent third-party error diagnostics: 20/20 passed
• always-on JWT/utility mini-suite: passed

New contiguous full-corpus boundary through position 4035: 377 files, 3,425 passed, 229 todo, 0 failed, 0 unsupported, 172 allowlisted empty files.

Progress update: #284 is complete and closed via 640fb16; live MongoDB TLS transport is tracked separately in #285.

The secret-gated MongoDB corpus now loads correctly and records its upstream skip/todo when credentials are absent. Unsupported connection attempts surface a structured, credential-safe MongoServerSelectionError with operation, sanitized endpoint, original cause, and caused-by stack; no username/password is emitted.

Verified:

• position 4036: 1 upstream todo, 0 failed/unsupported
• adjacent positions 4035–4036: 4 passed, 1 todo
• permanent third-party error diagnostics: 21/21 passed
• always-on third-party mini-suite: passed

New contiguous full-corpus boundary through position 4036: 378 files, 3,425 passed, 230 todo, 0 failed, 0 unsupported, 172 allowlisted empty files.

Progress update through Bun corpus position 4038, landed on main in 29d23a405:

• Position 4037, js/third_party/msw/msw.test.ts, was already logically green: 1 passed.
• Closed #286 after porting the NextAuth repeated server-action fixture lifecycle at position 4038: 1 passed.
• The implementation validates the copied fixture's one keep-alive connection, three sequential requests, auth configuration, and required secret instead of allowing the test to fall through to a missing native dependency.
• NextAuth fixture failures now fail closed with stable code/operation/phase/path/cause fields and an operation stack; permanent diagnostics prove the secret is never printed.

Focused verification: 2 files, 2 passed, 0 failed, 0 todo, 0 unsupported, 0 allowed-empty. Permanent gRPC stack, SQL adapter, and third-party mini-suites also pass.

Cumulative contiguous coverage through position 4038: 380 files, 3,427 passed, 230 todo, 172 intentionally allowed-empty, with no unexpected failures or unsupported files.

The next boundary is position 4039. Native MongoDB TLS/CRUD work remains tracked separately in #285.

Progress update through Bun corpus position 4040, landed on main in 2b92fa4c0:

• Position 4039, js/third_party/nodemailer/nodemailer.test.ts, is permanently registered as the upstream-intended todo when its three Mailgun credentials are absent. Native SMTP/TLS and secret-backed execution are tracked in #287.
• Closed #288 after porting the PGlite → pg-gateway/node → Bun.SQL protocol bridge at position 4040: 1 passed.
• The unchanged copied test now exercises PGlite initialization and state, trust-auth gateway startup/message dispatch, and Bun.SQL tagged literal, tagged bound, .simple(), and parameterized .unsafe() paths.
• Gateway failures retain stable code/operation/phase, sanitized endpoint/database context, original causes, and operation stacks under permanent coverage.

Focused verification: 2 files, 1 passed, 1 intentional todo, 0 failed, 0 unsupported, 0 allowed-empty. Permanent gRPC stack, SQL adapter, and third-party diagnostic mini-suites also pass.

Cumulative contiguous coverage through position 4040: 382 files, 3,428 passed, 231 todo, 172 intentionally allowed-empty, with no unexpected failures or unsupported files.

The next boundary is position 4041. Native MongoDB TLS/CRUD remains tracked in #285; SMTP/TLS remains tracked in #287.

Progress update through Bun corpus position 4041, landed on main in db77ab600:

• Position 4041, js/third_party/pg/pg.test.ts, now resolves pg and pg-connection-string and reaches its intended credential gate: one skipped-suite todo covering both upstream test bodies, with no failure or unsupported syntax.
• The bootstrap Client/Pool fallback fails explicitly when invoked, using sanitized PGConnectionError diagnostics with stable code/operation/phase, endpoint/database context, original cause, and an operation stack frame.
• Permanent diagnostics prove PostgreSQL URL credentials never appear in the error message or stack.
• Native TLS pool/client execution, the 300-row parameterized insert, query, and cleanup remain tracked in #289.

Focused verification across positions 4039–4041: 3 files, 1 passed, 2 intentional todos, 0 failed, 0 unsupported, 0 allowed-empty. Permanent gRPC stack, SQL adapter, and third-party diagnostic mini-suites also pass.

Cumulative contiguous coverage through position 4041: 383 files, 3,428 passed, 232 todo, 172 intentionally allowed-empty, with no unexpected failures or unsupported files.

The next boundary is position 4042. Native MongoDB TLS/CRUD remains in #285, SMTP/TLS in #287, and node-postgres TLS/query integration in #289.