Verification — bi-13-tests-wpt

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

  • Five behaviours mapped to their tests at each layer (or absence established)
  • One unit test, one web test directory, one WPT run
  • testharness.js test written for the parsing lab's Case B
  • Candidate pool built from TestExpectations with tractability judgements
  • Break-and-observe loop completed: spec -> test -> implementation -> break -> restore

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