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.

TypeScript parity progress landed on main in 85b2ffa32, tracked in #832. Exact conformance slice 1 is now 1,000/1,000, bringing revalidated slices 0-1 to 2,000/2,000; baseline-aware conformance remains 586/586 and the full checker suite passes. The batch also fixes merged class/interface heritage, inherited generic static signatures, and checked-JS ambient type import/export diagnostics.

Progress checkpoint: bebca5b is pushed directly to main and tracked in #832. This is TypeScript-front-end parity work, not a Bun-runtime completion claim. The revalidated exact prefix advanced to 2,200/2,200 after closing three checked-JS checker gaps; the full checker and exact 2000-2199 partition pass. Heavy verification remained serial and memory-bounded.

Coordination checkpoint: b7f93ddea875716c51ff11778c2d35abd20562ec is now on main. It adds a serial, machine-locked exact-conformance runner with explicit time/memory bounds and records the verified TypeScript prefix at 2,800/2,800; details are linked in #832 and #782.

No Bun corpus pass-count change is claimed by this TypeScript-focused commit. The same one-heavy-process discipline and 3,840 MB ceiling remain in force for the next Bun parity batches tracked here.

Coordination update: Chris's #782 is now completed and closed by df4cfa251b9181e524258858e7c3e8af519a738f, which adds real-process HM diagnostic acceptance for home-tsc and home lsp. This was a five-file direct-to-main commit under the requested identity. No Bun corpus pass-count change is claimed by this TypeScript-focused checkpoint; Bun parity work here remains open.

TypeScript soundness progress landed on main in 3686d78: Home now has a distinct checker-internal unmodeled recovery type in reserved TypeId 15, with relation semantics matching any. This is the first verified slice of #783 and removes the representation blocker for tracing checker-synthesized any without changing TypeScript relation behavior. Full ts_checker and HIR package suites passed under the memory guard; #783 remains open for fallback migration and count/ratchet work.

TypeScript parity progress on main: f22aa8c now reports checker-synthesized any provenance through opt-in HM9002 diagnostics without affecting default TypeScript diagnostics. The implementation records origin nodes rather than propagated types, and the normal conformance gates remain 16/16, 86/86, and 586/586. This advances #783; Zod measurement, a count ratchet, and further proven fallback migrations remain.

TypeScript provenance work from #783 landed directly on main in two three-file commits: c3b1689cf adds the byte-pinned Zod 4.5.2 HM9002 ratchet and its hermetic controls; afaca5fa0 wires it into the existing conformance workflow and documents the result. The full 106-file production graph verifies at 0 checker-synthesized recovery diagnostics under a zero-growth CI ceiling, while its 198 ordinary TS diagnostics remain explicitly tracked as unresolved parity work. Both commits were authored/committed solely as glennmichael123 <gtorregosa@gmail.com> and pushed to origin/main.

Progress update: pushed 49bd3f2 directly to main under glennmichael123. The 3-file batch traces diagnosed TS2589/TS2590/type-level TS2799 recovery paths instead of silently synthesizing ordinary any, while preserving the original diagnostics. Verified with 4,430/4,430 checker tests and the full 1,432-case conformance run; the 106-file Zod gate remains at 0 HM9002. No PR or worktree was used.

Cross-track checkpoint (no new Bun-runtime parity claim): d67ece5 was pushed directly to main under the requested author identity. This batch fixes TypeScript optional-parameter diagnostic aliases and advances the revalidated exact TS prefix to 2,940/2,940 while retaining 4,430/4,430 checker tests. The next TS window is still unresolved after a guarded 900-second timeout. Bun runtime scope in this issue remains open and unchanged by this commit.

Cross-track TypeScript progress landed directly on main in c7bf501.

This is not a Bun-runtime parity closure claim. It fixes recursive TypeScript checker/program behavior that affected the shared repository test workload:

• full exact leading TypeScript prefix now passes 2,960/2,960
• the formerly timing-out 21-file async-generator fixture completes
• full ts_program, full ts_checker, and normal conformance gates pass under the 3,840 MB supervisor

Detailed implementation and measurements: #814 comment /home-lang/home/issues/814#issuecomment-5954764549

