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.

Checkpoint pushed: 2be2334 (fix: port bun yaml tabbed plain continuations).

Frontier update:

• Copied Bun corpus gate js/bun/yaml/yaml-test-suite.test.ts now advances from yaml-test-suite/HS5T to yaml-test-suite/J3BT.
• Change size: 13 harness lines flipped total, 12 insertions and 1 deletion in packages/home_test/src/corpus_runner.zig.
• Behavior ported: leading tabs remain rejected as indentation unless they continue an existing plain root scalar, matching Bun HS5T folding behavior.

Verification:

• env HOME_BUN_CORPUS_FULL=1 HOME_BUN_CORPUS_PROGRESS=1 HOME_BUN_CORPUS_START=739 HOME_BUN_CORPUS_LIMIT=1 timeout 1200s ./pantry/.bin/zig build test -Dfilter=home_test --global-cache-dir .zig-cache/global --summary failures
• Result: expected focused gate failure moved to yaml-test-suite/J3BT, where tabs inside quoted scalars are currently normalized to spaces.

Checkpoint pushed: 1831cef (fix: port bun yaml quoted tabs).

Frontier update:

• Copied Bun corpus gate js/bun/yaml/yaml-test-suite.test.ts now advances from yaml-test-suite/J3BT to yaml-test-suite/JHB9.
• Change size: 22 harness lines flipped total, 21 insertions and 1 deletion in packages/home_test/src/corpus_runner.zig.
• Behavior ported: tabs used as YAML separation spaces are still expanded, while tabs inside quoted scalar text are preserved like Bun.

Verification:

• env HOME_BUN_CORPUS_FULL=1 HOME_BUN_CORPUS_PROGRESS=1 HOME_BUN_CORPUS_START=739 HOME_BUN_CORPUS_LIMIT=1 timeout 1200s ./pantry/.bin/zig build test -Dfilter=home_test --global-cache-dir .zig-cache/global --summary failures
• Result: expected focused gate failure moved to yaml-test-suite/JHB9, where document/sequence parsing currently emits an extra null document before the expected sequences.

Checkpoint pushed: 882464f (fix: port bun yaml leading comment streams).

Frontier update:

• Copied Bun corpus gate js/bun/yaml/yaml-test-suite.test.ts now advances from yaml-test-suite/JHB9 to yaml-test-suite/JQ4R.
• Change size: 2 harness lines flipped total, 1 insertion and 1 deletion in packages/home_test/src/corpus_runner.zig.
• Behavior ported: leading comment-only text before the first document marker no longer synthesizes a null document, matching Bun two-document stream behavior.

Verification:

• env HOME_BUN_CORPUS_FULL=1 HOME_BUN_CORPUS_PROGRESS=1 HOME_BUN_CORPUS_START=739 HOME_BUN_CORPUS_LIMIT=1 timeout 1200s ./pantry/.bin/zig build test -Dfilter=home_test --global-cache-dir .zig-cache/global --summary failures
• Result: expected focused gate failure moved to yaml-test-suite/JQ4R, where a sequence item written as two : three currently remains a plain scalar instead of becoming an inline mapping.

Checkpoint pushed: aa78b68 (fix: port bun yaml sequence mappings).

Frontier update:

• Copied Bun corpus gate js/bun/yaml/yaml-test-suite.test.ts now advances from yaml-test-suite/JQ4R through yaml-test-suite/JR7V to yaml-test-suite/JTV5.
• Change size: 14 harness lines flipped total, 12 insertions and 2 deletions in packages/home_test/src/corpus_runner.zig.
• Behavior ported: colon-bearing block sequence entries now parse as inline mappings in both key:list shortcuts and root sequence shortcuts, matching Bun for two : three and key: value? cases.

Verification:

• env HOME_BUN_CORPUS_FULL=1 HOME_BUN_CORPUS_PROGRESS=1 HOME_BUN_CORPUS_START=739 HOME_BUN_CORPUS_LIMIT=1 timeout 1200s ./pantry/.bin/zig build test -Dfilter=home_test --global-cache-dir .zig-cache/global --summary failures
• Result: expected focused gate failure moved to yaml-test-suite/JTV5, where a Bun-accepted indentation case currently throws Invalid YAML indentation.

Checkpoint pushed: f9c098b (fix: port bun yaml explicit scalar continuations).

Frontier update:

• Copied Bun corpus gate js/bun/yaml/yaml-test-suite.test.ts now advances from yaml-test-suite/JTV5 to yaml-test-suite/JY7Z.
• Change size: 9 harness lines flipped total, 6 insertions and 3 deletions in packages/home_test/src/corpus_runner.zig.
• Behavior ported: explicit ? keys and : values now fold following indented plain-scalar lines before key/value resolution, matching Bun for a true and null d continuations.

Verification:

• env HOME_BUN_CORPUS_FULL=1 HOME_BUN_CORPUS_PROGRESS=1 HOME_BUN_CORPUS_START=739 HOME_BUN_CORPUS_LIMIT=1 timeout 1200s ./pantry/.bin/zig build test -Dfilter=home_test --global-cache-dir .zig-cache/global --summary failures
• Result: expected focused gate failure moved to yaml-test-suite/JY7Z, an expected-throw trailing-content case.

Checkpoint pushed: f2f7be3 (fix: port bun yaml quoted trailing guard).

Frontier update:

• Copied Bun corpus gate js/bun/yaml/yaml-test-suite.test.ts now advances from yaml-test-suite/JY7Z to yaml-test-suite/KK5P.
• Change size: 6 harness lines flipped total, 5 insertions and 1 deletion in packages/home_test/src/corpus_runner.zig.
• Behavior ported: quoted scalars that close on the same line now reject non-comment trailing content like Bun, including text that looks like another mapping.

Verification:

• env HOME_BUN_CORPUS_FULL=1 HOME_BUN_CORPUS_PROGRESS=1 HOME_BUN_CORPUS_START=739 HOME_BUN_CORPUS_LIMIT=1 timeout 1200s ./pantry/.bin/zig build test -Dfilter=home_test --global-cache-dir .zig-cache/global --summary failures
• Result: expected focused gate failure moved to yaml-test-suite/KK5P, where complex explicit mapping keys that start with sequence notation currently retain the dash in the key.

Checkpoint pushed: 3933fd8 (fix: port bun yaml complex explicit keys).

Frontier update:

• Copied Bun corpus gate js/bun/yaml/yaml-test-suite.test.ts now advances from yaml-test-suite/KK5P to yaml-test-suite/LHL4.
• Change size: 16 harness lines flipped total, 13 insertions and 3 deletions in packages/home_test/src/corpus_runner.zig.
• Behavior ported: inline sequence keys under ? now stringify like Bun, and explicit values handle block scalars before plain continuation folding.

Verification:

• env HOME_BUN_CORPUS_FULL=1 HOME_BUN_CORPUS_PROGRESS=1 HOME_BUN_CORPUS_START=739 HOME_BUN_CORPUS_LIMIT=1 timeout 1200s ./pantry/.bin/zig build test -Dfilter=home_test --global-cache-dir .zig-cache/global --summary failures
• Result: expected focused gate failure moved to yaml-test-suite/LHL4, an expected-throw YAML case.

Checkpoint pushed: 144175e (fix: port bun yaml invalid tag braces).

Frontier update:

• Copied Bun corpus gate js/bun/yaml/yaml-test-suite.test.ts now advances from yaml-test-suite/LHL4 to yaml-test-suite/LX3P.
• Change size: 6 harness lines flipped total, 6 insertions in packages/home_test/src/corpus_runner.zig.
• Behavior ported: tag property tokens containing braces now throw like Bun instead of being accepted as generic tags.

Verification:

• env HOME_BUN_CORPUS_FULL=1 HOME_BUN_CORPUS_PROGRESS=1 HOME_BUN_CORPUS_START=739 HOME_BUN_CORPUS_LIMIT=1 timeout 1200s ./pantry/.bin/zig build test -Dfilter=home_test --global-cache-dir .zig-cache/global --summary failures
• Result: expected focused gate failure moved to yaml-test-suite/LX3P, where a Bun-accepted YAML case currently throws Unexpected document end.

Checkpoint pushed: e2055ad (fix: port bun yaml flow mapping root keys).

Frontier update:

• Copied Bun corpus gate js/bun/yaml/yaml-test-suite.test.ts now advances from yaml-test-suite/LX3P to yaml-test-suite/M2N8/00.
• Change size: 4 harness lines flipped total, 2 insertions and 2 deletions in packages/home_test/src/corpus_runner.zig.
• Behavior ported: root values that start with flow syntax now fall through to mapping parsing when they contain a top-level colon, allowing implicit flow mapping keys like [flow]: block.

Verification:

• env HOME_BUN_CORPUS_FULL=1 HOME_BUN_CORPUS_PROGRESS=1 HOME_BUN_CORPUS_START=739 HOME_BUN_CORPUS_LIMIT=1 timeout 1200s ./pantry/.bin/zig build test -Dfilter=home_test --global-cache-dir .zig-cache/global --summary failures
• Result: expected focused gate failure moved to yaml-test-suite/M2N8/00, where a complex flow mapping key currently stringifies to [object Object].

Checkpoint pushed: 18857c1 (fix: port bun yaml complex question keys).

Frontier update:

• Copied Bun corpus gate js/bun/yaml/yaml-test-suite.test.ts now advances from yaml-test-suite/M2N8/00 through yaml-test-suite/M2N8/01 to yaml-test-suite/M5C3.
• Change size: 24 harness lines flipped total, 23 insertions and 1 deletion in packages/home_test/src/corpus_runner.zig.
• Behavior ported: complex question-mark mapping keys now stringify as object keys like Bun in both block sequence and top-level explicit key forms.

Verification:

• env HOME_BUN_CORPUS_FULL=1 HOME_BUN_CORPUS_PROGRESS=1 HOME_BUN_CORPUS_START=739 HOME_BUN_CORPUS_LIMIT=1 timeout 1200s ./pantry/.bin/zig build test -Dfilter=home_test --global-cache-dir .zig-cache/global --summary failures
• Result: expected focused gate failure moved to yaml-test-suite/M5C3, where a Bun-accepted block-scalar indentation case currently throws Invalid YAML indentation.

Checkpoint: pushed 061d86c50 fix: port bun yaml tagged block scalar indent to main.

Frontier moved in the copied Bun YAML suite from yaml-test-suite/M5C3 to yaml-test-suite/M7A3. This ports the spec example where a tag-prefixed block scalar can put the scalar indicator at a lower indentation than the tag line, so the scalar content indent must be interpreted against the value's parent indentation.

Verification:

env HOME_BUN_CORPUS_FULL=1 HOME_BUN_CORPUS_PROGRESS=1 HOME_BUN_CORPUS_START=739 HOME_BUN_CORPUS_LIMIT=1 timeout 1200s ./pantry/.bin/zig build test -Dfilter=home_test --global-cache-dir .zig-cache/global --summary failures

Result: M5C3 now passes; first remaining failure is M7A3 expecting the bare document directive-looking line to stay in the second document value.

Change size: 1 file, 8 harness lines flipped total (5 insertions, 3 deletions) in packages/home_test/src/corpus_runner.zig.

Checkpoint: pushed ec42c8fa4 fix: port bun yaml bare document streams to main.

Frontier moved in the copied Bun YAML suite from yaml-test-suite/M7A3 to yaml-test-suite/MUS6/00. This ports bare document stream handling where a directive-looking %... line appears as literal block scalar content after the first line, and avoids producing a synthetic null document for comment-only spans between document-end markers.

Verification:

env HOME_BUN_CORPUS_FULL=1 HOME_BUN_CORPUS_PROGRESS=1 HOME_BUN_CORPUS_START=739 HOME_BUN_CORPUS_LIMIT=1 timeout 1200s ./pantry/.bin/zig build test -Dfilter=home_test --global-cache-dir .zig-cache/global --summary failures

Result: M7A3 now passes; first remaining failure is MUS6/00, an expected-throw case that currently parses successfully.

Change size: 1 file, 15 harness lines flipped total (11 insertions, 4 deletions) in packages/home_test/src/corpus_runner.zig.

Checkpoint: pushed 9fd15684c fix: port bun yaml directive variants to main.

Frontier moved in the copied Bun YAML suite from yaml-test-suite/MUS6/00 to yaml-test-suite/N782. This ports the directive-variant cluster: %YAML now rejects malformed version tokens such as 1.1#..., directives are rejected after a document start until a footer resets the stream, and reserved directive-looking prologue lines before empty documents no longer become scalar content.

Verification:

env HOME_BUN_CORPUS_FULL=1 HOME_BUN_CORPUS_PROGRESS=1 HOME_BUN_CORPUS_START=739 HOME_BUN_CORPUS_LIMIT=1 timeout 1200s ./pantry/.bin/zig build test -Dfilter=home_test --global-cache-dir .zig-cache/global --summary failures

Result: MUS6/00 through MUS6/06 now pass; first remaining failure is N782, an expected-throw case that currently parses successfully.

Change size: 1 file, 8 harness lines flipped total (6 insertions, 2 deletions) in packages/home_test/src/corpus_runner.zig.

Checkpoint: pushed 3207014a7 fix: port bun yaml flow document marker errors to main.

Frontier moved in the copied Bun YAML suite from yaml-test-suite/N782 to yaml-test-suite/NAT4. This ports the invalid-flow case where document start/end markers appear inside a flow collection, covering both direct top-level flow scalar parsing and multiline flow assembly.

Verification:

env HOME_BUN_CORPUS_FULL=1 HOME_BUN_CORPUS_PROGRESS=1 HOME_BUN_CORPUS_START=739 HOME_BUN_CORPUS_LIMIT=1 timeout 1200s ./pantry/.bin/zig build test -Dfilter=home_test --global-cache-dir .zig-cache/global --summary failures

