Design 47 H: H-A-190 a step-log entry names its mover; H-A-191 list's counts

This commit is contained in:
2026-11-20 21:19:16 +01:00
parent 93c7714c0d
commit edc44abc20
@@ -1010,3 +1010,12 @@ Where two preparers disagreed, the chosen one is named.
a large pipeline grows the record the same way. A mover's unlogged entries live under its own mover key beside its
steps, written in the same compare-and-set, and the tools' append reads them there; `list` answers each pipeline's
record with a count of its movers and steps, never the steps (one asks `show`, with a mover, for those). P1, P4, P7.
- **H-A-190 (a step-log entry names its mover, 21:19)** Met in the build of H-A-189: an entry of the step log names
pipeline, step and artifact but no module, and two movers' approval steps end alike at the same moment, so an
unlogged entry cannot be tied to its mover key. The log entry's form gains `module`, its mover's module, set wherever
an entry is made (a step's start and its end); the store files each entry under its mover's key, and the step log
names the mover. P1, P7.
- **H-A-191 (list's counts, 21:19)** Met in the build of H-A-189: the Pipeline value gains two optional integers,
`mover-count` and `step-count`, that `list` alone sets, answering each record with `steps` empty; `show` keeps the
steps; readers of list that use keys and outcomes see no change. P4, P7.