From 5d5653bfc31f8a1041baa147862c4057ec5aa4b5 Mon Sep 17 00:00:00 2001 From: Eric Rakestraw Date: Sun, 1 Nov 2026 21:52:51 +0000 Subject: [PATCH] Clarify ReleaseKit ownership of remediation work --- docs/roadmap/remediation.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/docs/roadmap/remediation.md b/docs/roadmap/remediation.md index 1764f6a..011a69d 100644 --- a/docs/roadmap/remediation.md +++ b/docs/roadmap/remediation.md @@ -22,6 +22,20 @@ when it reduces caller-owned release work. In particular, callers can reuse a repository location across preparation and subsequent orchestration without normalization code or another configuration option. +Preparation owns checkout-root resolution when the supplied location is inside +a checkout. Ordinary root-module callers keep the same request shape; callers +selecting a nested module supply its repository-relative `ModuleDir`. +Standalone preparation retains the supplied directory as its base. This is the +selected approach to the preparation-anchor question. + +Apply the same ownership principle to the other corrections: ReleaseKit +validates derived tags, prepares the selected module's dependencies, preserves +cancellation and uncertain publication outcomes, and classifies backend +observations. Consumers continue to use the existing operations and outcomes. +The empty-prebuilt and verification-order findings call for documentation that +accurately explains existing behavior. Evaluate each correction by whether an +ordinary consumer can use it without additional release code or configuration. + The existing public orchestration and runtime facades and internal package boundaries remain appropriate. These corrections use the existing public types, receipt schema, module/tag conventions, and publication/delivery model.