Fix Next TypeScript config package resolution

[0thernet]

Summary

• add default export fallbacks for every installed package subpath so Next.js TypeScript config loading can resolve the ESM build
• expand the packed-artifact smoke to exercise Node 24 import and require resolution
• build real installed Next.js 16.2.12 and 16.3.0 consumers whose next.config.ts imports the source-map wrapper
• prepare coherent package, inventory, and installation documentation for v0.1.1

Why

The v0.1.0 smoke covered ESM imports and TypeScript resolution but did not execute a real Next.js TypeScript config. Next transpiles that config through a require-compatible loader, which could not select an import-only package export.

Validation

• bun run check
• 29 deterministic tests and 4 property laws
• genuine Node 24 import and require checks for all eight installed exports
• installed Next.js 16.2.12 production build with next.config.ts
• installed Next.js 16.3.0 production build with next.config.ts

This PR does not create or publish the v0.1.1 tag.