CodeVetter · Repo Unpack · Contributor handoff
ReactiveX/rxjs
Future work should start from the project charter and accepted decisions, then follow the smallest relevant runtime or tooling boundary. Tests and CI were inspected, not executed, and this bounded inventory does not prove exhaustive coverage or current gate success. The active plan, lifecycle distinctions, and source-pinned migration evidence are essential safeguards against reintroducing legacy assumptions.
- Read the charter, architecture, decisions, plan, and open questions in that order; read compatibility guidance for API or behavior changes.
- P6.10 remains NEXT pending actual beta publication/verification, package automation-token restrictions, and an immutable GitHub Release; inspected local preparation is not completion evidence for publication.
- Preserve an existing realm Observable and platform string methods; public RxJS capabilities use exact imported Symbols, with accepted internal registry keys documented separately.
- Do not port RxJS 7 assumptions mechanically: subscribe returns undefined, cancellation uses AbortSignal, producers register teardown explicitly, and platform teardown order is reversed insertion order.
- Use package scripts for later authorized verification: rxjs has source/ported Vitest, public types, installation/import checks, and migration freshness gates; polyfill has dedicated lifecycle and package checks.
- Treat test definitions and CI wiring as inspected evidence only: native-unavailable mode substitutes a sentinel suite, Node 26 is advisory, and unit success alone cannot establish WPT conformance.
- Update architecture documentation alongside changes to package boundaries, initialization, Symbol identity, lifecycle, realms, compatibility, exports, or test gates; record durable decisions and revise open questions.
- Keep apps/rxjs.dev outside the Next plan unless explicitly coordinated, and inspect migration preflight/refusal behavior before enabling project writes rather than treating dry-run output as automatic write authorization.