Chris Tate 6328f47bfd Out-of-scope builtin modules say why: v8, inspector, node:sqlite, domain, and the underscore internals ...

- SC1010's wording routes through one helper (unsupportedModuleFeatureOf): pending modules keep the plain not-yet story, out-of-scope ones append the reason
- v8/inspector name the missing V8 engine, node:sqlite the unbundled SQLite library, domain its deprecation and engine-level interception, and the fourteen underscore-prefixed legacy modules their Node-internal implementation objects
- All five fence sites reword together: the four import/require edges in program.ts and the fenced-binding use site in lower-exprs.ts
- New diagnostics fixture module-out-of-scope.ts pins the reasons (and that stream/web stays plain not-yet); the coverage import-fences snapshot repins with the v8 reason

2026-07-23 21:27:19 -05:00

..

corpus

The monomorphization frontier: keyof constraints, interface receivers, and signature bindings

2026-07-23 18:48:49 -05:00

coverage-fixtures

Coverage fixtures keep their loose-equality pins mixed-kind

2026-07-23 01:26:57 -05:00

deadstrip

init

2026-07-22 18:08:04 -05:00

diagnostics

Out-of-scope builtin modules say why: v8, inspector, node:sqlite, domain, and the underscore internals

2026-07-23 21:27:19 -05:00

fixtures

Pin the getter-table shapes: npm cases 2465-2469

2026-07-23 11:47:44 -05:00

harness

Out-of-scope builtin modules say why: v8, inspector, node:sqlite, domain, and the underscore internals

2026-07-23 21:27:19 -05:00

library-mode

Library traps carry the structured teaching encoding

2026-07-23 18:01:24 -05:00