f7dd0605

By: Tom Sydney Kerckhove <syd@cs-syd.eu>

Say what is happening, not what to think about it

The output explained itself: which half was paired with what, that the
router would stop working, what a diff in the record would mean, that a
deployment could be followed by another. Gone. A step says what is being
done, a detail says what was run or what came back, and nothing says why
except where the why is the instruction.

Two steps were descriptions rather than descriptions of what happens. The
wait connects and runs :put ready until the router answers; the settle
reads /export until it has no error comments. Both say so now, in the
output and in --help.

A refused import printed two problems for one failure, one from the import
and one from the deployment around it. The import keeps the exit code and
the caveat; the deployment adds the command that finishes it.