From ab270e2c82e505f999d6dce6e6e1fd087ef7cae1 Mon Sep 17 00:00:00 2001 From: Eric Rakestraw Date: Mon, 12 Oct 2026 00:17:34 +0000 Subject: [PATCH] Align the feature roadmap with completed validation --- docs/roadmap/configkit.md | 18 +++++++++++++----- docs/roadmap/remediation.md | 11 +++++++++-- 2 files changed, 22 insertions(+), 7 deletions(-) diff --git a/docs/roadmap/configkit.md b/docs/roadmap/configkit.md index 22c66e2..6c815a7 100644 --- a/docs/roadmap/configkit.md +++ b/docs/roadmap/configkit.md @@ -1,8 +1,9 @@ # Adopt ConfigKit v0.7.1 and expose native configuration comparison -Status: ConfigKit v0.7.1 adoption and ConfigKit-backed `config diff` are -implemented. Distribution reconciliation and final validation remain in the -[implementation plan](implementation.md), which records the evidence and order. +Status: complete. ConfigKit v0.7.1 adoption and ConfigKit-backed `config diff`, +including distribution reconciliation and final validation, are implemented. +The [implementation record](implementation.md) records completion evidence; +release publication remains a separate process. ## Purpose and authority @@ -346,8 +347,15 @@ YAML reporting, end-to-end execution, and both maintained comparison examples are implemented. Current API and operator contracts belong to GoDoc, the [CLI reference](../cli.md#compare-configuration-selections), the [consumer guide](../consumers/guide.md#configkit-scopes), and the example -READMEs. The [implementation plan](implementation.md) records stage-by-stage -changes and validation; distribution reconciliation and final validation remain. +READMEs. The [implementation record](implementation.md) records stage-by-stage +changes and completed validation, including +[distribution reconciliation](implementation.md#stage-12-reconcile-manifests-notices-and-pending-integration-release-notes) +and [final sprint validation](implementation.md#stage-13-validate-the-complete-sprint-and-finish). +The isolated integration checks used local replacements for unpublished +CommandKit dependencies. They establish compatibility with local CommandKit +sources and released external dependencies, not availability of the intended +CommandKit module tags. No release was published as part of the sprint; +publication follows the [release procedure](../release.md). ### Focused behavioral evidence diff --git a/docs/roadmap/remediation.md b/docs/roadmap/remediation.md index 2594073..e11a9dc 100644 --- a/docs/roadmap/remediation.md +++ b/docs/roadmap/remediation.md @@ -1,6 +1,6 @@ # Configuration comparison review remediation -Status: three findings complete; one open. This document tracks required +Status: all four findings complete. This document tracks required follow-up work and its completion evidence. ## Review baseline and scope @@ -164,7 +164,7 @@ whitespace review passed. ## R-4: Reconcile the feature roadmap's completion status -**Status:** Open. **Priority:** Low. **Category:** Documentation divergence. +**Status:** Complete. **Priority:** Low. **Category:** Documentation divergence. **Evidence:** [configkit.md](configkit.md) still says distribution reconciliation and final validation remain outstanding in its opening status and Implementation @@ -182,3 +182,10 @@ recorded limitations around unpublished CommandKit dependency versions. **Completion evidence:** Neither passage assigns completed reconciliation or validation work as pending. The feature roadmap, implementation record, and deferred capabilities agree on what is implemented and what remains future work. + +**Completed 2026-10-12:** Both stale passages now record the feature's completed +end state and link to the distribution reconciliation and final validation +evidence. The feature roadmap retains the limitations of local replacements for +unpublished CommandKit dependencies and treats publication separately. The +implementation and deferred records remain consistent with this status. Relevant +local links, fragments, and documentation whitespace checks passed.