Skip to content

Docs: remove What Is Not Implemented after all release gates pass #246

Description

@chrisbbreuer

Parent: #134
Depends on: #147, #140, #141, #142, #143, #144, #145, #146

Track the final, reviewable change that removes the README What Is Not Implemented section after every implementation and evidence gate is genuinely complete.

This is the terminal documentation issue, not a duplicate implementation umbrella: implementation remains in #134 and its children; the compatibility/evidence matrix remains in #147.

Required implementation gates

  • Every declared Home and Bun private-JSC profile reaches zero pending inventoried entries, with unknown revisions rejected explicitly.
  • The Objective-C bridge and inspector/debugger profiles are complete for their pinned targets.
  • WebAssembly and the selected post-MVP feature profiles are implemented and pass versioned upstream inventories.
  • Every relevant PR-249 WebAssembly/JIT shell hook is implemented or explicitly dispositioned with no hidden skips.
  • Moving/compacting, multi-age generational GC and parallel mid-script minor collection pass relocation, weak-reference, leak, stress, and TSan gates.
  • The optimizing JIT includes speculation, deoptimization, OSR, stack maps, invalidation, precise-GC integration, and declared architecture coverage.

Final evidence and README gate

  • Release: enforce the #134 compatibility matrix and README removal gate #147 publishes a checked-in compatibility matrix covering exact OS, architecture, ABI, Wasm, GC, and JIT targets.
  • Normal, no-GIL, stress, leak, sanitizer/TSan, differential, bridge, inspector, ABI, Wasm, and JIT evidence is green with no unexplained exclusions.
  • README benchmark scores are regenerated from the latest committed single-thread, multithread, and JavaScriptCore artifact and clearly separate correctness from speed.
  • Unsupported hosts, revisions, or profiles fail clearly instead of exposing partial behavior.
  • Remove the section and its table-of-contents entry in one final commit, replacing any still-useful target limitations with links to the versioned compatibility matrix.

Completion rule

Close this issue only after the README no longer needs the warning section because every claim is backed by the exact declared inventories and evidence. No universal-JavaScriptCore claim is implied beyond those named targets.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions