Steps go through spawn rather than run: a clone and a hydrate are minutes of progress output
a user needs to see, and their output is never parsed. The one exception is the dirty-tree check
below, whose output IS the data.
The step lines go to STDERR for the same reason: stdout carries the report, and build --json
promises one parseable object there.
Runs a plan, stopping at the first non-zero exit.
Steps go through
spawnrather thanrun: a clone and a hydrate are minutes of progress output a user needs to see, and their output is never parsed. The one exception is the dirty-tree check below, whose output IS the data.The step lines go to STDERR for the same reason: stdout carries the report, and
build --jsonpromises one parseable object there.