Design 47 H2: three answers' times read from the clock

This commit is contained in:
2026-11-22 00:49:10 +01:00
parent 56deca5f34
commit e9bb740c7e
@@ -260,13 +260,13 @@ The lead's one-line answers to the questions H2's develop and review raise (impl
module reads a setting from the word the node-engine composes into its process environment, MESH_CONFIG_<KEY>
(H-A-370, E3), here MESH_CONFIG_ASK_TAKEN_BOUND, never from its config file: one word for a setting in every language;
the config file keeps only what no setting names. P3, H-A-370, ADR 0668 §2.
- **H-A-401 (a dropped ask's step ends could-not-run naming the drop; B1's two choices stand, 00:52)** B1, B2. The
- **H-A-401 (a dropped ask's step ends could-not-run naming the drop; B1's two choices stand, 00:47)** B1, B2. The
step-ended outcomes gain no `dropped`: an ask dropped through a seat's drop ends its step could-not-run with a why
naming the drop and who asked it (H-A-395's form), one way for an ask that never ran; the drop verb's description says
so. B1's choices stand: in-progress at the seat definition's value once the seat list is read, a third of the worker's
ack wait before; an ask id taken whose run no longer runs here is answered by running the step again against the
builds as they stand, one handed again while it runs is left to the run that holds it (H-A-381 (1)). P3.
- **H-A-402 (forge_merged reads a range of pull request numbers, paged, 00:55)** §812, §811, C5. `from` and `to` are
- **H-A-402 (forge_merged reads a range of pull request numbers, paged, 00:48)** §812, §811, C5. `from` and `to` are
pull request numbers, an inclusive range read by number (the forge lists none by number, so one read each; a 404 or
an unmerged one is left out); the answer holds at most 768 KB with `capped`, `total` (the numbers in the range) and
`cursor` (the next number, given back as `from`), each row {number, merge-commit, merged-at, call (the merge call id