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.

2026-10-29 #846 cross-reference: pushed 47fb80406 to origin/main as glennmichael123 without coauthors. It records a reproducible TypeScript 5.7.3 versus Home contextual-overload diagnostic gap tracked in #959 (TS2769 anchor, optional tuple markers, literal argument display). It does not change the runtime or increase the 99/99 passing #846 oracle count. The broader Bun test-suite objective in #66 remains open; the pinned Bun WebKit artifact is still unavailable locally, and low host memory prevented a new guarded Zig build/test run in this follow-up.

2026-10-29 #846 cross-reference: 71aa1fef0 was pushed directly to origin/main as glennmichael123, no coauthors. It fixes the related #959 TypeScript contextual-overload diagnostic chain/anchor and adds exact oracle controls; guarded test-tsc-streams passed and the direct checker executable passed 4,713/4,713. The separate #846 99-config auditor was blocked by a stale installed CLI and falling host memory, so no new broad parity claim is made. This is TypeScript checker progress, not a Bun runtime feature port: the pinned Bun WebKit artifact remains unavailable locally, and #66's 100% Bun-suite objective remains open.

2026-10-29 correction to my prior #846 cross-reference: the installed home-tsc was refreshed by a normal guarded build, and the independent #846 auditor now reports 99/99 exact TypeScript 5.7.3 config streams, zero mismatches, exit 0 on the current main revision 71aa1fef0. This removes the stale-binary verification gap. It remains TypeScript checker evidence only; the pinned Bun WebKit artifact is still absent locally, and #66's Bun runtime/test-suite parity remains open.

TypeScript admitted-JS parity checkpoint on origin/main: #964 landed in five glenn-authored commits 962dacb..2923854. Exact TS 5.7.3 CLI oracle audit now 106/106 streams; direct guarded checker 4,713/4,713. This fixes JSDoc module.exports readonly/optional projection and a false TS2309 for ordinary CommonJS property writes. The distinct function/class expando gap is tracked in #965; #846 and this broader Bun-parity issue remain open. No claim of full Bun suite parity.

TypeScript admitted-JS parity update: #965 code, fixtures, stream tests, and docs are pushed to origin/main (7ae079387..ee22b4f60, glenn-authored conventional commits). Exact TS 5.7.3 audit: 118/118 streams; guarded direct checker 4,713/4,713; full Program and CLI stream suites passed. Inferred CommonJS expandos and unchecked literal write constraints now match those controls. #966 and #967 capture remaining constructor and repeated-export gaps. The committed LSP regression has not executed because its compile twice hit the authorized 3,840 MB guard; #965/#846 stay open. This does not claim full Bun suite parity.

Three issue-linked #966 constructor differential fixtures are now on origin/main (35194c876, c83db1199, 4868b8db3) under glenn's Git identity. All pass in TypeScript 5.7.3 and still fail in Home with owner this typing and importer construct-signature diagnostics; #966 remains open. The prior 118/118 admitted-JS audit does not include these red controls, so full Bun/TS parity is still outstanding.

2026-10-29 TypeScript/JavaScript parity checkpoint linked from #846/#967: 55bc87775 preserves repeated CommonJS whole-export branch members and inline-class constructor schemas; c797c9e51 adds exact TypeScript 5.7.3 checked/unchecked controls. The admitted-JavaScript auditor passes 120/120 exact CLI streams; guarded Program and checker suites exited 0. #967 and #846 remain open for their stated remaining controls. This does not establish full Bun suite parity; that objective remains open here.

Admitted-JavaScript parity update: ae4efd3f4 completes the exact original repeated CommonJS fixture stream and adds owner-revision coverage for #967. Together with 55bc87775 and c797c9e51, the TypeScript 5.7.3 auditor passes 122/122 exact CLI streams; guarded full Program and checker suites exited 0. #967 remains open for LSP and overlapping assignment cases, #846 remains open for wider admitted-JavaScript parity, and full Bun suite parity remains open here.