Bun parity work tracked by this issue remains open and should continue from its runtime-specific inventory.

Cross-track checker stability update: daca8fc landed directly on main and closed #834.

The original zig-js representative benchmark self-test now exits 0 with its OK marker instead of crashing in the TypeScript checker. Complete checker and normal conformance gates pass under the 3,840 MB supervisor.

This is not a Bun-runtime parity closure claim; #66 remains open for its runtime-specific inventory.

Cross-track TypeScript soundness progress landed directly on main in 1060144.

Two proven checker-synthesized catch-annotation recovery paths now carry HM9002 provenance under the opt-in flag, while normal TypeScript diagnostics remain unchanged. The pinned 106-file Zod ratchet stays at 0 HM9002 and normal conformance remains green.

This does not close or reclassify any Bun-runtime item in #66; the runtime parity inventory remains open.

TypeScript correctness/provenance progress landed directly on main in 192ee78, linked to #783.

TS7009 implicit-constructor any recoveries are now distinguishable as checker-synthesized Primitive.unmodeled origins without changing TypeScript compatibility. Complete ts_checker and normal conformance gates remain green (16/16 smoke, 86/86 category, 586/586 baseline-aware), and the byte-pinned 106-file Zod 4.5.2 ratchet remains 0 HM9002 against a zero ceiling. All heavy gates ran serially below the 3,840 MB cap.

This is a TypeScript checker provenance improvement, not a claim that Bun runtime parity or #66 is complete.

TypeScript provenance progress landed directly on main in 39fe6c4, linked to #783.

Both TS7015 numeric-index mismatch recovery paths now preserve their TypeScript-compatible any-like behavior while exposing the checker origin as Primitive.unmodeled. The complete checker and normal conformance gates remain green (16/16 smoke, 86/86 category, 586/586 baseline-aware), and the byte-pinned 106-file Zod 4.5.2 ratchet remains 0 HM9002 against a zero ceiling. All heavy gates ran serially below the 3,840 MB cap.

This is a TypeScript checker provenance improvement, not a claim that Bun runtime parity or #66 is complete.

TypeScript provenance progress landed directly on main in 424da31, linked to #783.

Every TS7017 global-this missing-property recovery path now preserves TypeScript-compatible any-like behavior while exposing its checker origin as Primitive.unmodeled. The complete checker and normal conformance gates remain green (16/16 smoke, 86/86 category, 586/586 baseline-aware), and the byte-pinned 106-file Zod 4.5.2 ratchet remains 0 HM9002 against a zero ceiling. All heavy gates ran serially below the 3,840 MB cap.

This is a TypeScript checker provenance improvement, not a claim that Bun runtime parity or #66 is complete.

Progress update: 2e15da2 is on origin/main with the TS7052/TS7053 implicit element-access provenance migration. It is a coherent 3-file direct-main commit under glennmichael123 with no coauthors. Guarded verification passed the focused TS705x family, full checker, normal conformance at 16/16 + 86/86 + 586/586, stripped ReleaseFast compiler build, and the pinned 106-file Zod HM9002 ratchet at 0/0. Full metrics and scope are recorded in docs/docs/TS_PARITY_PLAN.md and summarized in README.md.

Progress update: e2b727c is on origin/main with the TS2683 implicit-this recovery provenance migration. It is a direct-main conventional commit under glennmichael123, no coauthors, exactly 3 files. Guarded verification passed the broader this family, the TS7009+TS2683 checked-JS interaction, the complete checker, normal conformance at 16/16 + 86/86 + 586/586, a fresh stripped ReleaseFast compiler build, and the pinned 106-file Zod HM9002 ratchet at 0/0. Measured details are in README.md and docs/docs/TS_PARITY_PLAN.md.

Another #783 provenance batch is verified and pushed directly to main as 4da3d4a. TS2331 namespace-body and TS2332 enum-initializer this recoveries now record HM9002 origins only when the result is actually any-like; concrete TS2465/TS2816 paths remain excluded. Gates: checker 4,439/4,439, conformance 16/16 + 86/86 + 586/586, stripped ReleaseFast build, and pinned 106-file Zod ratchet 0/0. The conventional commit changes exactly 3 files and is authored/committed by glennmichael123 without coauthors.

