Utility/deprecated-constructor checkpoint (2026-10-10): source b68665aa4 and verified evidence. util.deprecate converts built-in wrappers through the runtime constructor helper, preserving original prototype and arity with constructor/subclass/receiver semantics. Node comparison and unchanged warning/code-validation process checks pass. JUnit control-character escaping flushes and advances source text correctly; ordinary newline/tab/carriage-return names retain exact XML/metadata identity.
24 native groups; 32 validator controls; 54/54 Debug steps. Expanded final original scope: 599 passes, one upstream skip, three TODOs, 40 filtered cases and two process checks across 18 files. Sixteen utility/events/URL/MIME/path/assert files plus selected ordinary TLS/reporter cases validate. All 747 committed artifacts and 94 restored report outcomes reproduce retained results; final source hashes match committed bytes. Assertions and snapshots are unchanged. Initial constructor integration failures, metadata mismatch, rejected glob inference, disk refusals and terminal duplicate cleanup remain visible. Pickier has zero errors and one existing warning.
This is additional coverage, not a full-suite pass. The earlier performance scope retains #874 and was not rerun here. Historical invalid-URL metadata remains unvalidated and receives no final coverage credit. XML-invalid control-code policy, broader constructor/platform semantics and corpus integration remain in #876. Performance gaps remain in #869/#873; HTTPS receiver/lifecycle remain in #875/#532. Excluded regressions remain unverified; full Bun suite, #872 and Release/ASAN/all-platform coverage remain open under #66.
Current status: effective-cwd inventories, common-root aliases and overlapping targets are verified against direct native execution. Distinct roots and broader integration remain open.
- Name filters and retry/repeat/per-test timeout forwarding.
- Case provenance and filtered/skipped/TODO/retry-attempt accounting.
- Common-root suite shard/bail/order/concurrency/coverage controls.
- Isolation and ordinary parallel provenance/coverage/empty-module controls.
- Public dots/JUnit and parallel public JUnit alongside internal evidence.
- Tracked dependency changed-selection and clean-tree zero-case controls.
- Explicit relative config/preloads, short attached config values and cwd/config controls.
- No empty public JUnit document for clean changed-selection runs.
- Broader configuration/preload provenance, reporter combinations and watch/Git edge cases.
- Worker crash/signal/respawn/early-bail lifecycle paths.
- Relative targets under cwd, symlink cwd, common-root aliases and overlapping target controls.
- Distinct roots/mixed targets and prepared plan/vendor/script-mode integration.
- Broader configuration/cwd ordering and all-platform verification.
Corpus target resolution checkpoint (2026-10-10): source 01b1d7fa8 and verified evidence. Coordinated suite inventories resolve relative targets from the effective native cwd. Canonical cwd/root paths identify actual sources across dot and symlink aliases. Absolute and relative spellings of a common root work together; overlapping directory/file selection retains native deduplication and one inventory entry per canonical source. Direct native controls verify these routes while native execution preserves the requested symlink cwd spelling.
24 native groups verified across the batch and corrected suite; 32 validator controls; 54/54 Debug steps. Twenty-three native groups passed initially; the suite passed after correcting a symlink-cwd fixture expectation, with 26 reports. All 621 committed artifacts and 97 restored report outcomes validate; source hashes match committed bytes. Nine original selected files retain 62 passes plus three process checks, one failure/failed file (#874), 40 filtered cases and zero skips/TODOs. Original assertions and snapshots are unchanged. Initial failures, incomplete negative controls and terminal-only derived-cache cleanup remain visible. Root Pickier refused the generated file count; targeted Pickier passes.
#876 remains open for distinct roots/mixed targets, broader config/preload provenance, prepared plan/vendor/script-mode integration, worker lifecycle, watch/Git edges and all-platform verification. HTTPS receiver/lifecycle remain open in #875/#532. Excluded regressions remain unverified; full Bun suite, #872 and Release/ASAN/all-platform coverage remain open under #66.
Earlier checkpoints (historical):
Current status: explicit caller config/cwd and ordinary zero-case public JUnit behavior are verified alongside coordinated suite evidence. Broader combinations remain open.
- Name filters and retry/repeat/per-test timeout forwarding.
- Case provenance and filtered/skipped/TODO/retry-attempt accounting.
- Common-root suite shard/bail/order/concurrency/coverage controls.
- Isolation and ordinary parallel provenance/coverage/empty-module controls.
- Public dots/JUnit and parallel public JUnit alongside internal evidence.
- Tracked dependency changed-selection and clean-tree zero-case controls.
- Explicit relative config/preloads, short attached config values and cwd/config controls.
- No empty public JUnit document for clean changed-selection runs.
- Broader configuration/preload provenance, reporter combinations and watch/Git edge cases.
- Worker crash/signal/respawn/early-bail lifecycle paths.
- Mixed roots and prepared plan/vendor/script-mode integration.
- Broader configuration/cwd ordering and all-platform verification.
Explicit corpus context checkpoint (2026-10-10): source f82d339db and verified evidence. Explicit --config/-c and --cwd retain caller execution context, relative configuration/preloads and the effective case-source base. Short optional flags retain attached values such as -c=./file. A clean changed-selection run keeps internal terminal metadata without creating an empty public JUnit document. Suite source inventory preserves sentinel allocation ownership.
24 native groups; 32 validator controls; 54/54 Debug steps. Nine original selected files retain 62 passes plus three process checks, one failure/failed file (#874), 40 filtered cases and zero skips/TODOs. All 590 committed artifacts and 69 restored report outcomes validate; source hashes match committed bytes. Failure and incomplete-journal controls retain their expected outcomes. Initial configuration/disk, fixture-hash and short-config failures remain visible. Original assertions and snapshots are unchanged.
#876 remains open for broader config/preload provenance and combinations, mixed roots, prepared plan/vendor/script-mode integration, watch/Git edge cases, worker lifecycle and all-platform verification. #875/#532 retain HTTPS receiver/lifecycle gaps. Excluded regressions remain unverified; full Bun suite, #872 and Release/ASAN/all-platform coverage remain open under #66.
Earlier checkpoints (historical):
Current status: ordinary changed-dependency/clean-tree selection and public reporter output are verified with internal suite evidence. Broader combinations remain open.
- Name filters and retry/repeat/per-test timeout forwarding.
- Case provenance and filtered/skipped/TODO/retry-attempt accounting.
- Common-root suite shard/bail/order/concurrency/coverage controls.
- Isolation and ordinary parallel provenance/coverage/empty-module controls.
- Public dots/JUnit and parallel public JUnit alongside internal evidence.
- Tracked dependency changed-selection and clean-tree zero-case controls.
- Broader reporter/empty-output/config combinations and watch/Git edge cases.
- Worker crash/signal/respawn/early-bail lifecycle paths.
- Mixed roots and prepared plan/vendor/script-mode integration.
- Broader configuration/cwd ordering and all-platform verification.
Reporter/changed-selection checkpoint (2026-10-10): source 5088d7472 and verified evidence. Corpus capture has an internal report output option independent of public reporter/outfile flags. Ordinary public dots/JUnit and parallel public JUnit controls validate alongside internal evidence; native case collection feeds both outputs. Changed-file options use coordinated execution: a tracked dependency change selects the affected test like direct native execution, while a clean Git state runs no bodies and receives zero passing-case credit.
24 native groups; 31 validator controls; 54/54 Debug steps. Nine original selected files retain 62 passes plus three process checks, one failure/failed file (#874), 40 filtered cases and zero skips/TODOs. All 420 committed archives and 59 restored reports validate against retained outcomes; source hashes match committed bytes. Initial cache/compile diagnostics and disk-admission refusals/cleanup remain visible. Original assertions and snapshots are unchanged; guard limits were preserved.
#876 stays open for broader reporter/empty-output/config combinations, watch/Git edge cases, mixed roots, prepared plan/vendor/script-mode integration, worker lifecycle and all-platform verification. #875/#532 retain HTTPS receiver/lifecycle gaps. Excluded regressions remain unverified; full Bun suite, #872 and Release/ASAN/all-platform coverage remain open under #66.
Earlier checkpoints (historical):
Current status: the tested isolation/parallel execution paths now preserve worker case provenance and retry counts. The issue remains open for broader lifecycle and integration coverage.
- Name filters and retry/repeat/per-test timeout forwarding.
- Native case provenance and filtered/skipped/TODO/retry-attempt accounting.
- Common-root suite shard/bail/order/concurrency/coverage controls.
- Isolation, ordinary parallel worker provenance, mixed outcomes, parallel coverage and empty-module controls.
- Worker crash/signal/respawn/early-bail lifecycle paths.
- Changed/reporter options, mixed roots and prepared plan/vendor/script-mode integration.
- Broader configuration/cwd ordering and all-platform verification.
Isolation/parallel provenance checkpoint (2026-10-10): source 424f1c6ae and verified evidence. Isolation/parallel options use coordinated corpus execution. Worker IPC pairs metadata with JUnit fragments, propagates retry-attempt deltas and preserves aggregate order. Metadata ordinals are reindexed to the merged JUnit sequence with coordinator terminal counters. Missing/incomplete fragments remain unvalidated. Empty workers no longer announce nonexistent JUnit paths; capture options preserve trailing option/value pairs. Public JUnit remains unchanged.
Ordinary controls pass for fresh realms, mixed parallel retry/filter/skip/TODO outcomes, parallel coverage and empty modules without invented case credit. 24 native groups; 31 validator controls; 54/54 recovered Debug steps. Nine selected original files retain 62 passes plus three process checks, one failure/failed file (#874), 40 filtered cases and zero skips/TODOs. All 453 committed archives and 49 restored reports validate against retained outcomes; source hashes match committed bytes. Initial option-placement/empty-worker failures, disk stops/refusals and derived-cache cleanup remain visible; guard limits were preserved.
#876 stays open for worker crash/signal/respawn/early-bail paths, changed/reporter options, mixed roots, prepared plan/vendor/script-mode integration and broader config/cwd/platform verification. #875/#532 retain HTTPS receiver/lifecycle gaps. Excluded regressions remain unverified; full Bun suite, #872 and Release/ASAN/all-platform coverage remain open under #66.
Earlier checkpoints (historical):
Current status: common-root registered suites now preserve the tested shard, global bail, seeded order, concurrency/shared realm and coverage behavior through one native invocation. The issue remains open for broader execution routes and option combinations.
- Name filters and retry/repeat/per-test timeout forwarding.
- Native case provenance and filtered/skipped/TODO/retry-attempt accounting.
- Coordinated common-root suite execution with hashed source inventory and native terminal counters.
- Ordinary shard, global bail, seeded order, concurrency/shared realm and coverage controls.
- Mixed roots/targets, prepared subset/vendor and script-mode integration.
- Parallel/isolate/changed options, reporter overrides and remaining options.
- Broader configuration/cwd ordering and all-platform verification.
Coordinated native suite checkpoint (2026-10-10): source 05bff8757 and verified evidence. Suite-wide shard/bail/randomization/concurrency/coverage options route common-root registered corpus suites through one native invocation. Shard partitions and seeded order match direct native execution; global bail stops later bodies, concurrent tests preserve shared realm across files, and coverage includes the exercised helper. Native option parsing distinguishes file positionals from option values before corpus path rewriting.
Suite journals retain one invocation and a hashed source inventory separately from observed cases, with source hashes checked after execution. Native terminal counters allow strict bail reporting without a normal console summary. Excluded and bail-stopped inventory entries receive no passing credit. Public JUnit retains the pinned format. 24 native groups; 31 validator controls; 54/54 Debug steps. Nine original selected files retain 62 passes plus three process checks, one failure/failed file (#874), 40 filtered cases, zero skips/TODOs. All 286 committed archives and 39 restored reports validate against retained outcomes, including expected failures; source hashes match committed bytes. This is selected coverage and retains a failure.
#876 stays open for mixed roots/targets, prepared subset/vendor integration, script-mode, parallel/isolate/changed options, reporter overrides and broader config/cwd/platform semantics. #875/#532 retain HTTPS receiver and lifecycle gaps. Initial validator/compiler diagnostics remain visible. Excluded regressions remain unverified; full Bun suite, #872 and Release/ASAN/all-platform coverage remain open under #66.
Earlier checkpoints (historical):
Current status: filtered-case accounting and registered-test retry/repeat/timeout forwarding are implemented and verified on main. Public JUnit compatibility is preserved.
- Forward name-filter aliases across corpus execution routes.
- Retain native case provenance and reconcile filtered/skipped/TODO/retry-attempt records without passing credit.
- Forward retry/repetition/per-test timeout values and preserve explicit timeout precedence.
- Coordinate suite-wide shard/bail/concurrency/coverage behavior and audit remaining options.
- Verify broader configuration/cwd ordering, script-mode and platform semantics.
Native case-provenance/options checkpoint (2026-10-10): source ce78f49fd and verified evidence. Native metadata records each emitted JUnit entry's identity, ordinal, result and role. Journals retain its hash; validation checks exact correspondence with public JUnit and process counters. Filtered, skipped, TODO and failed retry-attempt records remain distinct and receive no passing-case credit. Public JUnit preserves the pinned format, including separate retry entries. Metadata is bound to the requested output path so nested reporters preserve parent evidence.
Corpus dispatch now forwards retry, rerun-each and timeout values. Explicit timeouts take precedence over the CI launch default. Ordinary mixed-outcome/retry/repeat/deadline controls pass, as do the unchanged original valid TLS callback and retry-reporter selections with strict evidence validation. 23 native groups; 28 validator controls; 54/54 Debug steps. Across nine selected original files: 62 passes plus three process checks, one failure/failed file (#874), 40 filtered cases, zero skips/TODOs. All 333 committed archives, nine restored original reports and 32 owned report controls validate against retained outcomes; source hashes match committed bytes. This is selected coverage and retains a failure.
#876 stays open for suite-wide shard/bail/concurrency/coverage, remaining options and broader config/cwd/platform semantics. #875/#532 retain HTTPS accepted-socket receiver and lifecycle gaps. Initial fixture/compile diagnostics, the profile-timeout override, disk stop and cleanup remain visible. Intermediate XML changes were discarded before publication to preserve the pin. Excluded regressions remain unverified; full Bun suite, #872 and Release/ASAN/all-platform coverage remain open under #66.
Earlier investigation (historical):
ALPN wire/corpus-filter checkpoint (2026-10-10): ALPN 9ec6ebcd6, filters efde19005, and verified evidence. HTTPS and tls.Server callback names decode as ASCII; native selection preserves the first matching offered wire bytes by offset, including valid byte aliases. Negotiated protocol getters use Latin-1. HTTPS constructor acceptance matches Node's deferred type-validation phase; later accepted-socket validation remains open. The complete ordinary trusted ALPN control passes on Node and Home. Corpus dispatch now forwards every supported name-filter alias across file/multiple-file/directory/subset routes; ordinary execution controls verify excluded bodies do not run.
22 native groups; ten ABI tests/684 assertions; five Zig tests; 54/54 Debug steps. Seven unchanged files retain 60 passes plus three process checks and one registered failure/failed file (#874), no skips/TODOs. All 176 committed archives and 16 restored reports validate against retained outcomes, including the existing failure and filtered-report rejection; final source hashes match committed bytes.
The additional original TLS selection receives no validated coverage credit. Initially the lost filter ran all 38 cases. After forwarding, one case passes and 37 are filtered, but JUnit represents them as skips while process counters report zero intentional skips. The strict validator still rejects that discrepancy. #876 tracks filtered-case accounting and remaining corpus CLI options; #481 documents direct native CLI work. #875/#532 remain open for HTTPS accepted-TLSSocket receiver, callback error/lifecycle and reload compatibility. Initial failures, disk refusal, cleanup and existing style/format findings are retained. Excluded regressions remain unverified; full Bun suite, #872 and Release/ASAN/all-platform coverage remain open under #66.
Corpus dispatch previously discarded -t / --test-name-pattern / --grep arguments before invoking the native test runner. That execution bug is fixed in the current batch, with ordinary body-execution controls covering all supported alias forms, single/multiple files and directories. Related direct native CLI work: #481; overall parity: #66.
Remaining work:
- Reconcile filtered cases in corpus journals. The original valid TLS callback selection now executes one passing case / 37 filtered out / zero failed, but the retained JUnit artifact represents those 37 filtered cases as
<skipped />. Process counters report zero intentional skips. The strict corpus validator rejects that discrepancy; the filtered file is not credited as validated passing coverage. Preserve the distinction between filtered, intentionally skipped, TODO and passing cases. - Forward the remaining native test runner options through corpus dispatch with their actual semantics. The current coordinator forwards name-filter arguments; options such as retry/repetition, timeout/bail, seed/shard and coverage still need an audit and conformance controls. Do not silently discard recognized options.
- Verify configuration/cwd ordering and the broader selection routes, without changing original corpus assertions or counting excluded cases as passes.
The earlier attempted TLS selection ran all 38 registered cases because the filter was dropped; it receives no filtered-scope credit. Initial and corrected artifacts will be linked in the retained batch evidence. #875 remains separate for HTTPS callback socket receiver and lifecycle compatibility.