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.

First tranche from the coverage map is on origin/main. Each port is measured against a control built from the same tree with the runtime changes stashed, on one Darwin arm64 JSC debug build, with pinned Bun 4982b91e37 as the upstream reference. No upstream fixture, snapshot, deadline or expectation changed.

What that fixed: --watch restarts the process again instead of killing the watcher thread on the first change (reloadProcess was an empty stub); --minify-syntax rewrites known-global constructors again (the routine returned null); glob no longer panics on a normalized symlink path; and the Inspector's dev-server domain receives its events (the setEnabled export was a native_stubs no-op).

Three gaps this exposed, each filed with its evidence rather than folded in: #766 (no debugger session can attach over a unix: inspector URL, which is what actually blocks the HTTPServer agent events, so #760 stays open), #767 (test/cli/hot's five remaining failures — preload text and four hot-reload sourcemap cases — all pre-existing), and the duplicate clientNavigated event noted on #760.

Two environment gaps earn no credit either way: test/js/bun/glob/scan.test.ts and test/cli/inspect/inspect.test.ts cannot load because fast-glob and strip-ansi are absent from ~/Code/bun/node_modules; pinned Bun fails to load both files the same way.

Full logical Bun parity remains incomplete.

RSA-PSS key interoperability is pushed to main in afa901f15, continuing #587.

Home now imports and exports RFC 4055 RSA-PSS PKCS#8/SPKI keys in PEM and DER, preserves independent digest/MGF1/minimum-salt restrictions, supports real BoringSSL PBES2 encryption for private keys, derives public keys from encrypted or plaintext PKCS#8, and retains Bun-compatible missing/wrong-passphrase behavior. Existing restricted Bun fixtures and generated unrestricted/restricted keys round-trip and sign/verify.

Validation: required ReleaseFast JSC build 48/48; dedicated RSA-PSS regression pass; exact crypto.key-objects.test.ts 83 pass / 22 skip / 1 existing TODO / 0 fail / 905 assertions; full js/node/crypto 851 pass / 22 skip / 1 existing TODO / 0 fail / 2,416 assertions across 17 files; Pickier and diff checks pass. No corpus assertion, fixture, skip, deadline, or expected result was changed.

#587 remains open for RSA JWK/remaining PKCS#1 cross-format coverage, synthetic bridge removal, and the upstream RSA-PSS TODO.

Pushed d03df5f407751bac2483bd11c9786ec4a7c030f9 directly to origin/main as Chris Breuer without coauthors.

The #587 RSA-PSS implementation no longer stores restrictions in the secret-key byte vector. Metadata is now owned and freed by the real BoringSSL RSA backend via ex-data, while preserving KeyObjectData's ABI layout for prebuilt Bun objects. The required build passed 48/48; the dedicated native regression passed; exact key objects stayed 83/0; and all Node crypto stayed 851/0. Pickier and whitespace checks passed. No tests, fixtures, assertions, deadlines, skips, TODOs, snapshots, or expected outcomes changed. Full logical Bun parity remains incomplete, and work continues from this clean pushed checkpoint.

Pushed 0e3f4a72f35f2bea3dc659aef99d8e1cb103bf0b directly to origin/main as Chris Breuer without coauthors.

RSA-PSS identity and restrictions now survive structuredClone() and worker transfer, including usable cross-thread signatures. Home owns the ABI-matched serializer object, synced to pinned Bun 4982b91e… before the focused key hooks, so Bun's current near-2 GiB capacity, CryptoKey storage, BlockList lifetime, and BIO ownership fixes are live too. Required build: 50/50. Structured clone: 313/0 and 1,550 assertions, including five near-2 GiB cases. Key objects remain 83/0; Node crypto remains 851/0. No upstream corpus behavior was edited. Full logical parity remains incomplete and work continues from this clean pushed checkpoint.

