Design 47 H: H-A-294, a test that needs tooling its step lacks says NOT RUN, and the need is declared

This commit is contained in:
2026-11-21 19:15:38 +01:00
parent 571a19c2de
commit 33d2647985
@@ -1700,3 +1700,11 @@ Where two preparers disagreed, the chosen one is named.
its info), never asking a second page and never refusing. And H-A-291 (1) is read per series: the newest reservation
and the newest release are found per module AND series (MAJOR.MINOR), so a standing 0.2 never retires a 0.1.x
build. P-failure-loud (an answer that says what it left out), H-A-292.
- **H-A-294 (a test that needs tooling its step lacks says NOT RUN, and the need is declared, 19:15)** Met live: the
forge module's whole-seat test (added 20 Nov, never passed in a pipeline) needs the module's npm packages installed
and fails every Go integration step, which fetches the tree without them; it sank every pipeline carrying the
forge. In H1 the test checks its needs first (node, npm, the installed SDK package) and, when one is missing, ends
NOT RUN with the reason and where it was proven (the build module's own precedent), never a failure; a NOT RUN is
said in the step's summary. Owed, H2: the Go integration level receives a module's npm tree installed by the Node
build module behind a declared need (check-needs node-modules), so the test runs on the mesh. Also owed: a read tool
for a run's test output (node-build-go.output answers nothing through the mesh MCP server). P-failure-loud, P3, H-A-267.