5c: the build, the freeze audit and the release pipeline

todo.md

@@ -129,9 +129,9 @@ The numbering is the order the work was planned in, not the order it ships.
       `dist/index.js` a browser can load — the compile gate names no host API, and a real page
       converting the corpus is the other half. Headless Firefox is that page, settling both at
       once: the browser proof, and the only SpiderMonkey there is, the gate's three engine legs
-      being two V8s and a JavaScriptCore that is not Safari's. The mechanism is the decision this
-      item opens with: a browser leg wants an image, a driver and a way to carry a verdict back
-      out, none of which the gate's plain `docker run` per engine has.
+      being two V8s and a JavaScriptCore that is not Safari's. 5c left this out because a browser
+      leg needs an image, a driver and a way to carry a verdict back out, none of which the gate's
+      `docker run` shape has today — decide the mechanism before the code.
 - [ ] **6 — The HTML dialect spec (`0.3.0`).** Element-by-element mapping, the `data-*` fidelity
       scheme, the opaque-carry form, and the documented foreign-element set `htmlToAdf` accepts.
 - [ ] **7 — HTML, ship `0.3.0`.** `adfToHtml`, `htmlToAdf`, the composed `markdownToHtml` /