Verification — fw-07-bundler

A module is complete when these pass against measured or observed output, not when the prose has been read.

  • Dependency graph, transform, bundle with module registry
  • Code splitting on dynamic import; tree shaking with a conservative fallback
  • Source maps; content-hash caching with incremental rebuild
  • All five failure-lab bugs reproduced
  • Over-splitting measured against one bundle on a throttled connection

Gate (§44) — for every source-reading exercise in this module

  • Why does this code exist?
  • What invariant does it maintain?
  • Who calls it?
  • What does it call?
  • Which process and thread executes it?
  • What happens if it is removed?
  • How is it tested?
  • What simpler design would fail, and why?

Record