Verification — fw-12-testing-devtools

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

  • mini-testing-library: role, accessible name, label, visible text queries
  • Four ways to defeat the role query found — each a real accessibility bug
  • Synthetic vs real input difference demonstrated (isTrusted, hit testing, compositor)
  • mini-devtools instruments without perturbing what it measures
  • DevTools Protocol architecture understood: why it is a protocol client

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