Landed and pushed ce5d0c0996d5f971a270f85f6a96722c0bb355a3 (fix(runtime): recover hot entries after startup errors), closing #767.

This ports three pinned-Bun runtime behaviors: rejected initial entries stay watchable under --hot, load failures retain resolver diagnostics such as preload not found, and standalone module graphs lazily load/cache their embedded sourcemaps for original stack positions.

Exact pushed-source validation: required ReleaseFast JSC build 50/50; unchanged complete test/cli/hot directory plus compiled-standalone sourcemap regression 16 pass / 0 fail / 489 assertions; Zig formatting and diff checks pass. The repository-wide Pickier command still reports the pre-existing vendored/submodule baseline (59,279 findings); this patch changes only Zig files. No upstream corpus test, fixture, workload, deadline, assertion, skip, TODO, snapshot, or expected result changed.

Pushed two commits directly to origin/main as Chris Breuer without coauthors:

• bf64acd59435499f92b679d4d12902e92461822b — fix(build): match Apple ICU symbol names
• c6ab9aeeb914a214d693e0f6d253907161473d31 — fix(runtime): complete inspector reload events

This closes #760 and #766. Development/TLS Bun.serve() instances now reuse every hot-map server variant instead of constructing a duplicate and panicking during reload. HMR SetUrl sends one clientNavigated event for matched and unmatched routes, aligned with pinned Bun's current Rust implementation. The exact pinned Bake data-view/error-decoder support modules and base test TypeScript config restore the copied Bun module graph without changing any fixture or assertion.

A deliberately clean build also found an incremental-cache-masked linker defect: the WebKit SDK headers renamed ICU calls to _74, while Apple libicucore exports stable unversioned names. The macOS IDNA wrapper now disables header renaming before including ICU, and the required native ReleaseFast build passes 50/50 from a regenerated cache.

Verification:

• unchanged complete test/cli/inspect: 35 pass / 0 fail / 4 upstream TODO / 122 assertions / 7 snapshots
• unchanged HTTPServerAgent.test.ts: 1/1, including initial routes, hot reload, updated routes and close
• unchanged BunFrontendDevServer.test.ts: 6 pass / 0 fail / 2 upstream TODO, including exact single-navigation-event coverage
• focused IDNA set: 143 pass / 0 fail / 20 existing Intl-data skips / 6,018 assertions
• focused Pickier, Zig formatting and whitespace checks pass

No fixture, workload, deadline, assertion, skip, TODO, snapshot or expected outcome was weakened. Full logical Bun parity remains incomplete; #66 stays open.

Current-main acceptance audit also closes #761 and #762 without additional source changes:

• known-global constructor minification: unchanged regression 1 pass / 0 fail / 1 snapshot; implementation commit be7e7b961
• glob trailing-separator symlink traversal: complete unchanged scan.test.ts 172 pass / 0 fail / 136 snapshots / 75,937 assertions; implementation commit 11e17c70f

Both were reverified with the required ReleaseFast binary at current origin/main c6ab9aeeb; no fixture or expectation changed. #587 remains open because its explicit acceptance asks to convert a copied upstream RSA-PSS TODO, which conflicts with the no-TODO-conversion boundary even though the dedicated native test covers the implemented modern behavior.

Current-main acceptance audit closes #759. The complete unchanged test/cli/watch and test/cli/hot directories pass 21 tests / 0 failures / 539 assertions on the required ReleaseFast binary at c6ab9aeeb, including real process restarts, non-ASCII paths, watcher tracing, startup-error recovery, every sourcemap case and the 129-directory stress case. The implementation is retained from 2b48dc083 with the later hot-entry/sourcemap completion in ce5d0c099; no fixture or expected outcome changed.

Published 3b3dae8ed5 to origin/main, authored and committed as Chris Breuer without coauthors. The local and remote hashes match exactly.