TypeScript admitted-JavaScript parity checkpoint: 7aff9c03d and 20ac00a9c are pushed to origin/main as glenn without coauthors. The existing exact TypeScript 5.7.3 audit remains 122/122 streams. The new #967 CommonJS overlap controls now match all six diagnostic codes and positions across three assignment orders; exact diagnostic type wording remains open, so those controls are not counted as passing. Details and the guarded checker result are in #967; broader admitted-JavaScript work remains in #846.

TypeScript admitted-JavaScript parity checkpoint: d0418fa4f is pushed to origin/main as glenn without coauthors. The #967 repeated CommonJS overlap cases now match TypeScript 5.7.3 exactly, and the #846 exact CLI audit has advanced from 122/122 to 124/124 streams in both checkJs modes. The guarded home-tsc build succeeded. Strengthened Zig diagnostic assertions await a rerun when host memory permits; the guard refused at 28% free and was not overridden. Detailed status and remaining LSP control: #967; broader import parity: #846.

TypeScript admitted-JavaScript parity checkpoint: #967 is implemented and closed in direct origin/main commits 7aff9c03d, 20ac00a9c, d0418fa4f, 983bfdd12 (Glenn author, no coauthors). The TypeScript 5.7.3 differential now matches 124/124 exact CLI streams for the covered configurations. The guarded Program suite and dedicated LSP owner-revision test passed. The guarded full checker build command exited 0 with an internal failed command: .../test --listen=- message, which remains an unresolved test-runner ambiguity; see #846 for the detailed checkpoint. Host free memory is 29%, so further Zig runs are deferred. #846 and #966 remain open; this does not claim full Bun or TypeScript parity.

TypeScript admitted-JavaScript checkpoint: #965's LSP edit/revert test passed under the approved guard and #965 is closed; #967 remains closed. A fresh guarded TypeScript 5.7.3 comparison of #966's four CommonJS constructor owner/importer fixtures in both checkJs modes shows tsc clean in 8/8 and Home exit 2 in 8/8. #966 now records exact diagnostics and stays open for the checker and Program constructor type work. #846 remains the detailed admitted-JavaScript tracker. No full Bun parity is claimed.

Compiler-side #846/#966 progress: c150e32bb is pushed to origin/main as glennmichael123, with no coauthor trailer. Guarded home-tsc build, focused schema/Program tests, and 132/132 exact TypeScript 5.7.3 CLI oracle comparisons passed. The pinned Bun WebKit artifact is still absent on this machine and the build used system JavaScriptCore, so this is compiler/import-parity evidence rather than a runtime or native-artifact parity claim. #966 remains open for broader suite and revision checks.

TypeScript admitted-JavaScript parity checkpoint from #846/#966: 3064adfa3 and 0cfda77e1 are pushed to origin/main as glenn, with a guarded build and focused Program test passing. The TypeScript 5.7.3 exact CLI oracle audit is 134/134, including chained CommonJS prototype constructor imports in both checkJs modes. This is compiler parity evidence, not a full Bun runtime/suite claim. The locally pinned Bun WebKit artifact is still missing, so the build used system JavaScriptCore; #66 remains open for the full port and test-suite objective.

TypeScript admitted-JavaScript checkpoint from #846/#966: e0e5e0983 is pushed to origin/main as glenn, with no coauthors. Guarded home-tsc, focused checker and Program tests passed, and the exact TypeScript 5.7.3 CLI audit remains 134/134. The broader checker suite is 4,705 pass / 11 fail, with the remaining cases tracked in #968; the LSP test build hit the authorized 3,840 MB tree ceiling, so no LSP pass is claimed. This is a compiler checkpoint, not full Bun suite parity. The pinned Bun WebKit artifact remains missing locally; #66 stays open.

2026-11-02 admitted-JavaScript update: 228b129f3, d7ce02aea, and 0632dcbd6 are pushed to origin/main as Glenn without coauthors. The guarded home-tsc build matched 134/134 exact TypeScript 5.7.3 CLI oracle streams. The #966 chained CommonJS LSP edit/revert regression passed under the dedicated 3,840 MB guarded package step and was pushed. The fresh full ts_checker run completed 4,705 pass / 11 fail / 4,716 total; the remaining checked-JS constructor/prototype/JSDoc gaps are documented in #968.

