Complete release tooling roadmap

This commit is contained in:
2026-11-03 15:47:34 +00:00
parent 75c0d5bce2
commit 124a9fa57f
2 changed files with 10 additions and 7 deletions

View File

@@ -1,6 +1,6 @@
# Release tooling implementation plan # Release tooling implementation plan
Status: Stages 1–5 complete; Stage 6 pending. Status: Stages 1–6 complete.
Follow the stages in integer order. This is one end-to-end sprint: intermediate Follow the stages in integer order. This is one end-to-end sprint: intermediate
stages may temporarily leave scripts, tests, and documentation inconsistent. stages may temporarily leave scripts, tests, and documentation inconsistent.
@@ -332,6 +332,10 @@ release-readiness limits accurately reported.
## Stage 6: Review, document completion, and commit ## Stage 6: Review, document completion, and commit
**Completed.** The implementation was reviewed against the feature roadmap;
validation and the integration dependency limitation are recorded above. The
roadmap documents remain available for later release preparation.
Review the complete diff against the feature roadmap. Confirm that all three Review the complete diff against the feature roadmap. Confirm that all three
profiles have the selected options and destination; one shared launcher owns profiles have the selected options and destination; one shared launcher owns
module routing; the old publication exercise and unused helpers are gone; module routing; the old publication exercise and unused helpers are gone;

View File

@@ -1,11 +1,10 @@
# Release tooling simplification # Release tooling simplification
Status: target design finalized for the release-tooling sprint; implementation Status: the selected release-tooling design has been implemented. All four
has not started. All four generic file checks, registered-tool execution, generic file checks, registered-tool execution, page-only hosted delivery, and
page-only hosted delivery, and protection of the supplied token path are selected. protection of the supplied token path are selected.
The [implementation plan](implementation.md) owns stage order, tasks, validation, The [implementation plan](implementation.md) owns stage order, tasks, validation,
and completion evidence. Current release behavior stays with its canonical owners and completion evidence. Current release behavior stays with its canonical owners.
until implementation updates them.
## Purpose and authority ## Purpose and authority
@@ -20,7 +19,7 @@ The [agent policy](../policy/agents.md),
[release policy](../policy/release.md#candidate-validation), and [release policy](../policy/release.md#candidate-validation), and
[testing policy](../policy/testing.md#upstream-integration-testing-ownership) [testing policy](../policy/testing.md#upstream-integration-testing-ownership)
govern implementation. The [release procedure](../release.md) continues to own govern implementation. The [release procedure](../release.md) continues to own
the current workflow until implementation updates it. the current workflow.
## Targeted end state ## Targeted end state