A cycle ended every open step of the pipeline at once and named edges outside
it. It now ends not asked only the steps of the movers without steps, names
the edges inside a strongly connected group alone, and leaves the pipeline's
end to the end judgement, so running steps run to their end.
Builds: design 47 H H-A-176, H-A-175, H-A-163, G §270, G-22 A-326
A cycle the running build module does not break left a pipeline running with
journal lines only, since validate is asked only for a placed mover. The
placing now ends it failed, its why naming each artifact and edge kind.
Builds: design 47 H H-A-175, G §270, G-22 A-326, H-A-101 (2)
A pipeline moving the Go build module with a package it imports (mesh-sdk,
mesh-delivery-contracts) placed nothing: the package's build awaited the new
build module's files, the build module awaited the package. What a build
module's new version is built from is built by its running version.
Builds: design 47 G §270, G-22 A-326, H §746, H-A-83 (2)