Verification — bi-07-css-engine

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

  • mini-browser M4–M6: parser, matching, specificity, cascade, inheritance
  • Recalculated-element counts + wall time for stages 4, 5, 6 and 7
  • Subtree-fallback cliff measured; the selector shapes that cost precision named
  • Two visually-identical changes with 100x different recalc scope constructed
  • Blink's fallback condition located and written in one English sentence

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