From 541defcd78d479a67566a03d79213581e2bcb1b7 Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 20 Nov 2026 17:32:48 +0100 Subject: [PATCH] Design 47 H: H-A-165, an unpinned package: the builder waits for its release, the indexer re-pins --- 03-DESIGN/01-to-be/47-milestones/H-lead-answers.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md b/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md index 35db64e1..7c4dfe03 100644 --- a/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md +++ b/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md @@ -844,3 +844,12 @@ Where two preparers disagreed, the chosen one is named. (its definition in mesh-delivery-contracts and the generated contracts), answered by the runner's process, which judges the pipeline's end once more and records the act with its why, the shape `cancel` has; the tool `runner_end_again` asks it. P1, P9, P7 (the existing form). +- **H-A-165 (an unpinned package: the builder waits for its release, the indexer re-pins on it, 17:32)** Met + in the build of H-A-161: the runner awaits a kind-1 edge only inside one pipeline, so an importer moving alone whose + package has no release is asked at once with no pin for it. Two parts. The builder: a build ask naming a mesh + package with no pin waits, in the wait of H-A-155, for that package's release (the version-released event the + builder already hears), under its own bound `package-wait-minutes` (a setting beside `revision-wait-minutes`, 1 to + 120, default 10), then builds with the pin the release gives; past the bound the step fails "package has no + released version". The indexer: a version-released of a package starts the re-pin of every module whose + `packages` hold it (the pass of H-A-161 for those modules alone), so pins move on the event and never wait for a + merge or a hand act. P3, P1, P11.