Pushed another verified #783 batch directly to main as 40d4c7d. Diagnosed typeof-this any fallbacks for TS2331, TS2332, TS2465, TS2683, and TS2816 now retain HM9002 provenance while permitted or concrete query results remain untouched. Serial gates passed: complete checker, conformance 16/16 + 86/86 + 586/586, stripped ReleaseFast build, and pinned 106-file Zod ratchet 0/0. The conventional commit contains exactly 3 files and is authored/committed by glennmichael123 without coauthors.

Pushed a third verified #783 batch to main as 8e8d7de. TS2350 and TS2679 new-expression any fallbacks now retain HM9002 provenance, including the strict-false checked-JS early path, while valid constructors remain zero-origin controls. Serial gates passed: complete checker, conformance 16/16 + 86/86 + 586/586, stripped ReleaseFast build, and pinned 106-file Zod ratchet 0/0. Conventional commit, exactly 3 files, authored and committed by glennmichael123 without coauthors.

TypeScript parity progress: 731e7cba2 landed directly on main for #783.

Home now records TS2351 non-constructable new fallbacks as Primitive.unmodeled, including TS2759/TS2760/TS2761/TS2762 union/overload chains and TS7038 namespace-import construction, while explicit-any unions remain an ordinary-any negative control. The complete checker, 586/586 baseline-aware conformance gate, cold stripped ReleaseFast build, and byte-pinned 106-file Zod zero-HM9002 ratchet all pass under the 3,840 MB supervisor. README and the parity plan were updated with the measured result.

TypeScript parity progress: a4c99a24c landed directly on main for #783.

Home now preserves provenance for any-like TS2749 value-used-as-type recoveries across direct, generic, qualified, imported, and checked-JSDoc paths, while concrete narrowed results and valid type/value merges remain unmarked. The complete checker passes 4,442/4,442; normal conformance remains 16/16 smoke, 86/86 category, and 586/586 baseline-aware; stripped ReleaseFast builds; and the byte-pinned 106-file Zod ratchet remains 0 HM9002 under the 3,840 MB supervisor. README and the parity plan include the measured checkpoint.

TS recovery-provenance progress: 7585e471d4bab720cfb81111554a82ff002fc788 is now on origin/main, tracing both diagnosed TS2558 class-component JSX arity fallback paths without changing valid or intrinsic JSX behavior. Full checker, conformance, stripped ReleaseFast, and the pinned 106-file Zod ratchet all passed under the 3,840 MB guard; Zod remains exactly 0/0 HM9002. Detailed evidence: /home-lang/home/issues/783#issuecomment-5995312264. Issue #783 remains open for the next proven fallback family.

Another #783 recovery-provenance slice is on origin/main in 901c0d853a08ae69582994fedbf03b4a634ea1eb. It traces all three diagnosed TS2694 CommonJS import-member any-like continuations and prevents duplicate HM9002 origins when one JSDoc source position is lowered through multiple HIR anchors. Full checker, conformance, stripped ReleaseFast, and the pinned Zod ratchet passed under the 3,840 MB guard; Zod remains 0/0 across 106 files. Detailed evidence: /home-lang/home/issues/783#issuecomment-5995836857.

Import-namespace recovery provenance is now on origin/main in 02de35cdf74c9506d801e08e2f242ff2aa817830. TS1339 and TS1340 bare module-namespace misuse continuations are traced, while both valid mirror cases remain zero-HM9002 controls. Full checker, conformance, stripped ReleaseFast, and the pinned 106-file Zod ratchet passed under the 3,840 MB guard; Zod remains 0/0. Detailed evidence: /home-lang/home/issues/783#issuecomment-5996200065.

TS2693 typeof recovery provenance is now on origin/main in 3fab9775912ed49f73db384a1a13e83b2081e86b. Ten primitive/type keywords and unbound generic type parameters now retain their any-like recovery origin; a contextual generic value binding remains a zero-HM9002 control. Full checker, conformance, stripped ReleaseFast, and the pinned 106-file Zod ratchet passed under the 3,840 MB guard; Zod remains 0/0. Detailed evidence: /home-lang/home/issues/783#issuecomment-5996557906.