This batch adds clean, bounded contextual typing for callbacks passed to later-declared generic functions. It fixes Zod core's false api.ts:1696:25 TS7006 without caching a speculative forward value signature or capturing the caller's generic binders. Broad global, suffix, reference-scoped, and on-demand value-resolution variants were measured and rejected because they either regressed the checker or corrupted Program/Zod type payloads.

Verification: checker 4,379/4,379, Program 216/216, ReleaseSafe home-tsc build, exact Zod v4.5.2 core 46 → 45 diagnostics with one removal and zero additions, and a TypeScript 6.0.2 oracle retaining the same two deliberate TS2322 errors with no TS7006. Focused Pickier, Zig formatting, and whitespace checks pass. #765 remains open for full forward value/overload resolution; #758 remains open with four Zod TS7006 diagnostics tracked by #763 and #764. Full logical Bun parity remains incomplete.

Published cdad20fe5d to origin/main, authored and committed as Chris Breuer without coauthors; local and remote hashes match exactly.

This batch completes #763 by retaining unsupported imported value declarations as projection-only metadata and using them solely for contextual member-assignment typing. Zod's new checks.$ZodCheck(...) remains any for ordinary reads and relations, while ch._zod.onattach = [(inst) => ...] receives the declared callback context. Malformed-source recovery still exposes only independently safe literal exports.

Verification: checker 4,379/4,379, Program 217/217, ReleaseSafe home-tsc, TypeScript 6.0.2 oracle parity, and exact Zod v4.5.2 core 45 → 43 diagnostics with only api.ts:1732:6 TS7006 and :1745:6 TS7006 removed and zero additions. Focused Pickier, Zig formatting, and whitespace checks pass. #758 remains open with the final two TS7006 sites tracked by #764. Full logical Bun parity remains incomplete.

Checkpoint advanced to 5fc16f92e on origin/main, authored and committed by Chris Breuer without coauthors.

#764 now has its safe local foundation: Record<any, V> retains V in the string index, and completed homomorphic any[K] templates reduce after key substitution. Checker 4,381/4,381, Program 217/217, ReleaseFast home-tsc, Zig formatting, focused Pickier, and diff integrity all pass. A focused TypeScript 6.0.2 oracle matches exactly. Unchanged Zod v4.5.2 remains 43 diagnostics with 0 removed / 0 added, so the remaining cross-file transport is still open in #764. No corpus fixture, assertion, deadline, skip, TODO, or expected outcome changed. Full Bun parity remains incomplete.

#764 follow-up: a contextual filtered-result projection matched TypeScript 6.0.2 on the complete reduced Normalize<T> oracle, but unchanged Zod API compilation crashed deterministically 4/4 with EXC_BAD_ACCESS. The candidate was rejected in full, its source changes were restored, generated cache data was deleted, and origin/main remains exactly 5fc16f92e. Crash output is not counted as progress. Full Bun parity remains incomplete.

Progress checkpoint: #768 landed on main in a1ce400a9.

Home now models Generator / AsyncGenerator defaults and lib tiers, type-side ErrorConstructor, and DOM/WebWorker atob / btoa, including Program cross-file transport and tsconfig lib / noLib / target propagation. Pinned Zod v4.5.2 core improved 43 → 39 by removing exactly those four false diagnostics with zero additions. Checker 4,382/4,382, Program 218/218, driver 189/189, ReleaseFast home-tsc, exact TypeScript 6.0.2 focused oracles, formatting, diff checks, and focused Pickier pass. Full Bun parity remains open.

Two of the three follow-ups from the previous tranche are closed out on origin/main at c6ab9aeeb. Verified on a fresh Darwin arm64 JSC debug build of that tree, unchanged directories, pinned Bun 4982b91e37 as reference:

Both now match pinned Bun exactly. cli/inspect's single remaining failure is inspect.test.ts failing to load strip-ansi, absent from ~/Code/bun/node_modules, which pinned Bun reproduces — an environment gap with no parity credit either way.

