The step wrapper (commons 0038-build-policyFR-013): bun commons/libraries/src/ci/step.ts --id ID --job JOB --module NAME --tool TOOL --timeout MINUTES --out DIR -- COMMAND... runs one command, keeps what it printed, prints it as it was printed, reads it into findings with the parser of the tool, writes the file of the step (DIR/ID.json, a build-findings/1 file of one step) and exits 0 whatever the command's own status was. A command that cannot be started, that fails and prints nothing a parser reads, or that is stopped by the time limit is a finding of the tool (tool-error, no-output, timeout) and never a red step. The only status that is not 0 is 2, for a wrapper called wrongly (the red cause wrapper-misused, FR-002).
It imports no package, only files of this folder and node: modules, so that it runs in a cell of the matrix before the cell's packages are installed. The time limit stops the command's whole process group, so that a command that started others does not outlive it.
buncommons/libraries/src/ci/step.ts--idverify--jobverify--modulecore--toolexit-status--timeout15--out"$RUNNER_TEMP/findings"--bash-c"bun run verify"