Verification — bi-05-bindings-v8

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

  • Toy binding layer with wrapper map, type coercion, two worlds
  • Wrapper identity broken deliberately: expando loss and === failure both shown
  • Property access through wrapper vs plain JS measured over 1e6 iterations
  • One .idl traced to its generated C++ and to the Blink method
  • One [Unforgeable] and one [RuntimeEnabled] member found; the latter verified via flag

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