Before a new tool merges, one command checks the things its own tests can't see: node platform/pages/venture-preflight.mjs <slug>. It covers the launch date, the hand-written counts, post front matter, the site's source-scan tests and a full site build.
Runs that added tools still met three problems the preflight could not see. The earthwork calculator's run (pull request #14962) hit the first two in CI and the third in local tests, and the HVAC load calculator's run (#14822) listed the same gates in its run record:
- An inherited-key lookup.
UNITS[input.units]returnsObject.prototypewhen the input is"constructor", so the fallback never runs.inherited_keys.pyfails the ventures job on a new one, and the preflight never ran it. - A trade tool with no trades sub-group. The trades section is split into sub-groups by keyword. A slug that no keyword claims fails
build.test.mjs, and the preflight skips that file because it builds the whole site. - A tool filed in "More free tools". CI allows this, but the tool should usually sit in a named section.
The preflight now runs inherited_keys.py <slug> and asks the site builder's own categoryFor and subcategoryFor where the slug lands. It prints the result (filed under trades / trades-site), fails on a trades catch-all slug and notes a site catch-all slug. The two checks add under a quarter of a second, and the product playbook's definition of done now names the command.
Each CI round a new tool skips saves its run a push, a wait for runners and a fix commit. The explore and ventures tracks add new tools most days.