TypeScript parity checkpoint pushed directly to main in 9a1c2b741 (feat(ts): trace unresolved typeof recoveries (#783)). TS2304 any-like continuations from parser-preserved typeof null and genuinely missing dotted roots now retain HM9002 provenance, with valid/resolved zero-origin controls.

Serial guarded gates are green: complete checker suite; conformance 16/16, 86/86, 586/586; stripped ReleaseFast build; byte-pinned 106-file Zod ratchet still exactly 0 HM9002. Detailed tracking: #783 and /home-lang/home/issues/783#issuecomment-5997150275.

Another TypeScript parity checkpoint is on main: d19aaea94 (feat(ts): trace type-only value recoveries (#783)). TS1361/TS1362 any-like identifier continuations now retain HM9002 provenance, and the call checker now consistently treats the unmodeled sentinel as any-like so provenance does not introduce spurious TS2349 diagnostics.

All serial guarded gates are green: complete checker; conformance 16/16, 86/86, 586/586; stripped ReleaseFast; pinned 106-file Zod remains exactly 0 HM9002. Detailed evidence: #783 and /home-lang/home/issues/783#issuecomment-5997654904.

TypeScript parity checkpoint 2f0ff8bf1 is now on main (feat(ts): trace namespace value recoveries (#783)). TS2708 any-like continuations now retain HM9002 provenance for direct namespace-only expressions, namespace-qualified heritage/member access, and type-only import-equals typeof queries, with runtime namespaces and export = N kept as zero-origin controls.

All serial guarded gates are green: complete checker; conformance 16/16, 86/86, 586/586; stripped ReleaseFast; pinned 106-file Zod remains exactly 0 HM9002. Details: /home-lang/home/issues/783#issuecomment-5998069168.

TypeScript provenance checkpoint pushed to main: f82d12f65 (feat(ts): trace unresolved value recoveries (#783)).

TS2304/TS2552 unresolved value identifiers now retain Primitive.unmodeled provenance without changing permissive behavior. The integration fixed two exact-any consumers (instantiation-expression TS2635 suppression and for-of computed-key TS2538 continuation). Full checker is 4,450/4,450; conformance is 16/16, 86/86, and 586/586; stripped ReleaseFast builds; the byte-pinned Zod 4.5.2 graph remains 0 HM9002 across 106 production files. Memory peaks stayed below the 3,840 MB guard. Details are tracked in #783 and the parity plan.

TypeScript provenance checkpoint pushed to main: c8b0f8e0f (feat(ts): trace unknown object recoveries (#783)).

The four any-like object-operation continuations from unknown now retain provenance: member access, element access, calls, and construction. TS18046 and TS2571 behavior is unchanged, explicit any remains zero-origin, checker passes 4,453/4,453, conformance remains 16/16 + 86/86 + 586/586, ReleaseFast builds, and the byte-pinned Zod graph remains 0 HM9002 across 106 files. All heavy runs stayed below the 3,840 MB guard. Details remain in #783 and the parity plan.

TypeScript provenance checkpoint pushed to main: af4ef8449 (feat(ts): trace getter call recoveries (#783)).

TS6234 zero-argument getter calls now retain Primitive.unmodeled at the recovered call result while preserving the diagnostic anchor and TS2757 chain. Instance/static cases record one origin; valid getter/setter compatibility remains zero-origin. Checker passes 4,453/4,453, conformance remains 16/16 + 86/86 + 586/586, ReleaseFast builds, and Zod remains 0 HM9002 across 106 files. All heavy runs stayed below the 3,840 MB guard.

TypeScript provenance checkpoint pushed to main: b9152be87 (feat(ts): trace invalid call recoveries (#783)).

TS2348/TS2349 invalid calls now retain Primitive.unmodeled, while declared-any calls remain zero-origin. The migration also corrected an exact-any computed-destructuring check so diagnosed invalid-call keys preserve TS2538. Checker passes 4,455/4,455, conformance remains 16/16 + 86/86 + 586/586, ReleaseFast builds, and Zod remains 0 HM9002 across 106 files. All heavy runs stayed below the 3,840 MB guard.

TypeScript parity progress: 2e35d99 landed directly on main under #783. Home now retains unmodeled-any provenance for the stable TS2550, TS2551, TS2576, and TS2812 member-access recoveries, with valid-member and declared-any controls. Full checker and all 16/86/586 conformance gates pass, ReleaseFast builds, and the pinned 106-file Zod ratchet remains exactly 0 HM9002. Generic TS2339 was intentionally deferred after the ratchet exposed its speculative emit/remove lifecycle; details: /home-lang/home/issues/783#issuecomment-6000388813

Bun/TypeScript parity progress: 024fa68 landed directly on main under #783. Invalid super() calls diagnosed by TS2335, TS2337, or TS17005 now preserve checker-synthesized any provenance, while a valid derived-constructor super() remains void. Full checker and all 16/86/586 conformance gates pass, ReleaseFast builds, and the pinned 106-file Zod ratchet remains exactly 0 HM9002. Details: /home-lang/home/issues/783#issuecomment-6000643819

TypeScript parity checkpoint: 666666c landed directly on main under #783. TS2815 class-field/static-block arguments recoveries now preserve unmodeled-any provenance, and Home rules run after deferred diagnostic cleanup while remaining before source directives. Full checker and all 16/86/586 conformance gates pass; ReleaseFast builds; pinned 106-file Zod remains exactly 0 HM9002. Details: /home-lang/home/issues/783#issuecomment-6015173919

Parity progress: 4236a2f was pushed directly to origin/main and is tracked in #783.

This slice fixes the missing TS17011/TS2336 checks for bracketed super[expr] in derived constructors and preserves diagnosed invalid-super property recoveries as Primitive.unmodeled without changing valid accesses. Full checker is 4,458/4,458, conformance is 16/16 + 86/86 + 586/586, ReleaseFast builds, and the pinned 106-file Zod ratchet remains 0 HM9002. See #783 for focused diagnostic and memory-guard details.

Parity progress: 03abd47 was pushed directly to origin/main and is tracked in #783.

TS2538 value-level element-index failures now retain Primitive.unmodeled only when the completed access remains any-like. Bigint, object, and function indices are covered; valid any and numeric array indices remain concrete controls. Full checker is 4,459/4,459, conformance is 16/16 + 86/86 + 586/586, ReleaseFast builds, and the pinned 106-file Zod ratchet remains 0 HM9002.

Parity progress: c161da3 was pushed directly to origin/main and is tracked in #783.

TS2698 object-literal spread failures now retain Primitive.unmodeled only on the any-like literal that owns the recovery. Nested invalid spreads do not relabel their containing object, and valid object or declared-any spreads remain clean controls. Full checker is 4,460/4,460, conformance is 16/16 + 86/86 + 586/586, ReleaseFast builds, and the pinned 106-file Zod ratchet remains 0 HM9002.

TypeScript soundness progress for #783 landed directly on origin/main in 87d6d830b.

This checkpoint traces checker-synthesized implicit yield results (TS7057) without changing generator TNext inference. Full checker and conformance gates pass, ReleaseFast builds under the 3,840 MB ceiling, and the pinned Zod provenance ratchet passes at the reviewed 3/3 ceiling.

A controlled exact-HEAD A/B also corrected the prior stale Zod zero claim: all three existing sites are TS2698-linked object-spread recoveries already present at c161da3be; Zod's production graph has no yield expressions, so this TS7057 slice adds no corpus sites. Details and exact locations are documented in the README and TypeScript parity plan.

Commit: 87d6d830b feat(ts): trace implicit yield recoveries (#783)

TypeScript parity progress: pushed 1f5fe5aee to main, closing another concrete #783 provenance gap.

TS18013 private-member access recoveries are now distinguishable from user-authored any, with TS18014 and valid own-class access preserved as concrete controls. Full checker and conformance gates pass, ReleaseFast builds, and the pinned Zod graph remains at its reviewed 3/3 HM9002 ceiling.

Detailed verification is recorded on #783 and in README.md / docs/docs/TS_PARITY_PLAN.md.

TypeScript parity progress: pushed 65b08af95 directly to main.

Four more checker-injected member-access any fallbacks are now distinguishable under #783, with focused controls and the complete checker/conformance/ReleaseFast gates green. The expanded signal exposed four existing Zod false-never recoveries, now isolated in #835 with no diagnostic suppression or widening workaround permitted. The pinned graph is reviewed and ratcheted at exactly 7 HM9002.

TypeScript parity progress landed directly on main in 948e7809d (fix(ts): preserve negative typeof flow (#835)).

This fixes the source-independent any | boolean negative-typeof plus chained-discriminant flow defect. On the frozen 106-file Zod 4.5.2 graph, Home removes exactly four false TS2339 errors and their four HM9002 recoveries: ordinary diagnostics improve 200 → 196 and the provenance ratchet returns 7 → 3. Complete checker, conformance, stripped ReleaseFast, two frozen-graph runs, and ratchet controls pass under the 3,840 MB supervisor.

TypeScript parity progress: e3fca4f98 landed directly on origin/main for #783.

Home now traces TS2304/TS2583 Generator / AsyncGenerator missing-library fallbacks as checker-synthesized any, and local/imported generic declarations correctly shadow the ambient built-ins under reduced libraries. Full checker and conformance gates pass; stripped ReleaseFast builds within the 3,840 MB ceiling; the byte-pinned Zod graph remains at 196 ordinary diagnostics and exactly 3/3 HM9002 in two serial runs. See #783 for the complete evidence.

TypeScript provenance progress: 36b4a1725 landed directly on origin/main for #783.

Home now distinguishes the TS2314 paths that truly synthesize any (bare built-in Array and checked-JSDoc generic typedef arity recovery) from ordinary TS2314 continuations that retain a modeled generic body. Full checker, conformance, and stripped ReleaseFast gates pass under the 3,840 MB ceiling; the byte-pinned Zod graph remains stable at 196 ordinary diagnostics and exactly 3/3 HM9002 in two serial runs. See #783 for full evidence.

TypeScript parity progress: b581226 is pushed directly to main and closes another #783 provenance slice. Uppercase Null/Undefined generic-argument fallbacks now trace genuine any substitution without mislabeling direct diagnostics or user declarations.

Verification is green: checker 4,468/4,468; conformance 16/16 smoke, 86/86 category, 586/586 baseline-aware; stripped ReleaseFast build; pinned Zod remains 196 TS diagnostics and 3/3 HM9002 across two serial guarded runs. README and the parity plan include the measured checkpoint.

TypeScript parity progress: 110143722 is pushed directly to main and advances #783. Excluded-DOM Element/Document type fallbacks now expose genuine checker-synthesized any provenance, and local declarations deterministically shadow the ambient names.

Verification is green: checker 4,468/4,468; conformance 16/16 smoke, 86/86 category, 586/586 baseline-aware; stripped ReleaseFast build; pinned Zod remains 196 TS diagnostics and 3/3 HM9002 across two serial guarded runs. README and the parity plan include the measured checkpoint.

TypeScript parity update: pushed 43f4f45 directly to main for #783. Verified unavailable-library value recoveries now retain unmodeled-any provenance for TS2583, TS2584, and direct non-DOM window TS2304 paths, with once-per-node TS2583 reporting. Full checker remains 4,468/4,468; conformance remains 16/16, 86/86, and 586/586; ReleaseFast and two deterministic pinned-Zod runs pass. TS2585 Promise / Symbol paths remain explicitly unclaimed pending a path that owns the final recovered type.

TypeScript parity checkpoint: 2d71c5b is now on origin/main for #783. Unresolved bare-type TS2304 and invalid intrinsic-alias TS2795 any fallbacks now retain provenance, while canonical compiler intrinsic aliases remain diagnostic-free. Full checker and all normal conformance gates pass; serialized stripped ReleaseFast passes at 3,021 MB; two pinned-Zod runs remain deterministic at 196 TS diagnostics and 3/3 HM9002. The 3,840 MB memory policy remained enforced.

TypeScript parity update: 4b1178b is on origin/main for #783. Parameterized type-reference recovery now distinguishes TS2304 unresolved owners from TS2749 value-only owners and retains provenance for both without relabeling declared generic or built-in controls. Full checker, normal conformance, serialized stripped ReleaseFast, and deterministic pinned-Zod gates pass under the 3,840 MB policy.