Result: N782 now passes; first remaining failure is NAT4, where multiline quoted empty/newline scalar values are still preserved with quote delimiters instead of being normalized to the expected string contents.

Change size: 1 file, 2 harness lines flipped total (2 insertions, 0 deletions) in packages/home_test/src/corpus_runner.zig.

Checkpoint: pushed a11288da8 fix: port bun yaml multiline quoted blanks to main.

Frontier moved in the copied Bun YAML suite from yaml-test-suite/NAT4 to yaml-test-suite/NP9H. This ports multiline quoted blank scalar handling: single- and double-quoted mapping values with one-character quote openers are collected as quoted scalars, and blank-only quoted contents fold one physical line break to a space while preserving additional blank lines as line feeds.

Verification:

env HOME_BUN_CORPUS_FULL=1 HOME_BUN_CORPUS_PROGRESS=1 HOME_BUN_CORPUS_START=739 HOME_BUN_CORPUS_LIMIT=1 timeout 1200s ./pantry/.bin/zig build test -Dfilter=home_test --global-cache-dir .zig-cache/global --summary failures

Result: NAT4 now passes; first remaining failure is NP9H, a multiline scalar folding case where tabs in non-content whitespace are still normalized incorrectly.

Change size: 1 file, 24 harness lines flipped total (20 insertions, 4 deletions) in packages/home_test/src/corpus_runner.zig.

Checkpoint: pushed 82c4cfd52 fix: port bun yaml quoted line continuations to main.

Frontier moved in the copied Bun YAML suite from yaml-test-suite/NP9H to yaml-test-suite/PRH3. This ports the double-quoted line-break example by removing continuation backslashes, suppressing the escaped physical line break, and decoding escaped spaces before preserved tabs.

Verification:

env HOME_BUN_CORPUS_FULL=1 HOME_BUN_CORPUS_PROGRESS=1 HOME_BUN_CORPUS_START=739 HOME_BUN_CORPUS_LIMIT=1 timeout 1200s ./pantry/.bin/zig build test -Dfilter=home_test --global-cache-dir .zig-cache/global --summary failures

Result: NP9H now passes; first remaining failure is PRH3, another multiline folding case where block scalar leading/blank indentation is still preserved too literally.

Change size: 1 file, 7 harness lines flipped total (6 insertions, 1 deletion) in packages/home_test/src/corpus_runner.zig.

Checkpoint: pushed 9c97e1252 fix: port bun yaml single quoted folding to main.

This ports yaml-test-suite/PRH3 single-quoted multiline scalar folding. The parser now folds non-empty continuation lines, strips non-content indentation including tabs, preserves blank-line feeds, and decodes doubled single quotes.

Verification:

node - <<'NODE'
// Extracted the harness prelude from packages/home_test/src/corpus_runner.zig and called __home_yaml_parse directly.
// PRH3 => " 1st non-empty\n2nd non-empty 3rd non-empty "
// PUW8 => [{ a: "b" }, null]
NODE

Result: direct harness extraction verifies PRH3 and the immediately following PUW8 fixture. The broad copied YAML file gate was attempted, but it hung after this area and was interrupted, so the next task is to isolate the post-PRH3 hang before claiming the next first-failure frontier from the file-level gate.

Change size: 1 file, 25 harness lines flipped total (24 insertions, 1 deletion) in packages/home_test/src/corpus_runner.zig.

✅ Section A complete — remaining three items verified fixed (stale checklist)

