The verb repoctl ci step (commons repoctl 0013-repoctl-ci) MUST run one step: it MUST take its options (--id, --job, --module, --tool, --timeout in minutes, --out), which the renderer of the workflows writes from the step's policy, run the command given after -- in the working directory with the time limit of the step, and give the later steps of the job the outputs outcome (success or failure, as GitHub says it), detail and findings, keep the output, read it into findings with the parser of the step's tool (a closed table: tsc, bun-test, lint, format, repoctl-check, mizan-check, kanon-check, generated-files, exit-status), write the findings file of the step, print the output as the command printed it, and exit 0 whatever the command's own status was; the only exits that are not 0 are those of FR-002 (wrapper-misused). A command that cannot be started, that exits non-zero with no output a parser can read, or that is stopped by the time limit MUST become a finding of the tool with the code tool-error, no-output or timeout, so that a crash is a finding and not a red run.
Enforced (check): .github: cd commons/libraries && bun test suite/ — 0002-libraries-ci-findings: ci-findings.test.ts: the wrapper exits 0 for a failing test, no output, a missing program and a timeout
Cited by: ci/parsers, ci/policy, ci/step, Libraries, Repoctl, physical/verbs/ci, Findings of the build, in the libraries library, Steps of a pipeline under the build policy