Chris Tate a21a7dd035 Library mode takes the static-or-refuse posture for bare npm specifiers ...

- Eligible packages compile statically into the archive through the npm-static machinery, transitive deps judged to the same bar at a fixpoint
- Ineligible packages refuse with a teaching naming the package, the failed bar, and the vendor-or-drop remedy — never the executable lane's dynamic advice
- npm module bytes join source_hash and build_id; npm declarations stay out of the contract type tables by construction
- Inter-package requires run the dependency's init in both lanes

# Conflicts:
#	packages/compiler/src/diagnostics/diagnostic.ts
#	packages/compiler/src/frontend/lowering/lowerer.ts
#	packages/compiler/src/index.ts
#	tests/harness/library-mode.test.ts

2026-07-23 21:07:29 -05:00

..

node_modules

Library mode takes the static-or-refuse npm posture: eligible packages compile, SC4013 refuses the rest

2026-07-23 20:06:31 -05:00

lib-markers.ts

Library mode takes the static-or-refuse posture for bare npm specifiers

2026-07-23 21:07:29 -05:00

lib-minified.ts

Library mode takes the static-or-refuse posture for bare npm specifiers

2026-07-23 21:07:29 -05:00

lib-untyped.ts

Library mode takes the static-or-refuse posture for bare npm specifiers

2026-07-23 21:07:29 -05:00