Answer A-469v: a drop's answer names the run and the readers it ended apart, so C1 can go on

This commit is contained in:
2026-11-17 11:11:27 +01:00
parent 5880f85e5b
commit 2ed3c5d368
@@ -1707,3 +1707,9 @@ the principle that settles it, cited as "design 47 G A-n".
`said`, a composition reader a `StepRun` with its ask `id` (A-468), a test reader `{pipeline, artifact}`, `verdict` a
free object, a test run's `packages` `[{package, digest}]` and `gone` with its words when the object is gone. A drop
answers the entry it deleted plus `ended`, the readers it ended.
- **A-469v** (G-24 C1; A-469t, A-469u, §731; principle 8) A drop answers `{run, ended}`: `run` the entry it deleted,
`ended` the readers it ended, so no answer holds two fields of one name. The entries and readers are named
definitions shared by read and drop: `CompositionRun` and `CompositionReader` (a `StepRun`'s fields plus `id`) in
`mesh-wants`; `TestRun`, `TestRunReader` `{pipeline, artifact}` and `TestRunPackage` `{package, digest}` in
`mesh-pipeline-runner`. A-469t's list covers `stands` too: `Wait`'s `shared` is a list of `Shared`, one entry for a
test step.