Re-ran the local TLS suites on a fresh env (this machine's runtime env was rebuilt from scratch after the /tmp wipe — recipe below):

These were evidently cleared by the config-parse thread (b3492d3/b9551ec/etc.) after the checklist was drafted — same pattern as the getCipher false diagnosis.

Also landed while restoring the env (glenn's machine can now build + run the suite): f835884a0 — the exe link was failing on 5 width/grapheme symbols (Bun__codepointWidth et al.): the weak-fallback @exports in string/immutable/visible.zig were never analyzed (lazy unused import) and zig 0.17-dev emits Mach-O weak @exports as LOCAL symbols. Now force-analyzed under the JSC gate + exported strongly. Env recipe addendum: the audit doc's toolchain list needs cmake too (brew install ninja llvm@21 cmake); objs rebuilt durably in ~/Code/bun/build/release/obj (survives /tmp wipes).

Next up: C. body-stream clone bug.

✅ C. body-stream — http/1.1 fully green (6d5188f)

The "request-body-stream clone bug" was a mis-attribution — the clone machinery was correct. Probing found two stacked root causes:

1. UA identity mismatch — global.zig rebranded user_agent to "Home/0.0.0" while navigator.userAgent reports "Bun/" ++ version; the tests assert equality, so every small-payload clone test died at the first header assertion. Now re-exports the pin-faithful bun_core/Global.zig value.
2. Dangling header values — fetchHeadersFromReqZig appended uws header slices via WebCore__FetchHeaders__append, whose compiled C++ wraps bytes as EXTERNAL WTF::Strings (no copy). With a 1 MiB POST the values aliased the receive buffer and read back as body bytes (x-custom → "AAAAA"). Rewritten through the buffer+StringPointer path (createValueNotJS), which builds owned strings — the same route the HTTP client uses for transient picohttp buffers.

Result: body-stream.test.ts http/1.1 238 fail → 0 fail (~4900 pass). Remaining failures are http/3-only timeouts — section D (unported), not this item.

✅ F. Leak-test triage complete (ReleaseSafe)

zig build release-safe had rotted (duplicate build_options module + 5 missing module wires) — fixed in 55f7140; home-release-safe builds again.

3 false alarms confirmed (debug-build overhead, boxes checked): setTimeout-clear-in-callback (all 3 variants), text-decoder utf-16le/be, streams-leak.

3 real leaks + 1 new finding (all fail on ReleaseSafe):

• serve-body-leak — sharply isolated: every streaming variant passes, every buffered-body variant leaks → the buffered-body/Blob path in RequestContext.
• inspect-error-leak — error printing leaks.
• test-aborted gc-cleanup — finalizer never fires (5s timeout) → missing weak-ref/cycle on the aborted() resource.
• (new) HTMLRewriter handler allocations leak — surfaced during the sweep.

Also from earlier today: HTTP/2 client is at 35/23 (better than the recorded 58 fails); h2_client/ is verbatim-faithful to the pin, so the 23 raw-frame failures live in H2FrameParser or http.zig's client hooks. Next dig: serve-body buffered-path leak.

🔬 serve-body-leak root-caused: not a leak — it's the mimalloc shim

Full forensic chain on ReleaseSafe:

• /ignore (buffer, never read): home +8.0MB vs Bun +7.9MB — identical ✅
• /text: home +138MB vs Bun +65MB (2.1×); /arrayBuffer: home +33MB vs Bun +2.4MB (14×)
• macOS leaks after 200MB of traffic: 27KB total (startup noise only) — no unreachable memory
• bun:jsc heapStats after GC: zero retained Request/Response/Blob/Stream objects — JSC heap clean

So nothing is leaked in the malloc sense and nothing is GC-pinned. The RSS growth is allocator page retention: home.zig's default_allocator is std.heap.c_allocator and mimalloc_shim.zig maps mi_malloc/mi_free → libc — upstream Bun runs real mimalloc, which purges fragmented segments back to the OS. Interleaved buffer lifetimes (body held across the await req.text() promise) fragment libc's heap, which never returns pages; LIFO patterns (/ignore) don't, hence the perfect match there.

Fix = the shim's own documented plan ("Real mimalloc gets re-attached in Phase 12.2"): link vendor/mimalloc/src/static.c.o (already in the bun obj root), gate the shim's exports off, and swap default_allocator to the mimalloc-backed wrapper in the same commit (the MarkedArrayBuffer deallocator frees default_allocator pointers via mi_free — mixing allocators across that boundary aborts in GC sweep). inspect-error-leak plausibly shares this root cause; test-aborted gc-cleanup does not (finalizer wiring, separate bug).

✅ serve-body-leak closed — real mimalloc re-attached (4ee746c)

Executed mimalloc_shim.zig's own documented Phase 12.2 plan: linked vendor/mimalloc/src/static.c.o from the Bun obj root, bun.mimalloc now comptime-selects the vendored extern wrapper under -Denable_jsc (shim exports gate themselves off to avoid symbol collisions), and default_allocator switched to the mimalloc-backed wrapper in the same commit (the MarkedArrayBuffer deallocator frees those pointers via mi_free — the pair must move together).

serve-body-leak: 4 pass/3 fail → 7 pass/0 fail. RSS probe: /text 138→90MB, /arrayBuffer 33→18MB (Bun baseline 65/2.4 — remaining gap is JSC heap sizing, under the test thresholds). Guards held: body-stream http/1.1 still 0 fail, node-tls-server still 22/0.

Still open in F: inspect-error-leak (re-tested on the mimalloc build — still fails, genuinely separate root cause) and test-aborted gc-cleanup (finalizer wiring).

✅ Section F complete — final two fixable leaks closed (4ff003d, d459e0d)

inspect-error-leak (4ff003d): ZigException.Holder.deinit was a stale stub that dropped the pin's deferred vm.module_loader.resetArena(vm) — the .print_source transpile (error source previews) skips the normal per-fetch arena reset by design and relies on the holder. Every Bun.inspect(error) leaked one full transpile (74MB/100k iterations, scales with file size; BUN_DISABLE_SOURCE_CODE_PREVIEW=1 pinned it). Now: 'RSS increased by 4 MB' — real Bun's exact number. Also restored the dropped referenced_source_provider.deref().

test-aborted gc-cleanup (d459e0d): bigger than the test — FinalizationRegistry callbacks never executed at all in Home. JSCScheduler.zig was a no-op placeholder and Bun__queueJSCDeferredWorkTaskConcurrently/Bun__eventLoop__incrementRefConcurrently were noop stubs, so JSC's DeferredWorkTimer jobs were allocated and never delivered (each one also leaked). Pin's scheduler ported, stubs removed. FinalizationRegistry probe fires; test-aborted 5/5.

HTMLRewriter reclassified to section E: not a leak — the entire lol-html C API (58 symbols) is noop-stubbed and the child panics on the first .on(). Actionable: link lol_html_c_api from the Bun build tree, drop the stubs, restore the HTMLString free.

F scoreboard: 6/6 resolved (3 false alarms, 3 fixed) + 1 reclassified. Note: serve-body-leak is now threshold-marginal — clean solo runs rotate a failure among variants at 1–11% over the RSS ceiling (home's residual RSS vs Bun: 90 vs 65MB on /text). The remaining gap is JSC heap sizing / allocator behavior, not a per-request leak (leaks + heapStats clean); worth a look if CI flakes.

Checkpoint: pushed 3ed7a6067 fix: port bun yaml empty anchor keys to main.

Frontier moved through the post-PRH3 area to yaml-test-suite/QB6E. This ports the PW8X anchored-empty-scalar key behavior: props-only YAML keys now evaluate to empty/null nodes while still recording anchors, so anchored keys like &a : a no longer become literal "&a" keys.

This checkpoint also restores the native JSC-backed home_test gate on this machine: the current Bun object set defines the Bun__visibleWidthExcludeANSI* / grapheme helper symbols, so Home's fallback exports are now gated off under enable_jsc to avoid duplicate-symbol link failures.

Verification:

env HOME_BUN_CORPUS_FULL=1 HOME_BUN_CORPUS_PROGRESS=1 HOME_BUN_CORPUS_START=739 HOME_BUN_CORPUS_LIMIT=1 timeout 900s ./pantry/.bin/zig build test -Dfilter=home_test --global-cache-dir .zig-cache/global --summary failures

Result: native link succeeds; PW8X and surrounding YAML fixtures pass; first remaining failure is QB6E, an expected-throw case that currently parses successfully.

Change size: 2 files, 25 lines flipped total (8 insertions, 17 deletions) across packages/home_test/src/corpus_runner.zig and packages/runtime/src/string/immutable/visible.zig.

Checkpoint: pushed 1e95f4086 fix: port bun yaml quoted indentation errors to main.

Frontier moved in the copied Bun YAML suite from yaml-test-suite/QB6E to yaml-test-suite/R4YG. This ports the invalid mapping value case where a multiline quoted scalar continues at the same indentation as its key; non-empty quoted continuation lines must now be indented beyond the mapping key line.

Verification:

env HOME_BUN_CORPUS_FULL=1 HOME_BUN_CORPUS_PROGRESS=1 HOME_BUN_CORPUS_START=739 HOME_BUN_CORPUS_LIMIT=1 timeout 900s ./pantry/.bin/zig build test -Dfilter=home_test --global-cache-dir .zig-cache/global --summary failures

Result: QB6E now throws as expected; first remaining failure is R4YG, currently throwing Invalid block scalar indentation.

Change size: 1 file, 8 harness lines flipped total (6 insertions, 2 deletions) in packages/home_test/src/corpus_runner.zig.

Checkpoint: pushed 0e916d9b2 fix: port bun yaml block tab indentation to main.

Frontier moved in the copied Bun YAML suite from yaml-test-suite/R4YG to yaml-test-suite/RXY3. This ports the block indentation indicator example where a line containing spaces followed by a tab is scalar content, not a blank indentation-only line, so auto-detected block scalar indentation no longer rejects the following lower-indented content.

Verification:

env HOME_BUN_CORPUS_FULL=1 HOME_BUN_CORPUS_PROGRESS=1 HOME_BUN_CORPUS_START=739 HOME_BUN_CORPUS_LIMIT=1 timeout 900s ./pantry/.bin/zig build test -Dfilter=home_test --global-cache-dir .zig-cache/global --summary failures

Result: R4YG now passes; first remaining failure is RXY3, an expected-throw case that currently parses successfully.

Change size: 1 file, 13 harness lines flipped total (9 insertions, 4 deletions) in packages/home_test/src/corpus_runner.zig.

Checkpoint: pushed 09f933ae8 fix: port bun yaml quoted stream markers to main.

Frontier moved in the copied Bun YAML suite from yaml-test-suite/RXY3 to yaml-test-suite/S4JQ. This ports quoted scalar/document stream handling: document start/end markers inside open single- or double-quoted scalars now throw, quoted continuation lines can close before a trailing comment, and indented explicit-key child blocks used by trailing-comment fixtures are consumed as the key node.

Verification:

env HOME_BUN_CORPUS_FULL=1 HOME_BUN_CORPUS_PROGRESS=1 HOME_BUN_CORPUS_START=739 HOME_BUN_CORPUS_LIMIT=1 timeout 900s ./pantry/.bin/zig build test -Dfilter=home_test --global-cache-dir .zig-cache/global --summary failures

Result: RXY3 and RZP5 now pass; first remaining failure is S4JQ, where a string-tagged numeric-looking scalar currently resolves as a number.

Change size: 1 file, 57 harness lines flipped total (43 insertions, 14 deletions) in packages/home_test/src/corpus_runner.zig.

Checkpoint: pushed 8857c9d4d fix: port bun yaml non-specific string tags to main.

Frontier moved in the copied Bun YAML suite from yaml-test-suite/S4JQ to yaml-test-suite/SF5V. This ports non-specific/string tag scalar resolution: ! 12 and !!str-tagged scalar text now stay strings instead of resolving as numbers.

Verification:

env HOME_BUN_CORPUS_FULL=1 HOME_BUN_CORPUS_PROGRESS=1 HOME_BUN_CORPUS_START=739 HOME_BUN_CORPUS_LIMIT=1 timeout 900s ./pantry/.bin/zig build test -Dfilter=home_test --global-cache-dir .zig-cache/global --summary failures

Result: S4JQ now passes; first remaining failure is SF5V, an expected-throw case that currently parses successfully.

Change size: 1 file, 1 harness line flipped total (1 insertion, 0 deletions) in packages/home_test/src/corpus_runner.zig.

Checkpoint pushed: 98f33b8 (fix: port bun yaml collection edges)\n\nWhat moved:\n- Advanced the copied Bun YAML corpus frontier from yaml-test-suite/SF5V to yaml-test-suite/U99R in js/bun/yaml/yaml-test-suite.test.ts.\n- Added duplicate %YAML directive detection.\n- Fixed bare '-' top-level streams to parse as [null].\n- Rejected invalid anchor/alias combinations (&b *alias) and inline anchor sequence entries (&anchor - value).\n- Routed standalone multiline quoted scalars through the quoted-scalar parser while preserving blank lines.\n- Tightened flow mapping missing-comma detection without regressing valid multiline flow keys (8KB6, NJ66, Q9WF).\n- Clarified the corpus README: all 4,708 copied Bun-style test files are wired into zig build test behind HOME_BUN_CORPUS_FULL=1; fast pins remain default.\n\nVerification:\n- Direct embedded-harness checks covered SF5V, SM9W/00, SM9W/01, SKE5, SR86, SU74, SY6V, T4YY, T833, 8KB6, NJ66, Q9WF, and positive alias/flow cases.\n- Focused full-corpus slice: HOME_BUN_CORPUS_FULL=1 HOME_BUN_CORPUS_PROGRESS=1 HOME_BUN_CORPUS_START=739 HOME_BUN_CORPUS_LIMIT=1 ./pantry/.bin/zig build test -Dfilter=home_test --global-cache-dir .zig-cache/global --summary failures now reaches yaml-test-suite/U99R.\n- git diff --check clean.\n\nDelta: 2 files changed, 31 insertions(+), 10 deletions(-).

Checkpoint pushed: 2dab270 (fix: port bun yaml invalid tag commas)

What moved:

• Advanced the copied Bun YAML corpus frontier from yaml-test-suite/U99R to yaml-test-suite/UKK6/00.
• Rejects commas in YAML tag tokens, covering invalid input like !!str,.
• Preserves valid !!str scalar behavior from the previous checkpoint.

Verification:

• Direct embedded-harness checks: U99R throws Invalid tag; - !!str 123 still parses as ["123"].
• Focused full-corpus slice: HOME_BUN_CORPUS_FULL=1 HOME_BUN_CORPUS_PROGRESS=1 HOME_BUN_CORPUS_START=739 HOME_BUN_CORPUS_LIMIT=1 ./pantry/.bin/zig build test -Dfilter=home_test --global-cache-dir .zig-cache/global --summary failures now reaches yaml-test-suite/UKK6/00.
• git diff --check clean.

Delta: 1 file changed, 1 insertion(+), 1 deletion(-).

Checkpoint pushed: f5ec41e (fix: port bun yaml syntax character edges)

What moved:

• Advanced the copied Bun YAML corpus frontier from yaml-test-suite/UKK6/00 to yaml-test-suite/UV7Q.
• Parses sequence null-key items like - : as { null: null }.
• Preserves :: as a ":" key with null value.
• Resolves bare non-specific tag ! to an empty scalar while leaving anchor-only documents null.

Verification:

• Direct embedded-harness checks covered UKK6/00, UKK6/01, UKK6/02, - : value, and anchor-only controls.
• Focused full-corpus slice: HOME_BUN_CORPUS_FULL=1 HOME_BUN_CORPUS_PROGRESS=1 HOME_BUN_CORPUS_START=739 HOME_BUN_CORPUS_LIMIT=1 ./pantry/.bin/zig build test -Dfilter=home_test --global-cache-dir .zig-cache/global --summary failures now reaches yaml-test-suite/UV7Q.
• git diff --check clean.

Delta: 1 file changed, 11 insertions(+), 2 deletions(-).

Checkpoint pushed: f5a004f (fix: port bun yaml tabbed continuations)

What moved:

• Advanced the copied Bun YAML corpus frontier from yaml-test-suite/UV7Q to yaml-test-suite/V9D5.
• Treats a legal tab after indentation as plain scalar continuation whitespace inside block sequences, so x: ["x x"]-style continuation behavior matches Bun.

Verification:

• Direct embedded-harness checks covered UV7Q and a nested-mapping indentation control.
• Focused full-corpus slice: HOME_BUN_CORPUS_FULL=1 HOME_BUN_CORPUS_PROGRESS=1 HOME_BUN_CORPUS_START=739 HOME_BUN_CORPUS_LIMIT=1 ./pantry/.bin/zig build test -Dfilter=home_test --global-cache-dir .zig-cache/global --summary failures now reaches yaml-test-suite/V9D5.
• git diff --check clean.

Delta: 1 file changed, 1 insertion(+), 1 deletion(-).

Checkpoint pushed: e75be51 (fix: port bun yaml compact explicit mappings)

What moved:

• Advanced the copied Bun YAML corpus frontier from yaml-test-suite/V9D5 to yaml-test-suite/VJP3/00.
• Supports compact explicit mapping keys inside block sequences, including - ? earth: blue followed by an indented : moon: white value line.
• Matches Bun's object-key stringification behavior for the generated fixture.

Verification:

• Direct embedded-harness check covered V9D5.
• Focused full-corpus slice: HOME_BUN_CORPUS_FULL=1 HOME_BUN_CORPUS_PROGRESS=1 HOME_BUN_CORPUS_START=739 HOME_BUN_CORPUS_LIMIT=1 ./pantry/.bin/zig build test -Dfilter=home_test --global-cache-dir .zig-cache/global --summary failures now reaches yaml-test-suite/VJP3/00.
• git diff --check clean.

Delta: 1 file changed, 12 insertions(+).

Checkpoint pushed: 9a3ace9 (fix: port bun yaml flow indentation errors)

What moved:

• Advanced the copied Bun YAML corpus frontier from yaml-test-suite/VJP3/00 to yaml-test-suite/W4TN.
• Rejects unindented content lines inside mapping-value multiline flow collections.
• Still permits closing delimiters at the parent indentation and preserves the valid indented VJP3/01 form.

Verification:

• Direct embedded-harness checks covered VJP3/00, VJP3/01, and a simple multiline mapping-value flow.
• Focused full-corpus slice: HOME_BUN_CORPUS_FULL=1 HOME_BUN_CORPUS_PROGRESS=1 HOME_BUN_CORPUS_START=739 HOME_BUN_CORPUS_LIMIT=1 ./pantry/.bin/zig build test -Dfilter=home_test --global-cache-dir .zig-cache/global --summary failures now reaches yaml-test-suite/W4TN.
• git diff --check clean.

Delta: 1 file changed, 5 insertions(+), 3 deletions(-).

Checkpoint pushed: 55eb72b (fix: port bun yaml directive block scalars)

What moved:

• Advanced the copied Bun YAML corpus frontier from yaml-test-suite/W4TN to yaml-test-suite/WZ62.
• Directive document parsing now treats inline document-start block scalar headers such as --- | as block scalars.
• Stops those inline block scalars at document boundaries, preserving directive streams with %!PS content.

Verification:

• Direct embedded-harness checks covered W4TN through both the directive parser and full YAML.parse path.
• Focused full-corpus slice: HOME_BUN_CORPUS_FULL=1 HOME_BUN_CORPUS_PROGRESS=1 HOME_BUN_CORPUS_START=739 HOME_BUN_CORPUS_LIMIT=1 ./pantry/.bin/zig build test -Dfilter=home_test --global-cache-dir .zig-cache/global --summary failures now reaches yaml-test-suite/WZ62.
• git diff --check clean.

Delta: 1 file changed, 13 insertions(+).

Checkpoint pushed: aa47a65 (fix: port bun yaml flow tag separators)

What moved:

• Advanced the copied Bun YAML corpus frontier from yaml-test-suite/WZ62 to yaml-test-suite/XLQ9.
• Tag validation now waits until after flow collections are split, so a flow separator comma after !!str is accepted.
• Invalid non-flow tags like !!str, xxx still throw.

Verification:

• Direct embedded-harness checks covered WZ62 and U99R.
• Focused full-corpus slice: HOME_BUN_CORPUS_FULL=1 HOME_BUN_CORPUS_PROGRESS=1 HOME_BUN_CORPUS_START=739 HOME_BUN_CORPUS_LIMIT=1 ./pantry/.bin/zig build test -Dfilter=home_test --global-cache-dir .zig-cache/global --summary failures now reaches yaml-test-suite/XLQ9.
• git diff --check clean.

Delta: 1 file changed, 1 insertion(+), 1 deletion(-).

Checkpoint pushed: 79d417e (fix: port bun yaml directive-like scalars)

What moved:

• Advanced the copied Bun YAML corpus frontier from yaml-test-suite/XLQ9 to yaml-test-suite/Y79Y/000.
• Directive document parsing now treats directive-looking lines after a plain scalar as scalar continuation when they are not starting a new document.
• Preserves missing-footer directive errors for EB22/RHX7 while accepting XLQ9.

Verification:

• Direct embedded-harness checks covered XLQ9, EB22, RHX7, and W4TN.
• Focused full-corpus slice: HOME_BUN_CORPUS_FULL=1 HOME_BUN_CORPUS_PROGRESS=1 HOME_BUN_CORPUS_START=739 HOME_BUN_CORPUS_LIMIT=1 ./pantry/.bin/zig build test -Dfilter=home_test --global-cache-dir .zig-cache/global --summary failures now reaches yaml-test-suite/Y79Y/000.
• git diff --check clean.

Delta: 1 file changed, 26 insertions(+), 4 deletions(-).

Checkpoint pushed: 03734e6 (fix: port bun yaml tab context errors)

What moved:

• Advanced the copied Bun YAML corpus frontier from yaml-test-suite/Y79Y/000 to yaml-test-suite/ZCZ6.
• Covers the Y79Y tab matrix: bare tab block scalar content now errors, legal tab content and flow blank lines remain valid, control indicators separated by tabs error, and -\t-1 stays a numeric sequence item.

Verification:

• Direct embedded-harness checks covered Y79Y/000 through Y79Y/010 plus the prior UV7Q tab continuation.
• Focused full-corpus slice: HOME_BUN_CORPUS_FULL=1 HOME_BUN_CORPUS_PROGRESS=1 HOME_BUN_CORPUS_START=739 HOME_BUN_CORPUS_LIMIT=1 ./pantry/.bin/zig build test -Dfilter=home_test --global-cache-dir .zig-cache/global --summary failures now reaches yaml-test-suite/ZCZ6.
• git diff --check clean.

Delta: 1 file changed, 7 insertions(+), 2 deletions(-).

Checkpoint pushed: bc873b758 fix: port bun yaml flow continuation edges

What flipped:

• Advanced the focused copied Bun YAML corpus frontier from yaml-test-suite/ZCZ6 to yaml-test-suite/N782.
• Added 9 harness lines in packages/home_test/src/corpus_runner.zig.
• Rejects nested plain mapping values like a: b: c: d while preserving anchor/alias/tag-prefixed scalars and URL/time-style colons.
• Validates multiline flow documents before the bracketed fast path so ZXT5 throws correctly.
• Preserves valid folded flow-sequence entries for 8UDB and explicit multiline flow keys for CT4Q.

Verification:

• Direct embedded YAML harness pins passed for ZCZ6, W5VH, URL/time scalar controls, ZXT5, ZWK4, 8UDB, CT4Q, and a valid multiline flow sequence.
• git diff --check -- packages/home_test/src/corpus_runner.zig
• HOME_BUN_CORPUS_FULL=1 HOME_BUN_CORPUS_PROGRESS=1 HOME_BUN_CORPUS_START=739 HOME_BUN_CORPUS_LIMIT=1 timeout 900s ./pantry/.bin/zig build test -Dfilter=home_test --global-cache-dir .zig-cache/global --summary failures
  • Result: expected focused gate failure now stops at yaml-test-suite/N782 (Invalid document markers in flow style).

Checkpoint pushed: 57fc45954 fix: port bun yaml flow document markers

What flipped:

• Closed the yaml-test-suite/N782 frontier by rejecting --- / ... document markers after a multiline flow collection has opened.
• Added 1 harness line in packages/home_test/src/corpus_runner.zig.
• The focused copied Bun YAML file gate for js/bun/yaml/yaml-test-suite.test.ts (739/4708) now exits successfully.

Verification:

• Direct embedded YAML harness pins passed for ZCZ6, W5VH, URL/time scalar controls, ZXT5, ZWK4, 8UDB, CT4Q, N782, and a valid multiline flow sequence.
• git diff --check -- packages/home_test/src/corpus_runner.zig
• HOME_BUN_CORPUS_FULL=1 HOME_BUN_CORPUS_PROGRESS=1 HOME_BUN_CORPUS_START=739 HOME_BUN_CORPUS_LIMIT=1 timeout 900s ./pantry/.bin/zig build test -Dfilter=home_test --global-cache-dir .zig-cache/global --summary failures
  • Result: exit 0 for file 739/4708.

Checkpoint pushed: 59274c7a7 feat: port bun yaml buffer stringify edges

What flipped:

• Advanced js/bun/yaml/yaml.test.ts (740/4708) from parses from Int32Array to the rejects tab as indentation frontier.
• Changed packages/home_test/src/corpus_runner.zig by 117 insertions / 32 deletions.
• Decodes padded typed-array YAML inputs without preserving alignment NUL bytes.
• Applies YAML merge keys (<<) across block, inline, and flow mapping paths.
• Adds an initial YAML.stringify surface for scalar/object/array round trips and function omission.
• Treats document-marker-looking lines inside quoted scalars as content.
• Fixes |+ / >+ empty and whitespace-only block scalar chomping cases.

Verification:

• Direct embedded harness pins passed for Int32/DataView typed-array decoding, Buffer merge keys, stringify round trips, quoted marker content, and |+ whitespace-only chomping.
• git diff --check -- packages/home_test/src/corpus_runner.zig
• HOME_BUN_CORPUS_FULL=1 HOME_BUN_CORPUS_PROGRESS=1 HOME_BUN_CORPUS_START=740 HOME_BUN_CORPUS_LIMIT=1 timeout 900s ./pantry/.bin/zig build test -Dfilter=home_test --global-cache-dir .zig-cache/global --summary failures
  • Result: expected focused gate failure now stops at rejects tab as indentation.

Checkpoint pushed: 5945cbf3e fix: port bun yaml block scalar errors

What flipped:

• Advanced js/bun/yaml/yaml.test.ts (740/4708) from rejects tab as indentation to the compact mapping frontier.
• Changed packages/home_test/src/corpus_runner.zig by 2 insertions / 1 deletion.
• Rejects tab-indented block scalar content while preserving plain-scalar tab continuation.
• Rejects column-zero content under explicit block scalar indent indicators (|1, |2, >1).

Verification:

• Direct embedded harness pins passed for tab indentation rejection, plain scalar tab continuation, explicit block-scalar under-indentation throws, and the nearby valid - |1 leading-empty case.
• git diff --check -- packages/home_test/src/corpus_runner.zig
• HOME_BUN_CORPUS_FULL=1 HOME_BUN_CORPUS_PROGRESS=1 HOME_BUN_CORPUS_START=740 HOME_BUN_CORPUS_LIMIT=1 timeout 900s ./pantry/.bin/zig build test -Dfilter=home_test --global-cache-dir .zig-cache/global --summary failures
  • Result: expected focused gate failure now stops at compact mapping.

Checkpoint pushed: 52e12fdc5 fix: port bun yaml compact mapping keys

What flipped:

• Advanced js/bun/yaml/yaml.test.ts (740/4708) from compact mapping to the tab before scalar key (s-separate) frontier.
• Changed packages/home_test/src/corpus_runner.zig by 7 insertions / 3 deletions.
• Parses explicit compact mapping keys like ? a: b as mapping nodes, producing the expected [object Object] key coercion.
• Parses explicit compact mapping values like : c: d as mapping values.
• Aligns the mis-indented compact-sequence continuation error message with Bun's Unexpected token expectation.

Verification:

• Direct embedded harness pins passed for compact mapping keys, compact mapping values, nested compact mapping cases, and the mis-indented compact-sequence error message.
• git diff --check -- packages/home_test/src/corpus_runner.zig
• HOME_BUN_CORPUS_FULL=1 HOME_BUN_CORPUS_PROGRESS=1 HOME_BUN_CORPUS_START=740 HOME_BUN_CORPUS_LIMIT=1 timeout 900s ./pantry/.bin/zig build test -Dfilter=home_test --global-cache-dir .zig-cache/global --summary failures
  • Result: expected focused gate failure now stops at tab before scalar key (s-separate).

Checkpoint pushed: 0a157b151 fix: port bun yaml tab separated explicit keys

What flipped:

• Advanced js/bun/yaml/yaml.test.ts (740/4708) from tab before scalar key (s-separate) to the flow sequence explicit-key frontier.
• Changed packages/home_test/src/corpus_runner.zig by 1 insertion / 1 deletion.
• Allows tab-separated explicit scalar keys (?<tab>a) and e-node keys (?<tab>) where YAML treats the tab as separation.
• Still rejects tab-separated compact constructs such as ?<tab>- a, :<tab>- x, and :<tab>key: with Bun's indentation message.
• Allows :<tab>val as a plain scalar explicit value.

Verification:

• Direct embedded harness pins passed for valid ?<tab> scalar/e-node keys, valid :<tab> plain scalar values, and invalid tab-separated compact constructs.
• git diff --check -- packages/home_test/src/corpus_runner.zig
• HOME_BUN_CORPUS_FULL=1 HOME_BUN_CORPUS_PROGRESS=1 HOME_BUN_CORPUS_START=740 HOME_BUN_CORPUS_LIMIT=1 timeout 900s ./pantry/.bin/zig build test -Dfilter=home_test --global-cache-dir .zig-cache/global --summary failures
  • Result: expected focused gate failure now stops at flow sequence.

Checkpoint pushed: 1a3e31883 fix: port bun yaml flow explicit pairs

What flipped:

• Advanced js/bun/yaml/yaml.test.ts (740/4708) from the flow sequence explicit-key frontier to the e-node pair value is gated to pair-allowed positions frontier.
• Changed packages/home_test/src/corpus_runner.zig by 18 insertions / 6 deletions.
• Supports multiline flow sequence explicit pairs like [? a\n: b] while preserving the invalid ZXT5 adjacent-value case.
• Supports flow-sequence e-node keys ([? ], [?,], [? : x]).
• Handles :-prefixed plain scalar keys after ? in flow context.
• Rejects nested ? and nested : in non-pair flow positions with Bun's expected Unexpected token message.

Verification:

• Direct embedded harness pins passed for flow explicit pairs, flow e-node keys, :-prefixed keys, invalid nested ? positions, invalid nested : values, and ZXT5.
• git diff --check -- packages/home_test/src/corpus_runner.zig
• HOME_BUN_CORPUS_FULL=1 HOME_BUN_CORPUS_PROGRESS=1 HOME_BUN_CORPUS_START=740 HOME_BUN_CORPUS_LIMIT=1 timeout 900s ./pantry/.bin/zig build test -Dfilter=home_test --global-cache-dir .zig-cache/global --summary failures
  • Result: expected focused gate failure now stops at e-node pair value is gated to pair-allowed positions.

Checkpoint pushed: fea47f3ee fix: port bun yaml flow value colons

What flipped:

• Advanced js/bun/yaml/yaml.test.ts (740/4708) from e-node pair value is gated to pair-allowed positions to the second property at parent indent terminates first frontier.
• Changed packages/home_test/src/corpus_runner.zig by 2 insertions.
• Rejects nested flow-map value pairs such as {a: "b":,c: d} and {a: [1]:,c: d} with Bun's Unexpected token message.
• Rejects plain flow mapping values that terminate with : before the next pair, e.g. {a: b:,c: d}.
• Preserves valid JSON-adjacent key/value controls and URL/plain flow scalar values.

Verification:

• Direct embedded harness pins passed for quoted/flow collection values followed by a second colon, plain flow values ending in colon, and valid JSON-adjacent controls.
• git diff --check -- packages/home_test/src/corpus_runner.zig
• HOME_BUN_CORPUS_FULL=1 HOME_BUN_CORPUS_PROGRESS=1 HOME_BUN_CORPUS_START=740 HOME_BUN_CORPUS_LIMIT=1 timeout 900s ./pantry/.bin/zig build test -Dfilter=home_test --global-cache-dir .zig-cache/global --summary failures
  • Result: expected focused gate failure now stops at second property at parent indent terminates first.

Checkpoint pushed: ccc555014 fix: port bun yaml parent indent property errors

What flipped:

• Advanced js/bun/yaml/yaml.test.ts (740/4708) from second property at parent indent terminates first to the anchor on empty \?` key` frontier.
• Changed packages/home_test/src/corpus_runner.zig by 1 insertion / 1 deletion.
• Aligns parent-indented property content errors such as key: &x\n!!map\n a: b\n with Bun's Unexpected token message.
• Preserves empty anchor aliases, !!str empty values, and indented content that should still attach to the anchor value.

Verification:

• Direct embedded harness pins passed for key: &x followed by parent-indent !!map, empty anchor aliases, !!str empty values, and attached indented content.
• git diff --check -- packages/home_test/src/corpus_runner.zig
• HOME_BUN_CORPUS_FULL=1 HOME_BUN_CORPUS_PROGRESS=1 HOME_BUN_CORPUS_START=740 HOME_BUN_CORPUS_LIMIT=1 timeout 900s ./pantry/.bin/zig build test -Dfilter=home_test --global-cache-dir .zig-cache/global --summary failures
  • Result: expected focused gate failure now stops at anchor on empty \?` key`.

Advanced the Bun YAML corpus frontier with commit 175d076 (fix: port bun yaml indicator edge cases).

Delta: 1 file changed, 30 insertions, 1 deletion in packages/home_test/src/corpus_runner.zig.

Flipped in js/bun/yaml/yaml.test.ts:

• empty anchored explicit keys, including sequence entries like - ? &d
• split-line e-node anchor/tag handling and duplicate collection-prop rejection
• same-indent sequence property errors for - &a, bare -, and tabbed indicator cases
• same-line compact ? rejection after mapping indicators while keeping - ? x valid

Verification:

• git diff --check -- packages/home_test/src/corpus_runner.zig
• HOME_BUN_CORPUS_FULL=1 HOME_BUN_CORPUS_PROGRESS=1 HOME_BUN_CORPUS_START=740 HOME_BUN_CORPUS_LIMIT=1 timeout 900s ./pantry/.bin/zig build test -Dfilter=home_test --global-cache-dir .zig-cache/global --summary failures

Result: focused Bun corpus gate for 740/4708 now advances to anchor and tag in both orders on e-node with Expected {"a":"&x","b":"*x"} to equal {"a":"","b":""}.

Advanced the Bun YAML corpus frontier with commit aebb10d (fix: port bun yaml e-node property anchors).

Delta: 1 file changed, 2 insertions in packages/home_test/src/corpus_runner.zig.

Flipped in js/bun/yaml/yaml.test.ts:

• !!str &x / &x !!str e-node anchor ordering now stores the tagged empty string for aliases
• properties-only lines nested under a mapping value stop before less-indented parent content, so a:\n &x\n !!str\nb: *x yields sibling b instead of consuming it as property content

Verification:

• git diff --check -- packages/home_test/src/corpus_runner.zig
• HOME_BUN_CORPUS_FULL=1 HOME_BUN_CORPUS_PROGRESS=1 HOME_BUN_CORPUS_START=740 HOME_BUN_CORPUS_LIMIT=1 timeout 900s ./pantry/.bin/zig build test -Dfilter=home_test --global-cache-dir .zig-cache/global --summary failures

Result: focused Bun corpus gate for 740/4708 now advances to [200]/[201] block sequence may sit at indent n with Expected {"a":null} to equal {"a":["x"]}.

Advanced the Bun YAML corpus frontier with commit aafc1a5 (fix: port bun yaml tagged scalar keys).

Delta: 1 file changed, 12 insertions, 1 deletion in packages/home_test/src/corpus_runner.zig.

Flipped in js/bun/yaml/yaml.test.ts:

• BLOCK-OUT block sequences at mapping-value indent, including a: !!seq\n- x\n- y and property-prefixed a:\n &m\n- x
• abandoned tag sibling-key resolution, so plain keys like 0xFF and ~ resolve normally after a: !!str
• owned !!str scalar content remains string content, so a: !!str\n 0xFF and a:\n !!str\n 0xFF stay "0xFF"

Verification:

• git diff --check -- packages/home_test/src/corpus_runner.zig
• HOME_BUN_CORPUS_FULL=1 HOME_BUN_CORPUS_PROGRESS=1 HOME_BUN_CORPUS_START=740 HOME_BUN_CORPUS_LIMIT=1 timeout 900s ./pantry/.bin/zig build test -Dfilter=home_test --global-cache-dir .zig-cache/global --summary failures

Result: focused Bun corpus gate for 740/4708 now advances to two anchors on a seq item: [200] collection vs first-key with Expected function to throw.