The run boundary of the command line (commons headless 0004-headless-cliFR-011): run(program, argv, io) gives { code, out, err } and touches no process global, so a test, a REPL and a tool that embeds the program all call it the same way. It resolves the words to a command, parses the options (the model's standard ones included), decides whether to proceed, preview, ask or refuse (the governance's decide), runs the command, draws the closing block, and ends with the status of the one table of exits.
The result of a command (its report text, or the one JSON document) goes to out; what narrates the run (the phases, the closing block) goes to err, so that a report can be piped and a document is never mixed with prose. A failure before the command runs (an unknown word, a wrong option, a refusal) is a sentence on err and the status 2, in every mode: the one JSON document is the document of a run that ran.
The look of the error stream, where the narration goes (0008-exit-style-consentFR-002). The style of the marks is an explicit decision, Io.marks: plain (the ASCII marks), emoji, or auto, the default, which is plain unless the stream is a terminal that shows emoji and nothing asks for plain: not NO_COLOR, not --no-color, not the program's <PREFIX>_PLAIN. The program's <PREFIX>_EMOJI turns emoji on where nothing asks for plain. So a run in CI, in a pipe or with colour off is the same plain text everywhere.