TypeScript admitted-JS parity: pushed a17074639 to origin/main for #968, resolving checked-JS prototype-method instance this in two focused TypeScript 5.7.3 control cases. Both focused Home checker tests pass under the 3,840 MB guard. Full checker and CLI verification for this commit is queued until host memory recovers above the agreed threshold; prior full checker baseline was 4,705 pass / 11 fail / 4,716 total. #846 tracks this area; #966 has the chained CommonJS LSP revision regression already pushed as 0632dcbd6.

TypeScript admitted-JS parity: pushed 476a8e4eb to origin/main for #968, fixing inferred checked-JS constructor names in JSDoc. The exact TypeScript 5.7.3 control and focused Home checker test both have zero diagnostics; Home also has zero unmodeled-any recoveries in that test. The full checker suite and 134-stream CLI audit for this batch are still pending because host memory remains below the authorized 40% Zig start threshold. #846 tracks the wider work; #966's CommonJS constructor LSP edit/revert regression was previously pushed and passed.

TypeScript parity checkpoint, 2026-11-02: 801061ed5 (#968) and f39287d68 (#966, #968) are pushed to origin/main under Glenn's identity. Focused TypeScript 5.7.3 controls and Home checker tests agree for JSDoc prototype field writes and inferred versus declared nested CommonJS exports; the related CommonJS checker group passes 52/52. #846 links the admitted-JavaScript import context. Full checker, LSP revisions, and 134-stream CLI revalidation are still pending; this does not claim 100% Bun or TypeScript parity.

2026-11-02 checker/Program parity checkpoint for #968 and #966 (also #846): exact TypeScript 5.7.3 controls identified two remaining gaps. Home now emits the expected TS7008 for an empty-array constructor field used by a prototype method, but its method-local this type still hid that field in the last guarded test, producing secondary TS2551 in place of TS2531. A separate two-file LSP revision test found that Program's checked CommonJS export schema retained exports.n = {} but dropped the later exports.n.K write on import. The exact diagnostics and reproductions are recorded in #968 and #966.

Source changes and regression tests are staged locally for validation; they are not yet committed or pushed. The last guarded Zig run peaked at 1,702 MB counted tree footprint and lowered host memory to 31%. Host memory remains below the goal's 40% start threshold, so further Zig builds are paused until it recovers. No parity or full-suite pass is claimed at this checkpoint.

Checker/Program/LSP parity update: bd3371310 is verified and pushed to origin/main as Glenn without coauthors. It preserves nested CommonJS export types and refreshes importer diagnostics after edits; the staged Program, LSP, and checker CommonJS tests passed. See #966 for test details.

The checked-JavaScript constructor follow-up remains open under #968 (three focused cases passing, four TypeScript 5.7.3 differences still being fixed). The full checker suite and 134-stream CLI audit remain pending under #846. All Zig builds are sequential and guarded by scripts/run-bounded.pl with a 3,840 MB process-tree cap and a >=40% host-memory launch gate.

Checked-JavaScript parity checkpoint linked to #968/#966/#846: 90b9d6325 is pushed to main. Home's JSDoc scanner now preserves multiple tags on one line, including a constructor @template followed by its typed @param; standalone parser tests passed 23/23 and the exact Box<number> checker regression passed under the 3,840 MB guard. The first full checker run after this change was 4,716 pass / 10 fail (4,726 total), so checker/LSP/CLI parity is still open. See #968 checkpoint for the TypeScript 5.7.3 differential results and remaining verification.

2026-11-03 parity progress: #968 has two more checked-JavaScript fixes on origin/main: 224a202e9 preserves declared JSDoc index types on writes, and 450330418 matches TypeScript 5.7.3 for checked-JS globalThis writes. Both focused regressions pass under the sequential memory guard. See the #968 checkpoint for controls and measurements. The full checker suite and #846 CLI audit still need reruns on the current checkout; the last full checker result before these changes was 4,723 pass / 7 fail.

2026-11-03 checkpoint for #846/#966/#968: three conventional commits pushed to origin/main as Glenn, with no coauthors: bed4f47, 5263ed1, 0fdb9e1. Full ts_checker and ts_program suites pass; rebuilt home-tsc matches physical TypeScript 5.7.3 on all 134 admitted-JavaScript CLI oracle streams (0 mismatches). LSP revision execution is still open because its focused build hit the 3,840 MB host safety guard twice; no cap increase was used. See #968 for constructor behavior, #966 for CommonJS controls, and #846 for the oracle audit. This is TypeScript parity progress only, not a claim that the Bun corpus is at 100%.

Follow-up to the 2026-11-03 TypeScript parity checkpoint: f0ece18 adds a #968 constructor-import oracle fixture and raises the admitted-JavaScript exact CLI audit to 135/135 streams against TypeScript 5.7.3, with zero mismatches. The batch comprises four pushed, issue-linked commits authored by Glenn without coauthors. Checker and Program full suites pass. LSP execution is still awaiting a build that fits the agreed 3,840 MB memory guard. This does not close the broader Bun test-suite parity target.

Correction to the 2026-11-03 TypeScript parity checkpoint: full guarded ts_checker, ts_program, and the exact test-ts-lsp package suite all pass. The earlier LSP memory stops came from the umbrella substring filter selecting ts_lsp_server as well; the exact LSP package step peaked at 2,203 MB under the unchanged 3,840 MB cap. The admitted-JavaScript CLI oracle audit matches TypeScript 5.7.3 on 135/135 exact streams. Constructor-specific #968 and CommonJS constructor #966 are closed; #846 stays open for wider admitted-JavaScript coverage. Bun test-suite parity and the pinned WebKit artifact remain open here.

TypeScript parity progress on origin/main: ecbffd7 (#963), e52365e and 7efc33f (#960/#846), authored as Glenn without coauthors. Direct checker suite: 4,733/4,733; pinned TypeScript 5.7.3 exact CLI streams: 138/138. Remaining ReadonlyArray surface, aggregate call-site audit, and Program/LSP gates are tracked in #960/#963/#846. Bun/runtime parity in this umbrella remains open.

TypeScript parity progress pushed directly to origin/main as Glenn: 26c6a4c (#963), 256d787 (#960/#969), d044874 (#960/#846), and 347f3ec (#969). Direct checker suite passed 4,735/4,735. The 139-stream admitted-JS audit passed, and the new #969 control matches TypeScript directly; aggregate 140-stream and Program/LSP gates for this batch remain pending the guarded build. Bun/runtime parity remains open.

Final gates for the current batch: direct checker 4,735/4,735; TypeScript 5.7.3 exact CLI audit 140/140; guarded Program step passed; guarded exact LSP step passed; targeted pickier passed. Latest pushed main commit: 3f68c9b. The checkout has only pre-existing unrelated untracked files. Keeping this issue open for the remaining behavior noted above.

Pushed 297d063 to origin/main as Glenn. Concrete [Symbol.unscopables] writes now resolve the readonly property before index-signature diagnostics, for both imported mutable and readonly arrays. The checked-JS fixture matches TypeScript 5.7.3 exactly: three TS2540 diagnostics in source order and no cascading TS2322/TS2542. Direct checker: 4,736/4,736; expanded exact-stream audit: 141/141; guarded Program and LSP steps passed; pickier passed. Remaining #960 work includes symbol identity in keyof, complete member/error rendering, and augmentation behavior.

TypeScript parity update: 4f6f106 is pushed to main for #963. Aggregate type flags no longer select type-parameter payloads in several default/inference readers; direct checker run passed 4,736/4,736. Following #960, #963, #969, and #846 for remaining work. Exact CLI audit is pending a memory-safe home-tsc rebuild.

Pushed #963 parity commits 4f6f106 and e5a73e3 directly to main as Glenn. Aggregate flags cannot select type-parameter payloads in the repaired default, keyof, mapped, JSX, overload, variance and const paths. Guarded final gates: checker 4,736/4,736; TypeScript 5.7.3 exact CLI audit 141/141; Program and LSP passed. Continuing #960/#963/#969 and admitted-JS #846.

ReadonlyArray parity: pushed #960 commits d370b25 and d145f4d to main, covering declaration-order [Symbol.unscopables] mapped flags and exact TS2339 shape diagnostics. TypeScript 5.7.3 checked-JS control and 142/142 CLI streams passed before a final name-set refactor. Post-refactor Zig gates await the 40% host-memory admission level. New #970 isolates unique-symbol identity in keyof; #971 records large inline-object diagnostic elision. #963 batch was already fully green.

Final guarded gates for #960 commits d370b25 and d145f4d are green: checker 4,736/4,736, exact TypeScript 5.7.3 CLI streams 142/142, Program and LSP passed. Both commits are on origin/main under Glenn with no coauthors. New #970 tracks unique-symbol keyof identity and #971 tracks inline-object TS2339 elision; #960/#963/#846 remain active parity work.

Additional #963 commit a83023b is pushed to origin/main under Glenn. It guards generic binder/default/label payload reads and adds an aggregate offset-collision regression. The previous #960 batch remains fully green (checker 4,736/4,736, CLI 142/142, Program/LSP passed). The new #963 commit is awaiting Zig tests because host memory is 31–34%, below the agreed 40% admission threshold; this is recorded on #963. Goal remains active.

TypeScript parity follow-up: reproduced a concrete #963 conditional-inference gap against TypeScript 5.7.3, and recorded the exact diagnostic/control in #963. The fix and checker/CLI regressions are drafted locally. Build verification is waiting for the established 40% host memory gate before commit and push.

TypeScript parity checkpoint: #963 union/intersection infer controls reached 4,738/4,738 direct checker tests, and the expanded exact CLI audit isolated one remaining conditional false-branch mismatch (143/144). The semantic correction and plain-diagnostic formatter alignment are drafted; final checker/CLI/Program/LSP verification and push wait for the agreed 40% host-memory Zig admission gate. Details: #963.

TypeScript parity: the current local #963/#846 batch reached 144/144 exact TypeScript 5.7.3 CLI streams after a fresh guarded home-tsc build. Full checker, diagnostics, Program, and LSP verification on the latest source remain queued behind the 40% memory gate; no unverified code has been pushed. Details: #963.

TypeScript parity progress pushed directly to origin/main: 005769a (#963 aggregate infer matching), ee23b3b (#846/#963 plain diagnostic related-info parity), 37f34d9 (#960/#971 object-shape elision), all authored/committed by Glenn with no coauthors. Guarded final gates: checker 4,739/4,739; diagnostics 25/25; Program 473/473; LSP 144/144; exact TypeScript 5.7.3 CLI streams 145/145. #971 closed; #960/#970, #963, and #846 remain open for their wider acceptance scope.

TypeScript parity checkpoint linked to #970/#960/#846/#963: 080a6c8d6, f29126d47, and 654c354cb are pushed to origin/main as Glenn, without coauthors. Nominal unique-symbol keys now survive arrays, computed interfaces, mapped utility types, imported Program schemas, indexed access and LSP rendering; #970's stated TypeScript 5.7.3 acceptance is complete. Evidence: 148/148 exact CLI streams, 4,742/4,742 checker, 473/473 Program, 144/144 LSP, sequential guarded runs capped at 3,840 MB. This is a TypeScript subsystem checkpoint, not a full Bun-corpus run or a claim of 100% Bun parity. #66 remains open.

TypeScript/Bun parity progress pushed to origin/main: #970 unique-symbol work (080a6c8, f29126d, 654c354), #963 type-parameter identity guard (c20f0e1), and #960 Array/ReadonlyArray keyof methods (5e3df0a). Latest combined validation: checker 4,742/4,742; Program 473/473; LSP 144/144; TypeScript 5.7.3 exact CLI audit 149/149. Remaining parity work is tracked in #960, #963, and #846.

Pushed #963 checker identity fix c465c60 to origin/main as Glenn. Aggregate type-parameter flags now traverse constituent unions/intersections where required and cannot select unrelated parameter payloads in the audited paths. Focused regression, full checker, Program, LSP, and fresh home-tsc build passed; TypeScript 5.7.3 exact CLI audit matched 149/149 streams. Continued parity work remains in #960, #963, and #846.

TypeScript parity progress: d82713c is pushed to origin/main as Glenn, adding direct type-parameter checks for iterable array unions and a matched TypeScript 5.7.3 CLI oracle (#963, #846). Focused and full checker suites passed. Program, LSP, and expanded exact-stream validation remain queued behind the agreed 40% host-memory gate. The generic array-union callback gap discovered during this work is tracked separately in #972 and linked to #960.

TypeScript parity checkpoint: 1eb43a5ab is pushed to origin/main as Glenn (no coauthors), closing the generic union callback gap #972 discovered through #960/#963/#846. The TypeScript 5.7.3 control for T | readonly string[] now matches Home exactly, including callback and result types and readonly assignability detail. Fresh home-tsc passed 151/151 admitted-JavaScript exact-stream configs; focused/full checker, Program, and LSP suites passed sequentially under the 3,840 MB guard. The broader Bun parity work in #66 remains open.

TypeScript parity checkpoint: pushed 8211512 directly to origin/main as Glenn, with no coauthor. JSX fallback now traverses aggregate type-parameter members safely (#963); declared-interface payload reads require direct identity. Focused/full checker, Program, LSP, fresh home-tsc, and 151/151 exact TypeScript 5.7.3 CLI streams passed under the memory guard. #960, #963, and #846 remain open for their broader acceptance scope.

TypeScript parity checkpoint linked to #846/#960: 801194f82 is pushed to origin/main as Glenn, with focused and full checker verification under the 3,840 MB guard. Follow-up semantic and exact-stream gaps are #973 (FlatArray depth), #974 (JSDoc union precedence), and #975 (diagnostic union order). The latter two source fixes are still in the checkout, not claimed complete; full Program/LSP and expanded exact-stream runs are pending memory-safe admission.

Related TypeScript/checked-JavaScript parity work on main: 4be9ed980 and b214ad08c fix default-depth flat() inference for imported readonly/mutable union arrays while preserving indexed objects, and add TypeScript 5.7.3 controls. Guarded checker, Program, and LSP suites pass. The admitted-JavaScript exact-stream audit is 153/155, with only #975 union display order differing. #973 still tracks explicit flat(depth) semantics. This update is for the TS surface; it does not imply the Bun corpus is fully passing.

TypeScript/checked-JavaScript parity update on main: df92bb1c8 fixes an aggregate type-parameter union return that Home accepted but TypeScript 5.7.3 rejects, with a matched exact-stream fixture (#963). Guarded full checker, Program, and LSP suites passed after the final patch. The expanded admitted-JavaScript oracle is 154/156 exact; the two remaining differences are #975 union display order. This is a TypeScript surface update and does not claim the Bun corpus is fully passing. #973 now documents matched controls for explicit flat(0), flat(2), and interfaces extending ReadonlyArray.

TypeScript parity update: pushed ee01d1d (test(ts), #960) directly to origin/main as Glenn. The new exact TypeScript 5.7.3 fixture distinguishes a true ReadonlyArray extension from an object with only length and a numeric index. Home currently accepts the incomplete object and rejects valid flattening of the derived interface. The fixture is in the expanded audit, so this regression is visible until the checker relation is fixed. Related work: #960, #973, #846; #963 union return-member fix remains in df92bb1.

The local 1.5 GB .zig-cache was pruned as requested. Host memory availability is currently below the agreed 40% build admission threshold, so no Zig build was started during this update.

The guarded expanded exact-stream audit completed after ee01d1d: 154/157 configs match TypeScript 5.7.3 exactly. The three mismatches are the two existing flat.ts union display-order cases (#975) and the new structural ReadonlyArray fixture (#960). Peak guarded tree footprint was 247 MB; host memory low-water was 26%. No Zig build was started below the 40% admission threshold.