Detail worth keeping: the four cli/hot "sourcemap" failures (#767) were never a remapping bug. A rejected entry point exited even with a reloader attached, so each of those tests died on the first of its 50 error/reload cycles; the mapped columns were correct all along. #766 is also resolved, and its original diagnosis (a unix-socket transport gap) was wrong — corrected there with the measurements.

That leaves this tranche's four directories at pinned-Bun parity: js/bun/glob (by repro; its test file cannot load fast-glob), regression/issue/minify-new-array-with-if, cli/hot, cli/inspect. Full logical Bun parity remains incomplete.

TypeScript parity checkpoint ff2a44cc5 is pushed to origin/main as Chris Breuer without coauthors; #769 is complete and cross-referenced from #548.

This batch ports object-literal structural checking for annotated parameter defaults and the standard Function fields with correct ES5/ES2015 Core library gating. It preserves invalid nonempty Record-default failures and callable-to-Function destructuring compatibility. The pinned Zod v4.5.2 core oracle improves 39 -> 34 through exactly five expected removals and zero additions. Checker 4,383/4,383, ReleaseFast build 50/50, focused cache/allocation/destructuring tests, formatting, diff checks, and Pickier all pass.

The issue body checkpoint now points at ff2a44cc5. Full logical Bun parity remains incomplete; the remaining Zod diagnostics and broader Bun corpus work continue here and in #548.

TypeScript parity checkpoint 6a947ead5 is pushed to origin/main as Chris Breuer without coauthors; #770 is complete and linked from #548.

This batch ports lazy source-file forward-overload discovery and member/element flow after logical assignment. It avoids eager generic-signature lowering, retains declared indexed shapes after {} initialization, and removes four pinned Zod false positives with zero additions, moving the core oracle 34 -> 30. Checker 4,385/4,385, ReleaseFast build 50/50, focused regressions, formatting, diff checks, and Pickier pass.

The issue body checkpoint now points at 6a947ead5. Full logical Bun parity remains incomplete; the remaining Zod diagnostics and broader Bun corpus work continue here and in #548.

Pushed the next Bun/TypeScript parity checkpoint to main: fd4339d (#771).

The checker now keeps fresh literal fallbacks when forming ?? unions and computes reachable post-if identifier flow across nested, partial, missing, and exiting branches. Contextually accepted constructor assignments retain the declared non-nullish collection type instead of leaking a raw under-instantiated shape.

Validation is green: 4,387/4,387 ReleaseFast checker tests, 50/50 full JSC-enabled build steps, and pinned Zod v4.5.2 core diagnostics improve 30 -> 25 with five expected removals and zero additions.

Checkpoint advanced to 3886689 via #772.

This batch fixes iterable collection narrowing after instanceof guards and prevents broad properties such as array length from driving invalid discriminated-object narrowing. The complete checker suite passes 4,389/4,389 in ReleaseFast, the JSC build passes 50/50, and pinned Zod 4.5.2 drops from 25 to 21 diagnostics with no additions.

Checkpoint advanced to 2e1a66e via #773.

This batch preserves guarded local flow across destructuring initializers, nested loop callbacks, conditional initialization, and stable typeof-guarded callback creation. The complete checker suite passes 4,393/4,393 in ReleaseFast, the JSC build passes 50/50, and pinned Zod 4.5.2 drops from 21 to 16 diagnostics with no additions.

Checkpoint e32642e is on origin/main; #774 tracks the completed batch.

This ports direct-IIFE result context for nested tuple members and preserves explicit type-only import meaning through cross-module recovery. Full checker is 4395/4395, full JSC build is 50/50, and pinned Zod 4.5.2 drops from 16 to 13 diagnostics with the tuple error plus both false TS2749 diagnostics removed and no additions.

Boundary update: the adjacent TypeScript parity checkpoint #775/#776/#777 landed on main in d1d9abb and f9548c2, with docs in 54ad7e8 and 07c6dc4. It removes two Zod false-positive identities and restores mapped-contract Program regressions, but it does not claim or count any Bun corpus case. Full logical Bun parity under this tracker remains incomplete and unchanged by this TypeScript-only checkpoint.

Type-checker statement coverage issue #778 is complete on main across c734d2c4f, 1978095ec, a821d1ac7, and 4f72dd59d.

Home now checks returns, nested/unsafe blocks, assertions, match statements, traits, implementations, and extensions; match and trait AST ownership leaks discovered by the new negative tests were fixed. The statement switch is exhaustive, and the uncalled duplicate codegen checker was deleted so packages/types is the sole Home semantic authority.

Guarded verification: checker 12/12, codegen 12/12, direct parser 145/145, plus the broader parser-family sweep 1,058/1,058. See #778 for per-checkpoint details and exact memory evidence.

Type-checker parity progress for #779 landed directly on origin/main in four additional verified checkpoints:

• edddec83c — validate every match-expression arm, guard, binding scope, and result join
• 396966a05 — infer concrete closure function types and repair closure AST ownership
• 5c5a572c6 — build typed import namespaces and reject missing/private alias members
• 37209536d — stop treating real void as unknown in core value contexts

Together with b090da922 and bec0808bc, all three focused semantic acceptance examples in #779 now have direct regressions. #779 remains open for the remaining container/member/index/unary Void escape sites and the examples rebaseline.

All pushed commits have sole author/committer glennmichael123 <gtorregosa@gmail.com>. Checker/parser/AST/codegen gates passed under the 3,840 MB process-tree ceiling. The full native debug link was not bypassed or given a larger allowance: it was correctly stopped at 3,847–4,336 MB, so the fresh-binary examples sweep remains pending a build path that fits the safety policy.

Detailed evidence: #779 comments ending at /home-lang/home/issues/779#issuecomment-5832400691

Type-system parity rollup — #779

Five additional verified checkpoints are now on origin/main:

• daf57c410 — reject void aggregate coercions and mixed unit/value joins
• 4bf29cda4 — reject nested unknown types in arrays, references, results, maps, and other wrappers
• 5b6b0bf0e — reject unresolved value calls; fix named-call AST teardown and environment rebinding ownership
• 1f8776b8a — reject non-callable values, unknown string/array methods, and void struct construction
• bab1c830a — preserve inline struct method signatures, return types, argument types, and self-excluded arity

The focused checker suite has grown from 38 to 57 passing assertions, with zero leaks in the latest run. All five commits were pushed directly to origin/main with sole author/committer glennmichael123 <gtorregosa@gmail.com>, and each detailed checkpoint is recorded on #779.

Remaining #779 work is tracked as inherent/trait implementation method metadata, static-call cleanup, and the guarded home check examples/ rebaseline. The fixed 3,840 MB ceiling remains in force; builds serialize through the shared machine lock.

Progress on direct main under Glenn’s identity:

• 199dc188c — feat(types): enforce match exhaustiveness (#781)
• 571df3d04 — fix(codegen): trap unmatched match expressions (#781)

Together these wire HM2000 for guarded-aware statement/expression exhaustiveness across bool, enum, and Result matches; retain incompatible-arm rejection; compile boolean expression patterns; replace unmatched expression fall-through 0 with an exit-101 panic path; and fix canonical codegen string-literal ownership. Exact guarded verification: 30/30 assertion checker tests, 44/44 control-flow checker tests, and 13/13 codegen tests, all under the 3,840 MB ceiling (largest observed peak 341 MB). Details: #781.

#781 is now fully completed and closed. Final commit 0636982bd adds the bounded native executable regression proving unmatched match expressions exit 101 with the Home panic rather than returning 0. Exact guarded codegen suite: 14/14, zero leaks, 368 MB peak. The complete #781 series is 199dc188c, 571df3d04, and 0636982bd, all pushed directly to origin/main under Glenn’s identity.

CLI correctness milestone: closed #780 via ddd3b12, 1149bd9, and 755493002. Home builds now fail before output generation on parse/type/import errors, home check is strict without HOME_STRICT, kernels are type-checked, and continuation requires explicit --allow-type-errors. Fresh native-only compiler acceptance passed every listed case under the 3,840 MB guard; focused suites passed 7/7, 45/45, and 2/2. Details: #780.

Native-build progress: pushed 94176de for #798. Incremental builds now cache and restore complete native executables instead of writing empty blobs; source validation, empty-artifact rejection, byte-identical restoration, and mode 0755 are covered. Guarded cache tests pass 11/11 and real two-build CLI acceptance passed. #798 remains open for comptime execution and module-symbol prefixing.

Native-build progress: pushed 3dbd760 for #798. Comptime evaluation now has one real checker→codegen path, failures are fatal diagnostics, expression types are preserved, and ARM64 consumes evaluated scalar values. Codegen passed 15/15, type checks 45/45, and a fresh Apple-silicon home build executable returned the compile-time result 42. #798 now only retains module-symbol collision/prefixing work.

Native-build parity checkpoint: #798 has a four-file ARM64 module-symbol implementation prepared locally and compile-only verification is green (290 MB peak under guard), but it remains uncommitted because macOS 26 currently freezes every freshly generated Zig executable in _dyld_start before main—including independent one-line ARM64 and x86_64 probes. No workaround, test weakening, or unverified push was used. Runtime acceptance will resume after the host launch state recovers.

Native build correctness update: #798 is now complete and closed. The final module-isolation patch is on main as 75c02cb, following the cache artifact fix 94176de and comptime evaluation fix 3dbd760.

The new regression genuinely ran under Node/WASI and passed 1/1, decoding final ARM64 BL and x64 CALL rel32 instructions to verify left.helper() and right.helper() target distinct corresponding module-qualified symbols. The full native codegen test artifact also compiles cleanly. The separate macOS 26 dyld launch problem remains explicitly excluded from runtime claims.

Progress update: pushed 2585d31 directly to origin/main under glennmichael123, completing the mutable-array soundness portion of #788. Mutable arrays are now invariant, immutable array views remain covariant, and source-level checker coverage prevents the classic writable covariance hole. Verification: 47/47 control-flow checker tests, 12/12 subtype regression tests, and the affected edge tests pass under guarded WASI execution; the complete native control-flow test artifact also compiles. Detailed issue update: /home-lang/home/issues/788#issuecomment-5870947443

Progress update: b406444 is now on origin/main under glennmichael123. It wires Home null-safety and static bounds analyses into the real type-checker traversal for #788, with positive and negative source-level tests; the full control-flow checker suite passes 51/51 under the guarded WASI runner. Details: /home-lang/home/issues/788#issuecomment-5871064419

Progress update: eb59946 is now on origin/main under glennmichael123, activating the formerly dormant overflow analysis for #788. Provable constant arithmetic overflow now fails source checking while valid arithmetic passes; the full checker suite is 53/53. Details: /home-lang/home/issues/788#issuecomment-5871137567

Progress update: 33d5cf1 is now on origin/main under glennmichael123, routing array subtype/assignment variance through the formerly test-only variance module for #788. Direct and source-level variance checks pass. Details: /home-lang/home/issues/788#issuecomment-5871200117

Type-system parity progress: pushed d4acad00c to main, activating the dormant drop-safety analysis with a source-level use-after-move regression. The guarded full control-flow checker suite passes 54/54 (627 MB peak). Tracking remains open for the other #788 dormant analyses and inference work.

Type-system parity progress: pushed 9de9e7761 to main, replacing the duplicate no-op TypeInferencer with the maintained inference engine and adding it to the repository test graph. Verification passed 12/12 dedicated inference tests, 8/8 internal diagnostic tests, and 54/54 control-flow regressions under the 3,840 MB guard.

Bun/Home parity progress pushed directly to main under glennmichael123:

• 3a74005 removes misleading, unwired taint/information-flow prototypes after proving they had no parser/TypeChecker/build consumers.
• d5e83d6 removes the likewise isolated capability-type prototype.

The security hardening guide now labels all three as future language-design proposals rather than implemented compiler enforcement. Detailed acceptance evidence is linked in #788.

Progress update: pushed 6b2e743f0 to main for #787. Home now preserves unsafe blocks/functions in the AST and rejects raw-pointer dereference/arithmetic plus extern or unsafe calls outside an unsafe boundary. Focused checker verification is 62/62 passing, no leak report, with a guarded 580 MB peak. Follow-up work remains tracked in #787.

Pushed a second #787 batch to main: b3be98ccb. The obsolete duplicate unsafe-checker prototype is gone, the safety package now points at its real tests, and ownership of unsafe enforcement is documented in the type checker. Its focused test target compile-checks successfully under the memory guard; #787 stays open for kernel-corpus validation.

Type-checker parity progress: pushed 65cdf9d for variadic print/println typing and argument validation (#779). Verified 64/64 + 31/31 focused tests under the memory guard. Three previously failing examples now type-check cleanly; the remaining array_slice failure is a separate undefined-variable diagnostic.

Threading parity progress: pushed 4c623eb for the #803 semaphore slice. Atomic permit inspection, CAS retry correctness, and overflow signaling are implemented and verified 5/5 under the memory guard. ThreadAttr and affinity remain tracked in #803.

Additional #803 progress on origin/main: 96e154d makes Thread.spawn honor the caller allocator and validated ThreadAttr stack size. Focused mapping tests and the native module compile gate pass under the memory guard; OS round-trip, priority, and affinity remain tracked in #803.

Documentation parity progress: d73153f corrects five AOT/HIR/standalone claims under #813. Public docs now separate Home AST native codegen, JSC-hosted bundled standalones, and the still-unimplemented TypeScript HIR-to-native path, with links to the actual regression suites.

Documentation parity progress: 610504234 corrects the false data-race-freedom, worker_threads, and full-POSIX threading claims under #813, with direct tests and remaining issues linked. The verified three-file batch is pushed to origin/main.

Pushed 9ad690ab9 and completed #813. README and user-facing stdlib/memory docs now label threading and Send/Sync guarantees experimental instead of presenting them as shipped safety guarantees. Scoped Pickier and whitespace validation passed under the memory guard.

Pushed 9a5a46d4c: full array slices (array[..]) now preserve a real SliceExpr with absent bounds, closing the last known array_slice.home checker diagnostic. Parser 1,060/1,060 and focused type artifacts passed under guarded memory limits. An unrelated committed codegen-target break found during validation is isolated in #822.

Pushed bfe0d9e20: the threading facade now exposes Linux current-thread affinity with native cpuset conversion and a restore-safe round-trip regression. Native threading passes 22 tests with the Linux test skipped on macOS; the Linux artifact cross-compiles under the guard. Remaining #803 platform work is explicit.

Porting/status update: 4e4ec5d is on origin/main and advances #803 with Windows processor-group affinity.\n\nVerification was bounded and sequential: native threading 25/27 with only platform-gated skips (168 MB peak), plus successful x86_64-windows and x86_64-linux scheduler cross-compilation. The documentation explicitly preserves the remaining live-Windows, priority, macOS-tag, and OS stack-verification gaps; no unsupported parity claim was made.

Porting/status update: b5c1962 adds OS-level verification that ThreadAttr.stack_size reaches a spawned pthread.\n\nThe native macOS threading suite passes 26/28 with only platform-gated affinity skips (161 MB peak). The exact Linux pthread_attr_getstacksize path cross-compiles with libc, as does the Windows regression target. Live Linux execution remains tracked rather than being reported as complete.